Replatforming without losing traffic or orders
Replatforming is the highest-risk routine project in ecommerce. Done carefully it is invisible to customers; done in a hurry it costs a third of organic traffic and a month of order errors, and both take longer to recover than the migration took to run.
Everything below is about making the change boring.
The four things that break#
| What breaks | Symptom | Prevention |
|---|---|---|
| URLs | Rankings and links collapse | A complete redirect map, tested before launch |
| Product data | Wrong prices, missing variants | Field-by-field mapping and a reconciliation report |
| Customer accounts | Password resets for everyone, angry inbox | Plan the identity migration explicitly |
| Order history | Support cannot answer questions | Migrate orders read-only, or keep the old admin available |
The redirect map is the project#
Export every indexed URL, not just the ones in your sitemap: use your analytics, your server logs and search console. Map each to its new destination — one to one where possible, to the nearest relevant page where not, and never to the homepage in bulk.
A homepage catch-all redirect is the single most common cause of a permanent traffic loss after replatforming.
A sequence that keeps the risk small#
- Freeze catalogue structure changes for the duration. Migrating a moving target doubles the work.
- Import data into the new platform and produce a reconciliation report: counts, prices, stock, per category.
- Build the redirect map and test it against the full URL list, automatically.
- Run both systems in parallel with the new one behind a password for at least a week of real order tests.
- Launch on a low-traffic day, with a documented rollback and someone available for 48 hours.
- Watch rankings, 404s and order errors daily for a month, and fix rather than wait.
What to accept#
A small, temporary dip is normal even when everything is done right. What is not normal is a dip that does not recover within four to six weeks — that means URLs or content genuinely went missing, and it is a bug, not weather.
Frequently asked questions
How much traffic loss is normal?
A short dip of a few percent that recovers in four to six weeks. Anything larger or longer is a defect.
Can customer passwords be migrated?
Sometimes, depending on hash compatibility. Plan for a forced reset with a clear explanation if not.
Should design change at the same time?
Ideally not. Changing platform and design together makes any problem impossible to diagnose.
replatformingecommerce migrationurl redirectsseo migrationplatform change
