Backups & storage
Restore a WordPress site from backup without losing newer data
Match your archive to the right restore method, preserve the current state, and check the recovered site before reopening.
To restore a WordPress site from backup, identify the backup format and recovery date, preserve the current state, and use a compatible restore method. Whenever possible, first restore into an isolated copy. Replacing the live database immediately can erase orders, enquiries, and edits created since the backup.
The right procedure depends on what you have: a host snapshot, a plugin archive, a full hosting-account archive, or separate files and SQL. These formats are not interchangeable.
Match the archive to the restore tool
| Backup available | Likely recovery route |
|---|---|
| Host-managed recovery point | The host’s interface or support team; confirm whether files and database can be restored separately. |
| Backup plugin archive | The same product’s supported importer, with its required edition and compatible versions. |
| Full cPanel account archive | A host-assisted account restore or careful extraction of the necessary site components. |
| Files and SQL export | A manual restoration with database access and correct configuration. |
For full account archives, cPanel distinguishes WHM restoration from the ordinary user interface. Ask the destination provider whether it accepts your format and what account-level items it restores. Do not assume that website recovery also recreates mailboxes or DNS.
Preserve what exists now
Record the failure time, last known working state, and changes made around the incident. Save the current files, database, and relevant logs before overwriting anything. Even a broken site may hold newer customer records you need to reconcile.
Choose a recovery point based on evidence. For a failed update, that may be the copy immediately before the update. For suspected compromise, the most recent backup may already be infected. Preserve incident evidence and get qualified cleanup help when you cannot establish a trustworthy state.
For a transactional site, agree on a write freeze and how to preserve orders made after the selected backup. Importing an older database is not a safe way to merge two timelines of purchases.
Restore an isolated copy first
Create a private destination with suitable PHP, database, and extension support. Prevent it from sending customer messages, taking payments, running live webhooks, or being indexed. A search-engine visibility checkbox alone does not make a copy private.
Follow the backup product’s restore sequence. For a manual recovery, the WordPress handbook describes restoring files and then the database. Set the destination database connection correctly in wp-config.php; credentials from the old host may not work.
The database backup documentation explains the separate database component. Confirm the target database before importing. Avoid broad search-and-replace edits in SQL: WordPress data can contain serialized values that require a compatible migration tool.
Accept the recovery at the application level
Open the home page, an older article, a recent media upload, and a nested URL directly. Log in using the restored account credentials. Review plugins, scheduled jobs, timezone, permalinks, and any credentials that need replacement.
Then check the workflow that matters to the business: a form reaching its intended destination, member access, booking availability, or checkout in an appropriate sandbox. Compare important record counts and dates against the chosen backup. A familiar-looking home page proves very little about the database behind it.
Return to service with a rollback point
Schedule the live switch, reconcile newer data, and take a recovery copy before making the restored site authoritative. Re-enable integrations deliberately so queued jobs do not create duplicate notifications or transactions. Clear relevant caches once the correct content is in place.
Monitor errors and the business workflow after reopening. Keep the previous state and the restoration archive until the result is accepted. If the restore required unexpected paid assistance or missing files, update your backup plan while the details are fresh.