After a migration: checklist for passwords, SSL, email and PHP
When an account shows done, go through this list. Most points take a minute and prevent support tickets.
On the account's migration page
- New passwords — passwords that could not be carried over (for example the account password from DirectAdmin, or old mailbox formats). They are shown only once: copy them and send them to the customer. If they were not copied, set new passwords from the account page.
- Warnings — read each one: skipped cron jobs that looked like malware, skipped forwarders or DNS records, an account larger than its package, renamed database users.
- Import report — Mailboxes copied and Config files updated (for example
wp-config.phpafter a rename).
On the account and the server
- Websites load: use Verify websites before the DNS switch, then open the sites after it.
- SSL certificates are issued automatically once the domains point here. Check the customer's SSL/TLS page, or Server Settings → Certificates for the server-wide count.
- Email: send and receive a test message. Check the SPF, DKIM and DMARC records on the customer's Email page.
- Email routing: if a domain's email stays with another provider, set its routing to Remote mail server (or Automatic).
- PHP version: the old PHP version is not copied. Choose the version each site needs, per account, per domain or in the package.
- Packages: if a warning says the account is larger than its package, give it a bigger package; until then uploads and new email are refused.
- Resellers: imported accounts belong to the administrator. Use Owner → Change owner on the account page to give an account to a reseller.
- Suspended accounts: accounts suspended on the old server stay suspended here. Unsuspend them when appropriate.
- WordPress sites are found automatically every day. Click Scan all accounts now on WordPress Sites to see them at once.
Clean up
- In the Transfer Tool, click Delete password on the server's page after the last final sync, or remove this server's key from
/root/.ssh/authorized_keyson the old server. - In Import a Backup, Remove uploaded migrations you no longer need, to delete their archives.
- Keep the old server for a few days, until DNS has spread everywhere. Then cancel it.
Common questions
A site shows "403 Forbidden" after the move.
Folders the web server could not enter are opened automatically after a transfer. If you still see it, check the folder permissions in the File Manager.
A site cannot connect to its database.
Check the database name, user and password in the site's configuration file. If the account was renamed, the database prefix changed; the updated files are listed in the Import report.
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
- What is copied in a migration, and what is not
The full list of what a transfer or backup import copies — websites, email, databases, DNS, cron, passwords — and what you must set up again.
- 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.
- How to check migrated websites before switching DNS
Compare every migrated website on the old and the new server with one click, before visitors are sent to the new server.
- 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.