Verify Migration and Switch DNS
Check restored websites, databases, email, DNS and ownership, coordinate final writes and complete a controlled migration cutover.
Verify each account before directing users to the destination. Keep a record of expected results, warnings and unresolved items; a terminal progress state is only one part of acceptance.
Service checks
| Area | What to verify |
|---|---|
| Transfer or conversion | Correct account, completed components, errors, warnings and intentional skips. |
| Identity and ownership | Username, domains, aliases, reseller, package and resource limits. |
| Files | Expected content, permissions, ownership, document roots and writable application directories. |
| Websites | Test through the destination using the real hostname, including login, uploads, redirects, application writes and background jobs. |
| Databases | Expected databases, users, grants, data and application connectivity. Check every required engine. |
| Runtimes | Required PHP or other runtime versions, extensions, environment settings and service configuration. |
| Mailboxes, messages, passwords/access, aliases, forwarders and inbound/outbound delivery. Check the actual supported mailbox conversion. | |
| DNS | Authoritative zone, A/AAAA, MX, TXT, aliases, delegated records and external DNS changes. |
| TLS | Certificate identity, chain, renewal path and HTTPS behavior. A scheduled request is not an issued certificate. |
| Automation | Scheduled jobs, queue workers, webhooks and external integrations. Prevent duplicate execution on both servers. |
Source-specific omissions may need manual work. Review the provider guide and conversion logs instead of assuming all configuration has an equivalent on the destination.
Coordinate the final copy
Confirm how you will stop or reconcile source writes. The earlier transfer may contain files, databases and mail captured at different times. Use an application-appropriate maintenance window or planned final synchronization, then repeat critical checks.
Avoid letting both servers accept independent application writes. Record the point at which the destination becomes authoritative and ensure scheduled jobs run on the intended server.
Change authoritative routing
Update records at the actual authoritative DNS provider. Review both IPv4 and IPv6 routes, mail routing and sender-authentication records. A WAP option that repoints source DNS does not automatically change an external provider's zone or registrar delegation.
Allow for previously cached TTLs. Check authoritative answers and representative client resolution, then test web and email traffic again. Monitor late mail and application errors during the transition.
Recovery and acceptance
If acceptance fails, use the agreed recovery plan. Stopping a transfer or returning DNS to the source does not undo destination writes. Preserve both sides and reconcile new data before choosing an authoritative copy.
Retain source backups, converted archives and relevant logs for the agreed period. Remove the old server only after account owners have accepted the migrated services and recovery requirements have been met.