cPanel to Plesk Migration

The Problem

You're moving from cPanel hosting to a Plesk server (or VPS), and cPanel's backup format, file structure and database setup don't translate directly — a naive copy breaks cron jobs, email routing and sometimes the site itself.

About this problem

cPanel and Plesk organise accounts, databases and mail completely differently under the hood, so there's no one-click bridge between them. A cPanel backup (.tar.gz in cpmove format) has to be unpacked and each piece — files, databases, DNS zone, email accounts, cron jobs — recreated manually inside Plesk's own structure.

This typically comes up when a client moves to new hosting that only offers Plesk, consolidates multiple cPanel accounts onto one Plesk server, or switches providers for cost or feature reasons.

What's Included

• Full export of the website files, databases, DNS records, email accounts and cron jobs from cPanel
• Recreating everything natively inside Plesk — domains, databases, mailboxes, cron jobs
• Matching PHP version and key settings so the site behaves identically
• Verifying the site, database and mail all work correctly before DNS points to the new server

What's NOT Included

• Provisioning or paying for the new Plesk server/licence
• Moving more than one cPanel account unless agreed upfront
• Fixing pre-existing site issues unrelated to the migration itself

How It Works

1. Generate a full cPanel backup (or access cPanel directly) and inventory every domain, database, mailbox and cron job that needs to move.
2. Create the matching domain structure in Plesk and import the website files.
3. Export each MySQL/MariaDB database from cPanel and import it into Plesk, updating connection details in the site's config as needed.
4. Recreate DNS zone records, mailboxes and cron jobs natively in Plesk rather than relying on an automated import that often misses edge cases.
5. Test the site and mail on the new server using a temporary hosts-file override before touching live DNS.
6. Once confirmed working, update DNS to point to the new Plesk server and do a final live check.

In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.

Frequently Asked Questions

Can I move from cPanel to Plesk without losing email?

Yes, as long as every mailbox and its settings are recreated before the DNS switch — mail risk comes from rushing the DNS change before mail is actually ready on the new server, not from the migration itself.

Will my website URLs change after moving from cPanel to Plesk?

No, the domain stays the same — only the hosting panel and server underneath change, so URLs, SEO and bookmarks are unaffected.

Do I need to buy a new Plesk licence?

Yes, Plesk requires its own licence (or comes bundled with certain VPS/hosting plans) — that's a cost between you and your host or Plesk directly, separate from the migration work itself.

Can a cPanel backup be imported directly into Plesk?

Not directly — the formats aren't compatible, so each component (files, databases, DNS, mail, cron) has to be extracted from the cPanel backup and recreated individually in Plesk.

How much downtime should I expect during the migration?

With DNS only switched after the new server is fully tested and ready, downtime is typically just DNS propagation time (minutes to a few hours), not the migration work itself.

What happens to my old cPanel account after migration?

That's between you and your previous host — I don't cancel or modify the old account, so you keep access until you decide to close it yourself.