- This is the complete onboarding task flow for migrating mailboxes from Zimbra to G Suite.
- Complete each step in the order listed. 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 multiple modules, e.g., for HealthCheck for Office 365 and DeploymentPro. It is not required to install DMA for this migration scenario. However, BitTitan will be adding several modules to DMA, and these will be important to power MSPComplete feeds (which will provide further information to you about upsell and cross-sell opportunities).
- MigrationWiz now supports the capability to share migration projects across a Workgroup. Migration projects are no longer tied to individual accounts, they are tied to Workgroups. When Workgroup Administrators turn on the Project Sharing feature, all Agents besides those who are Inactive are able to view all migrations projects. For more information, visit Project Sharing in MigrationWiz.
Prepare the Source Environment
- Export 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 with 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, e.g., 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
- Create users on G Suite. Refer to the G Suite admin help article here.
- Grant MigrationWiz OAuth 2.0 access to G Suite. For guidance, see Enable access to G Suite using OAuth 2.0.
- If migrating to multiple domains, repeat these steps for each domain.
- Create the customer. KB005421
- Create the Source and Destination endpoints. KB005427
- 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 Source Environment" section of this guide.
- Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type select G Suite/Gmail.
- It is necessary to add ALL domains that will be migrated to. This means that if there are users in one project with domain names Sourcedomain.com and Destinationdomain.com, then it is important to ensure that both are added under Your Domains when creating the endpoints. When you add a domain, you need to click the "+" button.
- Enter Administrative email address.
Note: This is the account that has admin access level to the Google admin portal.
- For the Source endpoint:
- For the Destination endpoint:
- Via Group Policy Object (GPO).
Note: This is the recommended methodology, because no end user interaction is required. KB005412 video
- Via email. KB005411
- 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:
Note: If you are 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