Migration backup

Back up your website before migration

Yes. Even when UKC copies the source directly, keep a current independent backup that you can restore without relying on either hosting account.

Independent copyStore it away from the source and destination.

Include the databaseFiles alone are not enough for most applications.

Verify the archiveA backup is useful only if it opens and restores.

Backup scope

Capture everything needed to rebuild the service

  • Website files, uploads and hidden configuration files.
  • All application databases and a note of database names/users.
  • PHP version, scheduled tasks, redirects and custom server settings.
  • Current DNS records and nameservers.
  • Mail data separately when email is part of the move.

Verification

Check the backup before the migration window

Confirm the archive size is plausible, open it, verify the database dump is readable and keep at least one copy on a local or independent storage service. Record the backup date and application version.

Retention

Keep it until the new service is proven

Retain the backup and source hosting until the website, administration, forms, email and integrations have worked on the new service long enough to be confident.

Was this answer helpful?

« Back