WordPress to Shopify Migration: When WooCommerce Starts Holding Growth Back

Most people who search for wordpress to shopify migration or moving from wordpress to shopify already know why they want to leave WooCommerce. What's missing everywhere else is the actual SEO mechanics: how URLs map, what a real redirect file looks like, where product data breaks, and how to keep the traffic you've spent years earning.

This guide is written for that person — a store owner, dev, or marketing lead who is past the "should we switch" conversation and into the "how do we do this without losing rankings" conversation. If you're doing a broader wordpress to shopify migration project, treat this as the SEO and technical-QA layer that sits underneath the rest of the build.

WordPress/WooCommerce and Shopify use different, non-negotiable URL patterns, and you cannot change Shopify's side of the equation.

For products, WooCommerce typically uses a structure like /product/product-name/, while Shopify locks this to /products/product-name. For categories or collections, WooCommerce uses /product-category/category-name/, whereas Shopify fixes this as /collections/category-name. Blog posts follow a similar pattern: WooCommerce commonly uses /blog-post-name/ or /category/blog-post-name/, while Shopify forces every post into /blogs/news/blog-post-name. Even the blog index page changes — WooCommerce's /blog/ becomes Shopify's /blogs/news.

Shopify's URL prefixes (/products/, /collections/, /blogs/) are hard-coded into the platform. You can't remove them, and most WooCommerce sites don't use them. That mismatch is the single biggest reason moving from wordpress to shopify tanks rankings when it's rushed.

The fix isn't "add a redirect plan" as a vague bullet point — it's building a literal mapping table before a single product is imported:

Old URL                                   New URL

/product/mens-leather-jacket/          →  /products/mens-leather-jacket

/product-category/jackets/             →  /collections/jackets

/blog/how-to-style-a-leather-jacket/   →  /blogs/news/how-to-style-a-leather-jacket

On Shopify, these redirects are added under Settings → Apps and Sales Channels → Online Store → Navigation → URL Redirects, or bulk-uploaded via a CSV with two columns: Redirect from and Redirect to. For large catalogs (500+ URLs), the CSV upload is the only realistic method — doing this manually one product at a time is how launches get delayed by weeks.

→ Download the URL Migration Mapping Template (pre-built CSV, ready to fill in and upload directly to Shopify)

If you're moving off Apache/WordPress hosting, your old .htaccess rewrite rules won't transfer — Shopify doesn't use .htaccess at all. Every redirect has to be rebuilt natively inside Shopify's redirect system or via an app if you're managing thousands of URLs.

WooCommerce stores rarely have clean, structured product data — even when the storefront looks fine. Custom fields get added by different plugins over the years (one for size, another for material, another for care instructions), and a lot of specification data ends up typed directly into the product description as plain text instead of being stored as structured attributes.

When that gets exported to a CSV and imported into Shopify, here's the practical problem: Shopify expects Options (like Size, Color) and Metafields (for specs like material, warranty, dimensions) to be defined before import — not inferred from a paragraph of text. A common failure pattern looks like this:

• WooCommerce CSV has a column called Attribute 1 value(s) with mixed data: "Red, Blue | Cotton | Machine Washable"
• Shopify's importer reads this as a single option value, not three separate pieces of structured data
• Result: a "Red, Blue | Cotton | Machine Washable" variant option nobody can filter by

The fix is to clean and split this data into separate columns before import — Size, Color, and Material as distinct fields — and map care instructions to a metafield rather than jamming it into the description. This is manual, unglamorous work, and it's exactly the step most rushed migrations skip.

If your WooCommerce site has a blog that drives top-of-funnel traffic, this section matters as much as the product migration.

Two things break almost every time:

This is the order that avoids rework. Skipping ahead — especially importing products before planning Shopify's structure — is the most common source of post-launch cleanup.

Timelines are driven far more by content and integration complexity than by product count. A 200-SKU store with no blog and no integrations can migrate in a few weeks. A 200-SKU store with a five-year-old blog, three marketing integrations, and custom checkout logic can take two to three months — most of that time spent on redirect mapping, content rebuilding, and integration QA, not on Shopify theme development itself.

Any timeline quoted without first auditing the blog content, plugin dependencies, and integrations is a guess, not a plan.

The steps above cover the technical mechanics. The strategic sequencing — how to audit dependencies, decide what to rebuild versus replace, and validate tracking and integrations before launch — is covered in more depth in our full migration framework. If you're evaluating a migration and want a second opinion on scope or timeline, that audit-first conversation is the right starting point before any data moves.