cPanel to Plesk Migration Tutorial for Hosting Customers

Before you move anything

This cPanel to Plesk migration tutorial starts with one simple rule: check the destination first. A clean migration depends more on preparation than on the copy step itself. If you are moving a live business site, do not treat the panel change as a cosmetic switch.

Most Hostperl customers move because they want a different admin experience, cleaner WordPress handling, or a better fit for a client workflow. If you are still deciding whether to move at all, compare the panel choice first with our guide to cPanel vs Plesk: Pick the Right Panel in 2026. It will help you avoid a migration you do not actually need.

• Confirm the Plesk version on the target server.
• Check PHP versions, disk space, and mail service status.
• Lower DNS TTL to 300 seconds at least 24 hours before the move.
• Make a full backup of files, databases, and mailboxes.

If you are starting from a fresh server, a Hostperl VPS gives you enough room to test the new panel before you touch production. That matters when your site also carries email, cron jobs, and multiple domains.

Map the cPanel account before the transfer

Open the cPanel account and write down what actually lives there. Migration problems usually come from what people forget: subdomains, forwarders, DNS records, and mailbox aliases.

Use this checklist:

1. Domains: main domain, add-on domains, parked domains, and subdomains.
2. Web root paths: note where each site lives under public_html.
3. Databases: database names, users, and which app uses each one.
4. Email: active mailboxes, forwards, autoresponders, and spam filters.
5. SSL: check whether AutoSSL is active or a third-party certificate is installed.

This is also the point where many shared hosting customers realize they need a plan change, not just a panel change. If the account has outgrown its current limits, Hostperl's shared hosting upgrade signals guide helps you spot the signs early.

Prepare the Plesk server for the move

On the destination server, set up the base environment before you import anything. Plesk can host multiple websites, but the defaults still deserve a quick review if you want a smooth cutover.

In Plesk, confirm the following:

• The subscription or service plan has enough disk and traffic allowance.
• PHP handlers match the versions your site uses.
• Mail service is enabled if you plan to host email there.
• Backup storage exists and is writable.
• Your firewall allows ports 80, 443, 25, 465, 587, 993, and 995 where needed.

For many hosting customers, a migration is the right time to reconsider server size. Our tutorial on VPS vs Dedicated Servers explains the trade-off in plain language. If the site is growing steadily, a dedicated server can be the cleaner long-term move.

Export the site, database, and mail data

Now take the actual backup from cPanel. You can use the built-in backup tools or a manual export, depending on how much control you want. For a small site, cPanel's full-account backup is usually the safest place to start.

Download these items separately if possible:

• Website files
• MySQL databases
• Email maildir data
• DNS zone notes

For WordPress and similar CMS sites, keep the database dump and wp-content directory together. That avoids the common mistake of restoring files but missing uploads or plugin settings. If you need a refresher on email setup after the move, use Hostperl's email hosting checklist so you know what should keep working after DNS changes.

Do not forget to verify the backup with a quick check:

tar -tzf backup.tar.gz | head
mysql -u user -p -e "SHOW DATABASES;"

You are not trying to be clever here. You are checking that the archive opens and the database dump exists before you trust it.

Restore into Plesk with the least disruption

Import the site into Plesk using the panel tools where you can. If the source account is straightforward, the Plesk import feature handles most of the layout. For more complex accounts, restore the site files and databases manually, then recreate the domain in Plesk.

Use this order:

1. Create the domain or subscription in Plesk.
2. Upload or extract the site files into the correct document root.
3. Import the database and update the application config.
4. Recreate email accounts, aliases, and forwarders.
5. Install or reissue SSL for the domain.

If you are moving from cPanel specifically, keep our cPanel migration checklist open beside you. It covers the small items that usually get missed, such as cron jobs and forwarders.

For customers on managed platforms, this is where Hostperl support often saves the most time. A migration looks simple on paper, then one legacy PHP version or mail filter breaks the launch. That is normal. It is also why the test phase matters.

Test the site before you change DNS

Before you point traffic to the new server, test the site on the Plesk server directly. Use the hosts file on your workstation or a temporary URL in Plesk. That lets you catch missing images, database connection errors, and broken redirects while the old site is still live.

Check these items one by one:

• Homepage loads over HTTPS.
• Forms submit and send email.
• Admin login works.
• Uploads appear in the media library or file manager.
• Scheduled tasks run on the new server.

If the site uses WordPress, compare your test against our new site setup guide. It is a useful cross-check for paths, databases, and basic panel settings.

One practical tip: send a test message from the new server to Gmail, Outlook, and a business mailbox you control. That gives you an early read on deliverability before customers start replying.

Switch DNS and watch the first 24 hours

Once the site is stable, update the A record or nameservers. If you lowered TTL earlier, the change should move quickly. Even so, some visitors will still hit the old server for a short time. Keep both environments available until traffic settles.

During the first day, watch for these signs:

• 404 errors from old paths
• Mail still arriving on the previous server
• Certificate warnings after the DNS change
• Skipped cron jobs or delayed tasks

If you need a safe rollback plan, follow Hostperl's no-downtime site move guide. It explains how to keep the old server in place long enough to catch late DNS propagation and missed mail.

For DNS and SSL details, keep the SSL, DNS, and email setup checklist nearby. It is especially helpful if the domain uses a separate DNS provider.

Fix the usual post-migration problems

The first broken item is often not the website itself. It is usually email, a path mismatch, or a forgotten permission setting.

Here is a fast triage sequence:

1. Website shows a database error: confirm the database name, user, and password in the app config.
2. Email stops working: check MX records, mailbox creation, and whether the mail service is enabled on Plesk.
3. SSL warning appears: reissue the certificate and confirm the domain resolves to the new IP.
4. Old content still appears: clear browser cache and check whether CDN or proxy caching is active.

If deliverability matters, review shared hosting vs VPS for email deliverability. Some customers only discover after a migration that the account now needs a dedicated IP or a different mail setup.

For VPS and server users who want to cut down brute-force login noise after the move, see our practical Fail2Ban setup guides for Debian VPS and Plesk VPS. Those are useful if the new server is public-facing and you want tighter login hygiene.

Quick checklist before you close the old cPanel account

• Website loads from the new Plesk server.
• SSL is active and renewed correctly.
• Email sends and receives from each mailbox.
• DNS points to the correct IP address.
• Backups are enabled on the new server.
• Cron jobs and scheduled tasks are running.

Once those items are confirmed, you can safely retire the old account. If you are still deciding whether the new setup should stay on a VPS or move to a dedicated server, Hostperl's VPS vs dedicated comparison gives you a clear side-by-side view.

FAQ

Can I move from cPanel to Plesk without downtime?
Yes, if you lower DNS TTL, test the site before the switch, and keep the old server online during propagation.

What usually breaks first after a cPanel to Plesk migration?
Email, database credentials, and cron jobs are the most common problems. Website files usually move more cleanly than account-level settings.

Should I move mailboxes with the site?
Only if you are ready to verify MX records, spam filtering, and mailbox permissions on the new server. If email is business-critical, test it before cutover.

Is Plesk better than cPanel for every site?
No. Plesk suits some workflows better, especially when the account mix includes WordPress, multiple domains, or a cleaner subscription model.

Can Hostperl help with the migration?
Yes. Hostperl supports hosting customers who need practical help with panel moves, server setup, DNS, SSL, and post-migration checks.