Migrate From cPanel to Plesk

What You Need Before You Start

This guide shows you how to migrate from cPanel to Plesk, moving a hosting account from one control panel to the other. It is for owners and administrators who manage their own hosting or work with a provider on the move. Before you start, you need administrative access to both panels, the ability to change DNS records and a full backup of the cPanel account. The differences between the two panels are covered in cPanel vs Plesk.

Steps to Move the Account

1. Back up the cPanel account. Create a full backup that includes files, databases, mailboxes and DNS records, and store a copy somewhere other than the old server. A backup made in one panel cannot be restored directly into the other, so the migration tool reads the account data instead.
2. Prepare the new server. Make sure the target server runs an operating system that the new panel supports, as described in control panel OS compatibility. Check that it has enough disk space and the PHP versions your applications need.
3. Run the migration tool. Enter the source server details and select the domains, websites, databases and mailboxes to transfer. Where possible, run a test migration to a staging copy first.
4. Correct paths and settings. Check the document root, since cPanel accounts commonly use public_html and Plesk commonly uses httpdocs. Update hard-coded paths in applications and confirm that database connection settings point to the right host and name.
5. Reinstall certificates and scheduled tasks. Reissue or reinstall SSL certificates on the new server, then recreate cron jobs and any custom server rules that did not carry over.
6. Test, then switch DNS. Check pages, databases, mail and logins through a test address or a local hosts file entry. Only then change the DNS records to the new server, and keep the old account running until everything works.

Common Mistakes and When to Ask for Help

• Assuming everything moves. Check each domain, mailbox, database and scheduled task after the migration.
• Cancelling the old account early. Keep it running until DNS has changed and mail has been checked.
• Ignoring mail passwords. Users may need new passwords if the stored ones do not carry over.
• Missing hard-coded paths. Applications that point to public_html stop working when the document root changes.

Ask your hosting provider's support team for help if the migration tool stops with errors, if a large database will not import or if you are unsure how to handle installed applications.

Can I move a cPanel account to Plesk without downtime?

Often not entirely. Migrations usually copy data, then switch DNS, and there can be a short gap in which the site or mail behaves differently. A final sync before the switch reduces lost changes, and careful planning keeps the gap small.

Should I test a migrated account before it goes live?

Yes. A test copy lets you confirm that pages render, databases connect, mail works and paths resolve before visitors see the new environment. Testing also reveals settings the migration tool did not carry across, so they can be fixed while the old account is still running.

Will my email addresses and passwords stay the same?

The addresses usually do, because mailboxes are normally copied, but passwords may not. Stored mail passwords can be in a format the new panel cannot reuse, so plan to reset them and tell users in advance. Check that incoming and outgoing mail work once DNS has changed.