Skip to content
← Blog

Technical · 19 min read

WooCommerce to Shopify migration: the complete guide

A practical guide to migrating WooCommerce to Shopify: audit, data mapping, 301 redirects, testing, DNS cutover and a 30-day checklist for agencies.

November 17, 2026

WooCommerce to Shopify migration: the complete guide

Key takeaways

  • Migrate when the client wants hosted checkout and less upkeep, not because Shopify is popular.
  • Audit everything first: products, variants, customers, orders, URLs, SEO data, plugins, gateways and subscriptions.
  • Passwords cannot be moved. Plan an account reactivation email.
  • Almost every URL changes, so a full 301 redirect map is the key SEO task.
  • Build and test on staging, keep the old store live and switch the domain in a quiet window.
  • Timelines are typical ranges, never guarantees.

To migrate WooCommerce to Shopify, audit the old store, export products, customers and orders, import them into a staging Shopify store, rebuild the theme, map every old URL to a new one with 301 redirects, test checkout end to end, then switch the domain. Customer passwords cannot be moved, so customers reactivate their accounts, and most ranking loss comes from skipped redirects rather than from Shopify itself.

This guide is written for agencies moving a client’s store, and it is just as useful if you own the store. It covers when a move is worth it, what to audit, three ways to move the data, a step-by-step plan, SEO preservation, testing, launch day and the first 30 days after.

When migrating makes sense, and when it does not

A migration has real cost and risk. Here is an honest comparison for the client conversation. Our separate piece on what to recommend to your clients goes deeper on the recommendation itself.

Topic WooCommerce (WordPress) Shopify
Hosting and upkeep You or the client arrange hosting, updates, backups and security for WordPress, the theme and every plugin. Hosted platform. Shopify runs servers, checkout security and platform updates; you still manage the theme and apps.
Checkout Highly customisable, but depends on the theme, plugins and gateway behaving together. Hosted checkout that is consistent and well tested; deep customisation is more limited and depends on the plan.
Flexibility Very high. Almost anything can be built in PHP, and content and shop live in one system. High within Shopify’s model. Custom logic usually means apps, theme code or Shopify’s developer tools.
Content and blog Excellent. WordPress is a full CMS, so editorial content is a strength. Blog and pages are built in, but less flexible than WordPress for large content sites.
Running costs Software is free, but hosting, premium plugins, developer time and maintenance add up and vary widely. Predictable platform subscription plus apps and, with third-party gateways, possible extra transaction fees. Check current plans.

Migrating usually makes sense when the client is tired of plugin conflicts and update anxiety, wants a hosted checkout and simpler operations, sells mostly physical or digital products with standard flows, or has outgrown a cheap host that struggles during sales. It usually does not make sense when the store depends on heavy custom WooCommerce logic (complex bookings, memberships, bespoke pricing rules), when the shop is a small part of a large editorial WordPress site, or when the client has no budget to rebuild the theme and redirect the old URLs properly.

Watch out: A migration done badly can cost a store months of search visibility. If the client cannot fund redirects, testing and a launch plan, the honest advice may be to stay on WooCommerce.

Pre-migration audit checklist

Every surprise in a migration is a thing nobody wrote down at the start. Before quoting or touching anything, take inventory of the live store. Note whether each item moves, gets rebuilt, gets replaced by an app or gets dropped. For agencies this audit is also the basis of the quote; see scoping a WooCommerce to Shopify migration covers the commercial side.

  • Products: count of simple, variable, grouped and external products; drafts and private products; digital downloads; custom fields and product add-ons.
  • Variants and options: how many options each product has and how many variant combinations. Shopify limits options per product and variants per product, so find the outliers now.
  • Customers: total count, guest versus registered, marketing consent status, and any customer roles or groups.
  • Orders: how many years of history, order statuses in use, custom order meta and refunds. Decide how much history the client genuinely needs inside Shopify.
  • URLs: a full crawl of the live site, plus the top landing pages from Google Search Console and analytics, so you know which URLs matter most.
  • SEO metadata: page titles, meta descriptions, image alt text and canonical settings, usually held by an SEO plugin, which need exporting separately.
  • Plugins and apps: list every active plugin and what job it does. Each one needs a Shopify equivalent, a theme feature or a decision to retire it.
  • Payment gateways: which gateways are live, which the client wants to keep, and whether Shopify supports them in the client’s country.
  • Taxes: tax classes, rates, tax-inclusive or exclusive pricing, and any exemptions for wholesale customers.
  • Shipping: zones, methods, rates, free-shipping thresholds, local pickup, and any real-time carrier rates.
  • Subscriptions: active subscribers, billing schedules and how payment details are stored. This is often the hardest part of a move.
  • Gift cards and coupons: outstanding gift card balances, active discount codes and any automatic discount rules.
