Migration
Migrate cPanel account: what transfers and what to verify
cPanel-to-cPanel transfers can automate a large part of a hosting move, but a successful account copy does not guarantee the destination server has identical PHP versions, extensions, DNS architecture, mail routing, limits, or third-party dependencies.
Inventory the account and destination differences
Record domains, subdomains, databases, users, mailboxes, forwarders, DNS, cron jobs, SSL, storage, PHP settings, application versions, and special server modules. Compare what the destination supports before beginning the transfer.
Use supported transfer tooling when both servers allow it
A full account transfer can preserve more metadata than manually copying public_html and a database. Follow the current cPanel/WHM transfer method available for the source and destination rather than assuming every host grants root-level transfer access.
Test mail and DNS independently from the website
A migrated site can load while mail still routes to the old server or DNS records differ. Verify MX, SPF, DKIM, DMARC, mailboxes, forwarders, autoresponders, and external DNS provider settings separately.
Check resource limits and runtime compatibility after the copy
Confirm account package limits, PHP version/extensions, database behaviour, cron commands, file ownership, SSL issuance, redirects, and application logs. Keep the source available until the destination handles normal production traffic.