Skip to content
Try it free
Ready for pilot

Bring your old messages with you.

Connect to the mailbox at your old provider over IMAP, map the folders and import the messages. The setup wizard draws up a migration plan; the MX record changes last.

Try it freeMigration steps

Nothing is deleted or flagged at the source; you can repeat the import as often as you like.

Import from your old providerSample content

imap.eski-saglayici.exampletarget mailbox:ayse@atolye.example

Importing messages1,580 of 2,460 messages
  • InboxDone
  • Sent ItemsImporting
  • ArchiveQueued

Migration plan

  1. Lower the MX record's TTLdone
  2. Create mailboxesdone
  3. Import old messagesin progress
  4. Switch the MX recordto do
  5. Confirm new mail arrivesto do

Nothing is deleted or changed at the source.

What the import preserves.

Messages arrive true to the original, and folders land in the right place.

  • Folder mapping

    Inbox, Sent, Drafts, Junk and Trash are mapped automatically, and Turkish and English folder names are recognized. Your own folders are created with the same names.

  • Flags and dates

    Read, starred and answered flags and each message's original received date are preserved.

  • No duplicates

    Re-running the import skips messages that already arrived, and a message that comes both ways during the MX switch isn't duplicated.

  • Secure connection

    The old server is reached only over an encrypted connection. The password never appears in any response or log and is deleted when the import ends.

Migration in five steps.

The dashboard's migration plan follows the same order and shows each step's status from real data.

  1. Step 1: Lower the TTL

    Lower your current MX record's TTL to 300 seconds, so the new record spreads within minutes when MX changes.

  2. Step 2: Create mailboxes

    Connect your domain and create a mailbox for each person. New mail doesn't come to Mühür Mail until MX changes, so nothing stops at this step.

  3. Step 3: Import old messages

    Connect to the old server over IMAP, confirm the folder mapping and start the import.

  4. Step 4: Switch the MX record

    Point the MX record to Mühür Mail; remove the old provider's MX and SPF entries once the move is done.

  5. Step 5: Confirm delivery

    Send a message from outside and see it arrive; run the import once more to collect anything that reached the old server in between.

The import never deletes or flags anything at the source; re-running the same job skips messages that already arrived.

Who runs the migration?

The organization admin uses the migration tool: for each mailbox they enter the old server's address, username and password (an app password if two-step verification is on), confirm the folder mapping and follow the progress.

  • A connection test first: folders and message counts are listed
  • Optionally only messages after a certain date
  • Progress per folder; a message that can't be imported doesn't stop the job
  • Cancel a job and retry with the same settings
  • Messages over 35 MB are skipped and counted separately

Related features

All features

Frequently asked questions

Ask us a question
Will email stop during the migration?

No. Until mailboxes and the import are ready, the MX record points to your old provider and new mail keeps arriving there. After switching MX, run the import once more to collect anything that reached the old server in between.

Which providers can I import from?

Any provider whose IMAP accepts a username and password (or app password): Gmail and Google Workspace, Yandex, Zoho, and hosting mail on cPanel or Plesk. Microsoft 365 requires Microsoft sign-in for IMAP, so messages there move through a mail app.

Are contacts and calendars moved too?

The import covers messages. You can bring contacts into webmail with a vCard or CSV file; Mühür Mail doesn't have a calendar yet.

Let's plan the move together.

Tell us how many mailboxes you're moving and your current provider; we plan migrations step by step with pilot organizations.

Try it freeMigration steps