Replatforming an online store is one of the few projects that can quietly undo years of SEO work in a weekend. The store looks new, the team celebrates, and three weeks later organic traffic has fallen off a cliff because nobody mapped the old URLs.
It does not have to go that way. A store migration is a data project first and a design project second. Get the inventory, the redirects, and the cutover right, and rankings survive. This guide walks through the process we use and the questions to ask whoever runs yours.
Why migrations go wrong
- URLs change and nothing redirects, so search engines treat every moved page as deleted.
- Products import but reviews, variants, or metafields do not, and product pages lose the content that made them rank.
- The new theme looks better but loads slower, and speed is part of ranking.
- The switch happens in one big bang with no fallback, so every small defect becomes an emergency.
Every one of these is preventable with planning. None of them is quick to fix after the fact.
Start with a full inventory
Before anything moves, crawl the existing store and export everything: every URL, every product, every category, every review, and every page that earns organic traffic. That list is the contract for the migration. At the end, every item on it must either exist at the same address, redirect to its new address, or be retired on purpose.
Pull rankings and traffic data too. The pages that earn money and rankings get special handling, checked by hand before and after cutover.
The redirect map is the ranking protection
Where the new platform forces different URL structures, and Shopify does for products and collections, every old address needs a 301 redirect to its exact new equivalent. One catch-all redirect to the homepage does not preserve rankings. It tells search engines the old pages are gone.
Title tags, meta descriptions, structured data, and canonical tags move with the pages. So do the technical basics: an accurate sitemap, a correct robots file, and internal links that point at the new URLs instead of passing through redirect chains.
Move the data like it matters
A catalog export rarely fits the new platform on the first pass. Fields need cleaning and remapping: variants, units, tax settings, image alt text, and the review history that gives product pages credibility and long-tail rankings. Check the counts on both sides, then spot-check records by hand. A one-click import that silently drops part of the catalog costs more than it saves.
Common routes and their catches
WooCommerce to Shopify
Export products, customers, orders, and reviews, clean the data, and remap it to Shopify product and variant models before import. WooCommerce URL paths differ from Shopify fixed structures, so the redirect map is large and worth automating. Rebuild the theme rather than imitating the old one. Page speed is usually the biggest single win of this route.
Magento to Shopify
Magento stores tend to carry heavy customization: custom attributes, layered navigation, and extensions with no direct Shopify equivalent. List every custom behavior the business actually uses and decide, feature by feature, whether it maps to a built-in feature, an app, or custom development. Budget the data work generously. Magento attributes are far more flexible than Shopify fields, and flattening them well is the hard part.
WordPress or Wix to Shopify
Content-heavy sites moving into Shopify need a plan for the blog and landing pages, not just products. Keep the content that ranks, redirect what moves, and resist the urge to throw pages away just because they are old. Old pages with backlinks are assets.
Cut over in stages, then watch
Stage the whole store in a development environment and verify it against the live site: products, prices, checkout, redirects, analytics events. Pick a low-traffic window for the switch, submit the updated sitemap immediately, and keep the old process available as a fallback for the first days.
Then watch. Server logs and Search Console show whether the redirects are being crawled and the new pages indexed. Rankings normally wobble for a short period after a clean migration. What they should not do is fall and stay down. If they do, something on the inventory list did not make the trip.
We handle store migrations end to end, including the redirect and data work most projects underestimate. Get a Custom Quote and tell us what you are moving from.