Two women talking and looking at a laptop screen together
Review the audit with the client. Most cost hides in items nobody mentioned.
Tip: Save the audit and a full export of the old store before any work starts.

Three ways to move the data

There is no single right method. The best choice depends on store size, how clean the data is and how much custom structure the store has. Treat the table as a starting point and test any tool on a small sample first. Supported platforms and import features change over time, so check Shopify’s current migrating to Shopify documentation before you promise anything.

Method How it works Pros Cons
Shopify’s own migration tool or CSV import Use Shopify’s built-in store import where your source is supported, or export WooCommerce data to CSV and import it into Shopify with Shopify’s CSV templates. No extra app cost; official and documented; good for straightforward catalogues; you control the data in spreadsheets. Manual cleanup of columns; limited handling of custom fields, orders and subscriptions; file size and format limits.
Third-party migration apps A migration app connects to both stores and copies products, customers, orders and sometimes pages and redirects. Faster for larger catalogues; can bring over order history; many offer a free or demo sample run. Pricing and features vary by app and by record count; mapping of custom data is limited; you depend on a third party’s quality and support.
Manual work or developer scripts Export from WooCommerce, transform the data in a script, then load it through Shopify’s Admin API. Maximum control; handles custom fields, odd variant structures, metafields and large volumes; repeatable for test and final runs. Needs a developer; takes longer to set up; you own the bugs; must respect API rate limits.

Many projects mix methods. Whichever you choose, run a full trial import first, then compare counts and spot-check records. Shopify’s Admin GraphQL API is the reference for the scripted route.

Step-by-step migration plan

This is the order we recommend. It keeps the live WooCommerce store untouched and trading until the final switch.

1. Create a staging store

Set up the new Shopify store (a development or trial store, depending on your access) and keep the old store live. Build and test everything here.

2. Import in a sensible order

  1. Settings first: currency, markets, taxes, shipping and legal pages, so imported data lands in a configured store.
  2. Collections and structure: plan collections before importing products, so you know where each product will live.
  3. Products and variants: including images, SEO fields and inventory quantities.
  4. Pages and blog content: so internal links can be rebuilt against real destinations.
  5. Customers: before orders, so historical orders can attach to a customer record.
  6. Orders: last, because they refer to products and customers.
  7. Redirects: prepared throughout, switched on at launch.

3. Map the data

The table below shows how common WooCommerce fields land in Shopify’s product and customer data.

WooCommerce field Shopify field Notes
Product name Title Straight copy.
Slug (permalink) Handle Becomes the end of the /products/ URL. Keep identical where possible to simplify redirects.
Description Description (Body HTML) Strip shortcodes and plugin markup that will not render.
SKU Variant SKU Every variant needs its own SKU.
Regular price and sale price Price and Compare-at price The WooCommerce regular price becomes the Compare-at price when a sale is active.
Stock quantity Inventory quantity (per location) Set the correct location. Quantities are a launch-day check.
Attributes Options (up to three) Products with more than three attributes need restructuring or metafields.
Categories Collections Collections are not categories; see below.
Images and gallery Product media Provide public image URLs or upload; carry across alt text.
SEO title and description (plugin) Page title and meta description Held by an SEO plugin, so export separately.
Custom fields Metafields Define metafield definitions first, then map.

Collections versus categories

WooCommerce categories form a tree, and one product can sit in several. Shopify collections are flat lists, either manual or automated by rules such as a tag, product type or price. Nested navigation is built in menus, not in the collection structure. Plan which categories become collections, which become filters or tags, and which are retired. Automated collections based on tags are usually the easiest way to recreate categories at scale.

Product variants and option limits

Shopify limits the number of options per product (three at the time of writing) and the number of variants per product. Those limits have changed over time, so confirm the current figures in Shopify’s product import documentation and the product help pages. A WooCommerce product with four attributes or an enormous combination count needs a plan: split it into several products, use a bundling or product options app, or move some choices into line item properties.

