Skip to content

Moving mail off Plesk

The same shape as cPanel: Plesk’s API tells the connector who exists, what forwards where and who is on holiday, and the mail comes across over IMAP.

Read this part first

What this connector cannot do. These are the facts that decide how long your weekend is.

  • There are no filters to import. Plesk exposes none through its API, and discovery says none were read rather than reporting a bare zero. Rules the old server ran are recreated by hand, and Sieve scripts users wrote through ManageSieve are invisible to the panel — copy them out yourself before the cutover.
  • Every mailbox gets a new password, and the panel credential cannot open a mailbox. Plesk stores passwords hashed. Unless the old host has a Dovecot master user, you collect each mailbox’s password to copy its mail.
  • Plesk does not report how much mail a mailbox holds, so discovery cannot tell you how long the copy will take. The copy reports real figures once it starts.
  • Plesk’s mail API varies between versions; the connector reports what it could not read rather than assuming an empty account list.
  • A near-full mailbox may not fit its copied quota. A mailbox at about 100% of its quota on the source can fail on quota here before the last messages land. Raise the destination quota and re-run; the re-run copies only what is missing.

How it goes

  1. 1

    Add the domain here first

    Add it in MailDock, publish everything except the MX, and verify it before any mail moves. The migration will not create a domain, and mailboxes on a missing one are skipped.

  2. 2

    Read the source

    Every mailbox with its quota, plus counts of forwarders and auto-responders. Anything the connector could not read is a warning, never a silent omission.

  3. 3

    Create the mailboxes and import the rules

    Missing mailboxes are created with new passwords, shown once. Forwarders, aliases and auto-responders are imported.

  4. 4

    Run the full copy

    Mail, folders and flags over IMAP, resumable, from your new server, while the old one is still taking mail.

  5. 5

    Change the MX, then sync the delta

    The final delta is what makes cutover lossless.

  6. 6

    Walk the checklist

    Clients, new passwords, any filters recreated by hand, and only then decommission.

What you need

  • A Plesk API key (preferred) or the panel login and password, on port 8443. An admin credential sees every domain; name one to move a single customer.
  • A way to open each mailbox over IMAP: a Dovecot master user if the old host added one (Plesk does not ship one), or each mailbox’s own password. The panel credential only discovers; a job with nothing else fails every mailbox on auth.
  • Network access from your new server to the panel.

Moving from somewhere else

Where these claims come from

  • mailserver · docs/feature-docs/migration-plesk.md
  • mailserver · docs/feature-docs/migration.md