cPanel to cPanel Migration (Full Account Move)

How cPanel-to-cPanel Migration Works

The shape of a safe migration: copy first, cut over last. Everything — site files, databases, email — moves to the new server while the old one keeps serving; DNS switches only after testing. Two methods:

1. Full backup and restore (any host) — old cPanel: Files → Backup → Download a Full Account Backup; restore on the new host (or hand the archive to their support).
2. WHM Transfer Tool (fastest, needs root) — pulls entire accounts wholesale over SSH, including databases and mail.

Then the cutover: lower DNS TTLs a day ahead, verify the new server via hosts-file preview, switch records together, and keep the old server running through the overlap. Or skip the checklist-keeping: WebJi® migrates it free for clients moving in from any cPanel origin.

Before You Start: The 5-Minute Checklist

Before You Start: The 5-Minute Checklist. Do the change this heading names on one site first, then check it in a private browser window or in the mail client, depending on the topic. Change one setting at a time, and undo it if the result is wrong before you try the next. If you want the Jaipur desk to look with you, email support@webji.services — that mailbox is staffed 24/7 in Hindi and English. Phone +91 141 4941811 is business hours only.

Method 1: Full Backup and Restore (Any Host)

How this plays out with WHM Transfer Tool: settings that look cosmetic usually decide page speed and uptime under real traffic. The defaults WebJi® ships are tuned for Indian network conditions, and support can review your setup on request.

Method 2: WHM Transfer Tool (Fastest)

WHM Transfer Tool (Fastest). Start the account copy from WHM's Transfer Tool on the destination server, let it finish, and browse the site on the new server's temporary URL before you change nameservers. Mail and databases come across only if you included them in the transfer. Keep the old host online until DNS has settled.

Moving Email Accounts and Filters

Email is the migration's most-lost item because it lives outside the website's obvious files. Mailbox accounts and contents: the full-account backup includes the mail directory, and Transfer Tool moves it wholesale; after restore, recreate or confirm every address and reset passwords.

The cutover mechanics matter most: mail flows to whichever server the MX records currently point at. The safe sequence: lower MX TTLs days ahead and copy mailboxes. Switch MX records at the same moment as the site's nameservers. Then run both mail servers in parallel for 48 hours, with the old one set to catch (not bounce) anything cached DNS still delivers. Forwarders and filters move with the account but deserve one-by-one verification; test send and receive from external providers immediately after cutover.

Switching DNS With Zero Downtime

Zero-downtime cutover, in order:

1. DNS TTLs already dropped (300s, a day prior).
2. New server verified via hosts-file preview — site, admin login, one test transaction or form.
3. MX records and A/nameserver records switched together.
4. Propagation: 1–12 hours across Indian ISPs, up to 24–48 globally.
5. Old server untouched and online through 48 hours of overlap.

Post-cutover testing: load every key template, submit a test form, place a test order on stores, send and receive mail externally, verify cron jobs fired, and re-issue SSL on the new server (AutoSSL, minutes). Watch logs on days two and three for stragglers still hitting the old server — cached DNS, hardcoded IPs — before decommissioning anything.

Post-Migration Testing Checklist

Free migration is offered subject to terms and approval. It is not an unattended button, and it is not a promise for every custom stack. Open a ticket with the current host login or a full backup, keep the old host online until you have checked the copy, and only then change DNS.