Migrate business email and calendar from Google Workspace
Article
Note
The videos and content in this article are meant to give customers a high-level overview of the process of how to use an automated batch migration in the Exchange admin center to migrate your users email, contacts, and calendars from Google Workspace.
Please refer to the resource links provided in this article for additional detailed information needed to use the batch migration tool successfully.
Overview of the using an automated batch migration to migrate from Google Workspace
You can use the batch migration tool in the Exchange admin center to migrate email, contacts, and calendars from Google Workspace to Microsoft 365. With it, you can:
Keep both environments active.
Migrate groups of email users to Microsoft 365 over time.
And then close your Google Workspace environment when you have completed moving your business.
An automated batch migration does some of the migration tasks for you, so it is recommended over the manual batch migration.
You can also migrate your email from Google Workspace to Microsoft 365 through an IMAP migration. You should compare methods to determine which is more suitable for migrating your email.
It is recommended that you get help from Microsoft or from a partner when planning to migrate with either of the above methods.
If you are a VSB (very small business) where you have a small number of users, you should migrate your email using a different method, such as importing to Outlook through a PST file.
Prerequisites for automated batch migration from Google Workspace
To successfully use the automated batch migration tool, it is important to correctly complete all of the prerequisite tasks. For more detailed information, see Google Workspace migration prerequisites.
These tasks include:
Creating a subdomain to correctly route email to users who have been migrated to Microsoft 365.
Creating a subdomain to correctly route email from users you have migrated to Microsoft 365 back to users in your Google Workspace environment.
Adding all mail user accounts to Microsoft 365 for users you are migrating.
Verifying that the Google migration admin account has the correct permissions.
Note
Completing the prerequisite tasks may require you to log into your domain hosts to create subdomains and update your DNS records. If you are not comfortable doing this, you should look for assistance with this.
Create a subdomain for email going to Microsoft 365
Return to the Google Workspace admin console.
Select Add a domain.
Enter a domain name for your subdomain, such as m365.contoso.com.
Select User alias domain, select Add domain and start verification, and then select Continue. Follow the instructions to verify domain ownership.
Domain verification usually takes just a few minutes, but it can take up to 48 hours.
Go to the Microsoft 365 admin center.
In the Microsoft 365 admin center, in the left nav, select Show all, select Settings, select Domains, and then Add domain.
Enter the subdomain you previously created, then select Use this domain.
To connect the domain, select Continue.
Select Add DNS records. Depending on your domain host provider, Microsoft 365 will try to update your DNS records for the domain.
When complete, select Done.
Create a subdomain for mail routing to Google Workspace
Return to the Google Workspace admin console.
Select Add a domain.
Enter a domain name for your subdomain, such as gsuite.contoso.com.
Select User alias domain, select Add domain and start verification, and then select Continue. Follow the instructions to verify domain ownership.
Provision mail user accounts for users you are migrating
In the Exchange admin center, select Contacts, then Add a mail user.
On the Set up basic information page, enter the information about the user you want to migrate, such as Name, display name, etc..
For External email address use the domain domain you created for mail routing to Google Workspace (for example, gsuite.contoso.com).
For Domain, select the primary domain you are using.
Select Next, and repeat this process for each user you are migrating.
Next, you need to add a proxy email address for each user for routing email to their Microsoft 365 routing domain.
In the Exchange admin center, select Mailboxes, then select a user.
In the user properties, select Manage email address types.
For Email address type, select SMTP.
Enter the user's alias, and from the drop-down menu select the Microsoft 365 routing domain (for example, m365.contoso.com).
Select OK, then Save.
Repeat the process for each user.
Verify that your Google migration admin has the required permissions
In the Google admin console, verify that your Google migration admin has the following roles assigned to them:
Project creator
Servicer account creator
Migrate your email, contacts, and calendars from Google Workspace
After successfully completing all the prerequisites, you can now use the batch migration tool to migrate your users from Google Workspace to Microsoft 365. Here is a summary of the required steps. For more detailed information, see Perform an automated Google Workspace migration to Microsoft 365.
In the Exchange admin center, select Migration.
On the Migration batches page, select Add migration batch.
Give the migration batch a unique name, and from the Select the mailbox migration path menu, select Migration to Exchange Online. Then select Next.
For the Migration type, select Google Workspace (Gmail) migration. Then select Next.
On the Prerequisites for Google Workspace migration page, select Start.
Sign in with your Google admin account and password.
On the EAC Migration wants access to your Google Account page, select Continue.
EAC Migration will then do four required tasks in Google Workspace that are needed for migration.
When all four tasks have been complete, take note of the ClientID and Scope values. Then select Link.
On the API Clients page, select Add new.
Copy the ClientID and Scope values from the migration page, and paste then into the corresponding fields (Client ID and OAuth scopes) in the Add a new client page. Then select Authorize.
On the Prerequisites for Google Workspace migration page, select Next.
On the Set a migration endpoint page, select Create a new migration endpoint, then Next.
Enter a unique Migration endpoint name, and use the default values for Maximum concurrent migrations and Maximum concurrent incremental syncs, then select Next.
On the Gmail migration configuration page, enter the email address of the Google admin account you are using to perform the migration.
Select Import JSON and then browse to the location where the JSON key file was created and downloaded to your local computer. This was done during the automated tasks configuration part of the migration (step 8) and should be found in your local Downloads folder. Select the file, select Open, and then Next.
Create a CSV file with a list of the mailboxes you want to migrate. Make sure the file follows this format:
On the Add user mailboxes page, select Import CSV file and then choose the CSV file you created containing the users emails you want to migrate. Select Next.
On the Move configuration page, enter the name of your target delivery domain. This was the subdomain you created in the prerequisite steps that was for email routing to Microsoft 365 (for example, m365.contoso.com). Then select Next.
On the Schedule batch migration page, you can:
Enter the email address of people you want a report to be sent.
Select how you want the batch to be started (manually, automatically, or at a specific time and date).
Select how you want the batch to be ended (manually, automatically, or at a specific time and date).
Select Save. When the migration batch runs successfully, select Done.
In the Exchange admin center, select Migration. On the Migration batches page, you can see the status of your batch migration.
When the batch shows a status of Synced, select Complete migration batch, then select Confirm.
Next, assign Exchange licenses to your migrated users, and have them check to see if their email, contacts, and calendars had migrated successfully.
Are you looking to move to the cloud and easily migrate to Business Central online? This module covers how you can use the built-in migration tools to migrate data to Business Central online from specific product versions.
Plan and execute an endpoint deployment strategy, using essential elements of modern management, co-management approaches, and Microsoft Intune integration.