Copy Email Between IMAP Servers: Planning and Verification

An IMAP copy transfers messages and folders between mail servers. It does not migrate an entire hosting account, create destination mailboxes or reproduce every mail setting. Choose the transfer method from the source and destination capabilities before changing mail routing.

IMAP copy versus a full-account transfer

For a compatible cPanel-to-cPanel or DirectAdmin-to-DirectAdmin web hosting move, first agree the full-account scope with support. It may already include local mail and account configuration; a separate message copy can then be needed for final synchronization. InterServer does not offer VPS or dedicated-server migrations, and cross-panel or external-provider mailbox moves described here are self-managed.

When using IMAP independently, create each destination mailbox, confirm its quota and credentials, and identify its actual server hostname. Messages accessible only in a local desktop archive are not available to an IMAP copier. POP3 clients may keep or delete downloaded mail according to their settings; POP3 does not universally delete every message after retrieval.

Choose a current, documented tool

The earlier version of this page named IMAP Copy without a dependable download source and showed a plain-port configuration that skipped Sent folders. Those instructions are withdrawn rather than presented as a supported installation procedure.

For a current command-line option, see the imapsync guide and the maintainer’s documentation. Choose a release with documented authentication and certificate verification for both providers. Do not upload mailbox passwords to an arbitrary online transfer service.

Inventory folders and settings

• Record each mailbox, source folder list and required Sent, Archive, Drafts and custom folders. Exclude Trash or Spam only when the owner deliberately agrees; skipping folders is not a complete migration.
• Check folder mapping and delimiter differences. Similar names can refer to different special folders on the destination.
• Handle contacts, calendars, rules, signatures, aliases, forwarding, passwords and two-factor authentication separately. Copying IMAP messages does not recreate these automatically.
• Allow for provider connection limits, destination quotas, oversized messages and authentication policies.

Test, copy and reconcile

Start with one authorized test mailbox or a deliberately scoped folder. Use encrypted connections with certificate and hostname verification, protect temporary credentials, and review the tool’s logs. Confirm destination folder placement, representative dates, flags, messages and attachments before broadening the copy.

Preserve the source. Avoid delete/expunge options during an initial migration and do not assume every tool’s retry or duplicate behavior is identical. A failed run can leave a partial copy that needs review.

Agree the mail cutover and final reconciliation: new mail may continue arriving on the old server while DNS caches update. Test sending and receiving through the intended destination and check mail-authentication records. Keep the source and private recovery material available until the mailbox owner accepts the result.

For cPanel-specific planning, use the cPanel email-transfer guide. Reviewed October 14, 2026. This is a planning guide, not a claim that a customer mailbox transfer was executed.