Migrate from Zimbra to Microsoft 365 Without Losing an Email

Many companies leave their Zimbra server for Microsoft 365: no more mail-server maintenance, and tighter integration with Outlook, Teams and OneDrive. The good news is that a Zimbra mailbox speaks standard IMAP — so it migrates cleanly into Exchange Online, with folders and messages preserved exactly, and no downtime for your users as long as you respect the order of the steps.

What gets migrated from Zimbra

A Zimbra mailbox holds several types of data that don't all follow the same path:

• Emails and the folder tree — transferred over IMAP, with read/unread state and subfolders preserved.
• Contacts — exported as CSV or vCard from the Zimbra webmail, re-imported into Outlook / Exchange Online.
• Calendars — exported as .ics and re-imported into the Microsoft 365 calendar.
• Shared folders and distribution lists — rebuilt on the target as Microsoft 365 groups.

Key point: IMAP transfers emails but not contacts or calendars. Those two data sets are handled separately by export/import — a classic oversight that leaves users without an address book on cutover day.

Step 1 — Audit the Zimbra platform

List every account, its data volume and its number of folders. Note aliases, distribution lists and service accounts. On the domain side, identify who manages the DNS zone, where the MX records point and what their TTL is. Lower that TTL to 300 seconds a few days before cutover: propagation will then be nearly instant on the day. Finally, confirm IMAP is enabled on the Zimbra server and note its hostname and port (993 over SSL).

Step 2 — Provision Microsoft 365

Create the tenant, assign licenses (Business Standard, Business Premium or Exchange Online as needed), then create each user with their final address. Add your domain in the Microsoft 365 admin center and verify it with the supplied TXT record. At this stage email still lands on Zimbra: you're only preparing the target.

Step 3 — Migrate the emails over IMAP

Microsoft offers a native IMAP migration that fits Zimbra perfectly. In the Exchange admin center, create an IMAP migration batch: you supply the Zimbra server, port 993, and a mapping file that pairs each source address with its target Microsoft 365 mailbox. Exchange Online then copies the emails in the background, without touching the Zimbra server. A first full pass is followed by incremental passes that only pull new messages — that's what lets you keep Zimbra live throughout the copy. Kick the batch off several days ahead so the heaviest mailboxes complete their initial sync early, and place very large accounts in their own batch so they don't slow the rest.

As long as the MX records still point to Zimbra, your users work as usual: the migration runs invisibly in the background.

Step 4 — Contacts, calendars and files

From the Zimbra webmail, export contacts (CSV/vCard) and calendars (.ics), then re-import them into Outlook or directly into Microsoft 365. If you stored documents on a network share or in the Zimbra Briefcase, move them to OneDrive or SharePoint, preserving the folder tree and sharing permissions.

Step 5 — Cut over the MX and verify

Once the last incremental pass is done, change the MX records to point at Microsoft 365, then update SPF, DKIM and DMARC to keep deliverability intact. Thanks to the lowered TTL, propagation is quick. Then verify a sample of mailboxes (message counts, folders, contacts, calendars), recreate Outlook profiles and reconfigure accounts on mobile.

Common Zimbra → Microsoft 365 pitfalls

• Forgotten contacts and calendars — IMAP doesn't migrate them; export/import is mandatory.
• Rate limits — the source IMAP and Microsoft quotas spread a large migration over several days.
• Special folders — Zimbra trash and tags may be named differently; check the mapping.
• Duplicates — never re-run a batch without resume; use the existing batch's incremental passes.

How much it costs: Yuna7 vs an IT contractor

Having an IT contractor migrate Zimbra to Microsoft 365 often costs several hundred dollars, with quotes and lead times. Yuna7 automates the cutover and you only pay for what you actually use — you can even try it for free.

Let Yuna7 migrate Zimbra to Microsoft 365 for you

Describe your migration in one sentence — "move my Zimbra mailboxes to Microsoft 365" — and Yuna7's AI handles the rest: it audits the Zimbra server, provisions the tenant, launches the IMAP migration, imports contacts and calendars, cuts over the DNS and verifies the result, asking you to approve each sensitive step. You stay in control from start to finish, for far less than the cost of a technician.