Online Store Migration Checklist

How to use the result

This tool is a structured planning aid, not a guarantee that a provider will meet every requirement. Save the assumptions, test the shortlist with a representative product and order, and verify current provider terms.

Assign evidence and ownership

Each completed item should have an owner, a stored export or screenshot, and a date. Do not mark a migration step complete because a vendor says it is supported. Verify the result with representative products, customer records, orders, discounts, taxes, shipping rules, refunds, and reports.

Control the launch window

Freeze high-risk changes, lower DNS time to live in advance, retain a read-only copy of the old system, and define rollback criteria. After launch, reconcile orders, payments, refunds, inventory, analytics, and customer notifications. Keep financial and consent records for the period required by the business, even when the new platform does not import them cleanly.

Use a representative reconciliation set

Choose a simple item, a difficult variant, an unavailable item, a discounted order, a tax and shipping exception, a partial refund, and an historical customer with the correct consent state. Record source count, destination count, transformed fields, skipped records, and the owner of every exception. A visually complete destination is not ready when totals, identifiers, or customer permissions cannot be reconciled.

Define rollback before changing DNS

Write the measurable events that pause or reverse launch: checkout failure, incorrect payment total, missing inventory, broken priority redirects, failed notifications, or an unexplained reconciliation gap. State who can trigger rollback and how new orders created during the window will be preserved. Keep the source platform read-only until the destination has passed the agreed business, finance, support, and search checks.