A Magento 1 store owner faces the need to migrate due to end of support and 1C integration requirements. Magento (especially version 1.x) uses the EAV model (Entity–Attribute–Value), where product attributes are scattered across dozens of tables. This complicates maintenance and slows queries for catalogs over 10,000 products. Bitrix with infoblocks v2.0 and ORM provides a flatter and faster structure, especially with tagged caching. Our expertise in ecommerce data migration ensures a smooth transition. We have completed more than 30 migration projects from Magento to Bitrix and guarantee data integrity at every stage. Typical project costs range from $2,000 to $20,000 depending on complexity.
Why Magento isn't always the best choice?
Integration with 1C via CommerceML is built into Bitrix, while Magento requires a third-party module or hacky synchronization. This reduces the total cost of ownership after migration. Moreover, in Magento 1.x, the EAV model requires JOINs across 5-6 tables to get full product data. In Bitrix, data is stored in a single infoblock table, accelerating queries. Bitrix is 4-8 times faster for product listing pages than Magento.
Problems we solve during migration
EAV model and performance
With catalogs over 10,000 products, Magento starts to lag on typical queries. In one project (an online clothing store with 12,000 products and variations), catalog page generation time reached 8 seconds. After migration to Bitrix with tagged cache, pages loaded in 1-2 seconds. This is critical for conversion.
Configurable products
In Magento, a configurable product is a parent with child simple products linked via catalog_product_super_link. In Bitrix, this hierarchy translates to the catalog infoblock (parent) and trade offers (children). Variation attributes (size, color) become SKU properties. We preserve all links and prices for each variation.
Orders and customers
Magento's customer base (table customer_entity) maps to Bitrix users. Orders migrate via CSaleOrder::Add() with reconstruction of order items and statuses. Order history in the personal account is restored — critical for B2B clients. In one project, we transferred 50,000 orders in 3 days without loss.
How we transfer data without loss
Export products from Magento
The standard Magento CSV export does not include media files and pricing for different customer groups. For a full export, SQL is more reliable:
-- Get products with name and price (Magento 1) SELECT p.entity_id, pv.value AS name, pt.value AS description, pd.value AS price, p.sku, p.type_id FROM catalog_product_entity p JOIN catalog_product_entity_varchar pv ON p.entity_id = pv.entity_id AND pv.attribute_id = 71 AND pv.store_id = 0 LEFT JOIN catalog_product_entity_text pt ON p.entity_id = pt.entity_id AND pt.attribute_id = 72 AND pt.store_id = 0 LEFT JOIN catalog_product_entity_decimal pd ON p.entity_id = pd.entity_id AND pd.attribute_id = 75 AND pd.store_id = 0 WHERE p.status = 1; attribute_id values must be determined for the specific Magento installation via the eav_attribute table.
Transfer categories and section tree
Magento categories are stored in catalog_category_entity (EAV). Hierarchy is defined by the path field (e.g., 1/2/5/12). In Bitrix, we recreate infoblock sections with corresponding nesting, preserving metadata and display settings.
Prices and customer groups
Magento supports tier pricing (by volume) and customer group pricing. In Bitrix, this is implemented via price types (b_catalog_price_type) and discount rules. We map Magento customer groups to Bitrix user groups and configure corresponding price types.
Our work process
- Audit the source Magento database: catalog structure, attributes, products, orders, customers.
- Write migration scripts in PHP accounting for the EAV model.
- Transfer products with attributes, images, and relations.
- Transfer orders, customers, addresses, and history.
- Configure prices and customer groups.
- Develop a new template on Bitrix (Magento design is not transferred).
- Test all functions: catalog, cart, checkout, personal account.
- Train administrators to work in Bitrix.
- 30-day post-launch support.
Every project includes: documentation of data mapping, access to a staging site, training for your team, and 30 days of post-launch support.
Estimated timelines
| Project type | Products | Timeline |
|---|---|---|
| Simple store, standard attributes | up to 3,000 | 6–10 weeks |
| Medium store with variations | 3,000–20,000 | 3–5 months |
| Large B2B store, multi-warehouse, tier pricing | 20,000+ | 5–8 months |
Concurrently with data transfer, the Bitrix site template is developed.
Our experience and guarantees
We are certified Bitrix specialists with over 30 migration projects. We guarantee that all data (products, orders, customers, prices) will be transferred without loss. After launch, we provide documentation and 30-day support. Contact us for a project evaluation to determine the optimal migration plan. Get a consultation on your project to learn exact timelines and cost.