Magento URLs
Audit product, category, CMS and configured rewrite paths, including relevant filter URLs.
Redirect planning
Map changed URLs to relevant destinations and test Shopify restrictions on source paths and query strings.
Product catalogue migration
Map configurable products and their associated variants to Shopify options and variants, and check platform limits.
Magento Open Source and Adobe Commerce stores can have configured URL rewrites, category paths, filters and product attributes that need individual decisions in Shopify. Audit the actual store before choosing the destination structure.
Inventory URLs and rewrites
Collect product, category, CMS and extension-generated page URLs from a crawl and sitemap. Include configured URL rewrites, Search Console landing pages and relevant analytics data. Adobe Commerce URL formats depend on configuration: product paths can include a category and an HTML suffix. Record the actual path and final response rather than assuming either is present.
For filter and parameter URLs, check which pages provide useful content, receive search impressions or have links. Decide on a relevant destination for each group and test the redirect mechanism with the exact source URL. Shopify warns that query strings may not work as expected in its redirects. Do not copy a filter parameter from another store without confirming the new store’s configuration.
Map configurable products
Export a representative configurable product and its associated simple products and examine their relationships. Map customer choices to Shopify options and variants; map other useful attributes to suitable fields or metafields. Preserve SKUs, images, inventory and prices, and check them after import.
Shopify documents a limit of 2,048 variants and three options per product. For products exceeding these limits, evaluate separate products, an app or line item properties against the way the store needs to price and track stock. Shopify Plus may offer combined listings for separate products. Test the chosen design and import before migrating the full catalogue.
Check existing integrations
List inventory, fulfilment, tax, customer and analytics integrations. Verify how each will connect to Shopify and who will reconcile data at cutover. Decide separately how to retain or transfer historical orders and customers, and check permissions and privacy obligations before handling customer data.
Redirects and launch checks
List old URLs from a site crawl, existing redirect rules, sitemaps and Search Console. Record the closest equivalent destination for each useful URL, including pages with external links. Keep unchanged URLs where they serve the same content. For a removed page with no close replacement, return a 404 or 410 rather than sending everyone to the home page.
Shopify redirects work only when the source URL is broken, and Shopify reserves certain paths. Its documentation lists /shop among prefixes that cannot be redirected. Query strings may not work as expected, and a .html URL cannot be redirected to the same path without the extension. Check each exception before committing to launch; agree a tested solution with your hosting or technical team. An app does not automatically bypass these restrictions.
Prepare the map and import eligible redirects using Shopify’s CSV template. Test on the Shopify domain where possible, then test the original URLs on the actual domain after DNS changes. Check the HTTP response, final destination and page content, including exceptions, and retain the results. A staging test alone cannot prove how the original domain will respond.
Before launch, check products, content, internal links, titles, descriptions, canonicals, sitemap and access settings. After launch, submit the new sitemap in Search Console, inspect important URLs, monitor indexing and search traffic, and investigate unexpected errors. Test checkout and analytics with an appropriate test order. Search results can fluctuate during a move; redirects and metadata do not guarantee rankings or a recovery date.
Shopify Plus has a higher documented redirect allowance than other plans, but its redirect path restrictions still need checking. Review expansion store eligibility and the contract before choosing a multi-store structure.
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 →
- Shopify Plus migration SEO
Quick answer
Prepare for a Shopify migration by recording old URLs, content and tracking before making changes.
What you will do
- Know which old URLs must be protected.
- Build redirects before launch pressure starts.
- Keep metadata, analytics and Search Console evidence available after the move.
- Reduce the risk of avoidable traffic loss.
What to check first
- Crawler export for the old site and Shopify staging site.
- Google Search Console page, query and indexing exports.
- GA4 annotations and landing-page reports.
- Shopify URL redirects.
- Redirect Mapping Sheet, Migration QA Checklist and Post-Migration Monitoring Sheet.
Work through it in this order
- Crawl the current site and export all indexable URLs.
- Export Search Console pages and queries for at least the last 16 months where available.
- Tag each old URL as protect, merge, replace, retire or investigate.
- Map protected URLs to the closest Shopify destination before launch.
- Copy or improve critical titles, descriptions, headings, content blocks and internal links.
- Test redirects, canonicals, sitemap output, robots rules and tracking on staging.
- Monitor Search Console, analytics and 404 logs for four weeks after launch.
Real-world notes
- Before launch, check that each old category URL has a suitable destination. Test the redirects after launch.
- Investigate tracking, redirects and internal links alongside Search Console data when traffic changes after a migration.
- Include blog URLs in the migration inventory and check their links and search traffic.
Final checks
- Old URL crawl saved.
- Search Console export saved.
- Top landing pages mapped.
- Redirects uploaded and tested.
- Metadata for priority pages reviewed.
- Analytics and conversion tracking checked.
- Post-launch monitoring owner assigned.
Watch-outs
- If the old site has faceted URLs indexed, decide which should become Shopify collections and which should be retired.
- If products are discontinued during migration, redirect only where the replacement is genuinely useful.
- If the domain also changes, follow the site-move guidance and monitor the transition.
Download the Migration Risk Kit or request an audit if organic revenue, product count or URL complexity is high.
Field questions
Will migrating from Magento to Shopify lose search rankings?
Rankings and traffic may change. Relevant redirects, accurate content and post-launch checks help manage the move but cannot guarantee search performance.
How long does a Magento to Shopify migration take?
The schedule depends on the catalogue, customisations, integrations, URL inventory and testing needed. Estimate it after auditing the actual store and dependencies.
Can Magento product data be imported to Shopify?
Yes, with suitable mapping and an import method. Check configurable products, associated SKUs, attributes, images and Shopify variant limits, then validate a representative import.