Control panels
What should I back up before deleting a site in a control panel?
Short answer
Back up the site files, the database, scheduled tasks, certificate and environment settings, and any email or DNS data the panel holds. Confirm the backup restores before you delete anything.
What changes the answer
- Files and databases
- Cron jobs, environment files and certificates
- Whether deletion also removes the system user and data
Deletion can remove more than a list entry
A control panel manages sites, databases, users and certificates. Depending on the panel, deleting a site can also delete its files, its database and the system user that owns them. The panel's own documentation says what its delete action does, so read it for the version you run, and do not rely on guesswork.
What to back up
- Site files: the application code, uploads and any generated data. Archive the whole site directory.
- Databases: export each database used by the site with the database's dump tool, so the copy is consistent.
- Configuration: environment files, web-server settings, redirect rules and any custom PHP or application settings.
- Scheduled tasks: cron jobs or queue workers set up for the site.
- Certificates and keys: note how TLS is issued, and keep copies of manually installed certificates and private keys in a protected place.
- Email and DNS: if the panel also hosts mailboxes or DNS zones for the domain, export those separately.
Check the copy
A backup you have not restored is unproven. Restore it into a test location, start the application and look at a few pages and database records. Check that file permissions and ownership came through correctly.
Then delete carefully
Confirm the exact site and database you are removing, especially on a server with several sites. Keep the backup for a while after deleting, so an overlooked dependency does not become a permanent loss. If another site shares a database user or directory, do not delete it. Store backups away from the server and protect them, because they contain your secrets.
Keep it organised
Name each archive with the site, the date and the panel version, and note what it contains and how to restore it. Record where it is stored and who can access it. If you hand the work to someone else later, a short README beside the backup saves guesswork and avoids a rushed restore.