Publish staging changes with WP Toolkit

Understand the overwrite risk

Copy Data transfers selected files and database data to the destination website. It does not automatically merge staging changes with new production orders, users or form submissions. Copying an old database can remove those records.

Confirm the feature is available, test the change and take a fresh backup of production files and its database. Plan a maintenance window when needed. Coordinate store database transfers with the website maintainer.

Select source, target and content

1. Open the staging site card in WP Toolkit and select Copy Data.
2. Choose the correct production site under Target. Check both addresses.
3. Limit the transfer to required files or database tables. A theme file change may not need a database copy, while page-builder settings may live in the database.
4. Review overwrite and deletion options. Do not enable deletion of missing files without understanding what it removes from production.
5. Enable creation of a restore point if offered. This complements a separate backup.
6. Start copying only after the review and wait for completion.

Verify publication

Clear caches and test pages, sign-in, forms and checkout. Check recent orders and content, and confirm production payment credentials and email settings are correct. Remove test-only access protection and maintenance mode from production as appropriate.

If the result is unexpected, pause new changes and assess recovery before copying again. Restoration can also overwrite data created since publication, so preserve that data first.