REPLATFORMING · WOOCOMMERCE → SHOPIFY
WooCommerce to Shopify, content included.
WooCommerce migrations have a complication the platform-to-platform guides tend to skip: the store is only half the site. The other half is WordPress — posts, pages, and often years of content that is doing more for your search and AI visibility than the product pages are. Migrating the catalog and treating the blog as a follow-up is the most common and most expensive mistake on this path.
What transfers
- Products, variations and images
- Customers, and orders as read-only records
- Product categories, becoming Shopify collections
- WordPress posts, via a separate and deliberate content migration
What does not
- Plugin-held data — subscriptions, bookings, custom fields — which sits outside WooCommerce's core tables
- WordPress URL structures, which are arbitrary and rarely map cleanly
- Page-builder layouts, which do not survive and are rebuilt
- Shortcodes embedded in product and post content, which arrive as literal text if nobody strips them
- SEO plugin metadata, which needs explicit export rather than assuming it rides along
The sequence.
Split the inventory
Catalog and content are two migrations with two different risk profiles. Scope them together even if you sequence them apart.
Plugin audit
Establish which data lives in WooCommerce core and which lives in plugin tables. The second group needs its own export path or it is silently left behind.
Catalog import
Variations become Shopify variants. Reconcile counts and check that image ordering and alt text survived.
Content migration
Posts and pages into Shopify's blog or a headless front end. Strip shortcodes before import, not after.
URL map
WordPress permalinks are arbitrary, so this map is larger and messier than a pure catalog migration. Crawl the live site; do not rebuild from a sitemap that may itself be stale.
Cutover and measure
Watch content URLs as closely as product URLs — on this path they are usually the ones carrying the visibility.
The part nobody scopes
What this move does to your AI visibility.
On WooCommerce stores the pages assistants cite are disproportionately blog posts and guides, not product pages — that is what a decade of WordPress content produces. Because the content half is usually scheduled after the catalog half, those are exactly the URLs sitting broken or unmapped during the window when assistants re-read the site. Sequence it deliberately: the content migration is not the low-risk half.
The mechanism is the same on every path. Assistants cite specific URLs; change the URLs and those citations point at pages that are gone. They re-read on their own cadence rather than on your launch date, so a redirect map signed off on crawl stats can still leave an assistant quoting a dead page for weeks — while the new theme rebuilds your structured data from scratch, because markup is theme-level on most platforms.
Before you freeze the old store
Take a citation baseline while the old site is still live. Which assistants name you, for which questions, and which URLs do they cite? After the cutover that record is unrecoverable — the pages those citations point at will not exist, and you will have no way to tell whether you lost ground or never held it.
During the URL map
Redirect maps are usually built for Googlebot and signed off on crawl stats. Assistants resolve citations on their own schedule and do not re-crawl on your launch date, so a 301 that satisfies Search Console can still leave an assistant quoting a page that now bounces. Map the specific URLs you were cited on first, not just the URLs with sessions.
When the new theme ships
Structured data is theme-level on most platforms, so a replatform silently rebuilds it. Product, Offer, availability and price markup that an agent could read on the old store may be absent, partial, or rendered client-side on the new one. Diff the emitted JSON-LD before and after — not the theme's feature list.
After cutover
Re-run the same prompt set you baselined. Recovery is not instant and is not uniform across assistants: each re-reads on its own cadence, so a surface that looks unchanged in week one can move in week six. Hold the measurement open for a quarter before calling it.
Only the baseline has a deadline — it is the one step that becomes impossible once the old store is dark. The free Citation Rank scan records it, and Visibility Score is where the measurement lives afterwards. House of Zelena is what that loop looked like end to end.
Who should do this work.
Not us — we do not migrate stores, and we are not a migration tool, vendor or agency. What we do sits underneath the migration: whether an agent can read your catalog, whether assistants recommend you, and whether an agent-driven purchase completes. A replatform is simply the cheapest moment to get that right, because your catalog structure and templates are already open.
For the migration itself, brief specialist firms and full agencies against the same written scope — including your extension list. The agency buyer’s guide covers the questions worth asking and the answers that should end a conversation. If you run migrations for clients, the agent layer is available to deliver on our platform via the partner programme.
How we connect to these platforms
Questions
Decide it before the migration rather than after, because the answer changes the URL map. Shopify's blogging is materially less capable than WordPress, so some brands keep WordPress on a subdirectory or subdomain for content and run Shopify for commerce. That is a legitimate architecture, but it is a decision with redirect consequences — making it late is what turns it into a problem.
Anything a plugin stored outside WooCommerce's core tables needs its own export path, and that includes the cases people assume are safe — subscriptions, bookings, custom product fields, and SEO metadata. Standard migration tools read core objects. Enumerate your plugins during scoping and ask, per plugin, where its data physically lives.
They fail in opposite directions. WooCommerce gives you control and hands you the maintenance, security and performance burden that comes with running WordPress at scale. Shopify removes that burden and takes back the control, including over checkout. If your team does not have someone whose job includes keeping WordPress patched, the calculation usually favours Shopify — but that is an operating question, not a feature comparison.
Not as-is. Shopify requires /products/ and /collections/ prefixes, while WooCommerce permalinks are configurable and frequently customised. Every indexed URL needs an explicit destination — and on this path the content URLs usually outnumber the product URLs, so budget the mapping work accordingly.