Most replatform traffic losses are not caused by the new platform. They are caused by URL structures that changed without a redirect map, category pages that no longer exist, and a launch that shipped before anyone crawled the old site properly.
There is a predictable shape to a bad replatform. Traffic holds for a week, drops in the second, and by week six it is down forty per cent and everyone is blaming the new platform. The platform is almost never the cause. The cause is that a few thousand URLs changed and nothing told Google where they went.
WooCommerce and Shopify disagree structurally about URLs. Woo will happily serve /shop/category/sub-category/product/. Shopify normalises to /products/handle and /collections/handle. That is not a preference you can configure away — it is a mapping exercise, and it is the single highest-value task in the project.
Sequence the work correctly
Five-phase migration timeline. Phase one, weeks one to two: crawl and inventory every URL, export analytics and Search Console data, identify the top pages by organic traffic and revenue. Phase two, weeks two to four: build the redirect map and have it reviewed before any theme work. Phase three, weeks three to seven: data migration of products, customers, company accounts and price lists, with structured data parity. Phase four, week eight: pre-launch verification including redirect testing and a full crawl of staging. Phase five, launch and the following six weeks: submit the sitemap, monitor Search Console coverage daily for two weeks, then weekly.
- Phase 1
Inventory what you actually have
Weeks 1–2- Full crawl of the live site — every indexable URL, not just what the CMS lists
- Export 12 months of Search Console query and page data before anything changes
- Rank pages by organic sessions and by assisted revenue
- Catalogue every parameterised and paginated URL pattern
- Phase 2
Build and review the redirect map
Weeks 2–4- One-to-one mapping for every URL with traffic or backlinks
- Pattern rules for the long tail; explicit rows for the top 500
- Decide deliberately where no equivalent exists — 410, or redirect to the nearest parent
- Have someone other than the author review it against the crawl
- Phase 3
Migrate data and rebuild
Weeks 3–7- Products, variants, metafields, media
- Company accounts, contacts, price lists and payment terms
- Structured data parity — match or improve what the old site emitted
- Theme and template build against real migrated data, never placeholders
- Phase 4
Verify before you launch
Week 8- Automated test asserting every mapped URL returns 301 to a live 200
- Full crawl of staging: no orphan pages, no redirect chains, no loops
- Canonical, title and meta description parity check on the top 500
- B2B regression: log in as three real account types and place a test order
- Phase 5
Watch it land
Launch + 6 weeks- Submit the new sitemap on day one; keep the old one accessible briefly
- Search Console coverage checked daily for two weeks, then weekly
- Track rankings for the top 50 terms against a pre-launch baseline
- Expect a 2–4 week wobble; investigate anything still down at week six
Redirect rules that survive contact with reality
- Redirect to the closest equivalent page, never to the homepage in bulk. Mass homepage redirects are treated as soft 404s and you lose the equity anyway.
- Never chain. A → B → C loses signal and wastes crawl budget. Flatten every chain to A → C before launch.
- Keep the map in version control as data, not in a spreadsheet someone emails around. It will be amended after launch, and you need the history.
- Where genuinely nothing equivalent exists, return 410 Gone rather than redirecting somewhere irrelevant. It is a cleaner signal and stops the URL lingering in reports for months.
- Do not forget non-product URLs: blog posts, downloadable spec sheets, and the PDF datasheets that trade buyers link to far more than you expect.
The B2B-specific migration surface
Consumer migrations move products and customers. B2B migrations move a commercial relationship, and there is materially more of it: company records with multiple contacts and locations, per-account price lists, payment terms, credit limits, tax exemption certificates, and the buying history customers use for reordering.
Reordering deserves specific attention. A wholesale buyer’s most common action is repeating a previous order. If order history does not come across, you have not migrated a store — you have launched a new one and asked loyal customers to start over. Expect that to show up as a revenue dip that nobody attributes to the migration.
What good looks like afterwards
Four target metrics for a well-executed migration. Organic sessions recovered to at least ninety-five percent of baseline within six weeks. Zero redirect chains at launch. One hundred percent of the top five hundred URLs mapped one to one. Search Console crawl errors returning to baseline within four weeks.
- ≥ 95%
- of baseline organic sessions by week 6
- 0
- redirect chains at launch
- 100%
- of top 500 URLs mapped 1:1
- ≤ 4 wks
- to return to baseline crawl errors
A short dip is normal — search engines need to recrawl and reprocess, and two to four weeks of noise is expected. A dip that is still there at week six is not settling. It is a redirect problem, and it is findable.
Key takeaways
- Build the redirect map in week two, before theme work. It is the highest-value artefact in the project.
- Crawl the real site rather than trusting the CMS export — orphaned and parameterised URLs carry traffic too.
- Flatten every redirect chain before launch and never bulk-redirect to the homepage.
- B2B migrations must carry company accounts, price lists, terms and order history — reordering is the core behaviour.
- Plan the password reset communication in advance; hashes cannot migrate between platforms.
360 Expert Solutions
E-commerce & ERP Integration Team
We build and scale B2B and DTC commerce on Shopify Plus, BigCommerce and WooCommerce, wired into NetSuite and Oracle. These articles are written by the engineers and architects who deliver those projects.
Building something like this?
We architect B2B commerce and ERP integrations end to end.