WP Engine Staging Push Can Overwrite WooCommerce Orders: The Data Loss Nobody Warns You About

How the data loss happens

WP Engine's Copy Environments feature offers two modes: Full Copy (all files + all database tables, complete overwrite) and Custom Copy (select files, database, or both, with optional table selection). The official documentation states it plainly:

"We do not recommend pushing the entire database to the production environment. If you do, the production database will be completely overwritten. This destructive process can cause the loss of important data, such as new orders or users."

Their Development Workflow Best Practices doc is more direct: "It is NEVER advised to include a database when copying to a live site." And: "Copying a database from your development instance will destroy newly added, live data."

The problem is that the warnings exist in documentation, not in the push UI. A store owner clicking "Push to Production" in the WP Engine dashboard sees the copy options but not an inline warning about WooCommerce orders. The ecommerce-specific guidance is in a separate Best Practices for eCommerce Sites document that you find only if you search for it.

WP Engine does create automatic backups of both source and destination environments before and after the copy. If you catch the problem immediately, you can restore from backup. If you discover the missing orders days later, after the backup retention window, the orders are unrecoverable.

Why HPOS changes the game

Traditional WooCommerce stores orders in wp_posts (as the shop_order custom post type) and wp_postmeta. This creates an impossible choice: exclude wp_posts from your staging push to protect orders, and you also exclude every page, post, and piece of content on your site. Or include wp_posts and lose every order placed since your staging snapshot.

High-Performance Order Storage (HPOS), default for new WooCommerce installations since version 8.2 (October 2023), moves orders to dedicated tables:

• wp_wc_orders
• wp_wc_order_addresses
• wp_wc_order_operational_data
• wp_wc_orders_meta

With HPOS enabled, you can use WP Engine's selective table push to exclude these four tables while pushing everything else. Orders stay in production, untouched. Content, settings, and plugin data get updated from staging. This is the first time the staging problem has had a clean technical solution.

The catch: older stores that have not migrated to HPOS still store orders in wp_posts. If your store has been running since before WooCommerce 8.2, check your WooCommerce > Settings > Advanced > Features page for "Custom order tables" status. If it says "Not in use," your orders are still in wp_posts and selective table exclusion will not help.

Which hosts have this problem (all of them)

This is not a WP Engine-specific issue. Every managed WordPress host with a staging feature has the same underlying problem because WordPress databases are not designed for partial merging. Delicious Brains, makers of WP Migrate DB Pro, retired their Mergebot product after concluding that automatic database merging between WordPress environments is not reliably achievable.

What differs between hosts is the mitigation tooling:

Pressable is the most restrictive: no selective table push, and they explicitly warn against using staging with WooCommerce. Flywheel (owned by WP Engine since 2019) offers only a binary checkbox for database inclusion with no table selection. WP Engine's own platform has better staging tools than its subsidiary.

The safe workflow for WooCommerce staging

WP Engine's own recommended workflow: code moves UP to production, the database moves DOWN to develop. In practice:

1. Copy production to staging (this direction is safe, fresh snapshot of live data)
2. Make your changes on staging (theme edits, plugin updates, custom code)
3. Test on staging (verify nothing breaks)
4. Push files only to production (Custom Copy > select files, deselect database)
5. If you need database changes in production, make them directly in production or use WP-CLI/migration scripts

If you absolutely must push database tables (for example, you restructured widget areas or menu items that live in the database), use Custom Copy with selective tables and exclude at minimum:

• HPOS stores: wp_wc_orders, wp_wc_order_addresses, wp_wc_order_operational_data, wp_wc_orders_meta
• User data: wp_users, wp_usermeta
• Legacy order storage (if not on HPOS): wp_posts, wp_postmeta (but this also excludes all content)
• WooCommerce sessions: wp_woocommerce_sessions

The WP STAGING Pro plugin ($89-239/year as of 2026) offers a "Skip WooCommerce Orders and Products" feature that automates this exclusion. InstaWP's 2-Way Sync takes a different approach with event-based change tracking, though it only captures changes made through the WordPress admin interface.

The bottom line: if your store processes even a handful of orders per week, treat the database push button as a "delete orders" button and plan accordingly.

FAQ