Introduction

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 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 Exchange Environment

Set up an administrator account for migration on the Source Exchange mailbox server. KB004725

It is necessary to add alldomains that will be part of the migration on either the Source or the Destination. This means that, if there are users in one project with domain names Sourcedomain.com and Destinationdomain.com, it is important to ensure that both of these are added under “Your Domains” when creating the endpoints. When adding a domain, you need to click the "+" button.

It is necessary to add alldomains that will be part of the migration on either the Source or the Destination. This means that, if there are users in one project with domain names Sourcedomain.com and Destinationdomain.com, it is important to ensure that both of these are added under “Your Domains” when creating the endpoints. When adding 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.

Purchase licenses. We recommend that you purchase the User Migration Bundle license for this migration scenario. 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:

Deploy DMA to users (optional). Once DMA has been deployed to users, check the Users tab in MSPComplete. This will be populated with the user accounts that have DMA installed. DMA can be deployed by these options:

Via Group Policy Object (GPO).Note: This is the recommended methodology because no end user interaction is required. ​KB005412

The following options are the most valuable for this migration scenario:

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

MX Record Cutover. Change over MX records on the DNS provider's portal. Also, include the AutoDiscover (CName) setting.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.

Send email to end users to let them know what to expect for their Outlook profile reconfiguration. If using DeploymentPro, refer to KB005799 for some sample text and screen shots that can be included in this email.

If users will be using Microsoft Outlook with G Suite, they will need to follow the instructions here, to download and install G Suite Sync for Outlook and create a new Outlook profile that connects to G Suite.

Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626