- This is the complete onboarding task flow for migrating mailboxes from Office 365 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. This migration scenario does not require installing DMA. However, BitTitan will be adding several modules to DMA in the future, and these will be important to power MSPComplete feeds (which will provide further information to you, in the future, 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 Source Exchange Environment
- Create an administrator account in Office 365 to be used for migration, or use the global admin account for the tenant. KB004948
- Export the user list to a CSV file. This can be used when bulk-adding users to your MigrationWiz project later. You can copy and paste the user list into the Source and Destination Email column in your MigrationWiz project dashboard under Add > Bulk Add. Steps: From Office 365 admin portal > Users > Active Users > Export > Continue.
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.
Note: If migrating to multiple domains, repeat these steps for each domain.
- Create the customer. KB005421
- Create the Source and Destination endpoints. KB005427
- For the Source endpoint:
- Click Endpoints > 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 purpose of migration, refer to the Office 365 section in KB004725.
- For the Destination endpoint:
- Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select G Suite/Gmail.
- Enter Administrative email address.
Note: This is the account that has admin access level to the Google admin portal.
- For the Source endpoint:
- Purchase licenses. 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 personal archives, plus Google coexistence configuration and allows the use of DeploymentPro to perform post-migration Outlook email profile configuration. 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:
- Create a Mailbox Migration project. Read the How do I create a new migration project? article for more information.
- Add the accounts (also referred to as items) that will be migrated to the project. KB004842
- Set the Project Advanced Options. KB004834
- The following options are most valuable for this migration scenario:
- Set to use impersonation at the Source. Checkmark the Use impersonation at Source box. KB004727
- If this is a large migration project, then the value for Maximum concurrent migrations, under the Performance section, can be set to a very high value, e.g., 250.
Note: There is no limit for this value (for cloud to cloud migrations) if using impersonation.
- 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