Ecommerce Website Migration Checklist: What to Preserve

By Dave TanguayPublished Editorial draft

Quick Answer

Before changing ecommerce platforms, inventory the records, customer tasks and connected systems the business must preserve. Define how products, customers, orders, subscriptions, URLs and tracking will move or remain accessible. Rehearse the transfer, reconcile the results and plan the final changes made while the old store is still trading.

A new storefront can look complete while order history, renewal billing or warehouse updates are still missing. Treat migration as a set of related data and operational decisions, with a named owner and an acceptance check for each.

Create a migration register

For each data type or function, record the source, destination, transfer method, limitations, responsible person and verification method. Mark whether it will be migrated, rebuilt, archived with controlled access or intentionally retired.

Preserve recoverable source copies and document how they can be used. A collection of exports is useful only when you know what it contains and which application can restore or read it. Keep customer and order exports restricted to authorized people and tools.

Products, inventory and merchandising

Map product identifiers, variants, options, prices, media, descriptions, collections and inventory locations. Document how bundles, custom options, digital items or other special products work. Preserve source-to-destination identifier mappings for integrations that depend on them.

Start with a small, representative import. Include an ordinary product and the difficult cases, then compare source and destination fields. Counts alone cannot reveal that options were attached to the wrong image or inventory location.

For Shopify, follow its current product import guidance. Import behavior depends on included fields and overwrite settings; blank values and changed option data can have consequences. Do not treat a routine spreadsheet edit as harmless without a backup and test.

Customers, account access and consent

Separate customer profiles from login credentials, order relationships and marketing preferences. Define duplicate handling, destination account behavior and any necessary customer communication.

Shopify’s customer CSV documentation states that customer passwords and order information do not transfer through that file. Its current customer accounts support passwordless email-code sign-in. Check the selected account setup and apps before telling customers that they must reset a password or that their previous login will continue.

Preserve channel-specific consent decisions and suppression records. A customer record is not permission to turn on marketing. Confirm how the destination represents existing opt-outs and which engagement history needs a separate archive or transfer.

Historical orders and ongoing fulfillment

Decide which historical orders must be available in the new admin, customer accounts or a retained system. Plan refunds, returns, chargebacks and support access for orders placed before the move. Identify outstanding orders separately from completed history.

Shopify’s migration guide distinguishes product and customer CSV transfers from historical-order migration methods. It also specifies a product, customer and historical-order import sequence to preserve relationships. Verify the chosen tool’s actual coverage rather than assuming an export can be imported unchanged.

Review import notifications and automation before rehearsal. Prevent historical records from accidentally triggering customer emails, fulfillment requests or accounting duplication. Document any temporary suppression and who will restore the required behavior.

Subscriptions and saved payment methods

Inventory active contracts, next billing dates, products, quantities, discounts, currencies, paused states and the provider holding each payment method. Establish who owns the contract migration and who owns payment migration. A product import does not recreate either.

Shopify documents different payment migration paths and limitations depending on the gateway, plan and scenario. Confirm eligibility with Shopify, the payment provider and subscription vendor before committing to a launch date. Do not put raw card details in an ordinary project spreadsheet.

Arrange an approved test of the relevant renewal and account-management path. Define how old and new systems will avoid duplicate billing, missed renewals and conflicting customer changes during the transition. Confirm when the former service can safely stop processing.

Integrations, shipping and operational settings

For every connected system, map the event, data fields, destination identifiers and expected acknowledgment. Include inventory, warehouse fulfillment, accounting, email, search and product feeds where used. Decide which system owns each field after launch.

Test failures and retries as well as a successful transfer. Check how a repeated event avoids creating a second order or record. Reconcile a representative order through payment, shipping, fulfillment and the destination system.

Have the responsible business owners approve shipping rules, tax configuration and policy content. Migration should reproduce the approved requirements, with changes reviewed explicitly. Our shipping and fulfillment planning guide helps identify operational inputs, while the ecommerce data handoff guide covers reconciliation responsibilities.

URLs, content and measurement

Inventory important pages, product URLs, image references and internal links. Keep useful content or map it to an appropriate destination. Follow Google’s site-move guidance for URL changes and monitoring. A blanket redirect to the homepage is not a suitable substitute for relevant mapping.

Our redirect mapping guide covers that supporting work in detail. The broader migration still needs data and functional checks.

Inventory analytics properties, tags, consent dependencies, events and product feeds. Preserve access to historical reports and record the cutover date. Verify expected events and look for duplicate tracking after launch. Do not assume a new platform imports old analytics history or preserves every event definition.

Rehearse, cut over and reconcile

  1. Rehearse: Transfer representative records and test complete customer and staff tasks in an approved environment.
  2. Reconcile: Compare counts, identifiers and selected field values. Document exceptions and resolve launch blockers.
  3. Plan the final transfer: Identify orders, inventory and customer changes created after the rehearsal. Define a freeze or supported incremental update method.
  4. Set a decision point: Name the launch owner, acceptance requirements and conditions for pausing or reverting. Reverting becomes more complex once the new system accepts live orders.
  5. Verify launch: Check representative URLs, payments, notifications, inventory, fulfillment, tracking and account access. Monitor the first real operational cycles with the responsible owners.

Illustrative acceptance record: A subscription customer should retain the approved product, billing cadence and next renewal date, with one responsible system processing the renewal. Record source and destination references and the authorized verification method. This describes what to check, not a completed transfer or billing test.

Bring the migration register to a Shopify development discussion or a website audit before choosing tools or a launch date.

Key Takeaways

  • Give each record type and business function an explicit destination and owner.
  • Verify credentials, history, subscriptions and payment migration separately.
  • Rehearse difficult cases and reconcile records beyond simple totals.
  • Plan final live-data changes and operational checks alongside redirects.

Frequently Asked Questions

Can one CSV file move the whole store?

No universal file covers every platform and data type. Products, customers, orders, subscriptions and app records can require different methods. Confirm field coverage and limitations with the destination platform and selected vendors.

Can we keep taking orders during migration?

Often a store continues trading during preparation, but the final transfer needs a plan for changes made in the meantime. Agree on a freeze or supported incremental process, inventory reconciliation and who controls the launch decision.

When can we cancel the old platform and apps?

After the responsible owners confirm that required processing, history, support and recovery access are covered. Check open orders, refunds, subscriptions and retained records before terminating a service.

Archives