Magento to Shopify migration

Magento (now Adobe Commerce) powers some of the largest ecommerce stores in the world. It also carries significant technical debt: custom URL structures built up over years, layered navigation that generates thousands of indexable (or nearly-indexable) filtered URLs, configurable products with complex attribute sets, and SEO that is deeply integrated into the platform’s architecture.

Moving from Magento to Shopify is not a like-for-like switch. It is a re-architecture project with SEO implications at every stage.

Why Magento migrations lose more traffic than WooCommerce migrations

WooCommerce migrations typically involve a few hundred to a few thousand URLs. Magento migrations often involve tens of thousands.

A Magento store that has been running for five or more years may have:

• 40,000+ product URLs at various attribute-path combinations
• Category URL paths with configurable prefix structures (e.g. /catalog/category/view/id/42/ or custom paths)
• Layered navigation filter URLs (/womens-shoes.html?color=Red&size=38) — some of which may be indexed
• CMS page URLs distinct from standard Shopify pages/ structures
• Custom URL rewrites created to fix or consolidate old paths

Each category of URL needs a different redirect strategy. Treating the migration as a simple 1:1 URL map will miss a significant portion of equity.

Magento URL structures and how they map to Shopify

Magento URL patterns differ by configuration, but common structures include:

The .html suffix is the most common redirect mapping error. A Magento store with 20,000 product URLs all ending in .html will create 20,000 redirect entries — and missing any URL that ranks will cost that ranking.

Configuring the redirect strategy for Magento

The right redirect approach depends on how many URLs need protecting:

Under 5,000 URLs: Map individually. Use the URL inventory to prioritise by traffic and revenue, then create a line-by-line redirect map.

5,000–50,000 URLs: Use a pattern-based approach where possible. If all Magento category URLs follow a consistent format (/category-name.html), a redirect rule handles the entire category pattern in one instruction. Then handle individual exceptions manually.

Over 50,000 URLs: Pattern rules plus manual exceptions for top-traffic pages. Validate with a crawl comparison of the Magento export against the redirect implementation before launch.

Shopify handles up to 20,000 redirects natively via the admin. Above that limit, server-level redirects (via Cloudflare Workers, nginx or a redirect app like Redirect App) are needed.

Product catalogue migration from Magento

The biggest product data challenge is Magento’s configurable product model.

In Magento, a configurable product is a parent product linked to simple products (the actual SKU variants). Each variant can have its own URL, images, stock level and custom attributes. In Shopify, a product has options (colour, size) and variants — a different data model.

Migration steps for product data:

1. Export the Magento catalogue via CSV or API, maintaining the configurable-to-simple product relationship
2. Map Magento attribute sets to Shopify product options — decide which attributes become options and which become metafields
3. Resolve variants that exceed Shopify’s 100-variant limit (600 with Plus combinations metafields) by splitting into multiple products or restructuring
4. Map product categories to Shopify collections — Magento products can belong to multiple category trees; Shopify collections follow a different taxonomy
5. Import, validate and test a sample of 50–100 products before full import

Large attribute sets (spec sheets, technical data, certifications) should move to Shopify metafields, not to product descriptions.

Layered navigation and filtered URL strategy

Magento’s layered navigation generates filter URLs that may be indexed, ranked and linked. The approach to these on Shopify depends on how the Magento store was configured.

If filtered URLs were canonicalised to the root category: These should redirect to the equivalent Shopify collection. The filtered pages were not independently ranking.

If filtered URLs were indexed and are receiving traffic: Each high-traffic filter URL needs individual redirect handling. Check Search Console for filter URL impressions before the migration — this is commonly overlooked.

If no specific filter strategy was in place: Crawl the live Magento site with a tool like Screaming Frog, filter for URLs with query parameters, sort by Google-indexed status, and treat any that appear in Search Console as requiring a redirect.

Shopify’s filter system generates its own parameterised URLs (?filter.p.m.global.colour=Red). Decide during the migration build whether these should be indexable or canonicalised to the root collection.

The Magento to Shopify redirect map

A complete redirect map for a Magento migration requires:

1. Full URL crawl of the live Magento store — including all category, product, CMS and blog URLs, with HTTP status codes
2. Search Console export — identify which URLs receive impressions, even if clicks are low
3. Revenue landing page report from GA4 or Universal Analytics — identify URLs that convert, not just rank
4. URL classification — categorise as: redirect to equivalent Shopify URL, redirect to parent collection, retire (404 with no equity), or investigate
5. Redirect implementation — Shopify admin for under 20,000; server-level for more
6. Staging validation — crawl the staging site to confirm redirect coverage before launch

The redirect map is the highest-risk migration document. It should be reviewed by someone who understands the store’s search history, not just the development team.

Post-launch validation for Magento migrations

Magento to Shopify migrations warrant a longer post-launch monitoring window than smaller migrations.

Week 1: Validate redirect coverage with a crawl of old URLs. Check Search Console for 404 errors. Verify GA4 purchase events fire correctly. Confirm XML sitemap resolves.

Weeks 2–6: Monitor Search Console impressions for the top 50 pages. Track 404 errors daily — new ones in the first 30 days are almost always uncovered redirect errors. Compare organic revenue with the pre-migration period (adjusted for seasonality).

Months 2–3: Review which ranking URLs have recovered versus which are still recovering. Investigate any persistent drops for missed redirects, canonicalisation issues or product data problems.

What Shopify Plus offers for Magento migrations

Shopify Plus removes the 100-variant limit (up to 2,000 with combinations metafields), provides higher API rate limits for large data migrations, and offers expansion stores for multi-region configurations. For Magento stores that were multi-site, multi-currency or B2B, Shopify Plus is typically required.

Where to go next

• Score your migration risk before committing to a launch date →
• Download the full migration checklist →
• Build the redirect map →
• Estimate how long your migration will take →
• Set up analytics tracking before launch →
• Diagnose traffic drops after migration →