This is the complete onboarding task flow for migrating mailboxes from Zimbra (version 6 and later) to On-Premises Microsoft Exchange versions 2007, 2010, 2013, or 2016. Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.
MigrationWiz no longer supports TLS 1.0. TLS 1.2 is now required. Verify TLS version and update, if necessary, before starting the migration.
MigrationWiz is a migration solution (not a synchronization solution) and will NOT propagate updates, deletes, or moves of the items previously migrated in the first migration pass because we do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.
MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all Agents besides those who are Inactive can view all migrations projects. For more information, visit Project Sharing in MigrationWiz.
Prepare the Source Environment
Note: Users will need to enter usernames on the Zimbra side, even when using an admin account.
- Export the list of users to a CSV file. This will be used when adding users to your MigrationWiz mailbox project. KB005011
- Inform users to split up folders that have a very large number of items.
- Zimbra will exhibit poor migration performance for folders with a large number of items.
- Calendar folders can be slower to migrate when the data is complex. For example, recurring calendar meetings result in a much higher number of calendar events.
- Use existing credentials.
- Create a new admin account for migration. This will create an additional admin account with the password of 'test123':
zmprov ca email@example.com test123 zimbraIsAdminAccount TRUE
- Transform a normal existing user account into an admin account (in this example future-admin will become an admin):
zmprov ma firstname.lastname@example.org zimbraIsAdminAccount TRUE
Prepare the Destination Environment
- Set up user accounts.
- Create an admin account for migration that has full access permissions to all mailboxes. KB004725
Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User MigrationWizNotes:
- In the PowerShell script above, change the -User account to match the name of the admin account that was set up for migration.
- Any user account that is a part of the domain administrator, schema administrator, or enterprise administrator groups will not have any administrative rights to mailboxes, no matter how many permissions are granted. A security default of Exchange Server is to explicitly deny any user that is a member of these groups. This is why we recommend creating a new user account specific for migration.
- Set up a remote PowerShell session with Exchange 2010+. KB005111
- To manually grant administrative access for migration, execute the following PowerShell command in the Exchange Powershell Console:
- Increase message size limits. KB004613
- Increase maximum accepted content length. KB004609
- Increase maximum receive message size. KB004532
- Increase maximum accepted request length. This is only valid if your Destination server is running Exchange 2007. KB004610
- Create the customer. KB005421
- Create the Source and Destination endpoints. KB005427
- For the Source endpoint:
- Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Zimbra 6.5+.
- Enter Zimbra server URL KB004331
- Click the Provide Credentials radio button, and enter the admin account credentials. These are either your existing admin credentials or the credentials for the account that was created under the "Prepare the Source Environment" section of this guide.
- For the Destination endpoint:
- Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Exchange Server 2003+.
- Enter the OWA URL KB004392
- Click the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the "Prepare the Destination Environment" section of this guide.
- For the Source endpoint:
- Purchase User Migration Bundle licenses. User Migration Bundle licenses allow multiple types of migrations to be performed with a single license. They also allow DeploymentPro to be used to configure Outlook email profiles. Refer to these articles for more information:
- Create a Mailbox Migration project. Read the How do I create a new migration project? article for more information.
- Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
- Set the Project Advanced Options. KB004834
The following options are most valuable for this migration scenario:
- Set Maximum concurrent migrations. We recommend setting this to a very low value, such as 5, to ensure that server utilization does not go above 80%. If the Source Zimbra server is running low on resources, it can result in email being migrated as blank. If the Source server has enough server resources, set this parameter based on the bandwidth guideline of three (3) mailboxes per 1Mbps of bandwidth. Therefore, for example, if there is a 10Mbps connection, we recommend setting the maximum concurrent migrations parameter to be 30. If the Source server has very few available server resources (e.g., it is running low on memory or it has very high CPU utilization), we recommend setting this value to a lower number to avoid overwhelming the Source server with requests.
- Under Support/Support options, add:
Note: If migrating in batches and mail coexistence is required, you will not be cutting over the MX records until your final batch of users has been migrated, and you must perform this extra step:
- Set up Zimbra mail forwarding. KB004256