Skip to content
WordPress November 19, 2026 12 min read

Shopify to WooCommerce Migration Without Losing Orders

Planning a Shopify to WooCommerce migration? Orders go missing in the gaps, not the copy. Freeze, export twice and cut over in order.

Parameter
Parameter
Author

Most store owners expect a Shopify to WooCommerce migration to lose orders during the data copy. That’s rarely where it happens. The copy is a file moving from one place to another, and you can check it. Orders go missing in the gaps between the two systems: the hours after your last export, the minutes when DNS points some buyers to the old store, and the days when a payment webhook still reports to a checkout nobody watches anymore.

So we plan this as a sequencing problem. Get the order of operations right and the copy mostly takes care of itself. Get it wrong and you can have a clean import and still lose orders.

Where Orders Actually Get Lost in a Shopify to WooCommerce Migration

Orders usually go missing in a few predictable places. Name them before you start, because each one needs its own fix.

The export-to-launch gap. You export orders on Monday and launch on Thursday. Every order placed in between lives only in Shopify. If nobody runs a second export, those orders never reach WooCommerce, and the customers who placed them get confused later.

The DNS gap. When you switch your domain, the change doesn’t reach every buyer at once. For a while, some people land on the new store and some still see the old one. If the old checkout is still open, they keep buying there.

The payment gap. Your payment provider sends events (payment captured, refund issued, dispute opened) to whatever endpoint it has on file. If that endpoint still points at Shopify, or if the new store’s endpoint is set up wrong, you get payments without orders or orders stuck on "pending" even though the money arrived.

The email gap. WordPress often sends order emails through the server’s default mail function, and many hosts handle that badly. Orders get created, but confirmations never arrive, and buyers place the same order twice. If your forms already have trouble sending mail, fix it first with our guide to fixing WordPress email delivery.

The app gap. Shopify apps quietly do work you stop seeing: fulfillment routing, subscription renewals, review requests, tax handling. When the store moves, those jobs stop. Nothing errors out. They just don’t run anymore.

Here is a hypothetical example of how these gaps stack up. A store exports everything on a weekday morning, imports it to WooCommerce, and switches DNS that evening. Shopify checkout stays open "just in case." Over the next day, a handful of buyers whose DNS hasn’t updated check out on Shopify. Those orders are paid, but they exist only in a store the team has stopped checking. Nobody finds them until customers email asking where their packages are. The import itself worked fine.

Before You Touch Anything: Audit, Export, and Freeze Rules

Start with an inventory of what the Shopify store actually does. Count products, variants, customers and orders. List every installed app and what it does. Write down shipping zones, tax settings, discount rules and any custom scripts. That list becomes your test plan later.

Then export. In the Shopify admin, exporting orders as a CSV works from the Orders page: sort and filter, click Export, choose which orders, pick a file format, then click Export orders. A few details matter for planning:

  • Exports of up to 50 orders, or the current page, download straight to your device. Larger exports, or exports by date, are emailed to you and the store owner.
  • If an export fails, Shopify emails you. Watch for that email instead of assuming silence means success.
  • Export time grows with volume. Shopify says fewer than 100,000 items might finish in under an hour, while 400,000 items might take about 4 hours. Large stores should run the full export well before cutover day.
  • Transaction histories are a separate export. They contain captured payments only. Authorization data is not included.

That last point matters a lot. If you authorize cards at checkout and capture them later at shipping, any open authorizations at cutover won’t show up in your transaction export. Capture or void them before you close the old store, or you will have money you can’t account for cleanly.

Shopify only imports and exports UTF-8 CSV files, and it recommends Google Sheets for editing because special characters can break in other spreadsheet programs. Text editors are a last resort. Keep an untouched copy of every export before anyone opens it.

Now set your freeze rules. Write them down and give each one an owner:

  1. Catalog freeze. No product, price or variant edits in Shopify after the final product export. Changes after that point go into a list and get applied to WooCommerce by hand.
  2. Discount freeze. No new discount codes or automatic discounts during the migration window.
  3. App freeze. No new apps, no removing apps, until cutover is done.
  4. Order export timestamp. Record the exact time of the last full order export. At cutover you’ll export everything after that time by date. This is the delta export, and it closes the export-to-launch gap.
  5. One cutover owner. One person decides when checkout closes on Shopify and when DNS switches. Shared ownership is how both stores end up taking orders at the same time.

