A bulk reseller account migration moves all your clients' cPanel accounts from another provider to an MdmHost reseller or master reseller plan. Because both sides run cPanel, each account moves as one cpmove archive that keeps files, databases, email, DNS zones and settings together. The work is mostly planning and batching.
Before you start
- Reseller WHM access at the old host and an MdmHost reseller or master reseller plan with enough disk space and account slots.
- Packages created in your new WHM with the same names as the old ones (WHM → Packages → Add a Package).
- A spreadsheet of every account: domain, size, package, nameservers and contact email.
Plan the batches
- Sort accounts by size and importance. Move one small test account first.
- Group the rest into batches you can finish and check in one session, for example 10–20 small accounts.
- Lower DNS TTLs a day ahead for each batch: TTL strategy.
- Tell clients the date, the short content freeze and what changes for them (new server IP, same passwords).
Create cpmove backups at the old host
Resellers normally cannot run the WHM Transfer Tool, which needs root on the destination. The reliable reseller method is one full backup per account:
- Log in to each client's cPanel from the old WHM (List Accounts → cPanel icon).
- Run Backup → Download a Full Account Backup, choosing remote FTP/SCP to your MdmHost account if offered, to save downloading and re-uploading.
Tip: If the old host gives you root, or MdmHost support can connect to the old server, the WHM Transfer Tool moves accounts directly. See transfer cPanel accounts between servers.
Restore the accounts
Restoring a full backup file is a root-level WHM task on most setups. Upload the archives to your account and open a ticket at MdmHost support listing the files and the packages each should get, or follow restore a cPanel account in WHM if your plan allows it. After the restore, check that each account is owned by your reseller user and has the right package in WHM → List Accounts.
Test before switching DNS
- Browse each site through a hosts-file entry pointing to the new IP.
- Log in to webmail with an existing mailbox; restored accounts keep their passwords.
- Check PHP versions in MultiPHP Manager per domain.
Switch DNS and sync late email
- If clients use your private nameservers, update the glue/child nameserver IPs at the registrar so all zones move at once. Otherwise change each domain's A and MX records or nameservers.
- Mail that reached the old server after the backup will be missing. Copy it with imapsync per mailbox: imapsync guide.
- Keep the old reseller account active for a week, then cancel it.
Post-migration checks
- The site loads over HTTPS with a valid certificate. AutoSSL issues it once DNS points to MdmHost; run it from cPanel → Security → SSL/TLS Status if needed.
- Forms, logins, checkouts and uploads work, and there are no database connection errors.
- Sending and receiving email works from webmail and from your mail client, and SPF/DKIM pass in cPanel → Email → Email Deliverability.
- Cron jobs are recreated under cPanel → Advanced → Cron Jobs with the new paths (
/home/username/…). - The PHP version in cPanel → Software → MultiPHP Manager matches what the old server used.
- Each client can log in to cPanel with their existing password.
- AutoSSL has issued certificates for every domain.
FAQ
Do clients keep their passwords?
Yes. A full cPanel backup keeps cPanel and mailbox passwords.
Can I move my WHMCS too?
Yes, separately; see move WHMCS to a new server.
What about WHM Reseller sub-resellers?
See migrate a reseller tree to MdmHost.
