Messages, folders and attachments — on your own computer. Online transfer without an account is getting ready for launch.
Online transfer is getting ready for launch. What you see here is the interface: data entry and outgoing requests are disabled. To move mail right now, use the local client.
Deletes messages on the destination that are missing from the source. Off by default: the base mode only copies.
The source is left untouched: the base mode only copies. Credentials are encrypted before the job is queued, and the plaintext password is never stored. If you would rather not hand over the password at all, the desktop client and Docker run without our infrastructure. Get the client →
One full mailbox of up to 5 GB transfers free. Above that, the plan is chosen after the size check.
Every folder, counts from both sides, and a reason for each skipped message.
Security
For an online transfer the worker needs access to both mailboxes — otherwise there is nothing to copy the messages with. So what matters is not a promise that “we take security seriously”, but a precise description of what happens to the credentials at each step.
Security model and how to report a vulnerabilityThe connection to the site is protected by HTTPS. Before a job is put in the queue, the credentials are additionally encrypted for the worker: what goes into storage is an encrypted bundle, the plaintext password is not stored and is not written to the logs. The bundle and the key are marked for deletion when the job finishes or on timeout.
The bundle is decrypted in the worker’s memory at start-up and lives there until the transfer ends. The transfer itself is carried out by a separate imapsync process managed by the worker — the credentials are passed to that process through the environment and do not end up in the command arguments.
Messages are streamed from the old server to the new one. We do not store message contents: MoveMailbox does not become a copy of your correspondence.
The desktop client and the Docker build run entirely on your side: mail goes directly between your servers, our infrastructure is not involved. This is the strictest option, and it is free.
How a transfer runs
What happens to your data
One product · two ways to transfer
The online version is handy for a one-off transfer and keeps going after you close the browser. The Windows client uses your own machine and does not eat into the cloud limit.
Nothing to install. Connect the two mailboxes, run a size check and leave the job to our server.
The interface and the controls run locally. Mail traffic does not consume MoveMailbox Cloud resources.
A single docker compose up and the web interface comes up on your side. Mail goes through your own server, with no MoveMailbox infrastructure involved.
FAQ
The connection runs over HTTPS. Before a job is queued, the credentials are encrypted for the worker: the plain password is never stored, only an encrypted package is kept for a while. It is decrypted in the worker’s memory for the duration of the transfer. With self-hosted, the password goes to your own mail servers and no MoveMailbox infrastructure is involved.
No. The default scenario is a one-way copy and the source is left untouched. Only switch the old mailbox off once you have compared the folder counts.
One whole mailbox that measures 5 GB or less moves for free. We do not copy the first 5 GB of a large mailbox and stop halfway — the size is known before the run starts.
Start it again. imapsync checks what is already on the destination and copies only what is missing — a rerun is cheap and creates no duplicates.
Connect two servers, look at the size and decide. Or take the client and keep everything on your side.
Code on GitHub · built on imapsync · no sign-up