Mapping Products, Customers, and Order History Into WooCommerce

Products. WooCommerce has a built-in product CSV importer at Products > All Products, with Import and Export buttons next to Add new product. You choose a CSV or TXT file, click Continue, review the column mapping, then run the importer. Don’t refresh or leave the page while it runs.

A Shopify product export won’t drop straight in. The column names and the structure differ, so you’ll build a mapping sheet. Things that trip people up:

  • Unmapped columns are skipped. WooCommerce auto-maps the columns it recognizes. Anything else is not imported by default. Custom fields can come across using a meta: prefix.
  • IDs aren’t yours to pick. You can’t assign a specific ID to a new product. WooCommerce uses the next available one. Plan your URLs and redirects around slugs and SKUs, not IDs.
  • SKUs carry the load. Update imports match rows by ID or SKU, and WooCommerce doesn’t create a SKU when the cell is blank. WooCommerce 11.2 and later can fall back to the GTIN, UPC, EAN or ISBN field if both are blank, but that’s a fallback, not a plan. Fix blank and duplicate SKUs in the spreadsheet before you import.
  • Variants become variations. A variable product needs a parent row with Type set to variable, plus variation rows with Type variation, a unique SKU and a Parent value. Attribute names and values must match exactly, or variations end up orphaned.
  • Images need a reachable URL. Images must be uploaded already or available online. Some hosts block the fetch, so upload failed images to the Media Library yourself. The core importer can’t set image alt text, so keep a list for the SEO pass.
  • Formatting. Use UTF-8, the store’s local timezone for dates, and 1 and 0 for true and false. A number in the stock column turns on stock management. A blank turns it off.
  • Publish status. The Published column controls status: 1 is published, 0 is private, -1 is draft, 2 is pending review. We import as drafts on staging first, then flip them to published once they look right.

When imports fail, the usual causes are duplicate SKUs or IDs without "Update existing products" checked, mismatched columns, an odd Published value, a plugin or theme conflict, or a file too big for the server. For large catalogs, back up, test on staging and split the CSV into batches. Upload limits are set at the server level, so ask your host to raise them. If the core importer isn’t enough, WooCommerce lists a premium Product CSV Import Suite extension for heavier jobs. This is the routine work Parameter’s WordPress maintenance plans are built around.

Customers. Customer records move fine. Passwords are another matter, so plan on customers resetting them, and check how your migration tool handles accounts before you write the announcement email.

Order history. This is where Shopify’s export format bites. An order with several line items puts the extra items on separate rows, and many fields are blank on those rows. Your import has to group rows by order number (the Name column) or Id. If it doesn’t, you get dozens of "orders" with no customer and no total.

Other details from the order CSV worth knowing:

  • The Discount Code column does not include automatic discounts. Order totals will still reconcile, but you can’t rebuild the discount history from that column alone.
  • The compare-at price column can be blank. The export shows historical data from when each order was placed, not today’s prices.
  • Payment References and Payment ID are there to match orders to your payment provider. When an order has more than one, they’re separated by a space, a plus sign and another space. Keep these fields, because they’re how you’ll reconcile refunds and disputes later.

Shopify order exports are one-way. Orders and discounts can be exported but not imported back into Shopify. If you roll back, the WooCommerce orders don’t come with you. Keep the Shopify store reachable as a read-only archive for a while, and keep the raw CSVs forever.

On the WooCommerce side, check where orders will live. High-Performance Order Storage (HPOS) is on by default for new installs from WooCommerce 8.2. It stores orders in four dedicated tables instead of the older posts and postmeta tables. Before you pick an order import tool, confirm it supports HPOS. If an incompatible extension isn’t from the Marketplace, it will disable the HPOS switch in the admin. If you switch modes on an existing install, WooCommerce > Settings > Advanced > Features lets you turn on compatibility mode to keep both storage types in sync. The backfill runs 25 orders at a time through scheduled actions, or you can run it with wp wc cot sync. The docs advise leaving compatibility mode on for a while. One warning from the same docs: deactivating extensions that use custom post types, such as Subscriptions or Bookings, before enabling HPOS can cause data mismatches.

You don’t have to import every order ever placed. Many stores bring over two or three years of history and keep the rest in the archived CSVs. Decide based on what customer service actually looks up.

