Migrating your hosting to HostingSwift
Move a website, mail and DNS from another host with minimal downtime and no data loss.
A migration is risk management. Move deliberately, keep a way back, and cut over when everything works.
The shape of a migration
Inventory what you have.
Stand up the destination and copy data.
Test the destination before anyone sees it.
Lower DNS TTLs, then cut over.
Verify, keep the old host for a while, then decommission.
1. Inventory
List every piece:
Websites and their files.
Databases (and their sizes).
Email accounts and mailboxes (with all existing mail).
DNS zones and every record.
Cron jobs, scheduled tasks, SSL certificates.
Any custom software, PHP/Node versions, environment variables.
Missing an item here is the main cause of a "successful" migration that breaks something.
2. Copy the data
Files — SFTP, rsync, or a panel migration tool. For a CMS, use its own export where available.
Databases — dump and restore, versions matched. See Database backups.
Mail — export mailboxes from the old host in mbox/Maildir and import into the new. MX changes only affect new mail; existing messages must be moved explicitly.
DNS — export the zone from the old provider as your checklist.
3. Test before you cut over
Serve the new site on a temporary hostname or via a local
hostsfile entry.Test logins, forms, checkout, and any path with real data.
Check file permissions and that uploads work.
Confirm TLS works on the new host.
For WordPress specifically, see Migrating WordPress.
4. Lower TTLs, then cut over
A day ahead, drop the TTL on records you will change to 300 seconds. Then switch:
DNS only (if your nameservers stay elsewhere) — update A/CNAME records.
Nameservers (our managed DNS) — recreate every record first, then change NS.
See Pointing your domain and Nameservers explained.
5. Verify
Load the site over HTTPS from an external network.
Send and receive a test email.
Confirm the new host is actually serving (check response headers / server IP).
Watch the error logs on both hosts for a day.
6. Keep a way back
Do not cancel the old host until the new one has been stable for at least the old TTL (often a day or two). If something is wrong, switching DNS back is your rollback.
Related reading