WebzstoreMagento's Export tool covers products, customers, customer addresses, advanced pricing and stock sources as CSV files (spreadsheet-style files). Categories sit as a column inside the product file. Orders are not in that tool: they are exported from the Orders grid, as CSV or Excel XML.
Magento to Shopify Migration
Magento to Shopify Migration
We move Magento (Adobe Commerce) stores to Shopify by turning your catalogue structure into Shopify products, variants and collections, then rebuilding the storefront and any custom checkout steps. Shopify's own Store Migration app does not list Magento as a source, so we plan the transfer from Magento's exports and check each file before it is used.
The hard part is rarely the product list. It is the way Magento organises that list, and Shopify organises it differently.
01Choose
Choose what you want to change
Choose the part of the Magento store you want handled, several parts, or the complete move. The plan you see is a discussion aid for the call, not a quote.
Where this startsOur Magento store is heavy to run and I want Shopify, but our products, store views and checkout rules are complicated.
In plain terms
- Configurable product
- One Magento product that offers choices such as size, where each choice is a separate product behind the scenes.
- Collection
- A Shopify group of products that shoppers can browse.
- Redirect
- An instruction that sends visitors from an old address to the new one.
- Customer account mode
- Shopify's setting for how customers sign in. Current accounts use a one-time code sent by email instead of a password.
02Decide
Where each Magento structure lands in Shopify
Attribute sets
In Shopify
No direct equivalent
What we decide
Which attributes become shopper-facing details, filters or internal notes
Configurable products (a parent with child products, each with its own SKU and stock)
In Shopify
One product with variants
What we decide
Which attributes become options
Products with many variation attributes
In Shopify
Three options per product
What we decide
How to merge, split or simplify
Categories
In Shopify
Collections
What we decide
Which become browsable groups and which are retired
Store views
In Shopify
Not a one-to-one match
What we decide
Which views are still needed and how each is served
Custom checkout rules
In Shopify
A rebuilt requirement
What we decide
What Shopify handles itself and what needs an app or development
03Transfer
What Magento's exports give us
Shopify takes product files up to 15 MB, so a large catalogue is split across several. A configurable product arrives as one parent row plus a row per child, and we rebuild that into a single Shopify product with variants. Shopify supports up to 2,048 variants per product. Adobe's documentation does not confirm that customer passwords can be exported, so we do not assume customers' passwords move. We agree how they sign in on Shopify, whose current accounts use a one-time emailed code instead of a password.
04Test
Test the awkward product before the easy ones
- A configurable product with every option combination in stock and out of stock
- A product that needs more than three variation attributes
- A child SKU whose stock level differs from its siblings
- A page that exists only in one store view
- Each custom checkout rule, from basket to payment to confirmation email
Your team checks prices, tax and wording on these records before the full transfer.
05Launch
Plan the switch, the URLs and the orders
Historical orders need their own route, because Shopify points to migration apps, its APIs or a Shopify Partner rather than a simple file upload.
- We import products first, then customers, then orders, so each step can be checked.
- Old category and product addresses go into a redirect file (a list that sends each old address to its new one).
- Shopify says redirects work only from addresses that would otherwise show a not-found page, and some fixed paths cannot be redirected.
- We list those cases early.
- Search performance is monitored after launch, with no promise that it will stay as it is.
- The wider process sits under Ecommerce Migration Services, and the new store is built through Shopify Development.
Questions about Magento to Shopify
Can Shopify's migration app import a Magento store?
No. Magento is not among the sources Shopify lists for that app, so we use Magento's own exports and a planned import.
Will my attribute sets transfer?
No. Attribute sets are a Magento admin structure with no direct Shopify match, so each attribute is mapped by decision.
Will configurable products become variants?
Yes, in principle. Each child SKU becomes a variant and each variation attribute an option, within Shopify's limit of three options.
Can I bring order history?
It can be part of the plan, but it is separate from products. Orders are exported from a grid and need an app, API or partner to import.
Make the move for a clear reason
Share your Magento version, how many store views you run and the checkout rules your business depends on. We will assess the mapping before proposing any build.
Explore the next step
- Ecommerce Migration ServicesPlan your ecommerce migration with clear decisions about products, accounts, URLs and connected systems before the switch. Book a free 30-minute call.
- Shopify DevelopmentDevelop a Shopify store around product choices, mobile buying and the tasks your team manages every day. Discuss the scope on a free 30-minute call.
- Volusion to Shopify MigrationPlan Volusion to Shopify migration with source records, storefront requirements and launch responsibilities checked first. Book a free 30-minute call.