Ecommerce migration guides for retail stores

Plan an ecommerce migration around products, customers and orders. Find the right platform guide and protect checkout, URLs and support records.

Ecommerce migration starts with your source store and intended destination. Use these guides to plan the records you’ll transfer and the storefront behaviour you’ll rebuild. If you’re closing without moving, read the guide to how to delete a Shopify store and retain the records needed for outstanding orders.

Choose a guide with the right transfer direction

Choose by where your store is going. The Shopify guide covers moving into Shopify, including WooCommerce and Magento source stores. For a WooCommerce destination, its guide separates product imports from customer and order transfers. Use the Magento guide for a Magento or Adobe Commerce destination, including the distinct Magento 1 to Magento 2 migration route.

Leaving a platform requires its export procedures. Moving into another requires the destination’s field mappings and import methods. A version migration also needs compatibility checks for extensions, themes and custom code. Adobe’s Data Migration Tool addresses Magento 1 to Magento 2 data transfers, so it isn’t a general importer for other platforms.

Map the records that keep a store working

List products and their variants separately, then map customers and orders with the relationships between them intact. Record media files, existing URLs and support history as their own transfer tasks. Give each record type a destination or a secure archive that authorised staff can search.

An export file has a defined scope. WooCommerce’s core product importer handles product data, while Shopify documents separate methods for historical orders. Payment credentials, passwords and app state need their own transfer assessment. Some require new configuration or a customer account reset. Keep source media accessible until the destination has copied the files it needs.

Protect checkout and support during the move

Before switching traffic, reconcile stock and order totals against retained source records. Check that old product URLs reach equivalent new pages. Reconnect delivery and returns policies to the systems staff and shopping assistance use, then answer a real order question from the retained history.

A completed transfer report doesn’t establish that checkout works or that staff can retrieve an older order. Keep unchanged source exports and a usable recovery point. Name the person who can pause cutover if payments fail or stock cannot be reconciled. Record how orders received during the move will be recovered before returning traffic to the former store.

Set acceptance before switching traffic

Write expected outcomes before the trial transfer. A size-and-colour variant must keep its correct price and stock. A test purchase must produce the expected payment result, order total and notification. An authorised older-order enquiry must retrieve the correct record, even when that record stays in an archive. An old product URL must reach its mapped destination without a broken redirect.

Use the destination guide below for the field mappings and execution sequence. Agree which failed checks stop cutover, and who signs off the corrected results, before moving live traffic.

Explore this topic

5 guides