A WooCommerce-to-Shopify migration (or the reverse, the mechanics mirror) is usually planned as a catalog-copy project and actually lived as an inventory problem: for the weeks of overlap, two storefronts sell from one physical stock pool, and every marketplace you run hangs off infrastructure you are actively replacing. The migrations that go quietly are the ones that treat stock truth as the workstream, not the afterthought.
The overlap architecture
Hard cutovers risk SEO, checkout edge cases, and revenue in the same week; the safer pattern overlaps, both stores live while traffic shifts. That makes the migration a temporary multi-store setup, with its one iron rule: one owner of the count. The working sequence:
- The old store stays the source of truth until the new one has proven checkout, taxes, and shipping in production, authority moves LATE, on evidence.
- Both storefronts connect to the hub as channels over one pool: a sale on either decrements the same count, in seconds, so the overlap period cannot double-sell.
- Cut over by slice: move a product segment’s traffic, watch, move the next, with the pool refereeing throughout.
SKU continuity: the spine
Every downstream reconnection, hub matching, marketplace listings, analytics history, joins on the SKU. The migration rules:
- Export from WooCommerce with SKUs intact, and audit for the blanks and near-duplicates FIRST, the cleanup checklist, a migration is the one natural moment to fix identity debt.
- Import to Shopify preserving exact SKUs, including per-variant children; Shopify’s variant model differs from WooCommerce’s, but the child SKU is the invariant that survives translation.
- Never renumber during migration. New naming conventions are a separate project for AFTER stability; changing identifiers while systems reconnect multiplies every failure.
Marketplaces must not notice
If eBay and Amazon connect through WooCommerce plugins today, the replatform orphans them, the in-store connector trap. The resilient order of operations: re-point marketplaces to the hub BEFORE touching the storefront. With Amazon, eBay, and Etsy as hub spokes, matched by SKU, the storefront swap becomes invisible to them: same pool, same sync, different store behind it. Unifystock connects WooCommerce and Shopify simultaneously as first-class sources, precisely for this window.
The cutover checklist
- Orders: both storefronts’ orders in one queue for the whole overlap, refunds and returns included.
- Pricing: rules re-pointed, not re-typed, channel markups survive the move because they derive from base price, not from a platform.
- Redirects and SEO: URL mapping on the store side (outside this article’s lane, but schedule it with the slice plan).
- The five-scenario sync test against the NEW store before it takes majority traffic.
- Retirement: the old store disconnects from the pool as a channel, cleanly, after its last slice moves, marketplaces never notice that either.
Common questions
How long should the overlap run?
Weeks, typically: long enough for each traffic slice to prove checkout and ops on the new store. The pool makes the duration a choice instead of a risk.
Do I migrate order history?
For records, export and archive it; operationally, the hub’s consolidated history covers the overlap forward. Legacy platform history rarely needs to live inside the new store.
What breaks most often in these migrations?
Variant SKUs mangled in translation (spot-check them first), marketplace connectors orphaned by the platform swap (re-point to the hub first), and stock split-brained between stores (one owner, always).
Can I use the migration to switch sync tools too?
Yes, and in hub-first order: hub in place, marketplaces on it, then the storefront move. Two migrations stacked in the other order is how weeks become quarters.
Replatform without the drift
Both stores, every marketplace, one pool, synced in seconds through the whole move, from $49/month with unlimited orders. See pricing.