Are you approaching a Google Workspace to M365 migration in MigrationWiz like an Exchange-to-Exchange move and running into Google API authentication problems?

MigrationWiz can migrate from Google Workspace to M365, but the source endpoint setup is materially different from Exchange-based migrations. Treating the configuration as equivalent is a common cause of failures.

For the source endpoint, authentication uses Google APIs via a Google Cloud service account with domain-wide delegation enabled in the Google Admin Console. Domain-wide delegation must include the correct OAuth scopes, at minimum Google Calendar API, Google Contacts API, and Gmail API. If even one required scope is missing, service account authentication may still succeed, but you will see permission failures at the item level for whichever workload is tied to the omitted scope.

Google Drive is not migrated in the same MigrationWiz project as Gmail and Calendar. Moving Drive content to OneDrive for Business requires a separate MigrationWiz project using the Google Drive to OneDrive migration path, with its own source endpoint configured against the Google Drive API.

Because Google native item formats must be converted into the Exchange MAPI schema, plan for a higher item-level error rate than you would expect in Exchange-to-Exchange migrations. Your post-migration audit should account for format conversion failures showing up in the item report.

Have you configured domain-wide delegation in the Google Admin Console with all required OAuth API scopes before starting your MigrationWiz Google Workspace migration?

#BitTitan #MigrationWiz