# Ecommerce Order History Migration

> Learn how to plan, test and reconcile ecommerce order history migration while protecting customers, data and daily operations.

- Type: Merchant guide
- Level: Intermediate
- Reading time: About 4 minutes
- Audience: Written for store owners, builders, and designers refining high-performance ecommerce stores.
- Last updated: 2026-11-04
- Canonical page: https://academy.getzenbasket.com/merchant-questions/ecommerce-order-history-migration/
- Part of: [Merchant Questions](https://academy.getzenbasket.com/merchant-questions/) on ZenBasket Academy

---

## What you need to know

### Should ecommerce order history be migrated?

Usually, yes when customers, service teams, finance, or legal records depend on it. If full history is unnecessary in the live store, keep older orders in a controlled searchable archive.

### How much order history should be migrated?

Choose the period from return windows, warranties, accounting, customer expectations and recordkeeping requirements. Document what remains live, what moves to an archive and how staff retrieve it.

### How should order statuses be mapped?

Create an explicit mapping for every source order state and its allowed destination state. Test uncommon states such as partially fulfilled, partially refunded, cancelled, and disputed orders.

### How should payment status be migrated?

Preserve the payment provider reference, amount, currency and real financial state separately from the order label. Do not mark an authorized payment as captured or a failed payment as paid.

### How should fulfillment status be migrated?

Map fulfillment at line and shipment level, preserving quantities, locations, tracking and partial states. Confirm that migrated orders do not accidentally trigger fulfillment again.

### How should refunds be represented?

Represent each refund with its amount, currency, date, payment reference, affected lines, and final status. Distinguish requested, pending, completed, and failed refunds.

### How do I reconcile migrated orders?

Match every required source order to one destination order, then compare line items, totals, discounts, tax, shipping, payments, fulfillment and refunds. Investigate exceptions individually instead of relying on record counts alone.

### A quick store check

Select a complex historical order and compare items, totals, payment, fulfillment, refunds and customer visibility across both systems.

---

## Frequently asked questions

### Must old orders remain editable?

Usually not. Historical orders should remain accurate and usable for service without allowing unsafe operational actions.

### Can order totals alone prove a correct migration?

No. The same total can hide wrong items, taxes, discounts or payment states.

## Related articles

- **Migrating Customer Accounts and Passwords**
- **Migrating Reviews and User-Generated Content**