Move from cPanel to AIO Panel
The importer connects to your cPanel/WHM server, packages each account and brings websites, databases, mail, DNS and SSL across. Here is the whole process, including what we learned moving real customers.
What moves
Websites
Document roots, addon domains, subdomains, aliases, redirects, .htaccess (served through the per-site Apache mode), PHP version per site.
Databases
MySQL/MariaDB and PostgreSQL databases, users and grants; WordPress and other apps keep their credentials.
Mailboxes with their mail, forwarders, autoresponders, the default address (catch-all), DKIM keys.
DNS
Every zone with its records, re-pointed to the new server; SPF, DKIM and DMARC kept or added.
SSL
Existing certificates are imported, then renewed by Let’s Encrypt once DNS points at the new server.
Cron, FTP, SSH keys
Cron jobs per account, FTP accounts, SSH keys and the account’s package limits.
The six steps
- Step 1
Install AIO Panel on a fresh server
Ubuntu or Debian, one command, 10 to 20 minutes. Keep the old server running.
- Step 2
Connect the old server
Migration → Remote: enter the cPanel/WHM host and SSH access. The panel lists the accounts, packages each one with pkgacct and shows what it found.
- Step 3
Import the accounts
Pick accounts, choose packages, start. Each account is imported with files, databases, mail, DNS and SSL; progress and warnings are shown per account.
- Step 4
Check every site before switching DNS
Open each site through the preview URL, log in to mail, run a cron job. Fix what the import flagged. Nothing is live yet.
- Step 5
Move the nameservers
Point the domains at the new server’s nameservers (or change the A and MX records). The old server keeps serving until the change propagates.
- Step 6
After the switch
Issue production certificates, update the SMTP host in apps that send mail, release the old server’s mail queue, and stop the old server’s cron and services before decommissioning it.
The same import from the command line:
sudo aio migrate:remote --host old.example.com --user root --accounts allWhat to watch out for
Every one of these happened in a real migration. The importer warns about most of them; this list is here so none surprises you.
Apps keep the old SMTP host
Laravel .env files, WordPress mail plugins and similar point at the old hostname. Change them to the new server (or a relay) or mail silently stops once the old server is off.
Staging certificates during a DNS mix-up
If a certificate was issued while DNS still pointed elsewhere it may be a Let’s Encrypt staging certificate that browsers reject. Re-issue it once DNS is right.
Reverse DNS is the provider’s
Set the PTR record of the new IP to the server hostname at your provider, or big mailbox providers will defer your mail.
Accounts deleted on the old server
An import that fails with "Unable to get user id" means the account no longer exists on the source; skip it.
Folders that shadow pages
An empty folder in a document root with the same name as a page (for example /shop) returns 403 instead of the page. Remove it.
Duplicate SPF records
Two SPF TXT records on one name make SPF fail. Keep exactly one.
Ready to move?
Install AIO Panel on a fresh server and run the importer; the old server keeps serving until you switch the nameservers.
Also from: Plesk · DirectAdmin · HestiaCP · CyberPanel · aaPanel