Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

WooCommerce · Guide

How to Migrate a WooCommerce Store With Zero Lost Orders

How to Migrate a WooCommerce Store With Zero Lost Orders

Short answer

To migrate a WooCommerce store without losing orders, copy the files and database to the new server while the old store keeps selling, test checkout fully, then freeze new orders, take a final database export, import it on the new server and switch DNS. The freeze window is what keeps every order in one place.

Key takeaways

  • A store keeps changing during a move, so an order placed after your database export exists only on the old server.
  • WooCommerce 10.8 and later needs WordPress 6.9 or higher, PHP 8.3 or higher and a 256 MB WordPress memory limit.
  • HPOS is the default order storage for new installations from WooCommerce 8.2 onward, and existing stores are not moved over on their own.
  • A short freeze window with a final database export is the simplest way to move a store with zero lost orders.
  • Keep the old server untouched for two weeks so any order found only there can be recreated or refunded.
  • Lower the DNS TTL to 300 seconds a day before the move so the switch spreads fast.

Why is moving a WooCommerce store different from moving a blog?

A store keeps changing while you move it, because new orders, payments and stock changes arrive every minute.

A blog is mostly fixed text and images, so a copy made at noon still matches the live site at night. A store is a live ledger, and an order placed after your database export exists only on the old server. That gap is how orders get lost, stock counts drift apart and a customer pays for an order that never reaches the new store.

WooCommerce also runs background jobs through Action Scheduler, which sends emails, fires webhooks and processes renewals. If both servers run those jobs at once, a customer can get two emails or a renewal can run twice. Plan the move around the order flow, not around the files.

What should you check before you start the move?

Check the order storage mode, the server requirements and the backup before you copy anything.

Open WooCommerce, then Settings, then Advanced, then Features, and note the order data storage mode. WooCommerce's HPOS documentation states that HPOS is enabled by default for new installations from WooCommerce 8.2 onward, and that existing stores are not moved over on their own (checked November 2026). The new server must use the same mode as the old one, so write it down before you start.

Next, compare the new host against the WooCommerce server recommendations. For WooCommerce 10.8 and later, the page lists WordPress 6.9 or higher, PHP 8.3 or higher tested up to PHP 8.4, MySQL 8.0 or higher or MariaDB 10.6 or higher, HTTPS support and a WordPress memory limit of 256 MB or higher (checked November 2026).

Older versions still run on PHP 7.4 and MySQL 5.6, but WooCommerce notes those versions are past end of life.

The WooCommerce plugin page on WordPress.org lists the current version as 11.3.1, released 19 November 2026, with the same 256 MB memory recommendation (checked November 2026).

Take a full backup of files and database, and keep it until the new server has run cleanly for a few weeks. Note the payment gateways, the shipping setup and any extension that stores data in custom post types, since those need care during the switch. A guide to how to back up a WooCommerce store covers the backup step in detail.

Which migration method fits your store?

Pick a full-site migration plugin for most stores, manual file and database transfer for full control, or a host-managed move when your new host offers one free.

A migration plugin copies files, database, settings and orders in one archive and rewrites URLs for you. It suits most stores because it handles serialized data, which plain search and replace in SQL can corrupt. Check the plugin's import size limit against your site size first, since a store with years of product images can exceed it.

Manual migration with WP-CLI or FTP and phpMyAdmin gives full control over each step. It suits developers who need to move only part of a store or who work on servers without plugin installs. It also takes longer and needs care with the database export, because a locked export can miss orders placed during the copy.

A host-managed move suits stores whose new host offers free migration. Ask the host whether they move WooCommerce orders and whether they test checkout before cutover. Some hosts move only files and the database and leave payment re-authentication to you.

MethodBest forSkill neededLost-order risk
Migration pluginMost stores of any sizeBeginnerLow, with a freeze window
Manual transferDevelopers who want full controlAdvancedMedium without a final export
Host-managed moveHosts that offer free migrationNoneVaries by host process

How do you build and test the new copy?

Copy the store to the new server while the old store keeps selling, then test the copy on a private address before you switch anything.

Export the database without locking tables so orders keep flowing. With WP-CLI, the command wp db export store.sql --single-transaction takes a consistent snapshot. Then copy wp-content and the config file to the new server and import the database there.

Edit wp-config.php on the new server so the database name, user and password match the new database. The copied file still holds the old server's details, and the new copy will fail to connect until you change them.

Test the copy on a staging address or by editing your local hosts file. Place a test order with a test payment, check the shop, cart and checkout pages, and confirm emails arrive. WooCommerce's HPOS documentation notes that background sync actions backfill 25 orders at a time, so give the sync time to finish on the copy before you judge it (checked November 2026).

If the sync stalls, the HPOS CLI reference lists wp wc hpos sync and wp wc hpos status for checking progress from the command line.

If the move also changes the domain, use wp search-replace, which handles serialized data safely and offers a --dry-run flag, as the WP-CLI search-replace documentation explains (checked November 2026).

The manual migration guide at how to migrate WordPress manually explains the file and database steps in detail.

