How to check migrated websites before switching DNS
Before you point the domains here, you can check that each website answers the same on the new server as on the old one. Visitors are not affected: they still use the old server.
Steps
- Open the account's migration page: Transfer Tool → the server → Details, or Import a Backup → Open.
- In the Cutover card, under Verify websites, click Compare old and new server.
- Reload the page after a few seconds. The line Checked … · old … → new … shows when and which addresses were compared.
- Read the table: Website, Old server, This server and Result.
What the result means
For each domain, the page is requested from the old server's IP and from this server's IP, with the domain's name. The HTTP status code and the page title are compared.
| Result | Meaning |
|---|---|
| match | Same status code and same page title on both servers |
| differs | The status or the title is different, or one server did not answer. Look at both columns |
A server that does not answer shows the reason instead of a status, for example no response. When the old server's IP is not known from the archive, the old column says old IP unknown.
When a website differs
- 403 Forbidden on this server: check the folder permissions of the site in the File Manager.
- 500 or a database error: check the database name, user and password in the site's configuration file; see the Import report for the files that were updated.
- A different title: often a site that redirects or shows a cached page. Open both versions to compare.
- No answer here: check that the account's import finished (done) and that the web server runs.
Fix the cause and click Compare old and new server again.
Good to know
- The check requests the page over HTTP and does not follow redirects, so a redirect to HTTPS shows as status 301 or 302 on both servers.
- You can run the check as often as you like, for example after the final sync.
Common questions
Can I open the migrated site in my browser before the DNS switch?
Point the domain to the new server's IP in your computer's hosts file, then open it. Remove the line afterwards.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to run the final sync before switching DNS
Copy only what changed on the old server since the transfer — new files, new email and fresh databases — just before you point the domains here.
- How to switch DNS after a migration (nameservers or A records)
Point migrated domains to the new server by changing the nameservers or the A records, and check which domains still reach the old server.
- After a migration: checklist for passwords, SSL, email and PHP
What to check after moving accounts: new passwords to send, warnings, SSL certificates, email records and routing, PHP versions, packages and resellers.
- Transfer failed or stuck: how to fix a failed migration
Fix common Transfer Tool and backup import errors: SSH connection or authentication failed, not enough disk space, unrecognized backup, stuck tasks.