How to verify a migration before you change DNS

How-to Migration verificationdns cutovermigrationchecks

Run the read-only verification to check that every site responds, every database has its tables and mail is present, before pointing DNS at the new server.

Verification is read-only on both sides and does not contact the old server again: it compares against the inventory you already took.

Steps

1. Run it from Migration, Verify or on the command line:

   panel migra-verificar -host old.example.com -panel cwp -cuenta acme -destino acme

2. Read the three outcomes for each item: OK, missing, or could not be verified (for example a timeout). A network problem is never reported as "missing" or "fine".
3. Check sites: each one is requested on the new node with the right Host header, because DNS still points to the old server.
4. Check databases: they must exist and have the same number of tables. A half-loaded dump has the right name but too few tables.
5. Check mailboxes and aliases. Extra items that exist here and not there are listed too.
6. Use Migration, Discover to see where each domain's DNS really lives (name servers, MX, SPF/DMARC and registrar) and decide whether to move the zone here or only change records elsewhere.
7. Fix what is missing, repeat, and only then change DNS.

After the cutover

Reissue certificates from each site's certificate page, or wait for the scheduler; the domain has to point at the new node first.

Last updated: 2026-10-10