Group of colleagues gathered around laptops working together at a shared table
Agree the data mapping as a team before the first trial import, not after.

Customers and passwords

Customer records import fine, but passwords cannot be migrated. The practical approach is account reactivation. After launch, invite imported customers to activate their account, using Shopify’s customer account sign-in, which may use emailed codes or a set-password link depending on the account type the store uses. Email customers before launch to explain. Import customers with the customer CSV import or through the app or script you chose.

Order history

Historical orders can be imported through apps or the API, and they appear as past records for reporting and customer service. They are not live orders: they will not be fulfilled again, will not charge anyone, and normally do not email customers. Decide how much history the client needs. Many stores import only recent years and archive the rest.

Reviews, subscriptions and gift cards

Reviews need a reviews app that accepts an import, so choose it early. Subscriptions are the riskiest item: subscribers, schedules and stored payment details may not move automatically, and customers may need to re-enter payment details. Gift cards can be recreated with their existing codes and balances; check plan support.

Preserving your SEO

Search visibility is the most valuable thing a store can lose in a migration, and it is almost entirely preventable. The domain stays the same, so you do not need Google’s change-of-address tool, but you do need to treat it like a site move with URL changes. Google’s guide to site moves with URL changes is the canonical reference.

How the URL structure differs

Shopify uses fixed path prefixes you cannot remove or rename: /products/ for products, /collections/ for collections, /pages/ for pages and /blogs/ for articles. WooCommerce stores usually use different patterns, so almost every product, category and blog URL changes.

Content Typical WooCommerce URL Shopify URL
Product /product/linen-shirt/ /products/linen-shirt
Category or collection /product-category/shirts/ /collections/shirts
Page /about-us/ /pages/about-us
Blog post /blog/care-guide/ or /care-guide/ /blogs/news/care-guide
Cart and account /cart/ and /my-account/ /cart and /account

301 redirects

A 301 redirect tells browsers and search engines that a page has permanently moved. Build a redirect map from the crawl and the top landing pages, then load it into Shopify’s URL redirects (Online Store, Navigation, URL Redirects), either one by one or by CSV import. See Shopify’s help page on URL redirects and Google’s explanation of 301 redirects. A redirect map looks like this:

Redirect from Redirect to Note
/product/linen-shirt/ /products/linen-shirt One to one, same handle.
/product-category/shirts/ /collections/shirts Category becomes collection.
/product-category/shirts/linen/ /collections/shirts Nested category merged into its parent collection.
/shop/ /collections/all Shop page maps to the all-products collection.
/about-us/ /pages/about-us Page.
/blog/care-guide/ /blogs/news/care-guide Blog post.
/product/discontinued-item/ /collections/shirts Product retired, so send to the closest collection, not the home page.
  • Redirect each old URL to the most relevant new page. Sending everything to the home page is treated as a soft 404 and wastes the old page’s value.
  • Avoid redirect chains. Redirect straight to the final destination.

Metadata, alt text, canonicals and sitemap

  • Meta titles and descriptions: export them from your SEO plugin and import them into Shopify’s SEO title and description fields. Do not leave them empty or let them default to the product title.
  • Image alt text: carry alt text across with each image. It is easy to lose in a CSV.
  • Canonical tags: Shopify adds canonical tags to pages automatically. Check that product pages reached through a collection point to the main product URL, and that your theme does not override them.
  • Sitemap: Shopify generates /sitemap.xml automatically. After launch, submit it in Google Search Console and remove the old WooCommerce sitemap if it is still listed. See Google’s sitemaps overview.
  • Monitoring 404s: after launch, check Search Console’s page indexing report and Shopify’s 404 report for URLs that were missed, and add redirects for the ones that matter.
Tip: Crawl the old store again just before launch. Recently added URLs are the ones most often forgotten.

Theme rebuild or template

Shopify does not run WooCommerce themes, so the design has to be rebuilt either way. The choice is between starting from a ready-made template and having a custom theme coded. A template is faster and cheaper to start with. A custom theme costs more but suits stores with a strong brand or unusual product pages. We compare the two in custom Shopify theme vs template: what to tell your client.

