How to Migrate a Legacy eCommerce Site to Shopify Without Losing Traffic

A real-world, step-by-step playbook — built from an actual migration involving 153 redirect rules, broken vanity URLs, and a Cloudflare failsafe layer — that keeps your Google rankings intact from day one.

Shopify Migration · SEO & Redirects · 12 min read · April 2026

Every time a business migrates its eCommerce store, the same nightmare scenario plays out: rankings that took years to build evaporate in days. URLs change, redirects break, Google crawls a graveyard of 404s — and organic traffic falls off a cliff.

It doesn't have to be this way. This guide documents exactly how to migrate a legacy eCommerce store to Shopify methodically, using a three-phase process that treats every single URL as a first-class asset worth protecting.

The core principle: a migration without a comprehensive redirect strategy isn't a migration — it's a demolition. Every ranked URL must have a clearly defined destination before the domain is ever switched.

The work that determines whether a migration succeeds or fails happens weeks before the domain is switched. The first job is a complete audit of what currently exists.

Export all existing redirect rules

From the legacy platform, export every redirect rule as a CSV. In this migration, that meant 153 rules — each one representing a URL that someone once thought was worth preserving. That instinct was correct. The moment you export them, you're working with institutional knowledge baked into the platform over years of operation.

Identify the known problems immediately

A raw redirect export from a legacy platform is almost never clean. Before doing anything else, audit the file for the most common failure modes:

Mixed HTTP/HTTPS protocols in redirect rules cause silent failures that are extremely hard to debug post-launch. Redirect chains — where URL A points to URL B which points to URL C — bleed PageRank and slow crawl budget. Both must be resolved before a single rule is uploaded to Shopify.

Get the Shopify development store ready

While the audit is underway, set up the Shopify development store in parallel. The key reason: you cannot finalise your redirect map until all final Shopify URLs are confirmed. Product URL slugs, collection handles, and page paths in Shopify may differ from what was on the legacy platform. Coordinate with the Shopify developer early and lock in every destination URL before the master redirect map is considered complete.

Step 1: Pre-Migration — Build the master redirect map

This phase is the most labour-intensive — and the most important. Every decision made here directly protects your rankings.

• Crawl the current live site: Export all discoverable URLs using Screaming Frog, Sitebulb, or equivalent. This gives you a ground-truth picture of what's actually live.
• Cross-reference with Google Search Console: The crawler will find all URLs; GSC will tell you which ones actually receive traffic or carry ranking signals. Any URL that has ever driven a click is worth protecting.
• Build a master redirect map: Use three columns: Old URL → Current Legacy URL → Final Shopify URL. This triple-column format captures historical URL structures, current redirect logic, and final destination in a single document.
• Clean the 153-rule CSV for Shopify upload: Strip all domains and protocols (Shopify requires relative paths). Fix HTTP/HTTPS inconsistencies. Collapse the 3 redirect chains into single-hop redirects. Rebuild the 4 broken vanity and coupon URLs as proper Shopify discount code pages.
• Confirm all final Shopify destination URLs: Validate with the developer before finalising the map. Product handles, collection slugs, and blog post paths can change during development — verify them all.

Tools used: Screaming Frog · Google Search Console · Excel / Google Sheets · Shopify URL structure docs

Step 2: Migration Day — Upload, configure, and test

With the master redirect map finalised, migration day becomes an execution exercise rather than a discovery exercise. Every action here should be pre-planned.

• Upload the cleaned redirect CSV to Shopify: Go to Admin → Online Store → Navigation → URL Redirects. Shopify supports bulk import via CSV — use it. Manual entry at 153 rules is error-prone.
• Set up Cloudflare as the domain DNS provider: Do this before switching the domain. Cloudflare adds an independent, platform-agnostic redirect layer that sits above Shopify.
• Upload redirect rules as Cloudflare Bulk Redirect Rules: Set all rules to permanent (301). This creates a failsafe layer — your redirects now live in two places simultaneously. If you ever migrate away from Shopify, the Cloudflare layer continues working.
• Batch-test 100% of redirects using Screaming Frog: Use List Mode — paste all old URLs and check final destination status codes. Every redirect should return a 301 to the correct Shopify URL. No 302s. No chains. No 404s.

Important: Do not skip the pre-switch test. Once the domain is live on Shopify, any broken redirect immediately affects real users and Google's crawlers. Batch-testing on the development store, before DNS is updated, gives you a clean window to fix problems with zero live traffic exposure.
Tools: Shopify Admin CSV import · Cloudflare Bulk Redirect Rules · Screaming Frog (List Mode)

Step 3: Post-Migration Monitoring — 30 days of active oversight

• Monitor Google Search Console daily for new 404 errors: After a migration, GSC will surface URLs that Google's crawler is still trying to visit based on its historical crawl data. Each 404 is a missed redirect.
• Resolve any broken redirects within 24 hours of discovery: Speed matters because Googlebot recrawls at unpredictable intervals. The sooner a 404 is patched with a proper 301, the sooner Google transfers ranking equity to the new URL.
• Deliver a final post-migration SEO health report: At the end of 30 days, document: total redirects implemented, any 404s resolved, crawl coverage changes, GSC impressions and clicks trends, and outstanding issues.

What a healthy migration looks like: Organic impressions hold steady within the first two weeks. A well-executed redirect strategy ensures ranking positions are preserved — and typically recover fully within 30–60 days.

"The Cloudflare layer isn't redundancy for its own sake — it's insurance against platform lock-in. Your redirect logic should outlive any single eCommerce platform."

Uploading the raw legacy redirect CSV directly

Legacy platforms export redirects in their own format — usually with full domains, mixed protocols, and chains baked in. Shopify expects relative paths and won't process absolute URLs correctly. The cleanup step isn't optional; it's the entire difference between a working and a broken redirect layer.

Forgetting vanity and coupon URLs

Short vanity URLs and coupon-code redirects are often the highest-traffic non-product pages on an eCommerce site. They appear in print ads, email campaigns, and social bios. In this migration, 4 were broken in the legacy export and needed to be rebuilt as active Shopify discount code pages that preserve the conversion intent behind them.

Treating 302 and 301 redirects interchangeably

Temporary (302) redirects do not pass PageRank. If any redirect in your Cloudflare or Shopify setup resolves as a 302, that URL's historical SEO value is not transferred to the new destination. Every migration redirect must be a permanent 301 — verify this explicitly in your pre-switch batch test.

Switching the domain before testing

The single most avoidable migration mistake: pointing DNS to the new store before running a full redirect test. Once real traffic is live, every broken redirect is a live SEO incident. The correct sequence is always: build → upload → test → switch.

Shopify migrations fail SEO when they're treated as technical projects rather than SEO projects. The platform switch is the least risky part. The risk lives entirely in whether every URL that Google has ever indexed has a clean, permanent, single-hop path to its new home.

Follow the three-phase process above — export and clean before building, test before switching, monitor after launching — and your traffic makes the journey with you.