Payments, Webhooks, and Email: The Cutover That Protects Live Orders

Set up your payment gateway on staging in test mode first. Run the full cycle: place an order, capture payment, ship, issue a partial refund, issue a full refund. Check that every step updates the order status in WooCommerce. If a refund in the provider’s dashboard doesn’t show up on the order, your webhook isn’t working yet.

In your payment provider’s dashboard, add the WooCommerce webhook endpoint. Don’t delete the Shopify connection until the delta window has closed and you’ve confirmed no stray orders. Removing it early is how refunds on old orders stop syncing.

Then the cutover itself, in this order:

  1. Lower DNS TTL a few days ahead so the switch spreads faster.
  2. Capture or void open authorizations on Shopify.
  3. Close checkout on Shopify. Use whatever store-closing or password option your plan offers. The point is that nobody can pay on the old store once the switch starts.
  4. Run the delta order export by date, starting from your recorded timestamp.
  5. Import the delta and compare counts. Order count, line item count and total revenue for the period should match.
  6. Switch DNS.
  7. Place a real order with a real card, then refund it. Confirm the customer email, the admin email and the webhook update.
  8. Watch both stores for 48 to 72 hours. Any order that shows up on Shopify after the close means a step got skipped.

Order numbers are a common snag. WooCommerce numbers orders its own way, so new orders won’t continue Shopify’s sequence by default. If your accounting or warehouse relies on sequential numbers, look at a sequential order number plugin or add a prefix, and test it on staging. This is the kind of ongoing work our Odoo support services are built to cover.

Transactional email deserves its own test. Send order confirmations, shipping notices and password resets to addresses on a few different providers. If they land in spam or don’t arrive, connect an SMTP service before launch, not after.

Redirects and SEO So Buyers (and Google) Find the New Store

Shopify and WooCommerce use different URL structures for products and categories, so nearly every product and collection URL changes. Without redirects, every bookmarked product, every ad and every search result points to a 404.

Build the redirect map from real data, not guesses. Pull URLs from the old sitemap, your analytics landing pages, and Search Console. Map each one to its new URL with a 301. Cover products, collections (which usually become categories), pages and blog posts. Avoid chains, where one redirect points to another redirect. Map old to final in one hop.

Then the on-page work:

  • Carry over meta titles and descriptions. Your mapping sheet should hold them.
  • Re-add image alt text, since the core importer skips it.
  • Check canonical tags, especially on variations, so they don’t compete with parent products.
  • Submit the new sitemap and watch coverage reports for a few weeks.

We cover the full process in our guide to keeping SEO through a rebuild. Most of it applies here too.

Post-Launch Checks and When to Connect Inventory or ERP

Run this list on launch day and again a week later:

  • Order counts and revenue for the migration period match across both systems.
  • No new orders on Shopify after checkout closed.
  • A test refund syncs from the payment provider to WooCommerce.
  • Confirmation, shipping and password reset emails all arrive.
  • Stock levels match a physical count on your top sellers.
  • Tax and shipping totals match on test orders to a few regions.
  • Top 50 old URLs redirect to the right new pages in one hop.
  • Search Console shows no spike in 404s.
  • Scheduled actions aren’t piling up as failed.
  • Backups run, and a restore has been tested.

If the site breaks after launch, our post-migration recovery walkthrough shows how we track down the cause. A white screen with a database message usually means credentials, covered in our database connection error fix.

Inventory and ERP are where a WooCommerce move turns into a bigger project. If you sell on more than one channel, ship from more than one warehouse, or your accountant rebuilds sales from exports every month, stock and orders need a single source of truth. Plug that in after launch without a plan and you bring back the same gaps you just closed, now between WooCommerce and your back office. Our guide to syncing ecommerce with an ERP covers order flow, and the inventory migration plan covers stock. Both are worth reading before you pick a connector.

At Parameter, we run migrations like this one as a sequence with owners and checkpoints, because that’s what keeps orders from falling into the gaps. Whether you do it yourself or bring in help, the rule for a Shopify to WooCommerce migration stays the same: freeze first, export twice, cut over in order, and watch both stores until the old one goes quiet.

Want WordPress to feel handled?

Self-serve onboarding takes minutes. Parameter takes care of the rest, hosting, ops, and improvements when you need them.