What does a migration not carry over?
Migrations do not carry dedicated IPs, DKIM private keys, PHP ini and FPM settings, cPanel team users, add-on registrations or package limits with no match on the target. Passwords cross panels only as certain hashes, and databases must be named after the account.
Not carried, or carried only in part
- Dedicated IPs (accounts land on the shared IP).
- DKIM private keys (the target signs with its own).
- PHP ini and FPM pool settings, cPanel team users, add-on registrations.
- Mail settings (forwarders, autoresponders, filters) travel where the target panel has an equivalent; the run's Report names any that did not map. Mailing lists are carried to cPanel accounts only, for the domains the target has.
- Package limits that have no match on the target are listed as "unmapped"; an unknown plan falls back to the default.
- PHP version: per domain when the target is DirectAdmin or Plesk, the primary domain only on cPanel. A domain's HTTPS redirect and its own suspension come along where the target panel has them; panel-specific web settings only to the same panel (a note names what did not).
- FTP sub-accounts are recreated only on the first run, with their source password where both panels keep it as a crypt hash (DirectAdmin and Plesk do); otherwise with a new password, listed in the report.
- Cron jobs from another panel become Plesk scheduled tasks;
@rebootand lines that are not a schedule are not, and the report names them.
Passwords
Passwords cross panels only as $1$, $5$ or $6$ crypt hashes. Debian 12 and Ubuntu 22.04+ default to yescrypt, and bcrypt hashes and locked entries are not carried either: those accounts get a random password and must reset it.
File layout across panels
Only the main web root, each mailbox folder and the account mailbox are mapped. Absolute symlinks and links that leave the web root are skipped and counted in the report. .htaccess handler blocks, php.ini and .user.ini are copied as they are.
Databases
Databases are imported only if they are named <source account>_*. Others are reported "not migrated" and the run ends partial. That is typical for free-named Plesk databases. If the target username differs, database names are renamed but application config files are not rewritten.
Resellers
An existing target reseller is never changed. Root-level WHM permissions are never granted. A Plesk reseller migrated to cPanel or DirectAdmin gets an account named <name>.reseller.test, and the console wizard has no field to change that.
Linking servers
Pairing is one way: the token is made on the target. A holder of the peer key can migrate into any existing account on the target, and the target's peer storage has no size limit. Treat peer tokens as secrets. Seed transfer refuses encrypted backups (even points of a job that has encryption off now) and local destinations; Direct push works with encrypted backups, because the source opens them and the target stores them with its own key.
Failed runs
BackupWall never deletes an account it created, so a failed run leaves the new account on the target for you to clean up.