Backups & migration · Practical guide

How to plan a website migration with less downtime

A practical checklist for moving your files, databases and email without rushing the DNS switch.

Quick answer

A practical checklist for moving your files, databases and email without rushing the DNS switch.

Start with the checks below. Each step explains what to look for and what to try next.

Prepare a migration checklist

List the source website files, databases, email providers, DNS records, SSL certificates, cron jobs, PHP requirements and integrations. Take an independent backup before doing anything.

Move and test before switching DNS

  1. Prepare the destination hosting account and compatible PHP/database environment.
  2. Transfer files securely and import the database.
  3. Update the application’s database credentials and paths where needed.
  4. Test the site on a temporary or hosts-file-based preview method where appropriate.
  5. Check forms, login, images, redirects, HTTPS and transaction flows.
  6. Lower DNS TTL ahead of a planned cutover when possible, then update the authoritative DNS records.
  7. Keep the old service available while DNS resolves and tests complete.

Be careful with email

Changing nameservers can change MX, SPF, DKIM and DMARC records. Copy the correct records to the new DNS zone before the cutover if email is staying elsewhere.

After migration

Monitor errors, redirects and indexing. Test from multiple networks, maintain backups, and only retire the old hosting service after confirming everything is working.

Guidance may vary by plan, control panel version and enabled features. Review the settings available to your account before changing live services.