Cloud & Infrastructure

Zimbra migration guide: how to move off Zimbra step by step

Plan your Zimbra migration with a practical inventory, destination comparison, coexistence, DNS cut-over and post-migration checks.

Archonova Systems Engineering Team19 November 202610 min read

Why teams are reviewing their Zimbra deployment

A mail migration starts with a business requirement, not an export command. Your organisation may need a supported release, clearer operating ownership, reliable mobile access or a collaboration platform that fits its workflows. Record those outcomes first. Changing the server without agreeing how people will work simply moves existing uncertainty into a different environment.

Zimbra 8.8.15 Open Source Edition reached the end of general support on 31 December 2023. ComputingForGeeks explains the end-of-support implications, and Zimbra’s own announcement confirms the general-support date. Treat that as a release-specific lifecycle fact, not a claim that every Zimbra installation is unsupported. Check your exact version, edition, patches and any contracted maintenance before deciding what must change.

Wikipedia records that free official binaries are no longer available for later versions, although much of the project remains open source. It also describes proprietary Outlook calendar/contact connectors and ActiveSync as commercially supported, Network Edition capabilities. Outlook can still use standard mail protocols; that is different from full calendar and contact integration. Community builds and third-party extensions need their own support and compatibility review.

If the running server shows signs of compromise, handle incident containment and recovery before treating a migration as the remedy. Preserve evidence, review credentials and recover from an approved state. Moving mail does not automatically remove stolen credentials, malicious forwarding rules or the consequences of an earlier breach.

Sources: Wikipedia: Zimbra editions and binaries; ComputingForGeeks: 8.8.15 end of support; Zimbra: general-support dates.

Compare destinations against your actual workflows

Network Edition is an option for teams that want to remain with Zimbra’s commercial product. Confirm a currently supported release, the required licensed connectors, migration tooling and the operating arrangement. An upgrade and a platform migration have different risks; neither should be selected solely because the name is familiar.

Microsoft 365 combines hosted Exchange mail with collaboration and applications that vary by plan. Assess identities, retention, shared resources, desktop-client needs and the integrations you expect to retain. Google Workspace provides hosted Gmail and collaboration; verify Outlook behaviour, administration, storage and compliance features for the selected plan. Neither destination makes every Zimbra object portable without separate mapping.

ARCO Mail provides email and collaboration with cloud, on-premise and hybrid deployment choices. On-Premise and Cloud Unlimited include unlimited users; Team follows a per-user model. Assess capacity, client compatibility, data location and support around your organisation. Archonova can plan a staged move with coexistence and a pilot. UAE hosting is delivered through our partners in the UAE.

A self-hosted alternative gives your team control over the environment but also responsibility for updates, filtering, certificates, delivery reputation, backups and recovery. Check whether the selected stack actually supplies the calendar, contact and mobile functions you need. Standard IMAP moves messages; it is not a substitute for a complete groupware migration. Document an accountable operator whichever destination you choose.

Pre-migration checklist: build an inventory you can trust

List domains, users, mailbox sizes, aliases, distribution lists, shared resources and disabled accounts. Include the largest mailbox and the oldest retained data, not just the average. Find archives, delegated mailboxes, calendars, address books, briefcases, filters and local Outlook files. Classify each item as transferable, recreated, archived separately or intentionally excluded, with an owner approving that decision.

Map applications that send email: ERP alerts, scanners, website forms, monitoring, help desks and scheduled jobs. Record authentication, relay addresses, sender domains and expected message volumes. Identify gateways, mailing services and routing rules ahead of the mail server. A working employee mailbox proves little about a forgotten finance system that sends through an old IP address.

Record Outlook versions, phone clients, authentication methods and any directory or SSO dependencies. Identify DNS registrar access, authoritative nameservers, current MX and TXT records, certificate ownership and public addresses. Confirm retention, legal hold, recovery and location requirements with the responsible people. Use a controlled inventory file; do not place passwords or message contents in a shared planning document.

Step 1: agree acceptance, recovery and ownership

Write what successful migration means before choosing a tool. Acceptance should cover inbound and outbound delivery, message history, folders, attachments, calendars, contacts, shared access and the required clients. Name the person who approves each area, a technical cut-over owner and a business contact who can decide whether to proceed when a test fails.

Take an approved backup and verify a restore path before copying data. Decide how long the source remains available, who can access it and when its records can be removed under the retention policy. Record rollback prerequisites and thresholds. Changing MX back is not a complete rollback once users have created new mail or calendar items on the destination; reconciliation must be planned too.

Step 2: prepare and secure the destination

Create domains, users, aliases, groups and shared resources from the reviewed inventory. Set mailbox capacity, access roles, multi-factor authentication and recovery ownership. Establish the destination’s supported client configuration and certificate chain. Keep administrator access narrowly scoped; migration credentials should be temporary where tooling supports that and removed after reconciliation.

Test outbound delivery and DNS authentication with controlled accounts before changing production routing. Where you run your own mail infrastructure, check provider-managed reverse DNS, forward DNS, relay restrictions and monitoring. Set up backup and restore procedures rather than waiting until after go-live. Record the actual destination configuration so troubleshooting does not depend on one administrator’s memory.

