Migrating from a cPanel host with a WHM transfer

The fastest way to move your accounts to ASEOHosting is a WHM-to-WHM transfer: instead of copying files by hand, WHM connects to your old server, packages each cPanel account into a full backup, and restores it here with the same files, databases, email, and DNS zones intact. You keep the same document structure and cPanel settings, and the only real change is the destination server and the dedicated IP each site gets on arrival.

What a WHM transfer actually moves

A cPanel account backup is a self-contained archive. When WHM restores it, it brings across the public_html files, all MySQL or MariaDB databases and their users, email accounts and messages, cron jobs, subdomains and addon domains, FTP accounts, and the DNS zone. Because the whole account is packaged as a unit, you avoid the classic mistakes of manual migration: missing a database user, forgetting a cron job, or leaving mail behind. SSL certificates stored in cPanel are included too, though you may reissue them after the IP changes. For a WordPress site this means no export/import dance and no plugin can corrupt the move; see our WordPress migration notes if you run many WordPress installs.

Before you start: three preconditions

• Your current host runs cPanel/WHM. If it does, a direct transfer is possible. If it uses Plesk, DirectAdmin, or a custom panel, we handle it differently, so reach out through our contact page.
• You have either WHM root access on the old server or a valid cPanel username and password for each account. Transfers can run per account without root, or in bulk with root.
• You know your registrar login. The move itself does not touch your domain registration, but you will repoint DNS at the end.

Step-by-step procedure

1. Open WHM here and go to Transfers > Transfer Tool.
2. Enter the source server hostname or IP and the SSH port (default 22), then authenticate with root or with the individual cPanel credentials.
3. Let WHM enumerate the accounts, then select the ones you want and choose to bring over full backups including home directory, databases, and email.
4. Start the transfer and watch the live log. WHM packages each account on the source and restores it here automatically.
5. When it finishes, test each site by editing your local hosts file to point the domain at the new dedicated IP, so you can confirm it loads before any public DNS change.
6. Reissue SSL if needed, then update your DNS. Change the A record to the new IP, or update nameservers at your registrar, and lower TTL to 300 a day beforehand for a quick cutover.

The dedicated IP and your footprint

On arrival each site lands on its own dedicated Class C IP. Be clear about what that does: a dedicated IP is a defensive, footprint-control measure, not a ranking boost. It keeps you off addresses shared with spammy neighbors and gives clean separation between sites you own, which is useful for footprint diversity. Rankings still come from content quality and genuine value, and Google's own guidance on traffic changes attributes almost all movement to content and search factors, not hosting.

After cutover

Keep the old account live for at least 48 to 72 hours so trailing DNS caches and mail resolve to the new server before you cancel anything. Verify email delivery, forms, and any hardcoded absolute URLs in your database. Once everything checks out on the new IP, you can decommission the old account. If a site relies on a specific IP range or you are consolidating a network, multiple A-class IP hosting and our migration FAQ cover the details.