Magento to Shopify Migration Checklist: The Right Order
A four-phase Magento to Shopify migration checklist: what to audit, import order, the real variant limits, and the redirect rule that quietly breaks SEO.

A Magento to Shopify migration checklist works best as four dependent phases: audit what you're running today, decide what actually moves, import data in the order Shopify requires, then build redirects and QA the result before cutover. Skipping that order is the usual reason a migration loses data or search traffic.
Start Your Magento to Shopify Migration Checklist With an Audit
Shopify's own migration guide frames step one as deciding what to migrate before you pick a transfer method: review your existing store and decide what data and content to move over, which commonly includes products, customers, historical orders (ones already fulfilled), gift cards, certificates and store credits, blogs, and pages such as shipping or contact policies.
For a Magento store specifically, extend that audit to cover product types (simple, configurable, bundle), attribute sets and custom fields without a direct Shopify equivalent, customer groups you use for tier pricing, any active extensions or integrations, and the current list of indexed URLs search engines already know about. This is what sets the scope for every phase that follows. Teams that skip it tend to discover mid-import that a catalog they called "simple" actually depends on three Magento extensions nobody scoped for the new platform. For stores that want this audit run by someone who has done it before, our Magento-to-Shopify migration service handles the scoping and build end to end.
Two parts of that audit are easy to under-scope. The first is attribute sets: Magento lets a store accumulate dozens of them over several years, often with overlapping or redundant fields, and importing all of them literally is usually the wrong move — the audit is the point where you decide which attributes are customer-facing (and need a Shopify equivalent) versus internal or dead weight that doesn't need to survive the move. The second is the indexed-URL list: pull it from Google Search Console and your Magento sitemap before you touch anything, because it becomes the source list for the redirect map later in the process, and it's far harder to reconstruct after the old store is gone.
Decide What Actually Migrates
Shopify names what commonly moves: products, customers, historical orders, gift cards/certificates/store credits, blogs, and pages. One mechanic catches teams off guard — customer passwords never transfer. That's not a platform limitation; passwords are encrypted at the source, so only the customer record imports, and shoppers need to set a new password once they reach your new store. Shopify's own migration guide also frames the move itself as a reasonable moment to retire old, low-performing content rather than carry it over by default.
Shopify lists five ways to move each type of content, ranging from least to most technically involved: copy-paste for a handful of static pages, CSV export/import for structured data like products and customers, a migration app from the Shopify App Store, a Shopify Partner who manages the move for you, or a custom build against the Shopify API for anything with real complexity. Which option fits depends on volume and complexity, not preference — a few hundred SKUs with simple attributes is a CSV job; a Magento catalog with deep configurable products, multiple customer groups, and ERP-fed pricing usually isn't. (If you're moving from WooCommerce instead, the overlapping decisions are covered in our WooCommerce-to-Shopify migration guide.)
A practical way to decide: group your content by how it fails if the import goes wrong. A missing blog post is an inconvenience you fix by republishing. A missing or wrongly priced product variant is a customer-facing error that can ship a wrong order. A missing customer-order link breaks support's ability to answer "what did this person buy." Rank your migration decisions by that failure cost, not by how much data exists in each category — it's usually a short list of high-cost items (pricing logic, order history, active customer accounts) and a much longer list of lower-cost ones (old blog posts, superseded static pages) that don't need the same scrutiny.
Import in the Order Shopify Requires
Shopify's documentation calls this a caution, not a suggestion: import products first, then customers, then historical orders, so that products and customers already exist in Shopify when orders try to reference them. Everything else can import in any order.
Each data type has its own bulk path: products and customers each support CSV import plus their respective Admin API; historical orders go through migration apps, the Order API, or the Transaction API; gift cards, certificates, and store credits go through migration apps or the GiftCard API.
One operational detail worth planning around: importing historical orders triggers a new-order notification email to any staff member subscribed to them, including the account owner. If you're importing thousands of past orders, deactivate new-order notifications first and turn them back on once the import finishes.
It's worth running the full import sequence once against a development or staging store before you touch the production one you intend to launch from. A dry run surfaces the CSV formatting issues, missing variant options, and attribute mismatches that are tedious to find one record at a time, and it gives you a realistic sense of how long each phase actually takes with your data volume — which matters for planning a cutover window that doesn't leave the storefront half-migrated during business hours.
Map Your Catalog Model — and Redo the Variant Math
Magento's attribute sets don't map one-to-one onto Shopify's model. Most teams rebuild them as Shopify metafield definitions, then connect variant options to category metafields where it makes sense, which keeps shared values (a color name, a material) editable from one place instead of duplicated across every product that uses them.
The number that actually changed, and that a lot of older migration guides still get wrong: Shopify raised its per-product variant limit from 100 to 2,048 on October 15, 2025, with up to three options per product. If your Magento catalog leans on configurable products with four or five attributes generating hundreds of combinations, that headroom matters — but it isn't universal. Shopify's own documentation flags that some third-party themes, theme app extensions, and sales channels still cap out at 100 variants, and names two apps explicitly: the Stocky app and the legacy Order Printer app don't support more than 100 variants. A custom app built on the REST Admin API also needs to move to the GraphQL Admin API to see products above the old ceiling. Check every theme, app, and integration in your stack against this before assuming the new limit applies everywhere — it's a per-component check, not a store-wide setting. Stores with 500,000 or more variants also face a daily upload rate limit of 10,000 new variants per day via app or CSV import, though that limit doesn't apply on Shopify Plus.
In practice, the variant-math exercise looks like this: take your most combinatorially complex Magento product, count its real option-value combinations, and check that number against 2,048 and against three options. Most catalogs fit comfortably. The ones that don't — a product configured with five or six independent options, which Magento allows more freely than Shopify does — need a decision before import: trim to the three most customer-meaningful options and push the rest into line-item properties or a theme customization, or split the product into several listings and, if you're on Shopify Plus, recombine them for display using Combined Listings. Either path is a design decision to make during catalog mapping, not something to discover after the import has already run.
Build the Redirect Map Inside Shopify's Real Rules
This is where a lot of "completed" migrations quietly leak SEO traffic. Shopify's redirect rule is specific: a URL redirect only takes effect when the old URL is genuinely broken — it has to return something like a 404 or "Page not found" error. If the old path still loads a real page, even an unrelated one, the redirect you built for it will not fire. That's the actual explanation behind most "the redirect isn't working" tickets: the redirect was configured correctly, the source URL just isn't broken yet.
Build your redirect map from the full Magento URL list before cutover, not after launch day — this is the step most generic guides on moving from Magento to Shopify skip, because the redirects look correct in isolation and only fail once the old page is actually gone. Build it against Shopify's real constraints:
- You can't redirect URLs under fixed Shopify paths (/products, /collections, /collections/all) or reserved prefixes like /apps, /cart, /carts, /orders, /services, or /shop.
- Redirects don't apply across market subfolders automatically — a redirect from /old-page needs a matching one for /en-ca/old-page if you run that market.
- Standard Shopify plans allow up to 100,000 URL redirects; Shopify Plus plans allow up to 20,000,000.
- URLs ending in .html can't be redirected to the same URL without .html — Shopify treats them as the same address and handles the formatting automatically.
A "Redirect Limit Exceeded" error from the Admin API is unrelated to the 100,000-redirect cap; it means an API request is causing too many server redirects, which is worth knowing before you spend time auditing your redirect count for nothing.
The practical build sequence: export every indexed Magento URL (from your sitemap and Search Console coverage report), map each one to its new Shopify equivalent, and only finalize the redirect once the old URL is actually gone from the live Magento store — not before. For a store with more than a few hundred URLs, Shopify's CSV import for redirects is the realistic path; building thousands of them one at a time in the admin isn't. Test a sample of redirects immediately after cutover, since 301s start working as soon as they're saved, and recheck the sample again a day later once DNS and caching have fully settled.
QA Before and After Cutover
Shopify's own checklist names the import failures to check for first: products that imported but stayed hidden because they were marked unpublished, product pages with details missing after import, and variants that failed to import because a variant option was missing from the source data. Those three cover most of what breaks mechanically.
Beyond that error table, spot-check manually: pull your top-revenue SKUs and your most complex configurable products and verify price, weight, inventory, and every variant combination landed correctly. Place a few test orders — successful ones and intentionally failed ones — to confirm checkout, refunds, cancellations, and partial fulfillment behave the way your team expects before real customers see the store.
Treat launch day itself as part of QA, not the finish line. Watch Search Console coverage reports in the days after cutover for a spike in 404s, which usually means a gap in the redirect map rather than a real content problem, and keep the Magento store accessible (even if unlisted) for a short overlap window so you can double-check anything the redirect audit missed against the original page.
Where Migrations Get Harder: ERPs, 3PLs, and B2B Pricing
None of the above touches a problem that's architecturally separate from the storefront move: if your Magento store synced customer-group tier pricing, inventory, or order data with an ERP, PIM, or 3PL, that sync doesn't migrate — it has to be rebuilt against Shopify's APIs. A straight product/customer/order import gets the storefront running; it says nothing about whether your ERP still knows what's in stock, or what price a wholesale account should see the next morning. That's a systems-integration project that runs alongside the migration, not a step inside it. Our guide to Shopify ERP integration patterns covers how that sync typically gets structured.
Magento customer groups that drove tier pricing are the clearest example of why this is a separate workstream. Shopify has its own model for B2B pricing and customer segmentation, and mapping Magento's groups onto it isn't a data-import problem — it's a business-logic mapping problem that needs someone who understands both the old pricing rules and how Shopify (or Shopify Plus, if wholesale volume justifies it) expects that logic to be expressed. Scoping this alongside the catalog audit, rather than after the storefront is already live, is what keeps a wholesale account from seeing the wrong price on day one.
If you want this migration scoped and run end to end, talk to our team.
Frequently asked questions
How long does a Magento to Shopify migration take to plan for?
It depends on catalog complexity, not a fixed number of weeks — a store with a few hundred simple SKUs and no ERP integration plans very differently than one with deep configurable products, multiple customer groups, and tier pricing synced to an external system. Scope the audit phase first; it's what tells you which transfer methods and how much redirect and QA work you're actually signing up for.
What data doesn't migrate automatically?
Customer passwords are the clearest example — they're encrypted at the source, so only the customer record imports, and shoppers need to set a new password on first login. Anything outside Shopify's commonly-migrated list (products, customers, historical orders, gift cards/credits, blogs, pages) generally needs a dedicated export, API call, or manual recreation.
Are Google rankings at risk during a Magento to Shopify move?
The risk is real but mechanical, not inevitable: it comes from redirects that don't actually fire. Shopify only activates a redirect when the old URL is genuinely broken, so a redirect map built and tested against that rule — before cutover, against your full list of indexed Magento URLs — is what protects rankings through the move.
Is a migration app alone enough for a complex catalog?
Often not on its own. Migration apps handle structured, repetitive data well within Shopify's documented limits, but deeply configurable products, ERP-synced pricing, and B2B customer groups usually need CSV mapping, direct API work, or custom development layered on top.
What happens to old Magento .html URLs after cutover?
Shopify treats a URL ending in .html and the same URL without it as identical, since the platform formats clean URLs automatically — so you can't create a redirect from one to the other. Point your redirect instead at the actual new destination page, not at a stripped-down version of the old .html address.