How to Move from cPanel to Plesk Safely in 2026

Before you start the cPanel to Plesk tutorial

This cPanel to Plesk tutorial assumes you already have the new server or hosting plan ready, a fresh backup in hand, and access to both control panels. If you are moving from shared hosting to a VPS, or from a smaller reseller account to a server with more headroom, planning the handoff now saves a lot of cleanup later.

If you still need a destination plan, Hostperl VPS hosting gives you room to move sites, email, and databases without cramming them into old resource limits. For heavier customer loads, a dedicated server can make the cutover easier because you control memory, CPU, and mail reputation more directly.

• Confirm the source server uses cPanel/WHM and the destination uses Plesk.
• Lower your DNS TTL to 300 seconds at least 24 hours before cutover.
• Check mailbox sizes, database size, and any addon domains.
• Write down the current PHP version, SSL state, and cron jobs.

One detail gets missed often: note the IP address used for mail. If you plan to keep email on the new server, the mail IP should be stable before you move records. Our email deliverability comparison explains why that matters for inbox placement.

Map the old cPanel account to the new Plesk subscription

Plesk works with subscriptions, domains, and service plans. cPanel uses accounts, add-on domains, and feature sets. Match those pieces before you copy anything, or you can end up with a half-moved site.

Use this simple mapping:

• cPanel account name → Plesk subscription or customer
• Main domain → Primary domain in Plesk
• Addon domains → Additional domains or separate subscriptions, depending on ownership
• Databases → Individual MySQL databases under the destination subscription
• Email accounts → Mailboxes created under the same domain in Plesk

If you are choosing a panel for a future project rather than migrating, our panel comparison guide helps you avoid a second migration later. That choice matters for agencies, because the cheapest panel is not always the one that cuts support work.

Back up the site, mail, and databases separately

Backups are easier to restore when you can pull pieces back independently. A full account archive helps, but you also want separate copies of the web root, database dumps, and email folders.

On cPanel, generate a full backup if your host allows it, then also download the parts you may need to verify by hand. For most transfers, this checklist is enough:

1. Download the website files from /home/username/public_html/.
2. Export each database from phpMyAdmin or with a mysqldump export.
3. Copy the mailbox data if the account stores important client mail locally.
4. Save SSL certificate details and any custom DNS records.

For a stricter cutover, use the method in our no-downtime site move guide. It covers the timing that keeps pages working while DNS updates.

Transfer the files first, then the database

Move the web files before you touch the database. That leaves the destination site ready for testing while you finish the data layer.

In Plesk, create the domain, open the file manager or connect by SFTP, and upload the site files into the correct document root. For WordPress, that is usually httpdocs/. For other applications, check the path shown in the domain settings.

Then import the database into the new Plesk subscription. If your app uses WordPress, Joomla, Drupal, or a custom PHP stack, update the database name, user, and password in the configuration file before testing. Common files include wp-config.php, configuration.php, or a custom .env file.

For WordPress sites, this setup guide for new hosting sites is a useful companion, especially if the client also needs a fresh staging domain after the move.

Recreate email accounts and DNS records in Plesk

Email is where migrations often fail quietly. The site loads, but mail bounces because MX, SPF, DKIM, or autodiscover records still point to the old host.

In Plesk, create each mailbox before you switch DNS. Then rebuild the DNS zone record by record:

• MX record pointing to the new mail host
• A record for the mail hostname
• SPF record matching the sending server
• DKIM enabled in the mail settings
• DMARC policy aligned with the domain’s current sending pattern

If you want the practical sequence for mail and DNS, use Hostperl’s SSL, DNS, and email setup checklist. It is the quickest way to avoid the common mistake where the website works but email is delayed or rejected.

For clients moving between shared plans and VPS plans, the mail setup deserves extra care. Shared hosting sometimes keeps outbound mail reputation cleaner, while a VPS gives you more control. Our shared hosting vs VPS for email guide covers that tradeoff in plain terms.

Test the site before you change nameservers

Do not point the domain at Plesk until you have opened the site on the new server and checked the obvious failures. You can test by editing your local hosts file, using the temporary Plesk preview URL, or loading the site through the server IP if the app allows it.

Check these items in order:

• The homepage loads without mixed content warnings.
• Login forms submit correctly.
• Contact forms send mail to a real mailbox.
• Uploads still write to the expected folder.
• Database-driven pages show live content, not an error page.

If the site uses HTTPS, install or renew the certificate in Plesk before testing forms. The fastest fix is usually to set the correct hostname, install the certificate, and then clear cache at the application level and browser level.

Switch DNS with a short rollback window

When the new server looks right, update the nameservers or the domain’s A records. Keep the old hosting active for at least 48 hours so delayed DNS resolvers and mail queues can catch up.

That window matters more for business sites than personal blogs. A local business may receive bookings, quote requests, and invoices from several channels at once. If one record is wrong, you may not hear about it until customers stop getting replies.

For the cleanest cutover, compare the live DNS zone against the old zone line by line. Our safe server move guide shows the order we use during customer migrations when uptime matters.

Fix the common post-migration problems

After the DNS switch, most issues fall into a small set of patterns. Start with the ones below instead of guessing.

• White screen or 500 error: check PHP version and extensions in Plesk.
• Database connection error: recheck the host, username, password, and database name.
• Mail stops arriving: confirm MX and A records, then inspect mailbox quotas.
• Broken images or CSS: clear the app cache and verify file paths.
• SSL warning: confirm the certificate matches the live domain, including www.

If the server feels slow after the move, the issue may be resource sizing rather than configuration. In that case, read our VPS vs dedicated servers guide before you decide whether to raise plan size or adjust the stack. Sometimes you need more memory. Sometimes you need a cleaner mail split.

Keep the old account for one billing cycle

Do not cancel the source hosting the same day you migrate. Keep it live long enough to catch straggling email, missed DNS propagation, and any files the client forgot to mention.

That extra overlap helps agencies and reseller customers most. It gives you a rollback point if a theme license, PHP setting, or mailbox import needs another pass. It also gives support a stable place to compare logs while you verify the new Plesk subscription.

Quick checklist before you close the ticket

• Site loads on the new Plesk server
• Email sends and receives on the new host
• SSL is active on the live domain
• DNS points to the correct IPs
• Old account stays active for rollback

Done well, a cPanel to Plesk tutorial is mostly about order, not complexity. Move files, verify data, rebuild email, test before DNS, then watch the logs for a full day. That is the same process we use when helping customers move production sites at Hostperl, whether they are on shared hosting, a VPS, or a dedicated server.

FAQ

Can I move cPanel email to Plesk without losing messages?
Yes, if you migrate the mail folders or leave the old mailbox active during the overlap window. Always verify IMAP folders after the transfer.

Do I need to change nameservers, or can I keep DNS elsewhere?
You can keep DNS elsewhere. Many customers only update A, MX, and related records at the existing DNS provider.

Will WordPress need changes after the move?
Usually yes, at least a PHP version check and a cache clear. Sometimes you also need to update the site URL if the domain or subdomain changed.

How long should I keep the old cPanel account?
Keep it for at least 48 hours, and longer if the site has active email or slow-propagating DNS.