G Suite to Office 365 Migration Guide

Introduction

This is the complete onboarding task flow for migrating mailboxes from G Suite to Office 365.

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

We also strongly recommend that you use DeploymentPro to reconfigure the Outlook profiles in this migration scenario.

To see what items are included in the migration, see What items are migrated with MigrationWiz? and What items are not migrated with MigrationWiz?

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 Environment

1. Grant MigrationWiz OAuth 2.0 access to G Suite. For guidance, see Enable access to G Suite using OAuth 2.0.
   Notes:
• If you are migrating from multiple domains, repeat these steps for each domain.
• OAuth administrative credentials will not function properly with G Suite for Business Legacy free accounts. Unfortunately, migrating G Suite for Business Legacy free accounts is not supported.
2. Ensure IMAP access is enabled for all users. For details on how to check this, refer to the Google support article here.
3. Ensure the folder size limits on IMAP folders have been removed for all users. For each user, click the gear icon > Settings > Forwarding and POP/IMAP tab > Folder Size Limits > Select the radio button for Do not limit the number of messages in an IMAP folder (default).
   Note: This is an end user setting, which can only be set on a per-user basis. Therefore, we recommend that you send instructions to your end users to check this setting. KB005104
4. Export mailboxes to CSV file(s). From Google Admin portal > Click Users > Click ⁝ (3 vertical dots) > Download Users > Download All Users > Click OK > Save.

Prepare the Destination Environment

1. Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. KB004948
2. Set up accounts on Office 365 and assign licenses. These can be created in several ways:
• Manually, one at a time. Microsoft instructions to add users individually
• By bulk import, via CSV file. Microsoft instructions to bulk add users
• By PowerShell script. TechNet article
• By DirSync, AAD Sync or AAD connect. KB004336
3. Prepare the tenant to send and receive large mail items. KB005139

MSPComplete Steps

1. Create the customer. KB005421
2. Create the Source and Destination endpoints. KB005427
   • For the Source endpoint:
     • Click Endpoint > Add Endpoint > Enter endpoint name > For endpoint type, select G Suite/Gmail.

     • It is necessary to add all domains 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.
   • For Destination endpoint:
     • Click Endpoint > Add Endpoint > Enter endpoint name > For endpoint type, select Office 365.

     • It is necessary to add all domains 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.

     • Click the Provide Credentials radio button, and enter the admin account credentials.
       Note: This should be a global admin account. If creating a separate admin account for the migration, refer to the Office 365 section in KB004725.
3. Purchase licenses.
   Note: We recommend that you purchase the User Migration Bundle license for this migration scenario. User Migration Bundle licenses allow you to perform multiple migrations of User mailboxes, documents, and in-place archives, plus Google coexistence configuration and allows the use of DeploymentPro to perform post-migration Outlook email profile configuration. Refer to the How do I purchase licenses? article for more information about purchasing licenses, or refer to the Which migration license should I choose? article for more information about licensing options.
4. Deploy DMA to users. 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 method because no end user interaction is required. KB005412
• Via email. KB005411

HealthCheck for Office 365 Steps

1. Go all All Products > HealthCheck for Office 365 and follow the prompts to launch.
2. 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.
3. Review results.
   Note: If any computers have a red X on their row, you should review the detailed results by clicking on the pie chart in the far right-hand part of the row.
4. Include upgrading action items and costs in your Statement of Work.
5. Perform remediation steps.

DeploymentPro Steps

1. Launch DeploymentPro.
1. Go to All Products > DeploymentPro and follow prompts to launch.
2. 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.
3. Configure customer DeploymentPro module:
   1. Enter the Domain.
   2. Select the Destination endpoint.
   3. Checkmark the Auto-populate box.
   4. 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.
   5. Save and continue.
2. Activate DeploymentPro module for users.
• Either select all users (by putting a checkmark the box to the left of the Primary Email column heading) or select the individual users (by putting a checkmark in the boxes to the left of the user email addresses).
  Note: DeploymentPro is included with the User Migration Bundle license. DeploymentPro cannot be purchased as a standalone service license, and it cannot be added to the single-use mailbox migration license. If you wish to remotely configure Outlook mail profiles using DeploymentPro after a migration, purchase the User Migration Bundle license.
• Click the Schedule Cutover button.
3. Schedule the profile cutover date.
   • Set the date and time for the Outlook profile configuration to occur, and click the Schedule Cutover button.
     Notes:
     • 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.
4. On the profile cutover date, users will be guided through the reconfiguration of their Outlook profile.

MigrationWiz Steps

1. Create a Mailbox Migration project. Read the How do I create a new migration project? article for more information.
2. Add the accounts (also referred to as "items") that will be migrated to the project. KB004842
3. Set the Project Advanced Options. KB004834
   • This will filter out the All Mail label from your migration passes, which will speed up your migration passes.
   • You will remove this folder filter before performing your final migration pass. These steps are included later in this section.
• The following options are the most valuable for this migration scenario:
• Under Filtering, add: (^All Mail$|^All Mail/) KB005626
  Notes:
• Set to use impersonation at Destination. Checkmark the Use impersonation at Destination box. KB004727
• 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=X KB004203
4. Run Verify Credentials. KB004511
5. Notify users that a migration is occurring. Send email to all users, telling them the time and date of the migration.
6. Pre-Stage pass: Select the users > Click the Start button from the top, and select Pre-Stage Migration > Under the Migration Scheduling section, from the drop-down list, select 90 days ago > Click Start Migration. KB004938
7. MX Record Cutover. Change over MX records on the DNS provider's portal. Also, include the AutoDiscover (CName) setting.
   Notes:
   • 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 Google Apps through the MigrationWiz management console tool.
     Note: This is the best option for large projects. KB005168
   • Set up mail routing on Office 365. KB005137
   • If calendar free/busy coexistence is required, you must enable Google coexistence to support free/busy information. Google Coexistence Setup Guide.
• If you are migrating in batches, you will not be cutting over the MX records until your final batch of users has been migrated.
8. 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.
9. Full (Delta) pass: Select the users > Click the Start button from the top, select Full Migration > Click Start Migration. KB004938
10. Run Retry Errors. KB004658
11. Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.
12. If problems persist, contact Support. KB004529
13. If you are not using DeploymentPro, users must create new Outlook profiles.
14. Remove the All Mail filter from project Advanced Options, and run one final (Full) migration pass.
• Under Project Advanced Options > Filtering section, delete: (^All Mail$|^All Mail/) KB005626
• Select the users > Click the Start button from the top, select Full Migration > Click Start Migration. KB004938
15. Click the bar chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. KB004626