Skip to content
AnswerMigration
Home/Answers/What should a WooCommerce store migration plan include?
Technical answer · store migration

What should a WooCommerce store migration plan include?

A store migration is a data and operations cutover, not just a theme change. Products, variations, customers, orders, payment state, stock and integrations all need explicit treatment before the new store handles live transactions.

Last reviewed

01The plan

Decide what is moving and what is not

Inventory product types, attributes, variations, tax and shipping rules, coupons, customer accounts, order history, subscriptions if present, and the systems that receive order or stock changes. Record which system is authoritative for each fact. A migration often fails because two sources both appear to own inventory or customer status.

Map product and category URLs before choosing the new structure. Preserve useful URLs where practical; otherwise make a one-to-one redirect map for relevant destinations. Confirm which records must remain available for accounting, support or legal requirements before deciding what to import.

Rehearse data and transaction behaviour

  1. Export a representative data sample including variable products, edge-case prices and unusual shipping rules.
  2. Import to staging and reconcile product counts, variation relationships, stock, images and key order totals.
  3. Test payment authorisation, cancellation, refund, tax, shipping and notification paths with test credentials.
  4. Freeze or reconcile writes during the final delta migration so new orders are not lost between systems.
  5. Set a cutover and rollback decision: who checks it, what must pass, and what triggers a return to the old store.

Protect live orders at cutover

Do not assume an order export captures transactions created while the migration is running. Decide how checkout is paused or how new orders are captured and replayed. Keep the old store available in read-only form when appropriate, and verify that payment callbacks and fulfilment integrations point to the intended environment.

After launch, compare new order records against gateway and fulfilment records. Watch errors and key journeys closely, and do not retire the old environment until the agreed reconciliation window has passed.

When to migrate

A migration is justified when the current platform cannot safely support the required catalogue or operating rules, or when its maintenance risk is no longer acceptable. If the issue is a single integration or template, price the smaller repair before committing to a full move.

Our Build work includes migration planning. For a first technical review, use Get your site measured.

02Questions

WooCommerce migration questions

Can WooCommerce order history be migrated?

Often, but the exact method depends on extensions, data volume and what the business needs to preserve. Reconcile a sample and confirm IDs, dates, statuses, totals and customer relationships before importing everything.

How do we avoid losing orders during cutover?

Plan how new writes are paused or captured, then run a final delta migration and reconcile it against gateway and fulfilment records before reopening the new checkout.

Should I migrate customers’ passwords?

That depends on the source hashing and authentication setup. Do not promise seamless password transfer until the existing hashes and target platform are confirmed; a secure reset flow may be required.

How do we preserve product URLs?

Keep URLs where they remain appropriate. For changed URLs, map each old address to the closest equivalent and test direct redirects before launch.

Case study

GeneLean360: commerce, membership and fulfilment connected

The study describes public and member commerce, subscription rules and the shared SKU model used to connect WooCommerce with ShipStation.

Read the GeneLean360 integration study →
NextStart here

Test the migration against real store rules.

We will map the data, integration and cutover risks before recommending a rebuild.