Plan and verify a WordPress host or domain migration with controlled cutover and recovery.
A WordPress migration moves an interconnected service: database, files, URLs, DNS, TLS, mail, scheduled jobs, cache, storage, redirects, integrations, monitoring, and operational access. Build a cutover that can be verified and reversed before changing public traffic.
Inventory everything that makes the site work
Map domain and DNS control, hosting, database, uploads, custom files, configuration outside WordPress, certificates, email delivery, cron, object or CDN cache, external storage, search, payment, webhooks, analytics consent, backups, logs, and administrator access. Identify which values contain the old URL.
Prepare source and destination
- Verified full backup plus an independent export
- Compatible PHP, database, web server, limits, and extensions
- Destination secrets, permissions, storage, mail, cron, and cache
- Safe serialized-data-aware URL replacement method when needed
- Lowered DNS TTL in advance when appropriate
- Cutover owner, freeze window, rollback threshold, and communication plan
Choose the cutover pattern
| Pattern | Useful when | Main concern |
|---|---|---|
| Clone then switch DNS | Hosts change, domain stays | Data written after clone |
| Domain change | URLs and identity change | Redirects, search, mail, integrations |
| In-place move | Infrastructure changes behind routing | Hidden configuration and rollback |
Execute and verify the cutover
- Freeze or reconcile new writes.
- Copy and verify database and files.
- Apply configuration and URL changes safely.
- Test destination through controlled routing.
- Switch traffic and monitor DNS and certificates.
- Validate transactions, then retire source only after the rollback window.
Watch the edges of the migration
- Forms or orders writing to both sites
- Serialized data corrupted by naive replacement
- Mail, cron, webhook, or payment callbacks still using old endpoints
- Old site deleted before backups and DNS rollback are proven
Use a migration acceptance sheet
Check canonical URLs, redirects, assets, media, login, roles, search, forms, mail, transactions, scheduled jobs, webhooks, certificates, security headers, analytics or consent, logs, backups, and monitoring. Record the first successful real transaction and the date source cleanup becomes safe.
Continue with the next decision
Sources and further reading
Primary and contextual sources used to verify definitions or give readers a relevant next resource.
- WordPress migration handbook Official WordPress guidance for moving files and databases, URLs, configuration, permalinks, and backups.