Every store owner who’s considered switching platforms has had the same nightmare: waking up to find their organic traffic has fallen off a cliff. It’s the single biggest fear that keeps people stuck on a platform they’ve outgrown — and it’s also the most preventable disaster in eCommerce, if the migration is planned properly instead of rushed.
I’ve migrated stores from legacy platforms onto Shopify with zero data loss and fully preserved SEO rankings — including one case where the client’s biggest worry was losing years of accumulated search authority on a platform they’d simply outgrown. Here’s the actual process, not the vague “just set up redirects” advice you’ll find in most generic guides.
Why migrations tank SEO in the first place
Search engines don’t rank your brand — they rank specific URLs. When you migrate platforms, your URL structure almost always changes: /products/item-name becomes /collections/category/products/item-name, or your CMS generates entirely different slugs. Every one of those changed URLs is a broken signal to Google unless you explicitly tell it where the content moved.
Beyond URLs, three other things commonly get lost in a rushed migration:
- Metadata — title tags, meta descriptions, and alt text that took months to refine
- Internal linking structure — the web of links between pages that helps Google understand site hierarchy and importance
- Page speed and Core Web Vitals — a slower new site can quietly tank rankings even if every redirect is perfect
None of these are exotic problems. They’re just easy to skip when you’re focused on “does the new store work” instead of “does the new store keep everything the old one earned.”
The pre-migration audit (do this before touching anything)
Before any migration work starts, export a full map of your current site:
- Crawl your existing site with a tool like Screaming Frog to get every live URL, its title tag, meta description, and current organic traffic (pull this from Google Search Console, not guesswork).
- Identify your top-performing pages by organic traffic and backlinks — these are non-negotiable priorities for redirect accuracy. A typo in a redirect for your #1 traffic page is far more costly than one on a page nobody visits.
- Document your current URL structure so you can map old → new systematically instead of redirect-by-redirect guesswork mid-migration.
This step alone is what separates a clean migration from a stressful one. Skipping it is the single most common mistake I see.
Setting up redirects correctly
This is the part everyone knows they need to do — but “just add redirects” undersells how much precision it takes to do well.
- Use 301 redirects, not 302s. A 301 tells search engines the move is permanent and passes along ranking authority. A 302 (temporary redirect) doesn’t pass that authority the same way, and leaving 302s in place after a migration is a quiet ranking killer.
- Map every URL 1:1 where possible. Redirecting everything to your homepage (“just in case”) is worse than no redirect at all — it tells Google none of your old pages have equivalent content anymore, which can look like the entire site’s content disappeared.
- Watch for redirect chains. If Page A redirects to Page B, which redirects to Page C, that’s a chain — and chains slow down crawling and can dilute the SEO value passed through. Always redirect directly to the final destination.
- Test redirects before going live, not after. A spreadsheet of old URL → new URL, checked against actual live redirects, catches mistakes while they’re still cheap to fix.
Preserving metadata and content
Title tags and meta descriptions should migrate exactly as they were unless you have a specific reason to change them — a migration is not the time to also run an SEO copywriting experiment. Do both at once and you won’t know which change caused which ranking shift if something goes wrong.
The same goes for on-page content: product descriptions, blog posts, and category page copy should transfer as-is. If a rewrite is genuinely overdue, do it after the migration has stabilized and rankings have held, not simultaneously.
Don’t forget your XML sitemap and robots.txt
Submit your new platform’s sitemap to Google Search Console the moment the new site goes live — don’t wait for Google to discover it organically. Also double check your robots.txt file isn’t accidentally blocking search engines from crawling the new site, which happens more often than you’d expect when a new platform’s default settings differ from what you’re used to.
Monitor for the first 4–6 weeks, not just launch day
Rankings don’t usually crater immediately — they drift, page by page, over the weeks following a migration if something’s wrong. Set a recurring check (weekly, for at least a month) on:
- Organic traffic in Google Analytics, compared to pre-migration baseline
- Search Console’s Coverage report, for any spike in 404s or “not indexed” pages
- Rankings for your 10–20 highest-value keywords, tracked individually
Catching a problem in week two, when it’s one broken redirect pattern, is a fifteen-minute fix. Catching it in month three, after Google has fully deindexed a chunk of your site, is a much longer recovery.