The addresses a Magento store shows today are only part of what it answers to. Whenever a product or category URL key changes, Adobe Commerce can create a permanent redirect from the old address, and that option is part of the standard catalog URL configuration. Years of renamed products, merged categories and retired ranges leave a layer of old addresses that still carry links and search equity, and it rarely gets noticed until it disappears.
A Magento to Shopify migration can keep rankings, customer relationships and order history intact when that hidden layer is part of the scope. Three pieces of work largely decide the outcome: a redirect map built from the store’s full URL history, a deliberate translation of the catalog into Shopify’s product model, and a plan for the records that cannot move as they are. When the business depends on deeply customised multi-store logic, staying on Magento may still be the better call.
What a Magento Store Carries That the Storefront Never Shows
Migration plans usually begin with an export of products, customers and orders. That export describes the store as it exists today. The parts that tend to cause damage after launch sit underneath it, in configuration and history no product CSV contains.
The first is URL structure. Magento lets the business choose whether product addresses end in a suffix such as .html and whether they include the category path. Adobe’s documentation recommends using the same setting consistently for product and category pages, but long-running stores often changed these settings over the years, so one catalog may answer to several URL patterns at once. Shopify, by contrast, places products under /products/ and collections under /collections/, so practically every indexed Magento address changes.
The second is the catalog model. In Magento, a configurable product is a parent that groups separate simple products, each with its own SKU and its own inventory. That structure often feeds the ERP, the feed sent to marketplaces and the stock rules in the warehouse. Moving it means deciding how each parent and child becomes a Shopify product and its variants, not just copying rows.
The third is everything the store’s extensions and custom modules quietly do. Customer group pricing, tier pricing, gift wrapping rules, store credit, custom checkout fields and nightly ERP jobs may all live in separate modules. Before anyone maps a single URL, it helps to inventory these sources:
- The URL rewrite table, which holds the older addresses Magento already redirects and therefore the history a crawl of the live site will miss.
- Search Console and analytics landing-page reports, so mapping effort can be ranked by the traffic and revenue each address earns.
- Backlink data, because an old category page with strong external links may deserve a carefully chosen destination even if it gets few visits now.
- Extensions and custom modules, each recorded with the business rule it enforces, since the rule needs a home on Shopify, not the module.
- Every system that reads from or writes to Magento, such as the ERP, PIM, 3PL and email platform, with the data each one owns.
Where Rankings Are Lost in a Magento to Shopify Migration
Search visibility after a platform move depends heavily on how precisely old addresses connect to new ones. Google’s guidance on site moves with URL changes asks for a mapping of old to new URLs, warns against sending many old URLs to one irrelevant destination such as the home page, and recommends keeping redirects for as long as possible, generally at least a year. It also warns that rankings may fluctuate temporarily during recrawling, which stakeholders should hear before launch.
The redirect map has to cover history, not just the current catalog
A redirect map built only from today’s product list misses the addresses Magento has been redirecting for years. Left out, those addresses either break or end up in chains: old address to current Magento address to new Shopify address. Google advises redirecting to the final destination directly and keeping chains short, so each historical address should point straight at its Shopify equivalent.
Shopify’s own redirect tool adds some practical constraints. According to the Shopify Help Center on creating and managing URL redirects, redirects work only from URLs that are broken, plans below Plus allow up to 100,000 redirects while Plus allows far more, and URLs that contain query strings might not work as expected. Large Magento catalogs with years of layered-navigation URLs can approach that limit, and filtered category pages that rank on a parameter may need a different solution than a simple redirect. Both points can influence the choice of Shopify plan, so they belong early in planning.
Content that ranks but is missing from the product export
Category descriptions, CMS pages, posts from a blog extension and product reviews often carry organic traffic but sit outside the standard catalog export. Each needs a destination on Shopify or a deliberate retirement with a relevant redirect. Our Shopify migration SEO checklist covers the metadata, sitemap and post-launch monitoring side of this work in more detail.
Translating the Catalog Without Losing Data
Magento’s flexible product modelling is where much of the translation effort goes. Shopify’s limits are documented clearly: each product can have up to three options and up to 2,048 variants. A configurable product that varies by colour and size moves across cleanly. One that varies by colour, size, length and material does not, and the business has to choose a structure.
Splitting such a product into several Shopify products keeps every option selectable, but it creates more pages, more redirect targets and a risk of thin or near-duplicate content. Moving the fourth attribute into metafields or line item properties keeps a single product page, but the attribute may then stop behaving like a true variant in inventory, filtering or the ERP. Neither choice is wrong in itself. The better one depends on whether the attribute changes the stock-keeping unit, the price or only the presentation.
Attribute sets raise a similar question. Attributes that drive filters or feed fields need a planned home in Shopify metafields, while attributes unused for years are candidates for retirement.
Pricing deserves its own review. Shopify’s enterprise guide to moving from Magento to Shopify suggests that a store relying heavily on tier pricing and customer group pricing should evaluate whether Shopify Plus B2B features cover its requirements. The evaluation works better when it starts from the pricing rules actually in use, written down with examples.
Customers, Historical Orders and Integrations
Customer records usually move without much difficulty, with one exception that affects returning shoppers. Passwords stored by Magento cannot be carried into Shopify in a usable form, so customers need to activate their accounts after launch. A single bulk invitation on launch day can look like phishing to cautious customers, while a staged sequence starting with the most active segment gives the support team time to handle questions.
Historical orders need more planning than they usually receive. The Shopify Help Center on migrating to Shopify recommends importing products first, then customers, then historical orders, so that orders connect to the right records. It lists migration apps and the Order API as the routes for historical orders, and it warns that staff set to receive new order notifications will get an email for each imported order unless those notifications are switched off first.
The harder question is how many historical orders to bring. Full history supports customer service, returns and lifetime-value reporting inside Shopify. A shorter window reduces import time and mapping errors, which may suit a business whose ERP already holds the complete record. The people who answer customer queries and close the books should share that decision.
Integrations are where a Magento to Shopify migration can quietly stall. A connector built against Magento’s APIs is replaced or rebuilt against Shopify’s, and the cutover order matters. If the ERP receives Shopify orders before stock levels flow back reliably, the store may oversell during the first busy weekend.
Internal expert input required: confirm which order-history import routes WD Market typically uses for Magento projects (migration app or custom API import) and any limits encountered, so this section reflects delivery practice.
When Staying on Magento May Be the Better Decision
A balanced assessment allows for the possibility that the move is not worth it yet. Magento’s multi-store architecture handles some requirements natively that need careful design on Shopify. WD Market’s work for Astra Velo is one example: the Astra Velo case study describes a Magento 2 multi-store solution with localised storefronts for 4 countries, each with its own inventory and pricing rules, built for a catalog of 50,000+ SKUs. Staying on Magento tends to be the sounder choice in situations like these:
- Pricing, catalog visibility or checkout rules are central to the business and would need extensive custom apps to reproduce.
- Several storefronts share one back office but differ in stock, prices and assortment in ways the team relies on daily.
- The main pain is an outdated version or a neglected codebase, which an upgrade and a cleanup could address at lower risk than a full platform change.
- A capable Magento team is in place and running costs are not what holds growth back.
When those conditions do not apply and the cost of upgrades, hosting and maintenance keeps rising, the case for Shopify can be strong. Our guide to Magento to Shopify Plus migration looks at that business case, including total cost of ownership.
Comparing Migration Approaches by Catalog Complexity
The method of moving data should match the store’s complexity. Shopify’s Magento guide sorts the options roughly this way; the table adds what each means for SEO and data risk.
| Approach | Typically suits | Redirect map and SEO | Historical orders | Internal effort | Main risk |
|---|---|---|---|---|---|
| Manual or CSV import | Small catalogs with simple products | Built and imported separately | Usually not covered by CSV | Low tooling, high manual checking | Errors in hand-edited files |
| Migration app or automated tool | Medium catalogs with standard products | Some tools help; history still needs review | Often supported, with mapping limits | Moderate | Assuming defaults fit custom data |
| Custom API migration with a partner | Large or multi-store catalogs, B2B pricing, many integrations | Built from the full URL history | Scoped to the business’s chosen window | Higher, shared with the partner | Cost and timeline if scope is unclear |
Read the table against the store’s own data rather than its size alone. A modest catalog with complex configurable products and an ERP that owns pricing may need the custom route, while a large but simple catalog may move well with a tool. Whichever method is chosen, the redirect map and the decision on historical orders remain the business’s responsibility.
Key takeaway: a migration from Magento tends to keep its search value and its customer records when the project maps the store’s full URL history, decides how each product structure translates before importing anything, and agrees in advance which records will be rebuilt rather than moved.
A Seven-Step Sequence That Protects Rankings and Records
The steps follow the order in which risks are cheapest to control, and each produces something the next depends on.
- Inventory URLs and their value. Combine the URL rewrite table, a crawl, landing-page data and backlinks into one list, ranked by traffic and revenue, so the redirect work starts with the pages that matter most.
- Audit what deserves to move. Shopify’s guide suggests keeping revenue-generating products, flagging discontinued SKUs and outdated pages, and leaving zero-traffic blog posts behind. Each retired address still needs a relevant redirect target.
- Design the Shopify data model. Decide how configurable products, attribute sets, customer groups and pricing rules translate, and record each decision with its reason so it can be tested.
- Run test imports in sequence. Import products, then customers, then historical orders into a development store, with order notifications switched off, and compare counts and sample records against Magento.
- Build and test the redirect map. Point every historical address straight at its final destination, collapse existing chains, and test a sample of high-value URLs before the domain moves.
- Rebuild integrations and plan the cutover. Connect the ERP, 3PL and other systems to Shopify, run them against test orders, and agree the order in which each data flow switches over.
- Launch and monitor. Watch crawl errors, 404 reports, rankings for priority pages, order flow and account activation rates for several weeks, and fix gaps while the old mapping is still fresh.
Steps one to three often take longer than expected, and they are where later problems are usually prevented or created.
Mistakes That Tend to Surface Only After Launch
Mapping today’s catalog and ignoring the rest
A redirect map built from the current product export can look complete in testing because every live page works. The gaps appear weeks later as 404 errors on older addresses that still had links and rankings.
Splitting products without planning their addresses
Breaking a configurable product into several Shopify products solves the option limit but changes the page structure. If the original product URL is redirected arbitrarily to one of the new products, the others may start from nothing in search results.
Treating historical orders as a single checkbox
Importing historical orders without agreeing the time window, status mapping and notification settings can lead to confused customers, duplicate emails and figures that do not reconcile with the ERP.
Carrying the Store’s History Onto the New Platform
Moving from Magento to Shopify without losing SEO or critical data is mainly a question of scope. The redirect map has to reflect the store’s full URL history, the catalog needs a deliberate translation into Shopify’s product model, and passwords, order history and integrations need agreed handling before launch. Where the business depends on multi-store logic or pricing rules that Shopify could only reproduce with heavy customisation, an upgrade on Magento may be the more sensible step. Either way, the inventory of URLs, rules and data flows is the right place to start.
From Magento Inventory to a Costed Shopify Migration Plan
WD Market’s Shopify migration services begin with a feasibility assessment of existing platform functionality and custom logic: what can be migrated fully, replaced or simplified, and which Shopify limitations need workarounds. The roadmap then sets data migration scope and sequencing alongside the app and integration strategy, so redirect, catalog and order-history decisions are settled before the build starts.
If you would like to review your Magento store’s URL history, extensions and integrations with our team, arrange a conversation through our contact page. For shorter notes on migrations, integrations and platform choices, follow WD Market on LinkedIn.
Internal expert input required: confirm whether a completed Magento to Shopify project can be referenced here as a verified example, with client approval and figures taken only from a published case study.
Questions About Migrating From Magento to Shopify
Will a Magento to Shopify migration hurt search rankings?
Some movement is common while search engines recrawl the new addresses, and Google says to expect temporary fluctuation after a site move. Lasting losses usually trace back to missing or poorly targeted redirects and content left behind, such as category descriptions. A redirect map built from the full URL history, with each old address pointing directly at its closest equivalent, gives the store the best chance of recovering its positions quickly.
Can customers keep their passwords after moving from Magento?
No. Shopify cannot use passwords encrypted by another platform, so imported customers have to activate their accounts or create a new password. Their names, addresses and order records can still be imported. Planning the invitation emails carefully, ideally in stages and with clear branding, reduces confusion and support requests in the first weeks after launch.
How much order history should be moved to Shopify?
It depends on who needs it and where else it is stored. Customer service teams often want enough history to handle returns and warranty questions, while finance may rely on the ERP for the complete record. A defined window rather than the full archive is a common compromise. Whatever the window, a test import into a development store, checked against sample records in the ERP, shows whether statuses and totals map correctly before launch.
What happens to Magento extensions during the move?
Extensions do not transfer. Each one should be listed with the business rule it supports, then matched to a Shopify app, a native feature, a custom app or a simpler process. Some rules may turn out to be unnecessary. Rules that are central to pricing or checkout deserve early attention, because they can influence whether Shopify Plus is needed.
When is a migration app enough for moving off Magento?
An automated tool may be enough for a medium-sized catalog with standard products, few integrations and simple pricing. It becomes less suitable when products use more than three options, when several storefronts share one back office, or when customer group pricing and ERP connections are central to operations. In those cases a scoped migration with custom data mapping usually carries less risk.