September 4, 2026 · Vedanshu Jain
Shopify to WooCommerce Migration: An Honest 2026 Guide
A Shopify to WooCommerce migration pays off only under specific conditions — here is what transfers, what breaks, and when you should stay put.
A Shopify to WooCommerce migration is worth doing when platform fees, app subscriptions, or checkout and backend limits cost more than running your own stack. It is a mistake when your store is simple, profitable, and you have nobody to own hosting, updates, and performance afterwards. Decide on that question first; the data moves either way.
Read this part before you plan anything: reasons to stay
Most stores that ask about this should not do it. Four cases where staying is correct:
- The store is standard and profitable. A normal catalog, Shopify Payments, no unusual pricing logic. You would spend real money rebuilding something that works.
- There is no engineering capacity and no partner. WooCommerce is software you run. Somebody applies updates, watches error rates, and answers the phone on Black Friday. If that capacity does not exist and you are not hiring it, the move converts a subscription into an outage.
- You want zero infrastructure responsibility. On Shopify, PCI scope, checkout uptime, and platform patching are Shopify’s problem. That transfer has a price, and for many stores it is a fair one.
- Your customization is cosmetic. If everything you want lives in the theme and a couple of apps, you are buying flexibility you will not use.
If two or more describe you, close this tab. Nothing below changes the answer.
Why stores actually leave Shopify
Per-transaction fees when you are not on Shopify Payments. Shopify’s published pricing lists an additional transaction fee for third-party payment providers of 2% on Basic ($29/mo), 1% on Grow ($79/mo), 0.6% on Advanced ($299/mo), and 0.2% on Plus (from $2,300/mo), on top of whatever your gateway charges. Shopify’s help documentation adds that for stores created after May 12, 2025, orders paid with store credit or gift cards attract the same fee, and that Plus merchants using only Shopify Payments have it waived. If your region, acquirer, or risk profile keeps you off Shopify Payments, that surcharge scales with revenue and never stops.
App subscription stacking. Shopify does not publish an average app spend figure, so ignore the ones floating around and add up twelve months of your own app charges. The shape matters more than the total: every capability is another vendor, another renewal, another thing that can break your product page.
Checkout and backend customization below Plus. The checkout.liquid layout is, per Shopify’s developer docs, “available only to Shopify Plus merchants” — and even there it was sunset for the Thank you and Order status pages on August 28, 2025, with script tags on those pages sunset for Plus the same day and for non-Plus stores on August 26, 2026. Checkout logic now runs through Checkout UI extensions and Shopify Functions against versioned APIs. That is a defensible platform decision and also a hard ceiling: if you need a checkout step nobody else has, you are negotiating with an API surface rather than writing code.
Template-language and URL constraints. Liquid renders in Shopify’s runtime, not yours, and the URL prefixes are fixed. Shopify’s redirect documentation states that “You can’t redirect URLs that use fixed Shopify paths: /products, /collections, /collections/all,” and that prefixes including /apps, /cart, /orders, and /services are off limits too; themes reference paths through the routes object rather than hardcoding them.
Owning the data and the storefront. This is the reason that holds up over five years. The order table is in your database, the storefront is code you can read, and content and commerce live in one system — which matters if your growth depends on editorial or a buying experience nobody sells as an app.
What transfers, what does not, and what it costs
WooCommerce ships a free Product CSV Importer/Exporter in core. It handles products, variations, images, attributes, and custom meta, and explicitly does not handle customers or orders — the gap the paid tools fill.
LitExtension prices from $59, calculated from your entity counts, with an All-in-One managed service also starting at $59. Cart2Cart is the other name you will see; its WordPress.org plugin listing was permanently closed on January 9, 2023 and it now runs as a hosted service quoted through its own estimator — a flat price is not published.
| What you are moving | Transfers cleanly? | Effort and notes |
|---|---|---|
| Products, variants, images, categories | Yes | Low. Core CSV importer or a paid tool; budget time for image re-hosting. |
| Customer records | Yes, minus passwords | Low. Paid tool required; every customer resets their password. |
| Order history | Yes, as records | Medium. They import as records, not live transactions; refunds go through the gateway. |
| Blog posts and pages | Mostly | Medium. Formatting and embedded app blocks need review. |
| Discount codes and Scripts/Functions logic | No | High. Codes can be recreated; conditional pricing logic is a rebuild on WooCommerce hooks. |
| Subscriptions and recurring billing | No | Highest. Payment tokens are the blocker, not the schedule data. |
| Gift cards and store credit | Partially | High. Balances can be reissued; live codes and their liability need a plan. |
| Apps with no WooCommerce equivalent | No | Varies. Decide replace, rebuild, or drop before you commit to a date. |
| URLs and SEO equity | Only via redirects | Medium. A complete 301 map, written before launch. See below. |
| Sources | WooCommerce CSV importer, Woo subscriber migration | LitExtension pricing, Shopify redirects |
Subscriptions deserve their own paragraph. Card tokens are held by the gateway and scoped to the platform’s vault; you cannot export saved cards and import them. WooCommerce’s subscriber migration documentation recommends manual entry under about 100 subscribers, points at a free CSV importer that is in beta on GitHub and explicitly unsupported (“Woo does not provide services to complete a migration with this extension or support for issues”), and warns that PayPal Standard subscriptions cannot be migrated at all because the IPN URL cannot be reliably updated. WooCommerce Subscriptions is listed at $279 a year. If subscriptions are a material share of revenue, price the migration around them, not the catalog.
URLs, redirects, and the SEO consequence
Shopify’s fixed /products/ and /collections/ prefixes are the biggest technical difference at launch. WooCommerce lets you choose permalinks, and the temptation is to design something tidier. Resist it: set product permalinks to /products/ and category permalinks to /collections/ so most indexed URLs stay identical.
Then you only need redirects for the exceptions — /pages/, blog posts, filtered collection URLs, and every legacy handle that ever changed. Export the URL list from Shopify plus your Search Console coverage report and analytics landing pages, build one 301 map, and test it against a crawl before the DNS switch. Redirect chains and 302s are where rankings leak, not the platform change itself.
A realistic sequence, timeline, and budget
A planning estimate for a mid-sized store, not a published figure.
- Weeks 1–2 — inventory. Every app, script, integration, and revenue stream: replace, rebuild, or drop.
- Weeks 2–4 — stand up the target. Hosting, staging, deploy pipeline, monitoring, backups.
- Weeks 3–8 — data and build. Repeated test migrations into staging, theme work, the discount and pricing rebuild, then redirects, tax, shipping, and payments — the part that breaks launches.
- Weeks 7–9 — freeze, delta import, cut over. Low-traffic window, short DNS TTL, Shopify kept live and payable for at least 30 days.
- Weeks 9–12 — watch. Search Console coverage, checkout error rates, conversion by device, gateway reconciliation.
Budget: tooling in the low hundreds (from $59), licensed extensions in the hundreds to low thousands a year, and the build as the dominant line item. Anyone quoting a flat fee before reading your app list has not read it.
Pre-migration checklist: Shopify export archived; complete URL inventory; app-by-app replacement decision; gateway tested for your countries and currencies; tax and shipping verified against real orders; subscription plan agreed with your gateway; staging matching production; monitoring live before launch; rollback rehearsed; someone on call for launch week.
Why this calculation looks different than it did
This move used to require a standing engineering relationship, which is why so many stores stayed on Shopify and were right to. Shopify launched in 2006 against a constraint that was entirely real: running commerce infrastructure meant employing someone who could administer a server. The platform absorbed that in exchange for control, and for plenty of merchants that is still the better trade — the reasons-to-stay section above is not a formality.
What has changed is that the maintenance work is increasingly something an AI agent does against open code, with a person reviewing the result. That does not apply evenly, and the reason is structural rather than a matter of which AI is better. Sidekick is capable inside Shopify’s admin, but no agent can change what the platform does not expose — the fixed URL paths described above are the plainest case, unreachable on Shopify by any tool and a routing rule on WooCommerce. An agent can read WooCommerce’s PHP and change it; on Shopify it drives the Admin API and edits Liquid, then stops at platform internals and checkout below Plus. Openness is what makes the difference, which is the same reason this move is possible at all.
Two honest limits. METR’s randomized trial found 16 experienced developers 19% slower with AI across 246 tasks while believing they were 20% faster, on a deliberately narrow population. And an agent still needs somewhere safe to work: staging, tests, review, a rollback path. Without those, AI accelerates breaking your store rather than maintaining it — which is the same operational floor this guide has already insisted on.
What has to be true on the WooCommerce side
WooCommerce is a good outcome only when it lands on infrastructure that is actually run. You need hosting sized for your traffic with a defined compute model, not a shared plan chosen on price. You need performance and updates owned as a standing responsibility — WooCommerce, WordPress core, PHP, and every extension move independently, and unattended stores drift into breakage. You need staging that mirrors production, monitoring that watches checkout and payment paths specifically because a store can serve 200s while its checkout quietly fails, and a rollback path you have used.
Say it plainly: a store that leaves Shopify for cheap shared hosting with no operational owner usually regrets it. You trade a predictable monthly fee for an unpredictable one, give up a checkout somebody else kept running, and gain flexibility you have no capacity to spend.
How Urumi handles this
Urumi is the platform layer for stores past roughly $1M GMV, where slow checkout and downtime cost real money: horizontal auto-scaling on multi-zone Google Cloud, a 99.99% uptime SLA with auto-failover, isolated staging per branch with one-click rollback, managed APM, and 30-day point-in-time recovery. The list above gets an owner. Already have a team or an agency? They ship faster with the grunt work covered.
Do Amore is the relevant case: an ethical engagement-ring business with a diamond search, a ring builder, partial payments, and impact tracking — the kind of customization that makes a Shopify Plus rebuild expensive. They stayed on WooCommerce. Engagement-ring pages went from 5.9 s to 0.9 s and order edits from 8.1 s to 0.67 s, the migration was zero-downtime with every custom plugin intact, and it saved $251.5K over three years versus a fragmented stack, with an estimated ~$940K Shopify Plus rebuild avoided.
“With Urumi, we avoided a costly move to Shopify. We get Shopify’s speed and scale while keeping the ease and open-source flexibility of WooCommerce.” — Krish Himmatramka, Founder, Do Amore
What that includes is set out on managed WooCommerce hosting.
Frequently asked questions
Is it worth migrating from Shopify to WooCommerce?
It is worth it when platform fees, app subscriptions, or checkout customization limits cost more than running your own stack would, and when you have hosting, an engineering owner, staging, and a rollback path in place. If your store is standard and profitable on Shopify and nobody will own the infrastructure afterwards, staying is the better decision.
Will I lose SEO rankings moving from Shopify to WooCommerce?
Not if you preserve the URL structure. Configure WooCommerce permalinks to keep /products/ and /collections/ paths identical, then build a complete 301 map for pages, blog posts, and any changed handle. Rankings drop when redirects are incomplete or chained, not because the platform changed.
How much does a Shopify to WooCommerce migration cost?
Data tooling starts around $59 with LitExtension, plus extensions such as WooCommerce Subscriptions at $279 a year. The build dominates: a simple catalog move is a few thousand dollars; subscriptions, custom pricing, and ERP integrations push it into tens of thousands.
Can I move my Shopify subscriptions to WooCommerce?
Not automatically. Saved card tokens live in the gateway’s vault and are not portable with store data, so subscriptions must be re-established against a supported gateway. WooCommerce’s documentation recommends manual entry under about 100 subscribers and says PayPal Standard subscriptions cannot be migrated at all.
If you move, plan the hosting side with the same rigor as the data side — start with what managed WooCommerce hosting must include and the Do Amore case study.
Last reviewed September 2026. Competitor details come from their public pages on the dates linked; check them before you buy.
Built by the people who built WooCommerce core.
We built WooCommerce core at Automattic — the parts that matter in production: performance, payments, reliability. Earlier, engineering at HackerRank (Y Combinator) through its enterprise scale-up. Naman led Payments and WooCommerce releases to 4.5M merchants; Vedanshu led HPOS, Taxes, and Shipping. Run by AI, overseen by the people who built WooCommerce core.
Grow your store's revenue on Urumi.
The AI platform D2C brands use to grow revenue — built by the people who built WooCommerce core.
See the WooCommerce platform · Start your WooCommerce store on Urumi · Talk to the founders
Agent live · 99.99% uptime · shipping today.