How do you stop new orders from getting lost at cutover?

Use a short freeze window: stop the old store taking orders, take a final database export, import it, then switch DNS.

The freeze window is the only simple way to get zero lost orders. Put the old store into maintenance mode or use a catalog mode setting, then export the database one final time. That export holds every order up to the minute you froze the store.

Import the final export on the new server and check the order count against the old server before you switch DNS. The two counts must match exactly, including pending and failed orders. If they differ by even one order, find the missing order before you go further.

If you cannot pause sales at all, cut over without a freeze and then copy across any orders placed on the old server after your final export. This delta sync is slower and needs care, because refunds, stock changes and coupon uses also move. For most small stores, a freeze window of 15 to 30 minutes at a quiet hour costs less than chasing missing orders for days.

How do you switch DNS and check the new store?

Lower the DNS TTL a day before the move, then switch the records and confirm the new server answers before you reopen the store.

A TTL of 300 seconds, which is 5 minutes, lets the change spread fast once you switch the records. Lower it at least a day ahead, because the old TTL value controls how long resolvers cache the old address until it expires.

Point the domain at the new server, wait for the records to spread, and load the site from a fresh network or a mobile connection to confirm you reach the new server. Check that the SSL certificate covers the domain, since payment gateways will refuse checkout on a certificate error.

Reopen the store only after you have placed a real test order on the new server and seen it in WooCommerce, then Orders. Confirm the order email arrived and the payment shows in your gateway dashboard. The guide to how to change the domain of a WordPress site covers URL changes when the move also changes the domain.

What should you check in the first 24 hours after the move?

Check orders, payments, stock, emails and scheduled actions in the first day, because small breaks hide behind a working home page.

Open WooCommerce, then Status, then Scheduled Actions, and look for past-due actions. The WooCommerce system tools documentation lists the cleanup and status tools on that screen (checked November 2026).

A backlog there means background jobs are not running on the new server, and renewal or email jobs will stall. Ask the new host to set up a real cron job if WP-Cron is not firing on schedule.

Compare the order totals on both servers and confirm that refunds and cancellations from the last day appear in one place only. Check stock levels on your five best-selling products, since a missed delta sync shows up first in stock counts.

Watch the payment gateway dashboard for failed payments and check that tax and shipping settings survived the move. Confirm the site still meets the server numbers from the WooCommerce server recommendations, including the 256 MB memory limit (checked November 2026).

What do you do if an order or payment breaks after the move?

Keep the old server untouched for two weeks, then recreate or refund the affected order from the old server's records.

Do not delete the old server right after cutover. If an order exists only on the old server, you can recreate it by hand on the new server or refund it from the old gateway account, then tell the customer what happened. The old database export is your source of truth for that order.

If payments fail on the new server, re-authenticate the gateway connection first. Many gateways tie keys or webhooks to a domain or server, and a move can break that link even when the keys look the same. WooCommerce's own fix guide for WooCommerce Stripe webhook errors covers the most common webhook break.

If checkout breaks only for some customers, clear the cache and check that the new server meets the PHP 8.3 minimum for WooCommerce 10.8 and later (checked November 2026). A PHP version mismatch can break a gateway that worked fine on the old host. When the problem is order storage, the guide to what is HPOS in WooCommerce explains the two storage modes and how to switch back safely.

Frequently asked questions

How long should the freeze window be when migrating a WooCommerce store?

For most small stores, 15 to 30 minutes at a quiet hour is enough to export the database, import it on the new server and switch DNS. Larger stores with big databases may need longer, so time a trial export on staging first and pick your quietest hour from the last month of order times.

Can I migrate a WooCommerce store with no downtime at all?

You can keep the site online, but you cannot keep taking orders on both servers without extra work. The safe no-freeze option is a delta sync: cut over, then copy across every order, refund and stock change placed on the old server after your final export. It takes longer and needs careful checking.

Do I need to change the HPOS setting during a migration?

No. Keep the same order storage mode on the new server as the old one. WooCommerce docs say HPOS is the default for new installations from version 8.2 onward, while existing stores stay on their current storage unless you switch. Never change storage mode in the same week as a host move.

Why did payments stop working after I moved my store?

Many gateways tie API keys or webhooks to a domain or server, so a move can break the link even when the keys look the same. Re-authenticate the gateway on the new server, check its webhook status, and confirm the new server meets the PHP and memory requirements for your WooCommerce version.

How long should I keep the old server after migrating?

Keep it for at least two weeks. That gives you time to spot a missing order, a failed renewal or a stock mismatch and fix it from the old server records. Only delete the old server once orders, payments and scheduled actions have run cleanly on the new one for a full sales cycle.

Sources

  1. High-Performance Order Storage WooCommerce
  2. WooCommerce Server Recommendations WooCommerce
  3. WooCommerce Shipping Documentation WooCommerce
  4. Accounts and Privacy Settings WooCommerce
  5. WooCommerce plugin WordPress.org
  6. WooCommerce System Tools Documentation WooCommerce
  7. wc hpos commands WooCommerce Developer Documentation

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test