Shopify to WooCommerce: What Migrates, What Does Not, and What It Costs
Products move, apps do not. A decision sequence for a Shopify migration, starting with the things that were free on Shopify and become your responsibility on WooCommerce.
Moving from Shopify to WooCommerce is usually a cost or control decision, not a technical one. The technical part is well understood. What surprises people is how much of the work is deciding what not to bring across.
This is the decision sequence we use, in the order the decisions actually need to be made.
First: what Shopify does for you that you are about to lose
WooCommerce is a plugin on top of WordPress. Shopify is a hosted platform with opinions baked in. Before migrating, list the things that were free and will now be work:
- Hosting and security — you now own patching, backups and uptime
- PCI compliance — reduced to a form if you use hosted payment fields, real work if you do not
- Tax calculation — Shopify handles nexus rules; WooCommerce needs a service or manual configuration
- Fraud screening — Shopify’s built-in checks have no exact equivalent
- Support — there is no one to call
None of these are reasons to stay. They are line items in the budget. A migration plan that does not account for them lands on the developer six weeks later as “the site is slow and nobody knows why”.
Second: what does not migrate cleanly
Products, customers, orders and images move with varying degrees of fidelity. The gaps are predictable:
| Data | Migration reality |
|---|---|
| Products and variants | Reliable. Variants become child products; option structure usually survives |
| Images | Reliable but heavy. Shopify serves sized variants; expect to regenerate thumbnails |
| Customers | Records move, passwords do not. A reset flow is mandatory |
| Orders | Move as historical records, but line-item metadata differs and reporting will not match |
| Discounts | Partial. Complex Shopify discount combinations have no direct equivalent |
| Gift cards | Not natively. Needs a plugin, and balances must be reconciled manually |
| Apps | Not at all. Each one is a decision: replace, rebuild, or drop |
| Theme | Not at all. Liquid does not become PHP |
| Blog and pages | Content moves; URLs and internal links need rewriting |
The app list is where budgets blow up. A store with fourteen Shopify apps may need four plugins, one custom integration, and three features quietly dropped. Enumerate that before quoting.
Third: URLs, and why this decides the timeline
Shopify URLs follow /products/handle and /collections/handle. WooCommerce follows /product/slug and /product-category/slug. Nothing matches, and every indexed URL that 404s is a lost ranking and a lost customer.
The redirect map is not optional and cannot be generated after launch. Export every URL from Shopify — products, collections, pages, blog posts, and the tags that accumulated traffic — then map each to its new destination.
Two details that get missed:
- Collection tags often rank. A tag page like
/collections/all/waterproofmay have traffic and backlinks, and has no WooCommerce equivalent unless you build filtered category URLs deliberately. - Duplicate product URLs. Shopify historically served products under multiple collection paths. Redirect the canonical one and let the duplicates 301 to it, not to the homepage.
The same discipline applies to any platform move. Our OpenCart migration guide covers the SKU and variant side of the same problem.
Fourth: checkout and payments
This is where a technically successful migration can still fail commercially.
Shopify Payments is not available on WooCommerce. Depending on your markets, you will need Stripe, PayPal, a local acquirer, or a combination. Each has onboarding requirements, and each affects conversion.
Three things to test before switching traffic:
- Decline rates. A new gateway with no transaction history declines more aggressively at first. Expect a temporary dip and monitor it
- Currency settlement. If you display multiple currencies, confirm the gateway settles in them rather than converting silently — see the multi-currency checklist
- 3-D Secure flows. The authentication step behaves differently per gateway and per country, and it is the step customers abandon at
Fifth: the parts people forget entirely
Email deliverability. Order confirmations now come from your domain. Without SPF, DKIM and DMARC configured, a meaningful share lands in spam, and you find out from customer complaints rather than from a dashboard.
Analytics and tracking continuity. If conversion tracking breaks at cutover, you lose weeks of attribution and cannot tell whether the migration hurt or helped. Set up the new property in parallel before launch, not after.
Inventory source. If Shopify was also your inventory system via an app, that integration disappears. Most stores need an ERP or warehouse connection rebuilt — which is a project of its own, not a migration task.
A realistic sequence
- Inventory apps, features and integrations; decide replace / rebuild / drop
- Build the redirect map from a full URL export
- Set up hosting, staging, payment gateways and transactional email
- Import products and images; verify variation and SKU counts
- Import customers; implement password reset
- Import historical orders only if reporting or B2B reordering needs them
- Configure tax, shipping and currency for each market
- Parallel tracking; test orders in every currency and payment method
- Cut over DNS during a low-traffic window; keep the old store reachable for a short period
- Monitor 404s, decline rates and search performance daily for two weeks
Steps 1 and 2 decide whether the project succeeds. Steps 3 to 10 decide whether it launches on time. Most failed migrations optimise the second list.
If you are weighing this move for a store with real order volume, the app-and-feature audit is the part worth doing first, before any code. That is the work we do under WooCommerce development, and it is usually a week of decisions rather than a week of programming.