Website Backups Before Migration
Create a recoverable archive of code, database, media and configuration before changing or deleting a legacy website.
Back up more than the database
A complete legacy archive may need web files, database dump, uploaded media, server configuration, environment variables, scheduled tasks and documentation of external integrations.
Verify the backup can be opened
A backup file existing is not proof of recoverability. Check archive integrity, confirm the database dump contains expected tables and test extraction before dismantling the old environment.
Store a copy away from the server
If the hosting account is lost or compromised, a backup stored only inside that account is not much protection. Keep at least one secured copy elsewhere.
Label the archive clearly
Include domain, date, platform version and migration stage in filenames or accompanying notes. Years later, this prevents confusion between pre-cleanup, compromised and final production copies.
Protect sensitive data
Database archives can contain personal data, credentials or tokens. Store and dispose of them according to their sensitivity rather than treating them like ordinary downloadable assets.
Separate operational backup from historical archive
An operational backup is designed for rapid rollback; a historical archive is designed to preserve the old site for future reference. They may contain the same data but should be labelled differently. The rollback copy should be easy to restore quickly, while the historical copy can include notes, screenshots and exported inventories that help future maintainers understand the old system.
Test a sample restore
For important sites, test more than whether the ZIP opens. Restore a sample database into a non-production environment or at minimum inspect tables, page records and media paths. A backup created by a failing plugin or exhausted hosting account can exist as a file while still being incomplete.