WooCommerce to Shopify Migration: The Complete Checklist
A step-by-step guide to moving products, customers, and SEO equity from WooCommerce to Shopify, with exact redirect rules and DNS records for cutover.
A woocommerce to shopify migration means moving your products, customers, and optionally your order history and blog content from WooCommerce to Shopify, then redirecting every changed URL and cutting your domain over without taking the store offline. Shopify documents this as a 19-step process built around CSV exports, column mapping, and a DNS cutover window of up to 48 hours.
The Five Ways to Run a WooCommerce to Shopify Migration
Before you move a single product, Shopify's own migration guide asks you to decide how you're going to move each type of content, because the right method depends on what you're moving and how much of it there is. Shopify lists five options: copying content over manually, using its free Store Migration app, exporting and importing CSV files, using a third-party migration app such as Matrixify, or hiring a Shopify Partner to manage the whole project.
Manual copy-paste is exactly what it sounds like, and it only makes sense for a handful of products or pages — past that, it's slower than any of the other four options and just as error-prone. The Store Migration app is Shopify's own free tool for importing WooCommerce products and customers straight from the CSV files WooCommerce exports; if you selected WooCommerce as your previous platform when you signed up for Shopify, it may already be offered as an import option on the Products or Customers page of your admin. CSV import without the app gives you more control over the mapping, but you do the column conversion by hand — that's the path most of this guide follows, since it's the one Shopify's documentation covers in the most structural detail. Third-party migration apps from the Shopify App Store, such as Matrixify, exist specifically to move the content that CSV import and the Store Migration app can't: coupons, historical orders, blog posts. And hiring a Shopify Partner is Shopify's own fifth listed option — the one it recommends when you'd rather have someone else run the data migration, the redirect mapping, and the domain cutover as a single project instead of coordinating four separate tools yourself. That's the role our shopify WooCommerce migration service is built to fill: moving your catalog, customers, and the integration work that comes after the storefront migration, in one engagement rather than several.
Which option makes sense depends mostly on catalog size and how much of your data falls into the exceptions covered below. A small catalog with simple products and no coupon or order-history requirements is a reasonable fit for the free Store Migration app. A larger catalog with variable products, categories to rebuild as collections, and historical orders to preserve usually needs either a third-party app to cover the gaps, or a Partner to run the whole sequence as one project instead of five separate handoffs.
Mapping and Importing Your Product CSV
If you're moving your catalog yourself, the product CSV is where most of the real work happens. WooCommerce's built-in exporter, under Products > All Products > Export in your WordPress admin, gives you a CSV, but it isn't in a format Shopify can import directly — you have to edit it to match Shopify's product CSV template first.
The column mapping is mostly mechanical. WooCommerce's Name column becomes Shopify's Title, entered only on the first row of each product. Attribute columns become Option name and Option value columns — a WooCommerce variable product exports as one parent row plus one row per variation, while Shopify's CSV expects the product details on the first variant's row and then one additional row per variant, each sharing the same URL handle. Stock becomes Inventory quantity, and SKU carries over unchanged. Weight needs a unit conversion depending on which column WooCommerce used: multiply kilograms by 1,000, pounds by 453.6, or ounces by 28.35 to get the grams value Shopify's CSV expects. WooCommerce's Categories have no direct equivalent in Shopify's CSV — the workaround is adding category names into the Tags column, then rebuilding them as collections using tag-based conditions once the import is done.
There's one hard limit worth knowing before you map anything: Shopify's product CSV import supports a maximum of three options per product. If a WooCommerce product uses four or more attributes to define its variations, it imports without variants at all — you'd need to add the variants back manually afterward, or handle them with a third-party app or metafields. It's also worth knowing that however you import, by CSV or the Store Migration app, every imported product lands in your store as a draft, not live, so you get a chance to review before anything goes public. Use that review window deliberately: check a sample of imported products for the variant and category edge cases above before you publish anything, rather than discovering a broken option set after customers can already see it.
What WooCommerce Data Doesn't Move Automatically
Not everything in your WooCommerce store has a clean path into Shopify, and knowing the gaps ahead of time saves you from cleanup after you move WooCommerce to Shopify.
- Coupons can't be imported through a CSV file at all. You'll need to recreate them as Shopify discounts by hand, or move them with a third-party migration app like Matrixify.
- Historical orders, meaning anything already fulfilled in WooCommerce, also can't come in through CSV. A third-party migration app is the only path Shopify documents for bringing order history across.
- Customer passwords don't transfer, since Shopify has no way to read them out of WooCommerce. Imported customers sign in with their email address and a one-time verification code instead of a password; stores on legacy customer accounts need to invite imported customers to set a new password.
- Blog posts and pages aren't included in the WooCommerce export at all, since they sit outside the product and customer data Shopify's importers expect. You'll either add them manually in Shopify or move them with a third-party app such as Matrixify.
- Product reviews follow the same pattern: they're not part of the WooCommerce product export, so they need their own import path if you want to keep them.
None of this is a reason to avoid a CSV-based migration. It just means the CSV handles the bulk, structured catalog and customer data, and a short, deliberate list of exceptions needs a different tool.
Protecting Your SEO Equity With URL Redirects
This is the step generic migration checklists tend to gloss over, and it's where most of the search-visibility risk in a WooCommerce to Shopify migration actually lives: your WooCommerce URLs and your new Shopify URLs won't match, and every mismatch is a potential 404 for both visitors and search engines.
Shopify's redirect tool has a specific, easy-to-miss mechanic: a redirect only fires when the "from" URL is genuinely broken, returning a 404 or similar error. If the old URL still resolves to a live page for any reason, the redirect you set up for it simply won't work. That matters during a migration because old collection or product URLs sometimes stay live by accident, which silently breaks a redirect you assumed was working.
There are also fixed limits worth planning around before you start mapping URLs. You can't redirect anything starting with /apps, /application, /cart, /carts, /orders, /services, or /shop, and the fixed paths /products, /collections, and /collections/all can never be redirected either, since Shopify reserves them. There's also a ceiling on volume: a maximum of 100,000 URL redirects on Shopify's standard plans, rising to 20,000,000 on the Shopify Plus plan. For a catalog with thousands of products, each with its own WooCommerce URL pattern, that ceiling is rarely a binding constraint, but it's worth checking against your sitemap before you assume every single URL can get a one-to-one redirect.
In practice, the fastest way to handle this at scale is in bulk: Shopify lets you export and import URL redirects as a CSV from Content > Menus > URL redirects in the admin, the same pattern as the product CSV. Build your full old-URL-to-new-URL map in a spreadsheet, generate the redirect CSV, and import it in one pass rather than creating redirects one at a time.
If a redirect you've created doesn't seem to be working, Shopify's own troubleshooting steps are worth running through before assuming the tool is broken: check both the "redirect from" and "redirect to" URLs for typos, confirm the "redirect from" URL doesn't resolve to an active page, confirm it isn't a fixed path or one of the blocked prefixes above, and clear your browser cache before testing again.
Cutting the Domain Over Without Downtime
Once your data is imported and your redirects are mapped, the domain cutover is the step that actually makes the new store live to the world, and it's also the step most likely to cause a visible outage if you rush it. Connecting a third-party domain to Shopify means changing three DNS records at your domain provider:
- A record → Shopify's IPv4 address, 23.227.38.65
- AAAA record → Shopify's IPv6 address, 2620:0127:f00f:5:: (use the expanded form, 2620:0127:f00f:0005:0000:0000:0000:0000, if your provider rejects the condensed version)
- www CNAME record → shops.myshopify.com., including the trailing period, which several providers require explicitly
A domain can only have one A record and one www CNAME record pointed at Shopify at a time, so if your current host already has an A record or CNAME in place, you're changing those records rather than adding new ones alongside them. Shopify also recommends keeping your domain provider's default nameservers unless you're managing DNS somewhere else, since custom or external nameservers can cause connection problems if they're not configured correctly; if another provider already hosts your DNS, you don't need to move the domain back, but a Cloudflare proxy in front of your records isn't supported and should be set to "DNS only" if it's present.
Once those records are saved and you've connected the domain from Settings > Domains in your Shopify admin, expect it to take up to 48 hours for the domain to be fully live. During that window, a pending TLS or SSL status in your Shopify admin is normal and expected; it reflects DNS propagation still working its way through, not a failed connection. If your A record ends up showing a different final number than 23.227.38.65 after connecting, that's also normal — Shopify assigns regional IP variants, and a different ending is still a valid, working A record.
After the Migration: What Still Needs to Sync
Getting the storefront live on Shopify is only half the job if your WooCommerce store wasn't running standalone. Plenty of merchants have WooCommerce wired into an ERP, a 3PL, or a CRM for inventory, fulfillment, or customer data, and none of those connections survive a platform migration automatically. They have to be rebuilt against Shopify's own APIs once the storefront itself is live.
That's a different kind of project than the CSV and DNS work above. It's integration engineering, not data migration, and it's worth scoping separately rather than assuming it falls out of the storefront move for free. If inventory and fulfillment logic were running through your ERP before, our breakdown of the best ERP for Shopify is a reasonable next read for picking the right system now that you're on Shopify. And if NetSuite specifically was, or will be, part of that stack, our Shopify NetSuite integration comparison covers the realistic paths for getting the two systems talking again.
If you want this migration, and whatever needs to sync afterward, set up for your store, talk to our team.
Frequently asked questions
Will I lose my Google rankings when I migrate from WooCommerce to Shopify?
Not inherently, but ranking loss is a real risk if you skip the redirect step. Shopify's redirect tool only fires on URLs that return a genuine 404, so any WooCommerce URL that changes and isn't mapped to a new Shopify URL can show search engines and visitors a broken page instead of a redirect. Mapping every changed URL before you cut the domain over is what protects the rankings those pages already have.
How many product variants can I import from WooCommerce to Shopify?
Shopify's CSV import and Store Migration app both cap products at a maximum of three options. If a WooCommerce product uses four or more variation attributes, it imports without variants at all, and you'd need to add the missing variants back manually, through a third-party app, or with metafields.
Can I migrate my WooCommerce order history to Shopify?
Not through a CSV file — Shopify's migration guide is explicit that historical, already-fulfilled orders can't be imported that way. A third-party migration app is the documented path for bringing order history across.
Do WooCommerce coupons transfer to Shopify automatically?
No. WooCommerce coupons can't be imported via CSV, so you'll need to recreate them manually as Shopify discounts or move them with a third-party migration app such as Matrixify.
How long does the domain cutover take?
Shopify says it can take up to 48 hours for a newly connected domain to be fully live, and a pending TLS/SSL status during that window is expected rather than a sign of a problem. DNS propagation is what's happening behind the scenes during that period.