Moving from cPanel to Plesk

The short answer

cPanel and Plesk do the same job with different menus, and Plesk can import a full cPanel backup directly. The move itself is routine; what needs care is the checklist afterwards. Email accounts, DNS records, databases, cron jobs and file paths all need checking because each one lives in a slightly different place.

If you are moving to WP Alpha, the free concierge migration handles all of this, including the DNS changeover, and 99 of 100 migrations have no downtime window.

What it means

cPanel and Plesk are both hosting control panels: the web interface you log into to manage files, email, databases and domains on a server. They are made by different companies, organise things differently, and store some settings in different formats, so you cannot simply copy a folder from one to the other.

Plesk includes a migration tool that reads a cPanel backup archive and recreates the account: website files, databases, email accounts, DNS zone and scheduled tasks. Most of it comes across cleanly. The job is then to verify each piece rather than assume it worked.

Two practical differences catch people. Paths change: a cPanel site usually lives under /home/username/public_html, while Plesk uses /var/www/vhosts/yourdomain.com/httpdocs. Anything that stored the old full path (a plugin setting, a cron job, a hard-coded upload directory) breaks until it is updated. File ownership and permissions are also handled differently, which shows up as upload errors or “permission denied” messages.

Plesk also has WP Toolkit, a WordPress-specific layer with one-click staging and update management, which is where most day-to-day WordPress tasks happen once you are on Plesk.

Common causes

• Incomplete cPanel backup. A home-directory-only backup from Backup > Backup Wizard misses email, databases and DNS. The full account backup is the one Plesk needs, and on a large account it can fail partway if disk space runs out during the export.
• Email not checked until it breaks. Mailboxes come across but passwords, forwarders, autoresponders and mail client settings (server name, ports) often need resetting.
• DNS zone copied wrong or not at all. The old zone from Zone Editor may carry the old server’s IP in every record, or MX and SPF records may be missed if the zone is rebuilt by hand.
• Database names and users changed. cPanel prefixes databases with the account name; Plesk may import them under a new name or user. wp-config.php then points at a database that does not exist.
• Cron jobs and paths. Scheduled tasks referencing /home/username/... fail quietly on the new server.

How to fix it

1. Take a full cPanel backup. Backup > Backup Wizard, then Full Backup, saved to the home directory or sent by FTP to the new server. Download a copy so you hold it regardless of what happens next.
2. Record what exists today. From cPanel note every email account and forwarder (Email Accounts), every DNS record (Zone Editor), every database and user, every cron job, and the PHP version. This list is your checklist later.
3. Import into Plesk. Use the Plesk migration tool VERIFY: exact menu label in the management console and point it at the cPanel backup file or at the old server directly.
4. Check the website files and paths. Open File Manager and confirm the site is in httpdocs. Search wp-config.php and plugin settings for any /home/ path and update it. If you see permission errors, ask support to reset file ownership; it is a quick fix on the server.
5. Check the database. Under Databases, confirm the database exists and open wp-config.php to confirm the name, user and password match. Use phpMyAdmin to confirm the tables are populated.
6. Set the PHP version. Under Hosting & DNS > Hosting Settings, select the same PHP version the site ran on before, then upgrade once it is stable.
7. Recreate or verify email. Under Mail, confirm every mailbox from step 2 exists. Reset passwords, recreate forwarders and autoresponders, and give users the new incoming and outgoing server names.
8. Fix the DNS zone. Under DNS Settings, compare every record with your step 2 list. Correct any A record still pointing at the old server, and confirm MX, SPF, DKIM and DMARC are present.
9. Recreate cron jobs. Under Scheduled Tasks in Plesk, add each job with the new path.
10. Test, then move DNS. Check the site on the new server using a temporary address or a hosts-file entry. Only then lower the TTL, change the A record or nameservers, and keep the cPanel account live until DNS has fully propagated.

On WP Alpha

WP Alpha runs on Plesk with WP Toolkit, and the free concierge migration handles the cPanel to Plesk move for you: files, database, DNS and testing, with 99 of 100 migrations having no downtime window. You give us the cPanel login or a full backup and we do the rest. VERIFY: whether email accounts are migrated and whether WP Alpha hosts email

Once the site is on our platform, the things you had to patch together on cPanel are built in: Redis object caching and page caching on every plan, staging sites in one click in WP Toolkit, backups every two hours kept for 30 days with restores from a single file up to the whole site, daily Imunify malware scans with cleanup included, and PHP 7.0 to 8.5 available (8.3 or 8.4 recommended). SSH, WP-CLI, phpMyAdmin and real server cron are all there for anything you prefer to do yourself.