A WooCommerce to Shopify migration is a website and operations project, not just a product import. You need to move the right records, rebuild the customer experience, preserve useful URLs, reconnect business tools, and confirm that orders can be processed correctly before switching the domain.
The safest plan separates preparation, trial imports, storefront development, testing, and the final switch. Keep the existing store operating while you build and review the replacement, then use a documented process for the data that changes close to launch.
This checklist is designed for a merchant with an existing WooCommerce store. It focuses on the decisions that are easy to miss when the migration is treated as a single automated transfer.
Define what a successful move needs to preserve
Start with the business reason for switching. Are you trying to simplify maintenance, improve the shopping experience, replace fragile integrations, or make the site easier for your team to manage? Use that reason to define the project.
List the workflows your business depends on, including the less visible ones: subscriptions, customer-specific pricing, product personalization, warehouse routing, returns, gift cards, and reporting. Assign an owner to confirm how each will work after the move.
Back up the WooCommerce site and export the data you need before changing the source store. Keep an inventory of plugins, integrations, and the business purpose of each. A migration should replace the function you need, not blindly reproduce every plugin you accumulated.
Separate data transfer from rebuilding the website
Shopify documents several migration methods, including CSV files, third-party apps, and professional support. Its WooCommerce migration guide explains that the method depends on the content being transferred. Products, customers, historical orders, and reviews do not all follow the same import process.
Use a migration inventory like this before selecting a tool:
| Area | Transfer or rebuild task | Check before launch |
|---|---|---|
| Products | Map products, variants, images, descriptions, and relevant custom fields | Correct options, prices, SKUs, stock, and product relationships |
| Customers | Move profiles and supported fields; preserve consent records | Accurate details and a clear account sign-in experience |
| Orders and reviews | Choose a supported method for each record type | Correct associations, statuses, and access for your team |
| Storefront | Build Shopify templates, navigation, and content layouts | A complete buying journey on mobile and desktop |
| Business tools | Reconnect fulfillment, email, analytics, and other services | Events and records reach the right destination once |
| Search visibility | Map old URLs, preserve useful content, and set redirects | Important old links reach the correct replacement pages |
This is a planning framework, not a claim that every field transfers automatically. Ask the migration provider to identify unsupported data and exceptions in writing.
A WooCommerce theme is not a Shopify theme. Even when a tool helps recreate part of the appearance, review the navigation, templates, product information, and responsive behavior as a new implementation.
Run a representative trial import
Do not choose only your simplest products for the trial. Include the cases that make your catalog complicated: a product with many variations, a sale item, a bundle, a product with special shipping, and one with substantial custom information.
Compare the resulting records against the source. Check option names, variant combinations, prices, images, SKUs, inventory behavior, weights, and tax settings. Review the actual product pages as well as the imported data.
Shopify's product CSV guidance explains how imports create and update products. Review overwrite behavior and field requirements before applying an import to a catalog you have already edited.
Document each transformation. If a WooCommerce field becomes a Shopify custom field or needs an app, record where it lives and how the storefront uses it. That record is useful when someone needs to maintain the store later.
Plan customer accounts and recurring relationships separately
A customer record is not the same as a working login, historical order record, or active subscription. Shopify's customer CSV documentation states that customer passwords and order information cannot be transferred through the customer CSV.
Choose the account experience you will use and test it with a representative customer. Shopify's current customer accounts support passwordless sign-in. Prepare customer-facing instructions that match your actual setup rather than assuming existing WooCommerce passwords will continue working.
For subscriptions, confirm the migration process with both the current and destination providers. Verify what happens to payment credentials, renewal dates, discounts, customer access, and the next charge. A copied customer list does not establish that recurring billing has moved successfully.
Treat gift cards, store credit, loyalty balances, and wholesale access as their own workstreams where relevant. Give each an owner and a reconciliation check. These are customer obligations, not optional design details.
Map URLs before the new site is finished
Export or crawl the existing URL inventory. Combine it with analytics and Search Console so you can identify pages receiving traffic, generating sales, or earning external links. Include useful guides and other content, not just products.
For each important old URL, record the intended new destination. Preserve the underlying information when it still serves the customer. Redirect to the closest useful replacement rather than sending every retired page to the homepage.
Google's site-move guidance recommends preparing a URL map and monitoring the move. It also warns that rankings can fluctuate while changed URLs are recrawled and reindexed. A careful plan reduces avoidable problems; it cannot promise zero traffic disruption.
Shopify's built-in redirects apply to eligible broken URLs, not pages that still resolve normally. Review its URL redirect requirements and test your mappings. Query-string URLs, reserved paths, and domain changes can need additional planning.
Update internal links to their final destinations so customers do not rely on a chain of redirects as they browse.
Rebuild the buying experience, then test the operation
A migration is an opportunity to fix gaps in the old website, but keep the scope deliberate. Preserve what customers understand, improve the information and interactions that cause problems, and avoid changing everything without a clear reason.
A comprehensive build should cover collection navigation, product-page depth, mobile usability, brand expression, and the way apps fit the experience. A quick visual copy can carry the old store's weaknesses into a new platform.
Test representative orders from the storefront through your operational systems. Include the cases your business actually sells: different shipping regions, discounts, product options, subscriptions, or wholesale orders. Confirm payment behavior, order notifications, inventory changes, and fulfillment handoff.
Use Shopify's test-order guidance and the relevant providers' test procedures. Make sure test records cannot accidentally trigger real fulfillment or duplicate customer messages.
Also verify analytics and advertising events. A migration can appear to change performance simply because tracking fires differently. Record what changed so post-launch comparisons have context.
Make the final switch a controlled event
Choose a launch window and define who makes the go/no-go decision. Document the final import, the point when the old store stops accepting orders, and how orders or inventory changes made after the trial import will be reconciled.
Before switching, confirm that the team can access domain settings, payment accounts, integrations, and both stores. Preserve existing email-related DNS records when connecting the domain. The website move should not unexpectedly interrupt business email.
Write a rollback plan that accounts for new orders. Simply restoring an old copy of the site can leave customer and inventory records split between systems. Decide who will reconcile that data if a rollback is needed.
Immediately after the switch, test the live domain, important redirects, account access, and a complete purchase journey using an appropriate payment test. Check that the storefront is public when intended and that launch-only indexing restrictions have been removed.
Keep a post-launch owner on the project
Monitor orders, payment failures, fulfillment handoffs, customer questions, and important URLs. Submit the Shopify sitemap and review Search Console for indexing or crawl problems. Shopify's sitemap guidance covers the generated file and submission process.
Keep the old environment available for reference until the migration has been reconciled and your retention requirements are covered. Do not cancel tools or hosting merely because the new homepage is visible.
Give the team a short handover: where product data lives, how to update the new templates, which integrations own each workflow, and who handles problems.
If you are planning a move, Sugoi Digital's website design and development service can bring the storefront and migration work into one project. Work with us to scope the data, design, integrations, and launch checks before committing to a switch.
