Tutorial · migration-hosting · Published 2026-08-16 · 3 min read
Plesk to cPanel hosting migration
Plesk to cPanel migration explained: what transfers, email and DNS gotchas, and the manual steps that keep the site intact.
What transfers and what does not
Plesk and cPanel are both hosting control panels, so the biggest risk in moving between them is assuming a built-in tool copies everything. The two panels store configuration in different places: Plesk keeps per-domain settings in its own database and configs, while cPanel stores them in whm areas, package files, and per-user conf/ directories. A direct "transfer" between panels does not always map cleanly.
What reliably transfers automatically:
- The website files you can download and upload.
- A SQL database exported as a dump and re-imported.
- Email messages if you move the mail directories and mailboxes.
What usually does not carry over without manual work:
- Per-account
max_execution_time, PHP version and extension settings, unless you note and re-create them. - Cron jobs, since Plesk and cPanel store cron entries per-cpanel differently.
- DNS zones, DKIM signatures and SPF records, which are attached to the domain in each panel's own area.
- The exact SSL keys and issuance configs, though the certificate itself is portable.
The manual migration steps
- Inventory the old server. Record the PHP version, PHP handlers, upload limits, cron jobs, redirect rules (
.htaccesson Plesk Apache) and any addon domains before you touch anything. - Export the website files. Download the public directory, excluding caches and logs, and upload it to the new account, keeping the structure intact.
- Export and import the database. Use a consistent dump and watch the character set:
mysqldump --single-transaction -u USER -p DBNAME > db.sqlImport it on the new cPanel host with the matching database name the app expects.
- Re-create configuration blocklets. Set the PHP version and limits to the values you recorded, re-add cron jobs (cPanel: Cron Jobs), and restore redirect rules.
- Re-point DNS. Update the nameservers or the A/AAAA records at the registrar to the new server, keeping a low TTL during the change.
- Move email last. Migrate mailboxes after the site is verified so no messages are written to an old server in the gap.
| Item | Plesk | cPanel | Auto transfer |
|---|---|---|---|
| Website files | public dir | public_html | Manual copy |
| Database | per-subscription DB | cPanel DB | Manual dump/import |
| FTP users | FTP accounts | FTP Accounts | Re-create |
| Cron jobs | Scheduled Tasks | Cron Jobs | Re-create |
| DNS zone | DNS settings | Zone Editor | Manual / re-point |
Email and DNS gotchas
Email is where a panel migration silently breaks mail. Each panel has its own DKIM selector, and the SPF/DKIM/DMARC records are attached to the domain. If you move the site but keep the old panel's name servers, mail signing keys may not match. Test every mailbox and re-verify the record at a DNS checker before you switch inbound mail.
A Plesk account may also hold an IPv6 address or a different web root name (/var/www/vhosts/... versus /home/user/public_html). Absolute paths in config files or cron scripts break when the layout changes, so replace absolute paths with the cPanel equivalent after the move.
The hosting panel basics guide covers what each panel's controls do, and the host migration checklist and move to new hosting guides walk the end-to-end cutover that this article assumes for the panel-specific part.