Switching hosts terrifies WordPress owners—and rightly so. DNS, serialized data, and mixed URLs turn simple moves into broken-image nightmares. A staged migration plan keeps downtime near zero and protects AdSense review status on established blogs.
Before you start
- Full backup: files plus database
- Document current PHP version, SSL cert, and cron jobs
- Lower DNS TTL to 300 seconds twenty-four hours before cutover
- Migrate to staging subdomain on new host first when possible
Migration plugin path
Duplicator, All-in-One WP Migration, and WP Migrate simplify exports. Install on old site, create package, import on new host, run installer script. Search-replace URLs during import—critical for serialized widgets and page builders.
Manual migration outline
- Export database via phpMyAdmin or WP-CLI
- Download wp-content and wp-config.php (redact secrets when sharing)
- Create database on new host, import SQL
- Upload files, update wp-config.php credentials
- Run search-replace for old domain to new
- Flush permalinks: Settings → Permalinks → Save
SSL and mixed content
Install SSL on new host before DNS flip. Run Better Search Replace for http:// remnants. Check browser console for mixed content on homepage and single posts.
DNS cutover
Point A record or nameservers to new host when staging tests pass. Keep old host alive forty-eight hours in case rollback needed. Monitor uptime and Search Console crawl errors for a week.
Post-migration checklist
- Test contact forms and SMTP
- Regenerate critical CSS in caching plugins
- Reconnect CDN and security plugin API keys
- Submit updated sitemap in Search Console
AdSense during migration
Avoid leaving site on "under construction" pages during review. Use maintenance mode with 503 only briefly. Policy URLs must resolve on new host immediately after DNS propagates.