If you need a developer to build the theme behind your agency, our white label Shopify development service builds custom themes under your brand, inside your client’s own store.

Apps that replace common WooCommerce plugins

Match plugins by the job they do, not by name. Shopify’s App Store has many options for each function, and pricing, features and quality change, so compare current listings before recommending one. Our piece on Shopify apps: what they cost and who pays covers the commercial side.

Function the WooCommerce plugin provided What replaces it on Shopify
Product reviews A reviews app that supports importing existing reviews.
Subscriptions and recurring billing A subscriptions app. Check gateway compatibility and how existing subscribers will move.
SEO fields, redirects and schema Native SEO fields and URL redirects, plus an SEO or structured-data app if more control is needed.
Email marketing and abandoned carts Shopify’s built-in tools, or an email platform’s Shopify integration.
Product options and add-ons Native options and variants, line item properties, or a product options app.
Bundles and upsells A bundles app or theme-level features.
Product filters and search Native storefront filtering, or a search and filter app for large catalogues.
Memberships and gated content Customer tags with theme logic, or a membership app. Often a good reason to keep that part elsewhere.

Testing checklist before go-live

Test on the staging store with real-world conditions, and keep a written record of what passed. Use test mode or a bogus gateway for payments, never live cards on a half-built store.

  • Checkout: place orders as a guest and as a customer, on desktop and phone, with and without a discount code.
  • Payments: every gateway the client plans to use, including wallets, plus a refund.
  • Taxes: check totals for each region you collect in, including inclusive or exclusive pricing and any exemptions.
  • Shipping: each zone, method and threshold, including free shipping and local pickup.
  • Emails: order confirmation, shipping confirmation, account invitation and password emails, with correct branding and sender details.
  • Products: a sample of products from each collection for price, variants, images, stock and descriptions.
  • Redirects: test the entire redirect map with a crawler or spreadsheet, not just a handful of pages.
  • Analytics: a GA4 property that receives page views, add-to-cart, begin checkout and purchase events with correct values.
  • Pixels and tags: ad platform pixels, conversion events and any tag manager setup. Check them with the tools those platforms provide.
White notebook beside a laptop on a desk
Keep a written test log. It protects both the agency and the client if something is questioned later.

Our website launch checklist for agencies has a general pre-launch list that complements this one.

DNS cutover and launch day

Pick a quiet trading window, not the day before a sale. Agree who does what and keep a rollback plan.

  1. Days before: lower the DNS record TTL so changes spread quickly, confirm who controls the domain registrar and DNS, and agree a freeze on product and order changes on the old store.
  2. Final sync: re-import products, stock levels and any customers and orders created since the trial import, then re-check counts.
  3. Connect the domain: add the domain in Shopify and set the DNS records exactly as shown in the admin, following Shopify’s guide to connecting a domain manually. Do not copy record values from an old article; use what your admin shows.
  4. Switch checkout live: remove any password protection on the storefront and turn on live payments.
  5. Smoke test: place one real order and refund it, test a handful of redirects and confirm analytics is receiving events.
  6. Resubmit and watch: submit the new sitemap, then watch orders, errors and the 404 report closely for the first day.
Watch out: Do not shut down the old hosting on launch day. Redirects, exports and anything you forgot to move may still be needed in the first weeks.

The first 30 days after launch

  • Days 1 to 3: watch orders, payments and emails daily. Fix anything customers report straight away.
  • Week 1: review the 404 report and Search Console coverage. Add redirects for missed URLs. Confirm GA4 and ad conversions match order counts.
  • Week 2: send the account reactivation reminder to customers who have not logged in. Check abandoned checkout and email flows.
  • Weeks 3 and 4: compare organic traffic, rankings for top pages and conversion rate against the pre-launch baseline. Investigate sustained drops.
  • Day 30: review apps in use, remove anything unused, document the setup for the client and then decommission the old store once the exports are archived.

Realistic timeline by store size

These are typical ranges from this kind of work, not guarantees. Real timelines depend on how fast the client supplies content and approvals, how clean the data is and how much of the theme is custom.

Store size Typical timeline What drives it
Small: up to a few hundred simple products, standard checkout About 3 to 6 weeks Template or light custom theme, CSV import, a short redirect map.
Medium: hundreds to a few thousand products with variants, blog content and several apps About 6 to 12 weeks Custom theme sections, order history, reviews import, larger redirect map, more testing.
Large or complex: many thousands of products, subscriptions, custom logic or several integrations About 12 to 20 weeks or more Developer scripts, app and integration rebuilds, staged testing, subscription migration.

