Plesk is a capable control panel, but its licensing costs — often $15–$30/month or more for a hosting server — add up quickly, especially when cPanel offers comparable features at similar or lower cost and better compatibility with the broader hosting ecosystem. If you're considering a Plesk to cPanel migration, you're not alone: it's one of the most common control panel switches hosting companies make, and with the right preparation, it can be done with minimal downtime.
This guide walks you through every phase of the migration: cost analysis, pre-migration assessment, the actual migration process using WHM's transfer tools, common issues you'll encounter, and how to decide whether to handle it yourself or hire a migration specialist.
Should You Migrate from Plesk to cPanel? Cost vs. Benefit Analysis
Before committing to a migration, run the numbers honestly. A Plesk-to-cPanel switch involves real costs beyond just licensing fees:
Licensing comparison (approximate monthly costs):
- Plesk Web Pro — ~$15/month (up to 30 domains)
- Plesk Web Host — ~$30/month (unlimited domains)
- cPanel/WHM — $27.99–$45.99/month depending on account count tier
At scale (100+ accounts), cPanel/WHM is often cheaper per-account than Plesk Web Host. But licensing cost alone rarely justifies a migration. The real reasons hosting companies migrate from Plesk to cPanel are:
- Client preference — most shared hosting clients are familiar with cPanel, not Plesk; reducing support tickets by switching panels can save dozens of hours monthly
- Ecosystem compatibility — more third-party hosting tools, scripts, and WHMCS integrations assume cPanel
- Reseller market — cPanel is the dominant panel for reseller hosting accounts
- WHM advantages — WHM provides more granular server management controls than Plesk's administrative interface
Costs and risks of migration:
- Potential downtime during cutover (typically 15 minutes to 4 hours depending on account count)
- DNS propagation lag (12–24 hours if nameservers change)
- Custom Plesk extensions don't transfer — any Plesk-specific functionality must be replicated manually
- Staff retraining if your team manages client accounts via Plesk's UI
- Migration window requires careful scheduling around client maintenance windows
Migration makes sense when: you have significant client demand for cPanel, you're already provisioning new servers with cPanel, or Plesk licensing is becoming a meaningful line item relative to your margins.
Migration doesn't make sense when: you have complex Plesk extensions in active use, your clients are specifically using Plesk features (Presence Builder, Plesk WordPress Toolkit workflows), or you have fewer than 20 accounts where migration cost exceeds years of licensing difference.
💡 None of these worked? Skip the guesswork.
Get Expert Help →Pre-Migration Checklist: Assessment and Backup
A failed migration without a complete backup is a data loss event. Before touching anything, complete this pre-migration checklist:
In Plesk, navigate to Tools & Settings → Backup Manager → Back Up. Select full server backup, including all databases, emails, and configuration. Store this backup offsite (S3, SFTP to another server) — not just on the same server you're migrating.
# List all Plesk domains
plesk bin domain --list
# List all databases
plesk db list
# List all email accounts
plesk bin mail --list
# Check Plesk extensions in use
plesk bin extension --listcPanel and Plesk handle PHP handler configuration differently. Export your current PHP version assignments per domain:
plesk bin php_handler --listYou'll need to replicate PHP version configurations manually in WHM after migration.
Applications installed via Plesk's Application Vault, Softaculous via Plesk, or Plesk WordPress Toolkit will need to be verified after migration. WordPress installations transfer correctly since they're just files + databases, but the Plesk-specific management layer won't exist in cPanel.
If you're changing nameservers or IP addresses as part of the migration, lower all DNS TTLs to 300 seconds (5 minutes) 48 hours before the cutover. This minimizes DNS propagation lag after the switch.
Install cPanel/WHM on your new server. Complete the WHM initial setup wizard: set hostname, nameservers, contact email, and configure your firewall (CSF recommended). Do this before starting any account transfers.
The WHM Transfer Tool needs root SSH access to the Plesk server. Set up SSH key-based authentication:
# On the WHM/cPanel server:
ssh-keygen -t ed25519 -f /root/.ssh/plesk_migration_key
# Copy public key to Plesk server:
ssh-copy-id -i /root/.ssh/plesk_migration_key.pub root@PLESK-SERVER-IPIn WHM, navigate to Transfer Tool under the main menu. Enter:
- Remote Server — IP or hostname of your Plesk server
- Root Password or SSH Key — credentials for root access
- Remote Server Type — select Plesk
Click Fetch Account List. WHM will connect to the Plesk server and enumerate all accounts. Select the accounts to transfer and click Transfer.
The Transfer Tool shows real-time progress per account. Transfer time depends on account size and network speed between servers — allow 10–30 minutes per GB of data. Monitor for errors and note any accounts that fail to transfer for manual remediation.
curl -H "Host: yourclientdomain.com" http://NEW-SERVER-IP/telnet NEW-SERVER-IP 25
EHLO testdomain.com
MAIL FROM: test@testdomain.com
RCPT TO: existing@clientdomain.comFor each critical web application, log in and perform a basic function test — submit a form, load a page that queries the database, check that user accounts are intact.
tail -f /home/USERNAME/logs/error_log # Per-account Apache error log
journalctl -u exim -f # Exim mail logsManaged vs. DIY Migration: When to Hire a Specialist
A Plesk-to-cPanel migration is well within reach for an experienced sysadmin. But certain scenarios significantly increase the risk of extended downtime or data loss:
- More than 50 accounts — transfer time increases substantially; a partial failure mid-migration requires careful triage
- Active e-commerce sites — any downtime during payment processing windows creates direct revenue loss
- Complex custom configurations — ModSecurity rule sets, custom Apache/Nginx configurations, and Plesk extensions all need manual replication
- No dedicated migration window — if you can't schedule a maintenance window, a live migration requires more careful coordination
- No rollback plan — if you don't have a working Plesk server you can revert to, errors become emergencies
If any of these apply, a professional server migration service reduces risk significantly. Migration specialists have handled hundreds of panel-to-panel transfers and know which issues will appear before they happen — preventing the 2 AM recovery situation that DIY migrations sometimes produce.