Copy the ClientID and Scope from the EAC, paste it here, and then select Authorize. You'll be redirected to Google Admin API Controls page. The ClientID and Scope are also listed for your reference. The link to add the ClientID and the Scope is provided.A JSON file (projectid-*.json) is downloaded to your local system.Once the APIs are successfully validated, the following things happen: In the Google sign-in page that appears, sign in to your Google account to validate your APIs. Verify that the Automate the configuration of your Google Workspace for migration section is expanded, and then select Start in that section to automate the four required prerequisite steps. The Prerequisites for Google Workspace migration page appears. Select Google Workspace (Gmail) migration, and then select Next. The Select the migration type page appears. Select the mailbox migration path: Verify that Migration to Exchange Online is selected.Give migration batch a unique name: Enter a unique name.

In the new Exchange Admin center at, go to Migration and then select Add migration batch. Therefore, Microsoft strongly recommends disabling all MRM and archival policies before attempting any data migration to mailboxes. Because of this unawareness, any messages that are deleted or moved to archive by these policies will result in the migration process flagging these items as 'missing.' The result is perceived data loss rather than actual data loss, which makes it much harder to identify actual data loss during any content verification checks. Microsoft's data migration tool is currently unaware of tools enforcing messaging records management (MRM) or archival policies.

Exchange online workspaces