Switching from cPanel to Plesk may sound daunting, but it’s manageable with a clear plan. First export all data from cPanel (files, databases, email, and DNS settings), then set up a new environment in Plesk, and test everything before switching over the domain. This prevents downtime and data loss. Below you’ll find exactly what to do for each part.
Why switch from cPanel to Plesk
cPanel and Plesk essentially do the same thing: they give you a clear control panel for websites, databases, email, and DNS. The difference lies mainly in the interface and licensing structure. Plesk works with a modern, clear interface and integrates well with Linux servers running on LiteSpeed. Many hosting providers choose Plesk because it’s stable, regularly updated, and works well with security features such as free SSL certificates and automatic updates.
A migration is also a good time to reassess your hosting. Is your website still running on outdated storage, or do you want to take advantage of NVMe storage and daily backups? Then check out the options for web hosting at a new provider.
What to prepare
Before you start, map out everything that needs to be moved. Think of:
- Website files (via FTP or file manager)
- Databases (usually MySQL/MariaDB)
- Email accounts, including existing mailboxes
- DNS settings (A records, MX records, CNAMEs)
- SSL certificates (often easy to request again in Plesk)
Make sure you log in to your current cPanel environment and note down all active domains, subdomains, and email accounts. This prevents you from forgetting to transfer something after the migration.
Migration plan
Make a full backup in cPanel
Use cPanel’s backup feature to create a complete archive of your files, databases, email, and settings. Download this archive locally so you have a secure copy.
Set up a new environment in Plesk
Create a new subscription or domain in Plesk that matches your current site. Upload your files via FTP or the file manager and import your databases via phpMyAdmin.
Set up email accounts again
Create the same email accounts in Plesk and configure them in your mail program. Note that existing emails may need to be migrated separately, for example via IMAP synchronization.
Test the website at the temporary address
Visit your website via the IP address or a temporary test link before changing DNS. Check forms, links, and database connections.
Change the DNS settings
Update the A and MX records so your domain points to the new server. Keep in mind that DNS changes take some time to propagate everywhere.
Check and disable the old account
Wait a few days, check that everything works correctly, and only then permanently disable the old cPanel account.
Common pitfalls
A migration usually goes smoothly, but a few things often go wrong. For example, email is often tested too late, causing incoming mail to be temporarily lost. Make sure you only change your MX records once you’re certain the new mail server is ready; consider also looking separately at business email if you want to modernize anyway.
Also, .htaccess files sometimes work slightly differently between Apache configurations and LiteSpeed servers. After migration, check that rewrite rules, redirects, and caching still function correctly. Also pay attention to whether your domain name stays with the same registrar or moves along with you; otherwise, check out the options for domain names. If you’re unsure about a full switch to another provider, you can check the steps for switching to Tandata, which also describes how support during the migration works.
Frequently Asked Questions
Can I import cPanel backups directly into Plesk?
Not directly. cPanel and Plesk use different backup formats. You need to transfer files, databases, and email settings separately rather than importing a single archive.
How long does a migration from cPanel to Plesk take?
This depends on the size of your website and the number of email accounts. A simple website can often be transferred within a few hours, while larger sites with lots of email may take a day or longer.
Will my website go offline during the migration?
If you leave the old site in place until the new environment is tested and working, there shouldn’t be any downtime. Only disable the old account once the DNS points to the new server.
Will my scripts and plugins work without modifications in Plesk?
Most standard PHP applications work without issues. Do check the PHP version and any server settings, as these may differ from your old cPanel environment.
Where can I find help if I get stuck during the migration?
Check the knowledge base for step-by-step guides, or contact your new provider’s support team.
Conclusion
A migration from cPanel to Plesk is manageable if you work step by step: make a backup, set up a new environment, test, and only then change DNS. Careful work prevents downtime and loss of email or data.