What is copied in a migration, and what is not
The Transfer Tool and Import a Backup copy the same things. You choose them under What to transfer or What to import: Website files, Email accounts & mail, MySQL databases, DNS zones and Cron jobs.
What is copied
- Domains: the main domain, addon domains, subdomains and aliases (parked domains), with their document roots.
- Website files of the account's home folder.
- Email: mailboxes with their mail and quota, and forwarders.
- MySQL databases with their users and privileges.
- DNS zones. SOA and NS records are replaced by this server's own; A records that point to the old IP are pointed here when you choose so.
- Cron jobs. Paths to the old home folder are changed to
/home/<username>/. - From cPanel only: FTP accounts with their passwords, and each domain's DKIM key.
Passwords
Passwords are kept where the format allows: the account, the mailboxes and the database users sign in with their current passwords. Anything that cannot be carried over gets a new password, shown on the account's migration page under New passwords — only once, so copy them at once and send them to the customer.
Typical cases with new passwords: DirectAdmin account passwords (not in its backups), mailboxes with old password formats, and some database users.
Safety rules during a move
- Accounts suspended on the old server stay suspended here.
- Cron jobs that look like malware (mining tools, code downloaded and run at once, programs run from temporary or hidden folders) are not imported. Such lines are also removed from shell startup files. Each one is listed in the warnings.
- An account larger than its package is still imported. The disk quota is lifted during the import and put back afterwards, with a warning to choose a bigger package.
- Configuration files (
wp-config.php,.env,configuration.phpand others) are updated when database names or the home path change. - Downloaded archives of the Transfer Tool are deleted once the account is imported.
What is not copied
Only the items above are copied. For example, these are not:
- SSL certificates. New free certificates are issued automatically once the domains point here.
- PostgreSQL databases.
- Email autoresponders, email filters and mailing lists.
- PHP version and PHP settings of the account. Choose them again on the new server.
- Bandwidth statistics of the old server.
- Reseller ownership. Imported accounts belong to the administrator; give them to a reseller afterwards.
- Forwarders to pipes or programs, and
:fail:forwarders. - DNS records of unsupported types or outside the zone (listed in the warnings).
Common questions
Will my customers have to change their email passwords?
Usually not. Mailbox passwords are kept when the old server stored them in a modern format. Mailboxes that need a new password are listed under New passwords.
Is the old server changed?
No. The websites keep running there until you switch DNS.
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
- 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.
- How to move hosting accounts from cPanel, Plesk or DirectAdmin
Compare the two ways to migrate accounts to this server — the Transfer Tool over SSH and importing a backup file — and choose the right one.
- How to migrate from cPanel/WHM: accounts, email and databases
Move cPanel accounts with the Transfer Tool or a cpmove backup file: websites, mailboxes with passwords, databases, DNS, cron jobs, FTP and DKIM keys.
- 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.