How Do I Migrate a WordPress Site to a New Host?
Why Testing Before DNS Switching Matters
DNS changes can take time to propagate globally and aren't instantly reversible in practice, so any problem discovered only after switching DNS becomes a live, customer-facing issue rather than something caught safely in testing. Setting up and thoroughly testing the new host first, before touching DNS at all, moves the riskiest discovery phase to a point where nothing customer-facing is affected yet.
The Migration Checklist
- Full backup first, both files and database, before touching anything.
- Set up the site on the new host using a temporary URL or a local hosts-file override to preview it with the real domain without affecting live DNS.
- Test thoroughly on the new host — page loads, forms, checkout if applicable, email sending, and any specific integrations — before considering it ready.
- Check for hardcoded URLs or absolute paths in the database that might reference the old host's specific configuration.
- Lower the DNS TTL (time to live) a day or two in advance of the actual cutover, so the eventual DNS change propagates faster when it happens.
- Switch DNS during a planned, low-traffic window, monitoring closely as it propagates.
- Keep the old host's site available and untouched for a period after cutover, as a fallback in case an issue is discovered post-migration.
Executing the Migration
- Complete every testing step on the new host before touching DNS at all.
- Lower DNS TTL in advance to speed up eventual propagation.
- Switch DNS during low traffic, monitoring the new host closely afterward.
- Retain the old host temporarily as a safety net until the new one is fully confirmed stable.
Need a WordPress migration handled carefully and completely? See WordPress bug fix.