Small brands usually leave WooCommerce for the same reason: they want to run a store, not maintain WordPress hosting, plugins and payment extensions. Shopify removes most of that. What most migration guides skip is that the move also changes every product URL and quietly replaces a custom brand site with a theme. This guide covers both. For non-commerce WordPress moves, see our guide to migrating from WordPress.
How do you move a WooCommerce store to Shopify?
You move a WooCommerce store to Shopify by exporting products, customers and orders, importing them with Shopify's migration tools or an app, rebuilding the storefront in a theme, and redirecting every old URL. Do the redirect map and the content plan before the import, not after.
Audit the catalog
List products, variants, categories, attributes and extensions. Retire discontinued products now so you don't migrate dead pages.
Crawl and export URLs
Export every product, category, tag, page and post URL, plus Search Console clicks and backlinks per URL. This becomes the redirect map.
Import the data
Use Shopify's store migration tools or a migration app to move products, customers and order history. Check variants, images and SEO fields on a sample before running the full import.
Choose and customize a theme
Pick a theme close to your layout needs, then customize the homepage, product templates and brand pages to match your identity.
Rebuild apps and integrations
Replace WooCommerce extensions for subscriptions, reviews, bundles and email with Shopify apps. Fewer is better.
Upload redirects
Import the redirect map as a CSV in Shopify's URL redirects settings, then test the highest-traffic URLs by hand.
Switch domain and payments
Point the domain, run test orders with each payment method, and send customers an account activation email.
Check Shopify's help center for the current import options, because the tools and apps available change.
How do product URL redirects work from WooCommerce to Shopify?
Product URL redirects from WooCommerce to Shopify map each old product, category and tag URL to its new Shopify path with a 301. They are needed because Shopify uses fixed URL prefixes, such as /products/ and /collections/, that you can't change.
WooCommerce URL | Shopify URL | Redirect needed? |
|---|---|---|
/product/linen-shirt | /products/linen-shirt | Yes, prefix changes |
/product-category/shirts | /collections/shirts | Yes, prefix changes |
/product-tag/summer | /collections/summer or a filtered collection | Yes, map to the closest collection |
/about | /pages/about | Yes, pages get /pages/ |
/blog/post-name | /blogs/news/post-name | Yes, blog path changes |
/cart, /checkout, /my-account | Shopify system pages | Usually yes, to the equivalents |
Keep product handles identical to the old slugs so most redirects follow one pattern. Variant URLs with query parameters usually don't need individual rows, but products with backlinks or real search traffic should each get a tested one-to-one redirect.
How do you protect SEO in a WooCommerce to Shopify migration?
You protect SEO by keeping product titles, descriptions and handles, carrying over meta titles and descriptions, redirecting every URL, and checking structured data and indexing after launch. Shopify themes generate product schema, but verify it on your chosen theme.
- Carry SEO fields across: Yoast or Rank Math titles and descriptions sit in WordPress meta fields, which basic exports can miss. Map them to Shopify's SEO fields for each product and collection.
- Watch duplicate URLs: Shopify can link products inside collection paths. Themes normally set the canonical to the main /products/ URL, but confirm it.
- Rebuild the blog carefully: if content drives traffic, migrate posts with their slugs and images, and redirect each one.
- Submit the new sitemap: Shopify generates one automatically. Add it in Search Console on launch day.
- Monitor for weeks: compare clicks by page against your baseline, and fix any product that keeps falling.
For the full checklist, the same principles in our SEO-safe WordPress to Webflow guide apply here: baseline first, map every URL, test on launch day.
What happens to the brand pages and marketing site?
In most WooCommerce to Shopify moves, the brand pages get rebuilt inside a Shopify theme, and that is where small brands lose the most. A custom WordPress homepage, about page, lookbook and story pages become theme sections that look like many other stores.
Treat the brand pages as a design project, not a data transfer. Write the homepage and product page copy first, then design the sections around it, and customize the theme rather than accepting its defaults. Typography, photography direction and the order of information on the product page do most of the work.
Hypothetical example: a small apparel brand's page plan
For example, suppose a small apparel brand with 80 products and a WordPress blog about fabric sourcing. The data moves with an import app. The work that needs real design is five templates: homepage, collection, product, about and journal post.
The product template gets a materials section and a fit guide that the stock theme lacks. The about page keeps its long-form story. The journal keeps its URLs under the new blog path, with redirects. Everything else uses theme defaults, because customizing pages nobody visits wastes budget.
Some brands keep the store on Shopify and run the brand and content site separately. Our guide to moving a brand site to Webflow while keeping the store explains when that split makes sense.
Should a small brand go headless instead?
Usually not. Headless Shopify, where a custom front end in Next.js or Hydrogen talks to Shopify's back end, gives full design control but costs far more to build and maintain. Typical ranges we see quoted for headless Shopify projects run into six figures, and they vary widely.
Pros
- Full control over design, speed and content structure.
- One codebase for store and rich content or editorial pages.
- Easier to add custom features apps don't cover.
Cons
- Much higher build and maintenance cost than a theme.
- Many Shopify apps assume a theme and need custom integration.
- Needs a developer for changes a theme editor would handle.
If you're already planning that path, read migrating a Shopify theme store to headless first. For moving content between headless systems later, see our headless CMS migration guide. If you sell in several countries, plan market and language URLs early with our guide to multilingual websites.
