Moving your old mailbox here

Before you start

You need the old address and an app password.

An app password is not your normal password. It is a separate code you generate at your provider, it works for one application only, and you can revoke it at any time. It cannot reach the account itself.

Your own domain

If you keep your address, one record decides everything: MX.

Moving from name@gmail.com to an address here means two different addresses, so the order does not matter: the old mailbox keeps running and the transfer never touches it.

But if you have your own domain and want to keep the same address, the source and the destination are one and the same name. What decides where new mail goes is then the MX record in your DNS — and it points either at your old provider or at us. There is nothing in between.

1. 1
   Prepare everything except MX Verify the domain with a TXT record and add SPF, DKIM and DMARC. Mail still goes where it went before — nothing changes for you.
2. 2
   The mailboxes must exist before you switch MX Mail for an address we do not have here is refused and comes back to the sender as undeliverable. In the portal such a domain is marked “MX still elsewhere” — you create the mailboxes and aliases on it as usual, before you switch.
3. 3
   Lower the TTL on MX a day ahead To five minutes. If you ever need to go back, you go back in five minutes instead of a day.
4. 4
   Switch MX, and only then start the transfer From that moment new mail arrives here and the old mailbox stops growing, so the transfer copies something that no longer moves.

Gmail

Without two-step verification Google will not offer app passwords at all.

1. 1
   Turn on two-step verification Google Account → Security → 2-Step Verification.
2. 2
   Generate an app password Security → App passwords. You get sixteen characters — copy them, they are shown only once.
3. 3
   Start the transfer in the portal Mailboxes → your mailbox → Import old mail. Pick Gmail, enter the full address and that generated password.

You do not need to fill in the server or port — both are filled in for you.

Seznam.cz

Enable IMAP first, or no application can connect.

1. 1
   Enable IMAP E-mail settings → POP3/IMAP. Without it no application reaches the mailbox, ours included.
2. 2
   Get your password ready The normal one usually works. With two-step verification on, or after a “login refused” error, generate an app password in settings.
3. 3
   Start the transfer In the portal pick Seznam and enter the address and password.

Outlook and Microsoft 365

Same as Gmail, just elsewhere in the settings.

Microsoft account → Security → Advanced security options → App passwords. In the portal pick Outlook / Microsoft 365; the server is filled in for you.

Your own server

Port 993 and an encrypted connection.

Pick Another server (IMAP) and fill in the server address. We do not support unencrypted connections — someone else's password does not travel in the clear.

Progress

It runs in the background, in batches, so you can close the portal.

A large mailbox can take hours. You can watch the progress on the same page — how many messages are done and which folder is being moved right now.

• Folders are preserved as you had them. Inbox, sent mail and drafts are matched to ours.
• An outage or a restart does not throw the transfer away. It resumes where it stopped and no message is transferred twice. That holds within one run, though — starting a new transfer starts from the beginning.
• The old mailbox is not modified. Nothing is deleted from it, it is only read.
• Trash and spam are not moved. With Gmail we also skip the “All Mail” folder — it is a copy of everything else, so every message would be transferred twice.
• You can stop it at any time. Whatever had already been moved stays in the mailbox — which is why a stopped transfer should not be restarted on your own; write to us and we will pick it up.

Security

We store the password encrypted and delete it when the transfer ends.

We need it only to fetch the mail. It is deleted whether the transfer succeeds, fails, or you cancel it. It is never printed anywhere: not in logs, not in the audit trail, not in API responses. The audit keeps only which provider and which username the mail came from.

When it fails

It is almost always the wrong password or IMAP left switched off.

• “Login refused” — the normal password instead of an app password, or IMAP disabled at the provider.
• Cannot connect — on your own server, check the address and that it listens on port 993 with encryption.
• The transfer ended with an error — do not start it again straight away. A second run starts from the beginning, so mail already moved would show up twice. Write to us and we will finish it with you.

If you are stuck, write to us and we will walk through it with you.