G Suite to Hosted Exchange Migration Guide
- This is the complete onboarding task flow for migrating mailboxes from G Suite to Hosted Exchange.
- 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. Deploying DMA to end users is a prerequisite if you will be using DeploymentPro.
- 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
- Grant MigrationWiz OAuth 2.0 access to G Suite. For guidance, see Enable access to G Suite using OAuth 2.0.
- If you are migrating from multiple domains, repeat these steps for each domain.
- G Suite as Source (read-only scopes):
https://mail.google.com/, https://www.google.com/m8/feeds, https://www.googleapis.com/auth/contacts.readonly, https://www.googleapis.com/auth/calendar.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/drive, https://sites.google.com/feeds/
Note: OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts. If a G Suite tenant is a G Suite for Business Legacy free account, end user credentials must be used. Refer to KB005124 for more information on migrating with end user credentials.
Prepare the Destination Environment
- Set up user accounts
- Ask the Hosted Exchange provider to create an account for migration that has full access permissions to all mailboxes.
- If you do not provide an admin account when setting up your Destination endpoint, it will be necessary to provide SMTP email addresses, login names, and passwords when adding Destination users to your MigrationWiz project. If you do provide an admin account, you only need to provide the SMTP email addresses.
- Below is an example PowerShell script which grants full access rights to an account called MigrationWiz. Your Hosted Exchange provider needs to change the user to match your admin account before running the script.
Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -User MigrationWiz
- For the Source endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select G Suite/Gmail.
- It is necessary to add ALL domains that will be migrated from. 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 you add a domain, you need to click on the "+" button.
- Enter Administrative email address. Note: This is the account that has admin access level to the Google admin portal.
- For the Destination endpoint:
- Click on EndPoints > Add Endpoint > + Find My Service Provider button > click on the down arrow in the Service Provider field, and select the Hosted Exchange Provider (taking care to select the correct version of Exchange that the customer is running). This will autopopulate the Outlook Web Access URL with their verified URL. (Or, instead of clicking on + Find My Service Provider button, click on theExchange Server 2003+ button and manually enter the Outlook Web Access URL.)
- Click on the Provide Credentials radio button, and enter the admin account credentials. These are the credentials that you obtained from your Hosted Exchange Provider when following the steps under the Prepare Destination Environment section.
Note: Check to see if there are any available bundles for discounts (e.g., MigrationWiz-Mailbox and DeploymentPro bundle). KB004647
- Via Group Policy Object (GPO). Note: This is the recommended methodology, because no end user interaction is required. KB005412 and video
- Via email. KB005411
- Launch DeploymentPro.
- Go to All Products > DeploymentPro and follow the prompts to launch.
- Select a customer from list by clicking on the customer name. Note: The status column will show enabled when a customer account has had DMA deployed.
- Configure 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 the most valuable for this migration scenario:
- Under Filtering, add: (^All Mail$|^All Mail/) KB005626
- This will filter out the All Mail label from your migration passes. This will speed up your migration passes.
- You will remove this folder filter before performing your final migration pass. These steps are included lower in this section.
- Under Support/Support options, add: StoreOverflowGooglePropertiesInNotes=1 KB005056
- Under Support/Support options, add: StoreOverflowGooglePropertiesInNotesPrefix="enter your text here" KB005056
- Under Support/Support options, add: SuppressReminderDays=N KB004203
- If you are migrating in batches, you will not be cutting over the MX records until your final batch of users has been migrated.
- If mail coexistence is required, you must set up mail forwards against those user accounts that are in the migration batches. Options:
- Manually set forwards during a migration on a per-user basis, from the individual users' portal. Note: This is only a valid option if there are a small number of users. KB004316
- Manually set forwards during a migration on a per-user basis, from the admin portal. Note: This is a suitable option for small- to medium-sized projects. KB004374
- Automate the setup of mail coexistence (forwards) for G Suite through the MigrationWiz management console tool. Note: This is the best option for large projects. KB005168
- Under Project Advanced Options > Filtering section, delete: (^All Mail$|^All Mail/) KB005626
- Select the users > Click on the Start button from the top, select Full Migration > Click on Start Migration. KB004938