A cPanel account is usually more than a website: mailboxes, addon domains, cron entries and years of .htaccess. Only one of those moves when you point the DNS somewhere new.
The site copies easily. The rest of the account is what makes this move worth planning.
cPanel usually hosts your mail on the same server as the site, so changing the domain's DNS without a mail plan takes the mailboxes down with it. We look at your MX records first.
One account frequently serves several sites. We enumerate them and you decide on each, rather than discovering a forgotten one a week after cutover.
Cron belongs to the hosting account rather than to WordPress, so anything scheduled there stops the day you leave and nothing announces it. Those become platform jobs.
Redirects, hotlink rules and access protection accumulate in one file. It is separated by purpose and reimplemented rather than copied into a stack that reads it differently.
Shared accounts often run a version the site has never been tested above, so we match it first and raise it on a clone.
Almost every unpleasant surprise in a cPanel migration is something that was in the account rather than in WordPress. That is what gets inventoried first.
The single biggest change leaving shared cPanel hosting is that your site stops competing for CPU and disk with accounts you have never heard of.
These are the specific things a cPanel migration needs, and most of them live in the account rather than in WordPress.
| Setting | What we do | Why |
|---|---|---|
| Email accounts | Identified and planned for before the DNS change | cPanel hosts mail on the same box as the site, so moving the domain without a mail plan takes the mailboxes offline along with it. |
| Addon and parked domains | Enumerated, with each one decided on rather than assumed dead | A single account frequently serves several sites, and only one of them is the site anybody was thinking about. |
| Cron entries | Read from the panel and recreated as platform jobs | Panel cron belongs to the hosting account rather than to WordPress, so scheduled work stops silently on the day you leave. |
| Accumulated .htaccess | Separated by purpose and reimplemented | A file that old normally contains redirects, hotlink rules and protection nobody has read in years. |
| PHP version | Matched on arrival, then raised on a clone | Shared accounts often run a version the site has never been tested above, and finding that out on production is avoidable. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Free migration, the email question settled first, and cron that keeps running.