Moving Order History Without Breaking Customer Support

Order history matters after migration because customers ask about returns, warranties and missing deliveries. A new store can take orders perfectly while the support team loses the evidence needed to resolve older ones. Decide what history must be visible and searchable before importing it.

How to make the decision

Map the source order ID, customer key, product key, payment status, fulfilment status, tax, shipping, refund and support notes. Check the destination’s import method and whether it triggers notifications or stock changes. Shopify warns that imported historical orders can send new-order emails to staff if notifications remain active. Rehearse with completed, partially refunded, cancelled and guest orders. Verify what customers see in their account and what support can find internally. If some history cannot be imported, provide a read-only archive with access controls and a lookup procedure.

Worked example

Synthetic support test: a customer requests a return for order 8124 placed before cutover. The new admin shows the order total but not the partial refund. Without the old record, support could refund twice. The team adds a refund-status mapping and keeps the source archive accessible to authorized agents. A second test finds the correct customer, order, payment status and prior refund within two minutes.

What to verify

• Can support search by old order ID?
• Are refunds and fulfilment states preserved?
• Are notifications controlled during import?
• Is the archive access limited and documented?

Limits and ownership

Imported history can have reporting and notification side effects. Do not treat historical orders as new sales or allow imports to reduce current inventory inadvertently.

What to hand over

Give support a lookup table connecting old order IDs to new records or the controlled archive. Give finance a separate note on whether imported history appears in revenue reports. Keep the two uses distinct; a support-friendly history import should not silently alter the current sales numbers.

Common question

Should every old order be visible in the new customer account?

That depends on platform capability and business need; at minimum, support needs a reliable retrieval path.

Next useful step

Use Preserving Product Reviews When Changing Ecommerce Platforms for the adjacent decision. For an implementation review, see Megvi’s ecommerce website development service and bring the source records, proposed checks and open exceptions.

Source checked 28 October 2026: Shopify Help Center: order migration and notification note. Check current platform settings before changing a live store or report.

The worked example is illustrative and is not presented as a Megvi client outcome.