- This is the complete onboarding task flow for migrating mailboxes from On-Premises Exchange servers (version 2007 and later) to G Suite.
- Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.
- If your Source server is running Exchange version 2003, or Small Business Server (SBS), refer to KB004965, for the steps to prepare your Source server.
- 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 Exchange Environment
- Set up an administrator account for migration on the Source Exchange mailbox server. KB004725
- EWS must be working on Source Exchange server. KB004392
- Test mailbox access. KB004616
- This is only relevant for Exchange 2010+. Exchange versions 2007 and earlier do not have throttling policies.
- If running Exchange 2010 and later, we highly recommend disabling the Exchange throttling policy in order to speed up your migrations.
- Follow the instructions under Option 1 in KB004945 to disable throttling for just the admin account, rather for than all users.
- Disable the Exchange throttling policy during migration. KB004945
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.
- For the Source 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 Source Environment" section of this guide.
- For the Destination endpoint:
- 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 Destination domain.com, it is important to ensure that both of these 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.
- Create the Mailbox Migration project. KB004380
- Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
- Set Maximum concurrent migrations. 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 a very high CPU utilization), we recommend setting this value to a lower number to avoid overwhelming the Source server with requests.
- Add folder mapping:
FolderMapping="^INBOX/->"under Support/Support options.
Note: This will map folders to the root label on the Destination mailboxes, rather than under inbox/labelname. KB005068
- The following options are the most valuable for this migration scenario:
Note: If you are migrating in batches and coexistence is required, you will not be cutting over the MX records until your final batch of users has been migrated, and you must set up mail forwarding.