Zimbra Migration FAQs

MigrationWiz supports migrations from Zimbra Version 6 or later, and requires TLS 1.2. Versions prior to 6, and TLS 1.0, are no longer supported. Verify your version before beginning the migration process.

We support Zimbra migrations to G Suite, Microsoft 365, and Exchange 2013+. Zimbra is only supported as a source, not as a destination. 

The following sections cover questions concerning Zimbra as a source and Zimbra migrations. Questions for the destinations listed above are found in the Google, Microsoft 365, and Exchange sections of the Help Center. 

Zimbra URL

The Zimbra URL you specify on your MigrationWiz project should be the one you use to access your webmail. This usually looks like http://zimbra.xxxxxxcompanyname.com.

You will then be asked for your user name and password. 

Export user list from Zimbra to CSV

  1. Open Zimbra Admin.
  2. Select Account.
  3. In the Search box, type the domain name to be exported.
  4. On the Toolbar Zimbra Admin, select the Download button.
  5. Save the CSV file generated.

Zimbra Connections

Zimbra server connection modes

There are two modes to connect to a Zimbra server, Regular mode and Admin User mode.

  1. In regular user mode, we need access to SOAP web services, which are typically the following:
    1. ​ on port 80 if it is an HTTP connection;
    2. on port 443 if an HTTPS connection.
  2. In admin user mode, we also need access to SOAP web services, typically:
    1. ​On port 80 and 7071 if the Zimbra URL is HTTP;​
    2. On port 443 and 7071 if the Zimbra URL is HTTPS.

You need to connect using both ports; some operations will go over the admin port, while others will go over the regular port.

Testing Zimbra server connection

This tool works best when using Internet Explorer for the browser. To test if we can access your Zimbra server, perform the following steps:

  1. Go to: https://dnswonder.bittitan.com/Tools/ZimbraTest.aspx
  2. Enter the URL of your Zimbra server, as well as your username and password.
  3. Click on Test.

In the Test Results section, you will see the status of the test we performed. If all the lights are green, you can configure your connector using the same URL.

Zimbra forwarding addresses

If you are not cutting over an entire domain/organization at once by changing MX records, you can perform a phased migration and setup coexistence by setting up forwards on the mailboxes you wish to migrate. The Zimbra wiki has more information on Relaying & domain forwarding.

Zimbra Calendars

Exceptions to recurring calendar meetings

These are exceptions to a series of calendar meetings that have been created. When you create an event, such as a series, the same event will repeat every n times, depending on the recurrence type.

Once this has been created, you can still update some instances independently:

  • Removing certain instances
  • Updating certain instances

Each updated or removed instance is called an exception, because they do not match the initial rule that defines the series.

Are exceptions migrated?

  • Yes, exceptions are migrated. From all supported Source systems to all supported Destination systems, the series, including any appointments with exception dates/times, will be migrated. However, the description text and attendee exceptions will not be migrated.
  • *Note* A cancelled on-going recurring event in Zimbra will be migrated over to M365 as a recurring event without an end date; this is because Zimbra does not give an end-date to a cancelled recurring event. 

When migrating from Zimbra, by default, exceptions will not be migrated. However, they will be migrated, if the following MigrationWiz project Advanced Option is added: ZimbraCalendarExpandInstances=1

In that case, the series, including any appointments with exception dates/times, will be migrated. However, the description text and attendee exceptions will not be migrated.

When migrating to G Suite, from all Source environments, no exceptions will be migrated.

IMAP and POP do not support calendar (or contacts) for migration, due to API limitations, thus exceptions will not be migrated.

Was this article helpful?
0 out of 1 found this helpful