WooCommerce · Guide
How to Back Up a WooCommerce Store Without Losing Orders
Short answer
A WooCommerce backup needs the database and the files together, made at about the same time. Back up the database first and then the files, keep at least 3 to 5 copies in different places, and restore files first and then the database, checking the four order tables before you reopen the store.
Key takeaways
- A WooCommerce backup needs the database and the files together, made at about the same time.
- Since WooCommerce 8.2, new installs store orders in four dedicated tables: wc_orders, wc_order_addresses, wc_order_operational_data, and wc_orders_meta.
- Keep at least 3 to 5 recent backups in different locations, with at least one copy off the server.
- Back up the database first and then the files; restore the files first and then the database.
- A backup you have never restored is unproven, so test every restore on staging.
What does a WooCommerce backup include?
A WooCommerce backup needs two parts: the database, which holds your products, orders, and customers, and the files, which hold your themes, plugins, and uploads.
The backup handbook says there are two parts to backing up a WordPress site, the database and the files, and you need both to fully restore a typical site.
Downloading your WordPress folder does not back up the database, because the database lives in a separate MySQL or MariaDB system, according to the same page.
Since WooCommerce 8.2, new installs store orders in four dedicated tables instead of the posts table, according to the High-Performance Order Storage documentation.
Those four tables are wc_orders, wc_order_addresses, wc_order_operational_data, and wc_orders_meta. A backup that skips one of them can leave orders half restored.
How often should you back up a WooCommerce store?
Back up as often as you take orders, because every order placed after your last backup is an order you cannot restore.
The backup handbook suggests once a week for smaller sites with fewer posts, and daily for high-activity sites, with a backup always before an upgrade.
A store that takes orders every day is a high-activity site by that measure. Daily backups are the floor for most stores, and busy stores need something more frequent.
Real-time or hourly backups close the gap between backups to minutes or seconds, so the worst case is a handful of orders instead of a full day. Ask your backup tool whether it supports that mode.
Read how often to back up WordPress to match the schedule to your order volume.
How do you back up with a plugin?
A backup plugin is the simplest route for most stores, since it can schedule the backup and send the copy off the server by itself.
- Go to Plugins > Add New and install a backup plugin from the WordPress plugin directory.
- Open its settings and choose to back up both the database and the files.
- Pick a schedule that matches your order volume, such as daily for a quiet store.
- Connect a remote storage location, such as cloud storage, so the copy leaves your server.
- Run one backup by hand and confirm the file appears in the remote location.
The backup handbook notes that automatic backup plugins exist in the plugin directory and can manage a backup collection for you.
Check that the plugin covers the four order tables named above. On a store using High-Performance Order Storage, the setting lives under WooCommerce > Settings > Advanced > Features, according to the High-Performance Order Storage documentation.
Allow about 30 minutes to set up a plugin backup the first time, including the first manual run and the storage check.
How do you back up with your host?
Most hosts back up the whole server, but you should still know what your plan covers, how long copies are kept, and how a restore is requested.
The backup handbook says most hosts back up the entire server, but requesting a copy of your site takes time, and a fast recovery is critical.
Open your hosting panel and look for a Backups section. Note the backup frequency, the retention period, and whether files and database are included in one restore.
Some plans back up daily, while others back up weekly or charge extra for backups. If your plan is unclear, ask your host in writing before you need a restore.
Ask your host whether a restore keeps orders placed after the backup, and how long a restore takes. A restore that rolls the store back a full day costs you a day of orders, so know that number before a crisis.
Read are host backups enough to see what host backups usually miss for a store.
How do you back up the database with phpMyAdmin?
Use phpMyAdmin in your hosting panel to export the database as a SQL file, which you can store with your file backup.
- Open phpMyAdmin from your hosting panel and click the database your store uses.
- Click Export at the top of the screen.
- Choose the Quick method for a simple export, or Custom to pick tables and options.
- In the Custom output section, check Save output to a file and pick SQL as the format.
- Click Go to download the file to your computer.
The backup handbook gives these exact export steps, including the SQL format and the save-to-file option.
The handbook also says to back up the database first and then the files, so the two halves describe the same moment as closely as possible.
A database export is usually a .sql, .gz, or .bz2 file, according to the backup handbook. Keep it with the matching file backup as one set.
Where should you store the backup copies?
Store copies in at least two places away from your server, so a server failure cannot take the store and its backups together.
The backup handbook says to keep at least 3 to 5 recent WordPress backups, with copies in different locations, such as one on your hosting server, one on cloud storage, and one on your local computer.
A copy that lives only on the same server as the store is not a real safety net. A hacked or failed server can take both.
Read where to store WordPress backups for storage options that fit a store, including cloud storage and a local drive.
Label each backup set with the date and time it was made, and keep the database export with its matching file backup.
How do you restore without losing new orders?
Restoring an old backup wipes out orders placed after that backup was made, so pause the store and note the newest orders before you restore.
The backup handbook says the restore order is files first, then the database, and to update wp-config.php if database credentials changed.
- Put the store into maintenance mode or pause new orders.
- Write down the newest order numbers and any orders placed since the backup.
- Restore the files first, then import the database.
- Check that the four order tables are present and the newest restored order matches your notes.
- Re-enter any orders placed after the backup, then reopen the store.
WooCommerce can sync order data between the posts table and the order tables with the wp wc cot sync command, according to the High-Performance Order Storage documentation.
Back up before any core, plugin, or theme update and before installing new plugins, as the backup lesson on Learn WordPress recommends. That habit gives you a fresh restore point before every risky change.
How do you check a backup actually works?
Restore the backup on a staging copy and place a test order, since a backup you have never restored is only a hope.
The backup handbook says it is highly recommended to back up automatic backups with a manual backup once in a while to guarantee the process is working.
Open the staging copy and check that products, prices, and customer accounts are present, and that the order tables hold the orders you expect.
Place a test order on staging and confirm the order number, the customer email, and the stock change all look right.
Read how to test a WordPress backup for a full checklist to run after each restore drill.
Repeat the drill after any change to your backup setup, such as a new storage location or a new plugin version. A backup routine that worked last year may not work after a settings change.
Which backup method should you use?
Use a plugin for scheduled daily backups, your host backup as a second copy, and phpMyAdmin when you need the database alone.
| Method | What it backs up | Schedule | Watch out |
|---|---|---|---|
| Plugin | Database and files, and sends the copy off the server | Daily for a quiet store, more often for a busy one | Confirm it covers the four HPOS order tables |
| Host backup | Whole server, files and database in one restore | Daily on some plans, weekly on others | Ask whether a restore keeps orders placed after the backup |
| phpMyAdmin export | Database only, as a .sql, .gz, or .bz2 file | Manual, whenever you export | Back up the database first, then the files |
What mistakes should you avoid?
The most common mistake is backing up only the files and finding out too late that the orders were never in them.
- Do not rely on host backups alone without checking retention, frequency, and restore steps.
- Do not store the only copy on the same server as the store.
- Do not skip the backup before an update. Updates are the most common reason a restore is needed.
- Do not restore on the live store without a staging check first.
For the general WordPress side of this job, read how to back up WordPress alongside this guide, since the same two-part rule applies to every site.
How do you back up before a big change?
Make a fresh backup before every WooCommerce update, theme change, or bulk product edit, since those are the moments a restore is most likely needed.
The backup lesson on Learn WordPress recommends backing up before core, plugin, or theme updates and before installing new plugins.
Run the backup, confirm the files exist in their storage location, and only then start the update. An update with no fresh backup leaves you with yesterday's orders as your only restore point.
Test the update on a staging copy first when you can. Place a test order on staging after the update and confirm the order number, totals, and stock levels look right before you touch the live store.
Frequently asked questions
Does downloading my site files back up my orders?
No. Downloading your WordPress folder copies themes, plugins, and uploads, but the database lives in a separate MySQL or MariaDB system. The WordPress backup handbook states this plainly: you usually cannot back up the database by downloading your WordPress directory.
Does WooCommerce store orders in special tables?
Yes. Since WooCommerce 8.2, new installs use High-Performance Order Storage, which keeps orders in four dedicated tables: wc_orders, wc_order_addresses, wc_order_operational_data, and wc_orders_meta. A backup that misses one table can leave orders half restored.
How often should a small WooCommerce store back up?
The WordPress backup handbook suggests weekly backups for smaller sites and daily backups for high-activity sites. A store taking daily orders counts as high activity, so daily is the floor, and busy stores should back up hourly or in real time.
Will restoring a backup delete recent orders?
Restoring an old backup removes orders placed after that backup was made. Pause new orders first, note the newest order numbers, restore files and then the database, and re-enter any orders placed after the backup before reopening the store.
How can I prove a backup works before I need it?
Restore it on a staging copy and place a test order there. Check that products, prices, customer accounts, and order numbers are all present. A backup that has never been restored is unproven, so run this drill after every change to your backup setup.
Sources
- Backups WordPress Developer Resources
- High-Performance Order Storage WooCommerce
- Backing Up Your WordPress Site Learn WordPress
- Requirements WordPress.org
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.
Thanks — we review requests within 3 business days.