The theme build and client approvals usually take longer than moving the data.

Common mistakes

  • Skipping the redirect map. The single biggest cause of lost rankings after a platform move.
  • Redirecting everything to the home page. Send each old URL to its closest equivalent.
  • Underestimating variants. Products with more than three attributes or very large combination counts cause late surprises.
  • Promising customer passwords will move. They will not. Tell customers early.
  • Launching without testing a real order. Test payments, taxes, shipping and emails before the switch.
  • Switching off the old store immediately. Keep it available until you are sure nothing was missed.

How agencies can price and white-label a migration

The effort sits in the details of the store, so quote from the audit.

  • Quote from the audit. Product and variant counts, apps to replace, subscriptions, redirect volume and integrations decide the scope. Our guide to scoping a Shopify build lists the questions to ask.
  • Separate the pieces. Price the data migration, the theme build, the redirect and SEO work, and testing and launch as separate lines, so the client sees where the money goes.
  • Keep apps outside your fee. Client-paid app subscriptions are a client decision, and listing them separately avoids margin surprises.
  • State what you do not promise. Say plainly that you cannot guarantee rankings or traffic, only that the migration is carried out carefully and redirects are planned.

That is what our white label Shopify migration service is for. We handle the move under your brand, quoted before work starts, and pair it with a custom Shopify theme build when the client needs one. If you have a store to move, book a call and send the audit.

Frequently asked questions

How do I migrate WooCommerce to Shopify?
Audit the old store, export products, customers and orders, import them into a staging Shopify store, rebuild the theme, add 301 redirects, test checkout and then connect the domain.
How long does a WooCommerce to Shopify migration take?
Typical ranges are about 3 to 6 weeks for a small store, 6 to 12 for a medium one and 12 to 20 or more for a complex one. These are typical ranges, not guarantees.
Can I migrate WooCommerce customers and passwords to Shopify?
Customer records can be imported, but passwords cannot. Customers activate their account again after launch, so email them beforehand.
Will I lose my SEO rankings when moving from WooCommerce to Shopify?
Not necessarily, but URLs change, so skipped redirects put rankings at risk. Map every old URL to its closest new page, carry across metadata and resubmit the sitemap.
Do I need 301 redirects when migrating WooCommerce to Shopify?
Yes. Shopify uses /products/, /collections/, /pages/ and /blogs/ paths that differ from most WooCommerce URLs, and redirects keep old links and results working.
Can I convert my WooCommerce theme to Shopify?
No. WooCommerce themes do not run on Shopify, so the design is rebuilt as a Shopify theme, either from a template or coded custom.
Can I transfer WooCommerce orders to Shopify?
Yes, historical orders can be imported through apps or the API as past records. They will not be fulfilled or charged again.
What happens to WooCommerce subscriptions when I move to Shopify?
They are one of the hardest parts. Subscribers and stored payment details may not move automatically, so plan the app and gateway early.
Is moving from WooCommerce to Shopify worth it?
It can be, if the client wants hosted checkout and less maintenance. It is less worthwhile for stores with heavy custom logic or large editorial sites.
Can an agency white-label a WooCommerce to Shopify migration?
Yes. Many agencies hand the data move, theme build and redirects to a white label partner who works under the agency brand.

Sources and further reading

  1. Shopify Help: migrating to Shopify — official overview of moving a store to Shopify.
  2. Shopify Help: importing products — the product CSV format and import steps.
  3. Shopify Help: importing and exporting customers — customer CSV requirements.
  4. Shopify Help: URL redirects — creating and importing redirects.
  5. Shopify Help: connecting a domain manually — DNS setup for the cutover.
  6. Shopify developer docs: Admin GraphQL API — reference for scripted imports.
  7. WooCommerce docs: product CSV importer and exporter — exporting your product data.
  8. Google Search Central: site moves with URL changes — the checklist for moving URLs safely.
  9. Google Search Central: redirects and Google Search — how permanent redirects work.
  10. Google Search Central: sitemaps overview — building and submitting sitemaps.

Ready to talk?

Looking for a white label web partner you can actually rely on?