Zimbra to On-Premises Exchange Migration Guide
- 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 order. Links to corresponding Knowledge Base articles are provided.
- The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. This is an Agent which includes modules for HealthCheck for Office 365 and DeploymentPro. Deploying DMA to end users is a prerequisite if you will be using HealthCheck for Office 365 and/or DeploymentPro.
- We strongly recommend that you use HealthCheck for Office 365 to check ahead of time to see if end user hardware and software is compatible with Office 365. Note: HealthCheck for Office 365 is a free utility. KB005407
- DeploymentPro can be used to configure the Outlook profiles. Note: DeploymentPro requires licenses to be purchased before it can be used. Refer to Scenario 2 in KB004875 to read why it is recommended (but not mandatory).
Prepare the Source Environment
- 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.
- Ensure that you have admin credentials available for use during migration.
- 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
- Test mailbox access. KB004332
- Make sure the neccessary ports to connect to the Zimbra server are open. Access to SOAP web services is needed for migration. This is via both regular and admin user mode. Ports 80, 443, and 7071 are the common ports. KB004139
Prepare the Destination Environment
- Set up user accounts.
- Create an admin account for migration that has full access permissions to all mailboxes. KB004725
- 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:
- Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User MigrationWiz
- In the PowerScript 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.
- 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
- For the Source endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Zimbra 6.5+.
- Enter Zimbra server URL KB004331
- Click on 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 Source Environment section.
- For the Destination endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Exchange Server 2003+.
- Enter the OWA URL KB004392
- Click on the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the Prepare the Destination Environment of this guide.
- Launch DeploymentPro.
- Go to All Products > DeploymentPro and follow the prompts to launch.
- Select a customer from the list by clicking on the customer name. Note: The status column will show enabled when a customer account has had DMA deployed.
- Configure the customer DeploymentPro module:
- Enter the Domain.
- Select the Destination endpoint.
- Checkmark the Auto-populate box.
- In the Client Interface Configurations section, upload your company logo and add supporting text. Note: We strongly recommend doing this, because this is the logo and text that end users will see in a desktop pop-up when they are prompted to reconfigure their Outlook profiles. If you do not upload your own logo, the default BitTitan logo will be included instead.
- Save and continue.
- Either select all users (by checkmarking the box to the left of the Primary Email column heading), or select the individual users (by checkmarking the boxes to the left of the user email addresses). Note: You will need to purchase DeploymentPro licenses for each user that will be using DeploymentPro. KB004647
- Click on the Run Module button.
- Set the date and time for the Outlook profile configuration to occur, and click on the Run Module button.
- The DeploymentPro module will install on user devices immediately, and then run silently until this date.
- The profile cutover date should be set to a date and time that is shortly after MX record cutover.
Watch this video to see a walk-through of the steps below.
- Create the Mailbox Migration project. KB004380
- Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
- 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: ZimbraCalendarExpandInstances=1 KB005122
- 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