Key Takeaways
- Products, customer profiles, order history and subscription contracts are different data sets. Confirm the migration method for each one.
- Import a representative sample first and check its meaning, not only the number of completed rows.
- Plan how customers will sign in after the move. A customer CSV does not transfer their old passwords or order history.
- Separate historical orders from open orders that still need payment, dispatch, returns or refunds.
- Agree a controlled cutover for stock, orders, integrations and domain changes, with SEO checks and a recovery decision before launch.
Moving from WooCommerce to Shopify means rebuilding the way your store operates as well as moving its content. Product pages may look familiar, but stock, customer access, order processing and integrations need their own checks.
Shopify's official WooCommerce migration guide identifies several possible transfer methods and separates products, customers, reviews and historical orders. Use it to confirm the options available for your store. Do not assume that one export file contains everything the business needs.
The practical aim is a move your team can explain and reconcile. Before switching the domain, you should know which system owns each order, where the current stock figure comes from and how a returning customer gets help.
Make a Data Inventory Before Choosing a Migration Tool
List what the current shop holds and who uses it. Include products, variants, images, downloads, customer profiles, addresses, marketing preferences, orders, refunds, reviews, gift cards and any specialist extension data.
Record the system that is authoritative for each item. If stock is managed in an external warehouse system, an old WooCommerce export may not be the latest source. If an accounts package owns invoice records, importing duplicate orders must not cause duplicate accounting entries.
Add a decision for every data set: migrate, archive securely, recreate, replace or retire. Record the owner and how the result will be checked. A useful migration scope names excluded data as clearly as included data.
An ecommerce development review should inspect those dependencies before giving a confident migration price. Keep customer exports in approved storage with restricted access, and avoid passing live personal data through unapproved conversion tools.
Map Products by Meaning, Not Column Position
Use stable product identifiers to connect old and new records. A product title can change or be shared by several variants; it is a poor sole matching key. Preserve a mapping between the old identifier and the target product or variant.
The WooCommerce product CSV documentation explains its built-in product import and export process. Exporting a supported field is only the first step. Check what the destination expects that field to mean.
For example, a weight may need a unit conversion, a category may become a collection rule, and an attribute may be a selectable variant or descriptive information. Decide this deliberately rather than treating every attribute as another purchase option.
Check custom fields, product relationships and extension-specific settings separately. If the new model cannot represent an existing ordering rule directly, agree how it will work before importing the entire catalogue. Otherwise, the team may discover the limitation after hundreds of products have been loaded.
If you are cleaning and mapping product data with AI, keep factual checks and approval ahead of the import.
Prove the Hard Products Before the Easy Ones
Choose a sample that includes a simple product, a product with several variants, an out-of-stock item and anything with special shipping or ordering rules. Add your longest description and an item with multiple images or downloads.
For a trade store, include the account-specific rules covered in our guide to trade pricing in WooCommerce and Shopify.
Inspect the storefront and the administration screens. Confirm the correct price, selected variant, image, weight, stock behaviour and purchase options. A successful import report cannot tell you whether a customer will receive the correct item.
Compare a few calculated totals as well as individual records. Count products separately from variants. Check the sum of stock by location where that comparison is meaningful. Keep a list of expected exclusions so a difference is investigated rather than automatically treated as a failure.
Once the sample passes, run the larger import and repeat both automated and manual checks. Preserve the import files and mapping rules so the process can be reproduced for the final cutover rather than rebuilt from memory.
Plan the Returning Customer's First Visit
Shopify's customer CSV guidance states that customer passwords cannot be migrated using a CSV, and that a customer CSV does not import order information. Importing a name and email address therefore does not recreate the whole customer experience.
Agree the sign-in method for the target store and test it with a controlled account. Explain what returning customers will see and what the support team should say if someone expects their old password or historical order list to appear.
Preserve marketing preferences accurately. Do not change a guest buyer into a newsletter subscriber because the new import template has a convenient yes-or-no field. Keep the evidence and source of the original preference according to your existing data-management process.
Check duplicate profiles and shared email addresses before import. Decide how the migration will handle them and review the result. Matching rules that seem harmless in a spreadsheet can merge people incorrectly or split one customer's history across several records.
Give Open Orders a Separate Plan
An old completed order is a historical record. An order awaiting stock, dispatch, cancellation or a refund is still operational work. Treating both in the same way can confuse staff and connected systems.
Decide where each open order will be completed. You might retain controlled access to WooCommerce for a defined transition period, or use a verified transfer method. The correct choice depends on payment, fulfilment and accounting connections.
Write a small exception list covering part-dispatched orders, deposits, pre-orders, returns and refunds. For each, identify the system and authorised person responsible after launch. A staff member should not have to guess whether to press refund in the old gateway or the new shop.
Prevent imported historical orders from triggering unintended customer notifications, stock reductions or new fulfilment tasks. Test the chosen migration tool's behaviour in a safe setup. Ask it to prove the state of a sample record rather than relying on the word “complete” in its progress report.
Check Subscriptions, Gift Cards and Specialist Rules
Active subscriptions need more than a customer and a product. Payment arrangements, renewal dates, contract states and cancellation behaviour need a supported transfer plan. Our Shopify versus WooCommerce subscription guide covers the questions to resolve before choosing that setup.
Apply the same care to gift-card balances, store credit, loyalty points and customer-specific prices. Identify the financial or service obligation represented by the data, not just the extension that stores it.
If a feature cannot be migrated as planned, surface the gap before launch. The business may need a revised workflow, a different tool or an agreed customer communication. Quietly dropping a field because it is difficult to import does not remove the underlying obligation.
Keep decisions about retained records, customer communications and financial treatment with the appropriate business owner. The developer can demonstrate system behaviour, but should not invent commercial policy while mapping the data.
Rebuild the Connections Around the Store
Inventory payment, shipping, stock, accounts, email, CRM, reviews and analytics integrations. For each one, record what triggers it, which identifiers it uses and what it sends back.
Test an ordinary order from the storefront through to the team's working queue. Check what happens when a payment fails, a delivery address is unsupported or a product becomes unavailable. Use the providers' safe testing methods and clearly labelled test data.
Give each connection one intended owner at cutover. If both shops send orders to the same fulfilment system, duplicate processing becomes possible. If neither does, orders can sit unseen despite the customer receiving a confirmation page.
A website maintenance and support arrangement should name who investigates these faults after launch. Confirm the observation period and escalation route before the migration team finishes its work.
Protect Search URLs as a Separate Workstream
Export the existing URL inventory and identify pages receiving search visits, links or useful customer traffic. Map changed URLs to the closest appropriate replacement and test the actual old addresses after the switch.
Google's site-move guidance covers preparing the new site, URL mapping, redirects and monitoring. Search visibility can fluctuate while a move is processed; no migration checklist guarantees unchanged rankings.
Check page content, titles, canonicals, internal links and indexability as well as redirects. Product imports do not automatically preserve every useful buying explanation or downloadable specification. Review the website migration SEO checklist alongside the operational plan.
Use our Shopify SEO guide for the destination store, and review changing your Shopify theme without hurting SEO if a theme change is part of the move.
If you need help investigating important landing pages, an SEO review can identify which search journeys need close attention. Keep that evidence separate from the store's order and stock reconciliation.
Rehearse the Cutover Before Changing the Domain
Choose a realistic launch window and name the person who can give the go-ahead. Record the order of operations, including the final data export, any temporary changes to ordering, stock reconciliation, integration switch and live checks.
Document what happens to data created after the first test import. Products, customers and orders may have changed while the new theme was being built. The final import needs a clear cut-off and a method for reconciling those changes.
Agree when to stop and postpone. Missing stock, incorrect pricing, failed payments or an unresolved order-processing gap can justify delaying launch. Do not let the domain switch become inevitable simply because a date is in the diary.
Also explain recovery. Repointing a domain does not merge orders taken on two different systems. If rollback becomes necessary, somebody must reconcile transactions, customer communications and fulfilment before normal trading resumes.
Sign Off the Shop Your Team Must Run
Ask the owner, fulfilment lead and technical lead to confirm their checks. Keep a record of remaining exceptions and the person dealing with each one. A migration can be accepted with a small known backlog, but the backlog should not hide unresolved trading risks.
Also review how to compare Shopify and WordPress running costs before agreeing the new store's ongoing support budget.
Monitor the first normal trading cycle, including dispatch, cancellations and routine reporting. Retire the old environment only after the agreed retention, access and operational requirements have been met.
If you are planning the move, send us the systems and order types involved. Start with one representative product and one awkward open order. They will tell us more about the migration than the homepage design alone.
Frequently Asked Questions
Can I move all WooCommerce data to Shopify with one CSV?
No. Products, customer profiles, order history and specialist extension data require separate checks and may need different transfer methods. Confirm the destination format and any tool limitations for each data set before importing.
Will customers keep their old WooCommerce passwords?
A Shopify customer CSV cannot migrate passwords from the old store. Agree and test the target account sign-in process, then prepare clear guidance for returning customers rather than assuming their old login will work.
What should happen to orders that have not been dispatched?
Assign each open order to the system and team that will complete it after launch. Include part-dispatched orders, refunds and returns. Do not assume that importing historical records also transfers payment and fulfilment responsibilities.
Will a WooCommerce-to-Shopify move preserve Google rankings?
No supplier can guarantee unchanged rankings. Preserve useful content, map changed URLs, test redirects and indexability, and monitor search performance. Keep SEO acceptance checks alongside the separate product, order and stock checks.
When can I turn off the old WooCommerce website?
Only after the agreed operational, record-retention and recovery requirements are met. You may need controlled access for historical orders or refunds during a transition. Document that arrangement and avoid leaving an unmanaged public copy online.
