Shopify migration for an existing store in 2026

Moving your store to Shopify? Map products, customers and URLs, handle Magento or WooCommerce exports, and check orders and checkout before switching.

Shopify migration is possible from WooCommerce, Magento and other stores, but a product import moves only part of your business. Products and customer profiles have import routes. Historical orders need a separate transfer, while your theme and integrations need rebuilding. The main risk is launching a working-looking storefront with incorrect stock or a broken checkout.

For an established retailer, plan the move around the records customers use to buy and get help. If you’re moving in the opposite direction, read how to switch from Shopify.

What can move into Shopify

Use mapped files or migration tools to bring WooCommerce and Magento catalogues into Shopify. Choose the method for each record type before estimating the work. A catalogue with ordinary variants needs less rebuilding than one whose pricing or product choices depend on extensions.

Shopify’s migration guidance separates product and customer imports from historical orders. Import products first, customers next and historical orders last so their relationships can be connected. A product CSV does not carry your apps, payment setup or storefront design.

CSV means comma-separated values, a tabular file format. Use a product CSV for supported catalogue fields and a customer CSV for profiles. Use an order-capable migration service or custom integration for historical orders. Keep records in a searchable archive if you decide against importing them.

Customer passwords don’t transfer through CSV. With Shopify’s Shopify customer accounts, customers can sign in using their email address and a one-time verification code. Plan the customer message around the sign-in method you actually enable.

Move when Shopify can reproduce the selling rules your store relies on. If a required subscription or extension workflow has no tested replacement, keep selling through the source store while you resolve it. Include overlapping subscriptions and migration services in the project budget.

Prepare source exports and a transfer matrix

Save untouched source exports and create a working copy for every conversion. Restrict customer and order files to the people doing the transfer. Record who can export the source store, configure Shopify and change the domain’s records.

Use the following transfer matrix as a starting point. Add the exact source column and destination field for each attribute your store uses.

RecordSource fields to retainShopify destination and methodManual action or limit
ProductsName, description, SKU and priceProduct CSV fields such as Title, Description, SKU and PriceMap columns and check tax treatment and weight units
VariantsParent relationship, option names, option values and variant SKUProduct options and variant rowsRebuild unsupported combinations and preserve a source-to-destination identifier map
MediaImage addresses, image order and alt textProduct images through supported import fieldsKeep originals and confirm images remain accessible during import
CollectionsCategory membership and category pagesShopify collectionsRecreate collection rules and navigation where source categories differ
CustomersName, email, phone, address and channel consentCustomer CSV profilesPreserve opt-outs and resolve duplicate profiles
Historical ordersSource order number, customer, line items, totals and fulfilment stateOrder-capable migration or retained archiveTest each field and its customer relationship with the chosen method
Policies and pagesDelivery rules, returns terms and page textShopify pages and policy settingsRebuild layouts and update internal links
App recordsReview references, loyalty balances and subscription relationshipsReplacement app or separate transferAgree the mapping with each app and test ongoing obligations

Shopify’s Shopify customer CSV documentation supports profile fields and channel-specific marketing consent. Total Spent and Total Orders aren’t imported through that file. Importing a customer profile therefore doesn’t establish that their purchase history is available.

Keep a separate URL map with each old address, its new destination and the redirect required. Export existing redirects as well as current product and category addresses. Preserve the original exports even after a test import succeeds.

Bring WooCommerce and Magento records across

WooCommerce and Magento need separate source handling, even when both ultimately produce CSV files. Test representative records before moving the full catalogue.

WooCommerce to Shopify migration

In WooCommerce, open Products > All Products > Export. The built-in product exporter lets you select product types and include custom metadata. Export the full required set and keep the original file.

Shopify’s WooCommerce migration route gives you two file workflows. Its Store Migration app accepts unchanged WooCommerce product and customer CSV files. A direct Shopify CSV import needs conversion to Shopify’s template. Keep those workflows separate.

The app imports products as drafts. Products with four or more variation attributes import without variants, so plan how those choices will work before publication. Include a simple product and a variable product in the rehearsal. Treat downloadable goods and subscription products as separate selling workflows that need their delivery or renewal configuration tested.

WooCommerce custom metadata needs a destination mapping. Exporting it doesn’t make it a Shopify product field automatically. Reviews and WordPress pages need separate handling, and historical orders need an order-capable transfer rather than the native CSV import.

Magento to Shopify migration

Record whether the source is Magento Open Source or Adobe Commerce, its version and the extensions supplying business data. A Magento 2 migration needs its actual attribute and product relationships mapped, not a generic flat product list.

Adobe’s export instructions use System > Data Transfer > Export. Export Products, Customers Main File and Customer Addresses separately as needed. Retain advanced pricing and stock-source data where your store uses them. Review export filters so required records aren’t accidentally excluded.

Shopify’s Magento migration guide maps configurable products to variants and custom attributes to metafields. It also identifies content blocks and widgets as rebuilding work. Give extension-owned reviews, loyalty balances and subscription records their own transfer decision.

For migration from Magento to Shopify Plus, test customer-group pricing and business purchasing rules against the intended Shopify configuration. Choosing Plus doesn’t itself translate those rules. Keep the source calculation beside the destination result for a representative business customer.

