Skip to content

Ecommerce Migration Reconciliation

Move ecommerce migration reconciliation safely by defining scope, testing real journeys and reconciling source and destination records.

About this path

Level
Intermediate
Reading time
About 4 minutes
Sections
3
Account needed
No

Written for store owners, builders, and designers refining high-performance ecommerce stores.

Foundation · 2 min

What you need to know

What is migration reconciliation?

Migration reconciliation proves that required source records, values, and relationships arrived accurately at the destination. It combines counts with identifier, field, total and exception checks.

How do I know whether all products migrated?

Compare the required source and destination product and variant identifiers, then reconcile missing, extra and rejected records. Check key fields and storefront status for a risk-based sample.

How do I know whether all customers migrated?

Match required customer identities across systems and report missing, duplicate and merged records. Validate contact, address, status, and permission fields for representative customers.

How do I know whether all required orders migrated?

Compare the approved source order population with destination order identifiers and investigate every omission or extra record. Validate totals, lines, payment, fulfillment, and refund states for samples and exceptions.

How should inventory totals be reconciled?

Reconcile available, reserved and physical quantities by SKU and location at the agreed cutoff time. Explain each delta with an order, adjustment, receipt, or transfer.

How should gift-card balances be reconciled?

Compare each card’s identifier, status, currency and balance, then reconcile aggregate liability by currency. Test a controlled redemption only after all material differences are resolved.

How should record counts be compared?

Use the same inclusion rules and cutoff time in both systems, then compare total and grouped counts. Follow with identifier and field checks because equal totals can conceal offsetting errors.

Is matching record count enough to prove migration accuracy?

No. Equal counts can hide missing records, duplicates, wrong values, broken relationships, and offsetting balance errors.

A quick store check

Reconcile one dataset using counts, identifiers, required fields, relationships and an exception list, not totals alone.

Foundation · 2 min

Frequently asked questions

When is reconciliation complete?

When every material exception is resolved or explicitly accepted by an accountable owner with evidence.

Should rejected import rows be excluded from totals?

Report them separately and include them in the explanation of the source-to-destination difference.

Ready for the next stage?

Continue through the Academy sequence to apply advanced optimization and scaling techniques.

Start Advanced techniques