Can BackupWall move accounts between servers and between panels?
Yes. BackupWall migrates a hosting account from one server to another, including between cPanel, DirectAdmin and Plesk in any direction. Both servers run BackupWall. It creates the account on the target, moves files, databases and email, then lets you re-sync and cut over.
What migration does
A migration takes an account's newest completed backup on the source server and applies it on the target server, creating the account there. Files, databases and email are always moved. You can also carry DNS, SSL, FTP and cron settings, choose a cutover plan, and re-sync as often as you like before you switch over. A Recurring clone keeps a completed push in sync on a schedule.
Migration is per account (or a reseller with all its accounts), admin-only, and always starts from an existing backup point.
Supported directions
All six directions between cPanel, DirectAdmin and Plesk passed an initial run and a re-sync on accounts from small to about 1 GB. A 7 GB account was tested between cPanel and DirectAdmin in both directions (about 12 minutes forward and 8.7 minutes in reverse). The final sync with cutover ran end to end in three directions only. DNS served from other name servers was unit-tested only.
What you need
- BackupWall installed on both servers, and the target's panel working. Both servers must run the same release; nothing checks it.
- Port 8087 on the target reachable from the source.
- A completed backup of the account on the source. The first run uses the newest completed point and does not take a new backup, so an old point means old data until you Re-sync.
- Once licence enforcement is on, both servers licensed (Licensed or Grace): the source refuses to start or continue a migration, and the target refuses the transfer, when unlicensed.
Transfer modes
Under Settings in the wizard, Transfer is either:
- Direct push (peer link), the default. Use it for accounts whose backups are encrypted: it opens them on the source and re-keys them for the target.
- Seed from backup destination. It works for unencrypted backups only, and it refuses local destinations. Seeding hands the target access to the source destination.
The process in short
- Link the two servers with a peer token.
- Run the Migration → New migration wizard.
- Watch the run until it shows COMPLETED, and use Re-sync to pull changes.
- Finalize… and Run final sync to switch over. See Cutover and DNS.
Limits
Mail that arrives while DNS is moving, dedicated IPs, DKIM private keys and some package limits are not carried. See Migration limits.