Migrate Reseller Accounts in WHM

What moving reseller accounts involves

Migrating reseller accounts in WHM means moving each client account with its package, ownership, DNS zone, mail and SSL to a new server, then pointing the domains there. The reseller account itself must exist on the destination first. Whether you can use the WHM Transfer Tool depends on one thing: root access on the destination server.

• Accounts — the reseller login plus every cPanel account it owns, with home directories and databases.
• Packages and feature lists — the quotas clients were sold, which must exist before the accounts arrive.
• Ownership — the link between account and reseller, stored in the panel, not in the website files.
• DNS, mail and SSL — zones, mailboxes and certificates, which move separately from the files.

Check these five things before the first transfer

An inventory taken now saves a support ticket later. Log in to the source WHM and record each item, because the destination has to be built to match it.

Create packages and the reseller account first

Build the destination before copying anything. In WHM, open Packages, then Add a Package, and recreate every package the clients are on with the same name and limits. Then create the reseller account under Resellers, then Reseller Center, with the same username where possible.

If the package names do not exist, the transfer still completes but every account lands on a default package, and clients silently lose disk, bandwidth or addon domain limits. Matching names first avoids that entirely.

Transfer Tool: the exact WHM clicks with root access

The Transfer Tool is a root feature. On the destination server, log in to WHM as root at https://SERVER-IP:2087 and follow this order.

1. Open Transfers, then Transfer Tool.
2. Enter the source server IP as Remote Server Address and its SSH port, usually 22. Choose root password, SSH key or API token for authentication.
3. In Security, clear Restricted Restore, which limits what a restore may overwrite.
4. Click Scan Remote Server and accept the Live Transfer notice.
5. Open the Packages tab and select every package prefixed with the reseller username, so limits map correctly.
6. Return to the Accounts tab, sort by the Reseller column, tick the reseller account and every account it owns.
7. For the reseller account itself, open the arrow in the Domain column, tick Reseller Privileges under What to Transfer, then click Apply. This box is off by default.
8. Click Copy and watch the queue until every account reports complete.

You know it worked when WHM, List Accounts shows each account with the reseller as owner, and the reseller can log in to WHM and see its own account list.

No root? Move accounts with full backups and restorepkg

A reseller-level WHM usually has no Transfer menu, because the feature needs root. Two routes remain, and both work account by account.

1. In each client's cPanel, open Files, then Backup, then Download a Full Account Backup. Save the archive somewhere you control.
2. Ask the destination provider to restore each archive, or upload it and restore it yourself from WHM, Backup, Restore a Full Backup if you have root there.
3. If you have SSH on the destination only, copy the archive into /home and run /usr/local/cpanel/scripts/restorepkg USERNAME as root.
4. If you have SSH on both, create the archive on the source with /usr/local/cpanel/scripts/pkgacct USERNAME /home, then fetch the cpmove file and restore it.
5. After each restore, set the owner in WHM, Reseller Center, Change Ownership so the reseller can manage it.

This route copies databases, mail and DNS zones inside the archive. It does not copy the reseller ACL, so compare the permissions list by hand.

Verify ownership, DNS and mail before you cancel anything

Run the checks in this order and keep the old server running throughout.

1. Confirm ownership from the shell: whmapi1 listaccts searchtype=owner search=RESELLERUSER must list every account you moved.
2. Test each site against the new IP before DNS moves, using a hosts file entry or curl --resolve domain.in:443:NEWIP https://domain.in/.
3. Send and receive one mail from each domain, then check the MX records still point where you expect.
4. Confirm AutoSSL issued a certificate on the new server, or reinstall the paid certificate on any dedicated IP account.
5. Check cron jobs and the reseller's own WHM login, then lower TTL and switch DNS per domain.

Roll back and handle mail delivered to both servers

Keep the source server and its DNS zones for at least seven days after cutover. Rollback is a DNS change back to the old IP, plus restoring the TTL you lowered.

Mail is the part people forget. Messages delivered to the new server after cutover are not on the old one, so before reverting, sync the mail directories back with rsync, or use the Transfer Tool's MailSync stage in the other direction. Reconcile any mailbox created after cutover by hand.

The failure that catches most resellers

Accounts arrive owned by root, so the reseller cannot see or manage them. The cause is the Reseller Privileges box, which is off by default. Fix it in WHM, Resellers, Reseller Center, Change Ownership, or rerun the transfer with the box ticked.

The second failure is a missing Transfers menu. That is not a bug: the Transfer Tool requires root. Use the backup route above, or ask the destination provider to run the transfer on your behalf.

Reseller hosting and migration on WebJi®

WebJi® reseller plans start at ₹4,000 per year before 18% GST for the LR-START tier, with LR-Pro at ₹7,000 and LR-Dev at ₹12,500 for a larger portfolio. Each plan includes WHM, cPanel accounts and the packages you resell.

Migration is free subject to terms and approval: send the account list, package names and total disk usage to support@webji.services and the desk checks capacity before the move. Support is 24/7 by email in Hindi and English with an average first reply under 60 minutes. The plans sit on reseller hosting and cPanel reseller hosting; a one-off move without hosting is on the website migration service page, and sizing questions go to the contact page.