Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Hello Kyler Smith**,**
Good day! Thank you for reaching out to Microsoft community.
As per your description and my understanding, you’re experiencing problems migrating from Google Workspace to Microsoft 365 using the Microsoft Migration Tool. Accounts with less than 1,000 emails migrate successfully, but for accounts with larger datasets, the migration fails after copying only about 10% of the data.
IMAP is enabled, 2FA is disabled, and email delegation or routing issues in Google Workspace have been ruled out. The issue persists even when running migrations in smaller batches. You suspect OAuth restrictions in Google Workspace may be a factor but are unsure. [correct me if I am wrong]
- OAuth restrictions or missing API scopes could prevent the migration tool from fully authenticating or accessing certain data.
- Google Workspace enforces per-user and organization-wide limits on IMAP access, which can cause failures when migrating large datasets.
- Migration issues might correlate with throttling, especially during high-traffic periods.
As you know, the process/ navigation method depends on which type of app version/ license/ subscription you have. To better understand your issue, I need some addition information so that we can narrow down the main reason and find out the root cause by working together.
Please correct me if I am wrong and I need your help on sending all the answers along with the data only via Private Message:
- Which Microsoft Migration tool are you using?
- Are you using Microsoft 365 Exchange online admin center to migrate Google workspace?
- What actions have you taken to perform this migration?
- Have you contacted google support Team?
- Have you verified that the service account used for migration has the Google Workspace Migration API enabled and the necessary OAuth scopes added in Google Workspace?
- Have you recreated Migration Batch in M365?
- How many accounts you are trying for migration?
- Have you reviewed all the APIs on the Google side?
Possible reasons:
TooManyTransientFailureRetriesPermanentException:
The error often involves MapiExceptionNetworkError, which indicates network-related issues during the migration.
It can also be related to specific conditions like incorrect sub-domain configurations during Google Workspace onboarding.
- For Google Workspace onboarding, ensure that the sub-domain is correctly configured and verify the forwarding email address manually.
SyncProviderTokenUnexpectedInvalidationException:
This error might occur due to quota limitations on the Google Developers project used for migration. Content verification can be heavy on quotas, leading to this issue. Recommendations include lowering the MaxConcurrentMigrations, contacting Google Support to request an increase in quotas, or retrying the operation whenever this error is encountered.
Google Workspace migrations utilize Google APIs, and Google may throttle access to these APIs. This throttling can cause the SyncProviderTokenUnexpectedInvalidationException error. It's advisable to check the throttling information in the move report.
Throttling information can easily be viewed in the move report, which should be exported as an XML file by running:
Get-MoveRequestStatistics "move identity" -IncludeReport -DiagnosticInfo "Verbose, ShowTimeSlots, ShowTimeLine" | Export-CliXml movereport.xml
Note: to access private message platform, please click on this link: Private Messages - Microsoft Community.
Please understand that our initial response may not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution.
Thanks for choosing the MS community.
Looking forward to your response and have a great day ahead!!
Sincerely
S M Nazmun Nur | Microsoft Community Moderator