Practical guide

Move a WooCommerce store without losing recent orders

Last materially reviewed 2026-09-21

Quick answerDefine how new writes are handled before replacing a database or changing traffic.
What to know

Before cutover, identify changing order data

A WooCommerce migration is not only a file transfer. Orders, customer actions and other records can change while a copy is being prepared. Identify the authoritative system for each stage and decide how writes are controlled or reconciled during the move. A staging database made yesterday is not automatically safe to place over today’s production database, even when its design and plugin changes have passed visual review.

What to know

Define the transfer scope precisely

Cloudways staging and restore tools expose choices involving files and database content. Use those choices according to an understood application plan, not as a shortcut around data analysis. A fictional store changing a theme may not need to replace its entire order database. Conversely, a change involving schema or plugin data may require more than copying files. Establish the exact requirement and supported procedure before authorizing a potentially destructive operation.

What to know

Verify without creating false business activity

Use disconnected or specifically authorized test workflows for checkout behavior. Do not charge a card, email customers or create real affiliate referrals merely to make a test look complete. Record the boundaries of the test and which production facts remain unverified. During an actual move, reconcile the relevant records across the cutover period so a successful homepage load is not mistaken for proof that every recent order survived.

What to know

Make recovery account for newer records

Restoring an older database can reverse a code problem while also removing legitimate activity that occurred afterward. The recovery plan must address both consequences. Identify who can authorize a restore, which data must be preserved separately and how reconciliation will be verified. If the plan cannot explain what happens to recent orders, stop the risky step. A fast rollback that loses business records is not a complete recovery.

Continue when useful

Next: Choose a restore point with the data consequences in view

An older database can remove newer records even when the application files are correct.

Open Choose a restore point with the data consequences in view →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Cloudways staging: file/database selection — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21
  2. Cloudways restore points and recovery boundaries — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21