How to Move a Site from cPanel to Plesk in 2026

Before you move anything

If you need to move site from cpanel to plesk, start with a short inventory, not the migration tool. List the domain, document root, PHP version, cron jobs, email accounts, databases, SSL status, and any third-party DNS records. That gives you a clear map of what needs to be rebuilt on the new panel.

For many Hostperl customers, the hard part is not copying files. It is keeping mail working, preserving redirects, and making sure the new Plesk subscription matches the old cPanel account closely enough that nothing breaks after cutover. If you are still choosing a panel for a fresh launch, our panel comparison guide helps you decide before you commit.

Here is the practical pre-move checklist:

• Export the cPanel backup or at least the home directory, databases, and email data you need.
• Write down every DNS record that is not hosted at the registrar.
• Confirm the active PHP version and extension set.
• Check disk usage so the target plan has enough room.
• Make sure you know which mailbox users still need access after the move.

If your site already feels tight on storage or mail volume, compare the destination carefully. A Hostperl Hostperl VPS can be a better fit for sites that need more control than shared hosting can offer, while still staying manageable.

Set up the Plesk subscription first

On the Plesk server, create the subscription before you copy anything. Match the domain name exactly, set the correct system user, and confirm the PHP handler you plan to use. If the site uses multiple domains or aliases, add those now so you do not have to patch them after launch.

In Plesk, check Domains > example.com and verify the following:

• Document root points to the right folder, usually httpdocs.
• PHP version matches the current application requirement.
• Mail service is enabled only if you intend to host email there.
• SSL/TLS support is available for the domain.

For customers who are moving a WordPress or CMS site as part of the panel change, our hosting site setup guide covers the cleanest way to prepare the destination account before the transfer.

Copy files and databases without rushing

Now move the site content. If you have a full cPanel backup, extract it carefully and copy the website files into the Plesk document root. If you are moving only selected content, use SFTP or the file manager, then restore the database separately.

Use the process that best fits the site size:

1. Upload website files to httpdocs or the required subfolder.
2. Import the database in Plesk using phpMyAdmin or the command line if you manage the server directly.
3. Update the application configuration file with the new database name, user, and password.
4. Fix file ownership if the app returns a permissions error.

A common mistake is copying the files first and assuming the site will work right away. If the database connection string still points to the old server, you will get a blank page or a connection error even though all the files are present.

For database-heavy sites, a VPS is usually the safer place to host the migrated application because you can tune PHP, MariaDB, and disk I/O around the site’s actual needs. If you are evaluating that path, see VPS vs dedicated servers before deciding on the final home for the site.

Move email, the part people usually miss

Email is where panel migrations often go wrong. cPanel and Plesk both support mail, but mailbox paths, filters, and antispam settings are not interchangeable. If the domain uses mail hosted on the old cPanel account, create the same mailboxes in Plesk before cutover and copy the messages only after testing the new login.

Use this sequence:

• Create identical mailbox names in Plesk.
• Set passwords and quotas to match the old plan.
• Update MX records only after the destination mailboxes are ready.
• Test SMTP, IMAP, and webmail access from one device before moving everyone.

If you want a deeper look at the email side of the decision, our email deliverability guide explains why mailbox reputation and sending volume matter as much as panel choice.

For customers who keep email on shared hosting while the website moves to Plesk, that split is completely workable. It just needs clean DNS records and a clear cutover plan.

Check DNS, SSL, and redirects before launch

Before you switch nameservers or change A records, lower the DNS TTL a day ahead if possible. A TTL of 300 seconds is usually enough for a controlled cutover. Then make sure the Plesk server has a valid certificate installed for the domain and any key aliases.

Run through this launch checklist:

• Point the domain to the new server IP.
• Confirm the SSL certificate covers www and the root domain.
• Test HTTP to HTTPS redirects.
• Check canonical URLs and any hardcoded old links in the app.
• Verify SPF, DKIM, and DMARC records if the server sends email.

Our SSL, DNS, and email checklist is a useful companion if you want one place to confirm the basics before release day.

Test like a customer, not like an admin

Once the site is live on Plesk, test the public experience. Open the homepage in a private browser window, submit a contact form, log in as a normal user, and send a test email. Then inspect the server logs if something looks slow or broken.

A quick diagnostic run should include:

• Page load from a mobile connection.
• Image upload or checkout flow if the site uses one.
• Mail delivery to Gmail and Outlook addresses.
• Backup job status in the new panel.

If you discover issues only after DNS has changed, do not panic. Keep the old cPanel account active until the new setup has been stable for at least a full mail cycle. That gives you a rollback path if one mailbox, redirect rule, or cron job needs attention.

Common problems after a cPanel to Plesk move

The most common post-migration complaints are missing images, database errors, email not syncing, and SSL warnings. In most cases, one of three things is wrong: the document root is off, the config file still uses the old database details, or DNS has not finished propagating.

Use this troubleshooting order:

1. Check the Plesk domain path and ownership.
2. Confirm the database name, user, and password in the application config.
3. Review the DNS zone and wait for propagation if needed.
4. Reissue the certificate if the browser still shows a mismatch.
5. Inspect mail routing if messages are landing on the wrong server.

If you are moving from one panel to another as part of a broader hosting change, our safe server migration guide walks through the same operational checks in a slightly wider context.

FAQ

Can I move a site from cPanel to Plesk without downtime?

Yes, if you prepare the Plesk subscription first, copy the files and database before switching DNS, and keep the old cPanel account active during testing.

Should I move email at the same time as the website?

Only if you have time to test every mailbox. Many customers keep email on the old server for a short window and move it after the website is stable.

Do I need to change my domain registrar settings?

Not always. If you manage DNS at the registrar, update the A and MX records there. If you use Hostperl DNS or another external DNS host, update the zone records in that platform instead.

What if my WordPress site breaks after the move?

Check the database credentials, site URL, and PHP version first. Those three items solve most post-migration WordPress issues.

Is Plesk better than cPanel for a migrated site?

Not universally. Plesk can be easier for some mixed hosting environments, while cPanel may suit teams already familiar with it. The right choice depends on how you manage email, apps, and support.