Migrating email from cPanel to Plesk with Plesk Migrator: mailboxes, MX and IMAP verification
How Plesk Migrator transfers email mailboxes from cPanel, what to check on MX and SPF before cutover, and how to verify via IMAP that all mail has arrived.
UptimeMag editorial team · 18 November 2026 · 3 min read

If you've already read our guide on moving a site from cPanel to Plesk with Plesk Migrator, you've likely hit the same sticking point: file and database transfers go smoothly, but email doesn't. Here's the missing piece, updated 18 November 2026.
What Plesk Migrator actually transfers for mail
When migrating from cPanel, Plesk Migrator transfers domains with all objects, including email accounts, and copies mail content. If you want to move only mail without touching web and databases, in the migration screen select Copy mail content and deselect the other copy options: in this case, according to the official Plesk knowledge base, only domain configuration and mail content will be migrated.
Two limitations to know before you start. First: Plesk Migrator doesn't support migrating mail accounts on subdomains, so if you have mailboxes like user@mail.example.com on cPanel, you'll need to handle them separately and manually. Second: Mailman mailing lists aren't included in the standard package. Plesk Migrator transfers only basic mailing list settings: list administrator and subscribers; mailing list archives and other settings aren't transferred because Plesk doesn't manage them. To move the full configuration as well, use Mailman's config_list tool via SSH.
The check that config.ini does for you: mail-messages-delta-limit
The migrator's configuration file (config.ini) includes a little-known but useful parameter for anyone needing to give clients a number before cutover: mail-messages-delta-limit. It compares the message count between source and destination mailbox after migration. If the difference exceeds the set value, Plesk Migrator logs an error. The default value is 10 messages, as stated in the sample configuration file published on doc.plesk.com. For a customer with thousands of emails in a single mailbox, 10 is a tight threshold: if you have heavyweight mailboxes, it's worth raising it in config.ini before running the migration to avoid false alarms on mail still being delivered on the IMAP side.
The same configuration file also manages conversion between mail storage formats: the courier-to-dovecot-migration option, active by default, converts mail directories when migrating from Courier to Dovecot; if disabled and files aren't converted, POP3 clients may receive duplicate messages after migration.
MX, SPF and cutover: what to check before shutting down the old server
Plesk Migrator doesn't touch your domain's external DNS zone: it moves mailboxes and panel-side configuration, but MX records remain those published by your DNS provider. Before shutting down the old mailbox on cPanel, the practical order is:
- Complete the migration with Copy mail content, leaving the old server running.
- Verify via IMAP client (or with an
openssl s_client -connect newserver:993command followed by IMAP login) that all folders and messages are present on the new server, comparing the count with what's shown in the mail-restore log (path shown in config.ini:<session-dir>/mail/<domain>/<mailbox>/mail-restore.log). - Only after verification is complete, update the MX record and, if necessary, the SPF record to include the IP of your new Plesk server: as long as the old MX remains active, incoming mail continues to pass through the old server and any migration error won't result in message loss.
- Wait for DNS propagation (the old zone's TTL tells you how long) before shutting down the old server.
The known bug: mail disappearing from Plesk webmail
A documented case in the official knowledge base concerns mailboxes that, after migration from cPanel, appear empty in Plesk webmail despite having files on disk. The cause identified by Plesk is that emails migrated from cPanel are in mdbox format, which isn't yet implemented in Plesk. The official solution involves converting the email format to maildir on the cPanel/WHM side and then relaunching the sync from the Plesk panel, from Tools & Settings > Migration & Transfer Manager, selecting the domain and clicking Re-sync. If a customer reports "I can't see old mail" after a cPanel→Plesk move, it's the first thing to check before opening a support ticket.
Sources: official Plesk Migrator documentation on docs.plesk.com and doc.plesk.com, knowledge base support.plesk.com, forum talk.plesk.com.
Written with the help of artificial intelligence and checked by the editors (EU AI Act, art. 50).