How to push changes between your WordPress staging and live site

A staging site lets you test themes, plugins, and layout changes safely, but moving those changes to a live WordPress install can be nerve racking. If you need to push staging site without overwriting the database, this guide walks through practical, low-risk way to transfer code, media, and configuration without destroying live content like posts, users, or WooCommerce orders. You will get a preflight checklist, step by step instructions, FAQs and a recommended toolchain featuring UpdraftPlus for backups, cloning, and selective restores.

• Standard staging pushes often overwrite the live database, which can erase real-time data like new customer orders, user comments, or membership registrations.
• The safest way to update a live site is to push files only (themes, plugins, and uploads) or to use table-level selection for specific database changes.
• Always perform a manual backup of your live site via UpdraftPlus before any push to ensure a one-click rollback path in case of conflicts.
• Staging should be a “near-identical” mirror of your live site to ensure that the changes you push will behave predictably in the production environment.

The live database contains dynamic content, user accounts, and transactional records. Overwriting it removes any changes made on production since the staging snapshot, such as new posts, comments, or orders. Most teams therefore separate file changes from database changes and selectively deploy only what is needed.

For many use cases, pushing files only is the fastest and safest route. If you absolutely must change content stored in the DB, identify exactly which tables need updates and apply them carefully. Note that true automated database merging is not a solved problem and most migration tools cannot merge two active databases automatically. Plan accordingly.

• Take a full backup of the live site, including files and database
• Take a backup of the staging site you will push from
• Put the live site in maintenance mode if needed
• Confirm staging uses a separate database from production
• Note any time-sensitive content (orders, form submissions) that may arrive during deployment
• Test the push workflow on an UpdraftClone where possible

Best for site owners who prefer GUI workflows and safe rollback.

UpdraftPlus makes backups and lets you restore specific components (plugins, themes, uploads, database) rather than everything. Use the restore wizard to pick what to apply.

1. Go to the live site and create a full backup (including the files and the database)
2. Go to the staging site and create a backup where the database is excluded
3. On production, upload or locate the staging backup in Existing Backups
4. Choose Restore and select only the components you want to overwrite, for example, themes and plugins
5. Run the restore and test

This approach gives a controlled way to push code and media without touching the live database.

Scenario: You updated a theme and one custom plugin on staging; you want those changes live without touching posts or orders.

1. Backup production (files + DB) with UpdraftPlus.

2. Backup staging with Database unchecked (files-only; Themes + Plugins).

3. Optional: Create an UpdraftClone of production and upload the staging backup to the clone.

4. Optional: In the clone, Restore → Themes + Plugins only, DB unchecked → test.

5. On production, upload the same staging backup (if it’s not already listed).

6. Restore → Themes + Plugins only, DB unchecked → flush caches → smoke test key flows.

This ensures the code updates are live while the production database remains intact.

With UpdraftPlus Premium, you get finer control:

• Select specific database tables (like wp-options) to restore alongside the files.
• Include/exclude particular plugins, so you could restore just the single custom plugin instead of all plugins.

Always treat the database like sacred ground. For layout and code changes, push files only. When a database change is unavoidable, export and import only the necessary tables and validate on a clone first.

Pushing changes from staging to live doesn’t have to mean risking your database. By using UpdraftPlus Premium’s selective restore and free clone tokens, you can move code and files with confidence while keeping live content untouched. Always test on a clone first, then push only what’s needed.