Rebuild payments, delivery and storefront behaviour

Finish a test import before connecting the live domain, then rebuild the storefront around the imported records. Follow this order so later checks use the data and settings customers will encounter.

  1. Import a representative product set. Review the preview and report, then inspect the products. Include an unavailable variant and a product with custom attributes.
  2. Set up the Shopify theme, collections and navigation. Recreate policy pages and test the mobile product-selection flow.
  3. Configure the payment provider and capture settings. Set tax treatment and shipping zones, then test delivery rates for the addresses you serve.
  4. Configure customer accounts, staff permissions and notifications. Shopify warns that historical-order imports can send staff new-order emails. Control those during import and restore operational notifications afterwards.
  5. Reconnect stock, fulfilment and accounting integrations. Agree which system owns stock updates so the old and new connections don’t both write quantities.
  6. Test successful and failed payments, refunds and fulfilment. Confirm the correct customer emails arrive and that staff can process the resulting order.

Use Shopify’s Shopify product CSV field reference for the mapping. Product metafields have supported CSV fields, but variant metafields need separate handling. Multi-location quantities use the inventory CSV rather than the single-location product quantity column.

A product CSV also leaves payment-provider authorisation, staff access and app permissions to be configured separately. Reauthorise each connection for the new store and test its actual read or write action.

Shopify’s import instructions warn that CSV imports can’t be cancelled once started. Back up destination products before repeat imports. Blank included fields can overwrite existing values, and changing option values can create new variant identifiers that break app references.

Preserve product URLs and search visibility

Map old URLs to equivalent Shopify destinations before launch. For example, an old /catalog/linen-shirt.html address can point to /products/linen-shirt when that page contains the same product. Send an old category page to the matching collection, not automatically to the homepage.

Create permanent redirects and test the old addresses through to the final page. Shopify’s redirect rules apply only to broken source URLs and exclude reserved paths. Query strings can behave differently, so test filtered addresses separately from plain product paths.

Inspect the new pages’ canonical URLs, which identify their preferred address to search engines. They must point to the intended live domain and page. Update internal links to the final destinations and remove launch-time indexing blocks from public pages. Google’s site-move guidance covers these checks and warns that rankings can fluctuate during a move.

Shopify generates a sitemap automatically. Follow its sitemap submission instructions and confirm the listed product and collection URLs are the new ones. Keep monitoring missing pages and search traffic after launch. These migration SEO checks preserve access to existing content. They don’t replace ongoing work on product content and search demand.

Reconnect catalogue and order support

Point catalogue sync at the new Shopify records and replace old policy-page sources with the new published pages. Update product links and any stored variant references. Order-support access needs its own check because customer-profile imports don’t bring order history with them.

Run the following checks in your shopping assistant or support integration. The examples describe expected outcomes for a test fixture you create.

CheckExample setupExpected outcome
Exact productSKU LINEN-NAVY-M has one matching productThe assistant returns that product and its new Shopify link
Variant stockNavy medium has 7 units and navy small has 0The assistant reports the correct variant availability
In-chat purchaseAdd one navy medium through the assistant’s purchase flowThe resulting order contains LINEN-NAVY-M once, with the expected payment status
Old-order supportAn authorised test customer asks about a retained source orderThe response matches its fulfilment record or sends staff to the correct archive
Order privacyA different customer requests that same orderThe integration withholds personal order details

For imported orders, compare the original order reference, customer association and line items with the source record. Also check totals, refunds and fulfilment information that your transfer method supports. For archived orders, give staff a lookup procedure and retained access. Keep an archive outside public knowledge documents so an assistant can’t expose customer records as general answers.

Cut over, reconcile and retain a recovery route

Switch the domain only after checkout and the required data checks pass. Assign one person to approve the cutover and another to reconcile orders and payments.

  1. Record the final source export point and pause catalogue edits. Capture subsequent orders, returns and stock changes so the final transfer has a defined boundary.
  2. Apply those final changes with the rehearsed method. Prevent duplicate imports and reconcile stock against the system that owns it.
  3. Save the existing domain records before changing them. Connect the domain to Shopify, confirm HTTPS works and check that email-related records remain intact.
  4. Compare product and variant counts separately with the agreed transfer scope. Investigate every difference, including intentional exclusions. Sample prices, images and custom attributes against the untouched exports.
  5. Complete a payment through the live customer path and match its order to the payment-provider record. Confirm fulfilment receives it once and the customer gets the expected notification.

Pause the move if customers can’t complete payment, orders go missing or stock is materially wrong. Stop the affected selling path while you investigate. Keep the former store and source records available through validation where feasible, with access restricted after public traffic moves.

A domain reversal alone won’t reconcile orders accepted by Shopify. Before directing traffic back, account for every new payment, order and stock change and prevent both stores from fulfilling the same purchase. Give the migration provider a failed record’s source reference, destination reference and import error so they can repair the mapping without repeating the whole transfer.

Keep the recovery route until the new store reliably takes payment, fulfils orders and answers questions about earlier purchases.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup