Magento to Shopify: what really needs to move with your catalogue

A Magento storefront can hide several markets, customer groups and product models. Before moving to Shopify, work out how those pieces fit together. A catalogue can look complete while customers receive the wrong price or choose a variant with the wrong stock.
Identify the installation first
Record the version, edition, websites, stores and store views. For Adobe Commerce, include the B2B features people actually use. Ask sales to demonstrate an unusual order and support to show a typical return. Installed extensions alone won't tell you how the business works.
Decide what Shopify will own, what stays in the ERP and what can be simplified. Moving the storefront does not automatically mean replacing the back office.
Preserve configurable product relationships
Adobe's configurable product export documentation explains the relationship between the parent and its simple product variants. Your Shopify mapping needs that relationship, as well as the individual SKUs.
Test a product with several sizes and colours. Check each combination, its image, available stock and displayed price after import. Bundles, personalised items and downloads need separate decisions. Treating a bundle as an ordinary variant can change what the warehouse receives.
- Map purchasable choices to product options.
- Give descriptive attributes suitable data fields.
- Keep translations attached to the right product.
- Verify pricing rules with a representative basket.
Translate store views into a market setup
For each market, list its language, currency, assortment and delivery conditions. Use that to plan Shopify Markets. Historical divisions don't all have to survive the move.
Capture old addresses while the source shop is still available. Include category paths, products with multiple entry URLs and translated pages. Check each important redirect together with its destination, rather than counting redirect rows alone.
Reconcile customers and orders separately
A successful product import says nothing about order history. Decide what customers need in their new accounts and what records remain accessible elsewhere. Include customer matching, discounts, shipping and refunds in the test import. Adobe's export documentation separates entity types, so check the scope of each export independently.
Before launch, schedule the final update for orders and stock changes. Switch off old synchronisation jobs deliberately so two systems cannot overwrite each other. Release the new store after a purchase reaches the warehouse correctly and the team knows how to respond to a critical failure.
Our migration checklist and field map help prepare the data. The Shopify migration service explains how we can work together.