Migrate from Plesk to cPanel (websites, databases, email and DNS)

A Plesk to cPanel migration is a common move when a site outgrows its old host or when you want cPanel's tools and WHM reselling. Plesk backups cannot be restored directly by cPanel, so the reliable path is to copy each piece separately: files, databases, email and DNS. This guide walks through that process for a move to MdmHost cPanel hosting.

Before you start

• Plesk access (the customer panel is enough; server administrator access makes it easier).
• An MdmHost cPanel account with enough disk space. See move a website to MdmHost cPanel for an overview.
• A list of domains, subdomains, databases, mailboxes and scheduled tasks in each Plesk subscription.

Take a full Plesk backup first

Even though you will copy items manually, keep a complete backup as a safety net. In Plesk go to Websites & Domains → Backup & Restore → Back Up, select the whole subscription (configuration, mail and user files) and download the result.

Plesk to cPanel migration: copy the website files

1. On Linux Plesk, document roots usually live in /var/www/vhosts/example.com/httpdocs. In Files, compress httpdocs into a zip and download it, or pull it over SFTP.
2. In cPanel open Files → File Manager, go to public_html (main domain) or the addon domain's folder, upload the zip and choose Extract.
3. If you have SSH on both sides, rsync is faster and resumable: rsync backups and sync.

Move the databases

1. In Plesk go to Databases, pick each database and choose Export Dump (or use phpMyAdmin → Export).
2. In cPanel create the database and user in Databases → Manage My Databases. cPanel prefixes names with your username, for example user_shop.
3. Import the dump with phpMyAdmin → Import, or over SSH as shown in mysqldump backup and restore.
4. Update the site's config file (wp-config.php, .env, configuration.php) with the new database name, user and password. The host stays localhost.

Windows Plesk servers

If the Plesk server ran Windows, the site may rely on web.config rules, ASP.NET or MSSQL. cPanel runs Linux with LiteSpeed, so rewrite rules must move into .htaccess, and ASP.NET or MSSQL applications need a rewrite or a different platform.

Migrate email with IMAP sync

Mailboxes rarely restore cleanly between different control panels, so the dependable method is to create the same addresses in cPanel → Email → Email Accounts and copy the messages over IMAP:

1. List every mailbox on Plesk with its approximate size.
2. Create the same addresses on cPanel and give each enough quota.
3. Run an IMAP sync per mailbox from the old server (by IP or hostname, since DNS still points there) to the new one. imapsync between servers explains the command; migrate email to cPanel over IMAP covers the cPanel side.
4. After the DNS switch, run the same sync again. imapsync skips messages it has already copied, so the second pass only picks up mail that arrived in between.

Recreate DNS records

Open Websites & Domains → DNS Settings in Plesk and note custom records: TXT verification records, SPF, DKIM, CNAMEs for third-party services, SRV records. Add the ones you still need in cPanel → Domains → Zone Editor. Do not copy old A and MX records that point to the Plesk server.

Switch DNS with minimal downtime

1. One or two days before the move, lower the TTL of the A, AAAA and MX records at the current DNS host to 300 seconds. See DNS TTL strategy for a server migration.
2. Test the new copy before switching: add the new server IP for the domain to your computer's hosts file and browse the site.
3. Freeze changes on the old site (no new orders, posts or comments), take a final database export and import it on cPanel if content has changed since the first copy.
4. Either point the A records to the new IP, or change the domain's nameservers to the ones in your MdmHost welcome email. Changing records is faster when the TTL is already low; nameserver changes can take up to 24–48 hours.
5. Keep the old account running for at least a week so slow resolvers and delayed mail still land somewhere.

Post-migration checks

• The site loads over HTTPS with a valid certificate. AutoSSL issues it once DNS points to MdmHost; run it from cPanel → Security → SSL/TLS Status if needed.
• Forms, logins, checkouts and uploads work, and there are no database connection errors.
• Sending and receiving email works from webmail and from your mail client, and SPF/DKIM pass in cPanel → Email → Email Deliverability.
• Cron jobs are recreated under cPanel → Advanced → Cron Jobs with the new paths (/home/username/…).
• The PHP version in cPanel → Software → MultiPHP Manager matches what the old server used.
• Plesk scheduled tasks are recreated as cPanel cron jobs.

Troubleshooting

• 500 errors after upload: Plesk-specific php_value lines or nginx-only rules may be in .htaccess; remove them and set PHP options in MultiPHP INI Editor.
• Database import fails on collation: change utf8mb4_0900_ai_ci to utf8mb4_unicode_ci in the dump, or re-export with compatible settings.
• Permissions: files should be 644 and folders 755 under your cPanel user.

FAQ

Can cPanel restore a Plesk backup file directly?

No. Extract files and database dumps from the Plesk archive and import them separately, as described above.

Does WHM's Transfer Tool work with Plesk?

WHM's Transfer Tool is built for cPanel-to-cPanel moves. For Plesk sources, the manual method in this guide is the dependable route.

Will email passwords carry over?

No. Mailboxes are created fresh in cPanel, so users get new passwords unless you set them to match.

How long does a Plesk to cPanel move take?

A small site takes an hour or two of work; with a lowered TTL the DNS switch is usually visible within minutes.

Next steps

• Plesk email migration with IMAP import
• Migrate WordPress to MdmHost
• Plan TTLs for a migration