Hosting Migration Checklist
“Migration” is where good hosts differentiate themselves and bad migrations create SEO and email disasters. Use this checklist whether you move to SupportHost, Kinsta, SiteGround, or a VPS. It is written from the same issues we raise in blind migration support tickets during testing.
1. Freeze scope
- List sites, databases, email boxes, cron jobs, and third-party DNS
- Note PHP version, WordPress version, and critical plugins
- Decide: host-assisted migration vs DIY vs agency
2. Backup before anything else
Take a full file + database backup you control (download it). Do not rely only on the old host’s panel backup. Verify you can open the archive. If email is on the same server, export or document IMAP strategy — web migrations often forget mail.
3. Build the new environment first
- Provision the new plan and confirm PHP, SSL staging, and disk headroom
- Create databases and users with strong passwords
- Deploy files and import DB on a temporary URL or hosts-file test
4. Test on a private URL
Walk critical paths: homepage, login, checkout, forms, media, admin. Fix mixed content (HTTP assets on HTTPS pages). Re-save permalinks on WordPress. Confirm cron and object cache behavior if used.
5. DNS cutover plan
Lower TTL to 300 seconds 24–48 hours before cutover if you control DNS. Schedule cutover in a low-traffic window. Update A/AAAA/CNAME and any email records (MX, SPF, DKIM, DMARC) deliberately — website and email DNS are easy to break independently.
Email warning: Moving only the website while MX still points at the old host is fine. Moving email requires a parallel plan (side-by-side IMAP sync or scheduled cut). Never assume “hosting migration” includes mail unless explicitly confirmed.
6. SSL and redirects
- Issue SSL on the new host before public DNS flip when possible
- Map HTTP→HTTPS and apex↔www with a single canonical choice
- Preserve important 301 redirects from the old site
7. Post-cutover verification (first 48 hours)
- Watch uptime and error logs
- Submit updated sitemap if URLs changed (ideally they did not)
- Keep old host paid for at least one billing cycle as rollback insurance
- Re-test forms, payments, and webhooks
8. How HostLab hosts differ on migration help
In our tickets, SupportHost and Kinsta outlined concrete assisted migration processes; SiteGround is also experienced with WordPress moves; VPS providers (RDP Monster, QuantVPS) typically expect you to migrate at the system level unless you buy a managed add-on. Match help level to your skill level.
9. When not to migrate yet
If you are mid-campaign, mid-redesign, or missing backups, stabilize first. Migrations amplify chaos; they rarely fix broken content strategy.
Need a host recommendation after you know the category? Start at the Best Web Hosting 2026 comparison and Shared vs VPS vs Managed guide.