Migrate cPanel Email Without Overwriting Live Mailboxes

For a cPanel-to-cPanel web hosting migration, agree whether mail is included in the full-account transfer before copying messages separately. A website-only export does not establish that mailboxes, aliases and filters are included. New mail arriving during cutover needs a final synchronization plan.

InterServer’s complimentary migrations apply only to cPanel-to-cPanel or DirectAdmin-to-DirectAdmin web hosting transfers. VPS and dedicated-server migrations are not offered. Confirm the source, destination and mail scope through the migration support process.

Inventory the existing email service

• List mailboxes, domains, aliases, forwarders, quotas and required folders. Identify any mail hosted outside cPanel, such as Microsoft 365 or Zoho.
• Record current MX and relevant mail-authentication records. Moving the website does not require moving an external mail service.
• Identify source access, backup age, destination capacity and any existing destination messages that must be retained.

Choose the appropriate transfer route

Full-account transfer: use an authorized cPanel account archive/restore or administrator transfer workflow after confirming included mail and account settings. A full restore can replace an account; do not use it as a merge over a destination containing unrelated data. See the WHM restore precautions.

Message-only copy: create the destination mailboxes first and use an approved IMAP copy when both ends support it. The imapsync guide covers encrypted connection settings, temporary credentials and verification. Message copying does not transfer mailbox passwords, contacts, calendars or all server-side rules.

Do not unzip a mail directory over live mail

The former instructions compressed a raw mail directory and extracted it over the destination. That is not a general-purpose migration method. Directory layout, ownership, mail-storage format, indexes and simultaneous delivery matter. Creating a new mailbox and unpacking files into its directory does not prove a valid or complete transfer.

Keep filesystem-level recovery for an administrator who has verified the exact source/destination format and can manage service state and permissions. Ordinary account users should use the agreed account-transfer or IMAP route rather than experimenting on the only live mailbox.

Reconcile mail around cutover

1. Copy or restore the agreed mail scope while preserving the source.
2. Check folders, representative messages and attachments, dates, read/unread flags and any missing or rejected items. Different server totals are a reason to investigate, not automatically proof of failure or success.
3. Update mail routing only after the destination is ready. Preserve external mail records when mail is staying elsewhere.
4. Run the agreed final reconciliation for mail arriving on the old server during the transition. Do not assume a single initial copy captures later delivery.
5. Test receiving and sending through the new service and check SPF/DKIM/DMARC configuration as applicable. Avoid duplicate forwarder loops.

Retain the old service and a private backup until the mailbox owner accepts the result. Use temporary access where possible and revoke it afterward; do not put passwords or anonymous archive links in public messages.

Reference: cPanel Transfer Tool documentation. Reviewed October 14, 2026. This editorial review did not transfer a customer mailbox.