Use staging for risky changes
- WordPress core, plugin or theme updates that change major versions.
- WooCommerce checkout, payment or shipping changes.
- PHP-version changes and dependency upgrades.
- Layout work that affects templates across the site.
- Database migrations or large content imports.
Create the staging copy
- Create a current backup of the production site.
- Open the website in Enhance and choose the staging or clone action available for the installation.
- Choose a clear staging name and wait for files and the database to finish copying.
- Confirm the staging site discourages search-engine indexing and is not connected to production payment or email services.
- Sign in to staging and verify that media, links and administration work before making changes.
Test before going live
- Test forms without sending messages to real customers.
- Use payment sandbox mode when available.
- Check scheduled tasks, caching and outgoing webhooks.
- Compare the production content date before replacing a database, especially on stores or membership sites.
Important
A staging database can become outdated while customers continue using production. Do not overwrite live orders, users or form entries with an older staging database.
Official references
Platforms and tools change over time. Use these official references for the current product documentation.