Rehearse a Shopify migration by moving a representative set of products and customers, taking test orders and following those orders through fulfilment and support. Do this while the old store is still selling. Decide which data must match before launch and which differences are deliberate changes to the business.
A successful import proves that records arrived. A successful rehearsal proves that the team can sell the same products at the intended prices, ship them from the right place and recognise what happened when a customer asks for help.
Make an inventory of the decisions behind the data
List the systems that own products, prices, stock, customers and orders today. A Shopify migration may involve a storefront, a stock system, a shipping tool and an accounting process. Write down which system will own each record after the move, and who resolves disagreements during the transition.
Give the migration team a representative catalogue sample before you ask for a date. Include a product with several variants, an item that is out of stock, a bundle or multipack and a product with a special shipping rule if you sell one. Check how the destination identifies variants. A red medium shirt and a blue medium shirt must still be separate items where stock is counted.
Decide how staff will find an old order and what customers should expect from their accounts. Historical orders, returns, discounts and gift balances can have different transfer paths depending on your source platform and tools. Give each one an explicit disposition, whether imported, preserved in an accessible archive or handled through a documented transition process.
Rehearse a day of work in the new store
Give staff realistic orders to run through a test environment. Use items a real customer might buy together. Try a discounted order, a multi-item order with different stock locations and an order with an item that becomes unavailable. Include a shipment that needs a refund or partial cancellation after the sale.
| Rehearsal | Evidence to keep |
|---|---|
| Import a representative product set | Variant identifiers, prices, stock and product images match the agreed mapping. |
| Place an ordinary and an exception order | Totals and shipping choices agree with the expected business rules, and the order appears in the right downstream system. |
| Pack, ship and cancel | Staff can complete the work, with stock, order state and customer communications behaving as expected. |
| Handle a customer from the old store | Staff can find the earlier order and explain where the customer should go for help. |
Record where staff had to improvise. A warehouse employee copying an order number between tabs may be fine for three test orders and unworkable on Monday morning. The rehearsal should reveal which manual steps are acceptable for a short transition and which would threaten fulfilment at normal volume.
Check what changed after the first export
Between the first export and launch, customers keep ordering, staff change prices and stock levels move. Decide how the last set of changes will reach Shopify. You may be able to apply an incremental import. If a part of the move needs a temporary freeze, agree on the exact start and end, the teams affected and who can extend it.
At the final reconciliation, compare counts and critical records. A product count alone can conceal a lost variant or duplicate entry. Check the live prices and stock for your best sellers, recent order numbers, outstanding refunds and the systems that receive new orders. For changes that were intentional, record what the team expects to differ.
Keep a URL map for important product and category pages. Use real destinations for the pages customers still need, and test representative old links. Include navigation, customer emails and ads among the places that may still reference those URLs. A catalogue that looks right in the admin can still leave a returning customer at a broken link.
Write the switch decision before the switch
Set the launch criteria with the staff who will operate the new store. Name who signs off payments, fulfilment, customer access and analytics. Write down what would make the team postpone, such as paid orders failing to reach the warehouse or an unexplained stock discrepancy on key items.
Decide what reversal means after an order lands in the new store. Restoring the old storefront does not carry that order back. Preserve the new order records and give staff a reconciliation plan before directing customers elsewhere. Keep the first monitoring window staffed so the person who notices an issue can reach the person who can act.
The most useful rehearsal ends with evidence that people can repeat. A small spreadsheet listing scenario, expected result, actual result and owner can be enough to make the cutover decision visible.
Frequently asked questions
Do we need the whole catalogue for the first test?
Start with a representative sample, then reconcile the full import. Choose sample records for the rules they exercise, including your hardest variants, stock locations and shipping exceptions.
What should happen to old orders?
Decide what staff and customers need to access, what can be migrated and what needs a dependable archive. Test that support can find an old order and handle a return.
Can we keep selling during the migration?
Plan the early import and rehearsal while the old store is operating. Agree on how to capture later changes and whether any final step requires a short freeze.
Who should sign off before launch?
Include people responsible for the store, payments, fulfilment and support. Each should verify the cases they will own once real orders arrive.