Step 3: pilot representative users and data

Choose a small pilot that includes ordinary mail users and difficult cases: a large mailbox, delegated access, recurring meetings, mobile sync and an application sender. Use tooling suited to the source and destination. A trial IMAP copy can validate messages and folders, but contacts, calendars, permissions and rules need a separate supported method or an explicit recreation plan.

Compare item counts alongside samples of old and recent mail, nested folders, attachments and non-English content. Counts can differ because of deduplication, exclusions or source objects, so investigate differences rather than assuming equal totals mean completeness. Test meeting updates, organiser identity, shared-calendar permissions and reply behaviour. Capture exceptions and obtain pilot sign-off before adding more users.

Working through this in your own environment?

Send us the context and we'll tell you plainly what we'd do first — and whether it's a fit for us at all.

Talk to our team

Step 4: run controlled coexistence and staged copies

Coexistence is a routing design, not just two servers being switched on. Decide which system receives each domain’s mail and how messages reach users on the other system. Use validated connectors, routing rules or a migration subdomain according to the platforms’ capabilities. Prevent loops and duplicate delivery; ensure unknown recipients are rejected or routed deliberately rather than silently dropped.

Perform the initial bulk copy while users continue on the agreed source system. Track per-mailbox progress and failures, then run incremental synchronisation using the tool’s supported method. Schedule batches around storage and network capacity. Explain which account users should send from during each phase. Calendar free/busy, shared resources and address-book consistency may need additional configuration during coexistence.

Step 5: cut over MX, SPF, DKIM, DMARC and autodiscover

Prepare a change sheet with the current records, proposed records, DNS owner and reversal instructions. Lower the relevant TTL sufficiently in advance if the plan calls for it, allowing the previous TTL to expire before cut-over. DNS caches and remote senders do not all switch simultaneously. Keep the old receiving path functional during the transition and monitor both systems.

MX decides the inbound mail destination. Change it only after the destination can receive the production domain and route every required recipient. Do not assume equal-priority MX records divide users between platforms; remote senders do not know your mailbox batches. Validate inbound tests from independent external domains, delivery to aliases and replies to those test messages.

SPF should remain one record for each sending domain, authorising the legitimate source, destination and other senders needed during coexistence without exceeding lookup limits. Publish the destination’s DKIM selector and verify actual signatures. Existing and new selectors can coexist while each is used. Check DMARC alignment for real messages and review reporting before tightening policy; authentication failures from overlooked applications can interrupt business mail.

Update autodiscover and any related client-discovery records according to the destination’s documented requirements. Validate HTTPS endpoints and certificates, not just record resolution. Confirm that Outlook and mobile devices connect to the intended system with the correct authentication. Check CalDAV, CardDAV or ActiveSync configuration where used. After the agreed final delta copy, reconcile both receiving paths before declaring the source idle.

Common pitfalls that a mail copy will not solve

Calendar migration can change recurring meetings, exceptions, organiser ownership or room bookings. Imported invitations may behave differently when attendees reply. Test those cases with the people who rely on them. Similarly, recreating shared-mailbox permissions without reviewing delegation can expose information or prevent an assistant from handling the account. Preserve access intent, not merely the old configuration.

Old client profiles can continue talking to the source after DNS changes. Local archives may never have been stored on Zimbra, and cached copies can conceal missing server-side data. Give staff clear configuration instructions and an escalation route. Avoid migrating deleted or inactive accounts indiscriminately; agree retention and access for former employees with the responsible owner.

Forwarders, scanners and third-party mail services are easy to miss. Some need different SMTP authentication or relay rules on the destination, and forwarding may affect authentication results. Do not solve a failed test by opening an unrestricted relay. Record the sender, permitted route and expected authentication, then retest. Remove obsolete source authorisations only after confirming those applications no longer depend on them.

Post-migration checklist and operational handover

Confirm mail flow in both directions, DNS authentication, aliases, groups, shared access and supported clients. Review failed-copy logs and unresolved differences with mailbox owners. Run a final source-versus-destination reconciliation, including late-arriving messages. Check retention, backup schedules and a representative restore. Acceptance is a recorded decision based on these checks, not the moment the new login page loads.

Monitor queues, rejected messages, certificate expiry and authentication reports during the agreed observation period. Document support contacts, incident escalation, administrator roles and joiner/leaver tasks. Give users concise instructions for their actual devices. Keep a controlled exception register with owners and dates for follow-up, so unresolved calendar or archive issues are not lost when the migration team hands over.

Retire the source only when reconciliation, recovery, retention and business sign-off permit it. Revoke temporary credentials, remove obsolete DNS records and relay permissions, and dispose of data using the approved policy. If you need a starting point, request the free Zimbra migration readiness check: Archonova reviews your inventory and sends a written outline with dependencies, coexistence and an optional next-step proposal.

What to do next

Bring your Zimbra version, mailbox totals, client requirements and DNS owner. Start with a readiness outline before setting a production cut-over date.

Questions about this guide.

Have a project where this applies?

Tell us what you're running today and what you need it to do. We'll come back with a straight assessment and a route forward.