Replatforming to Shopify: What to Get Right Before You Move
A migration is a rare chance to fix structural problems — and a rare chance to lose your search rankings. Both depend on preparation.
The short answer
The technical migration is the easy part. Protect rankings with a complete redirect map, rebuild your lifecycle flows rather than porting them, and treat the move as an opportunity to fix conversion rather than recreate the old site.
Replatforming is disruptive, expensive, and occasionally the highest-leverage thing a business can do — usually when the current platform is actively limiting integrations, checkout quality, or data.
Having taken a client through a full migration to Shopify, here is what actually determines whether it goes well.
Protect the rankings first
This is where migrations do real damage, and it is entirely preventable.
Build a complete redirect map before launch. Every existing URL that has traffic, rankings or backlinks needs a 301 to its closest equivalent. Not to the homepage — to the equivalent page. Homepage redirects are the single most common migration mistake and they discard the value of the original page.
Crawl the old site properly to build the list. Do not rely on the sitemap; it will be incomplete. Cross-reference with Search Console for pages that rank but are not linked.
Keep the URL structure where you can. Changing platforms and URL patterns simultaneously doubles the risk for no benefit.
Expect a dip anyway. Two to six weeks of volatility is normal even when done correctly. Plan for it so nobody panics and starts changing things mid-recovery.
Rebuild the lifecycle flows, do not port them
The temptation is to recreate what you had. A migration is a better opportunity than that.
Most flows in a mature account have accumulated years of patches — segments nobody remembers creating, conditions that no longer apply, emails referencing products that were discontinued. Porting that forward migrates the mess.
Rebuild the five flows that matter from scratch, using the migration as the excuse. It takes longer and produces something maintainable.
Critically: test that events fire correctly on the new platform before launch. Abandoned checkout that silently stops working is a common and expensive migration failure, because nothing errors — revenue just quietly stops.
Get the data right
Customer records and purchase history need to arrive intact, or your segmentation resets to zero and every customer looks new.
Reviews are an asset. Migrate them, and check they stay associated with the right products.
Analytics should be set up and verified before launch, not after. Compare a week of parallel data if you can.
Attribution and conversion tracking across ad platforms needs to be reconfigured and tested. Broken conversion tracking mid-migration means bidding algorithms lose their signal at exactly the wrong moment.
Do not just recreate the old site
The most common missed opportunity. Teams rebuild pixel-for-pixel because it feels safest, and inherit every conversion problem they had before.
A migration is the cheapest time to fix:
- Product page structure — photography, specifications, shipping and returns visibility
- Checkout friction, including guest checkout
- Email capture placement and offer
- Site speed, which is easier to get right at build time than to retrofit
- Navigation and category structure
The sequence that works
- Audit and document everything the current site does, including the things nobody has looked at in two years
- Build the redirect map — this takes longer than expected
- Build and stage the new site, with analytics and flows configured
- Test properly: checkout end to end, every flow trigger, tracking on every platform
- Launch during a quiet period. Never during peak season, and never on a Friday
- Monitor daily for a month — rankings, conversion rate, flow revenue, error logs
What good looks like afterwards
Cleaner data, working attribution, better integrations, and a conversion rate that is at minimum no worse. If the migration was also used to fix conversion problems, meaningfully better.
The Chilly Dogs migration is the version of this we can point at with numbers attached.
Where this sits in the framework
Replatforming is Architect the System — foundational infrastructure work.
And it is a good illustration of why that stage comes before scaling traffic. Nobody should be increasing ad spend into a site they are about to rebuild.
Related reading
Abandoned Cart Emails Without the Discount Reflex
Leading with a code closes sales that would have closed anyway and teaches customers to abandon on purpose. Here's what to send instead.
Why AI Writes Like Nobody: The Brand Context Problem
Your AI output sounds generic because the model has no idea who you are. The fix isn't better prompting — it's maintained brand context every tool can read.
Email vs SMS: What Each One Is Actually For
SMS gets read almost immediately, which is exactly why overusing it is expensive. A practical split between the two channels.