Fix G Suite to Exchange Online Migration Batch Completion Errors
Question details
The user needs to resolve G Suite to Exchange Online migration batches that fail during batch completion with TooManyTransientFailureRetriesPermanentException or BadRequestWebTransientException errors related to the Gmail forwardingAddresses API.

- Product
- Google Workspace (G Suite) and Microsoft Exchange Online / Microsoft 365
- Device & OS
- not provided
- Scenario
- An administrator is migrating G Suite mailboxes to Exchange Online. Mail items transfer successfully, but the batch does not complete.
- Observed behavior
- Batch completion fails with TooManyTransientFailureRetriesPermanentException or BadRequestWebTransientException errors tied to the Gmail forwardingAddresses API.
Before retrying the migration, confirm that you have Exchange Online admin access and note the target delivery domain configured for the failing migration batch. Also check whether that target domain is the same as the primary G Suite domain.
Switch the Migration Target Delivery Domain to a Temporary Microsoft 365 Subdomain
Use this solution when mail items migrate successfully but the batch fails during completion with forwardingAddresses API errors.
Google may interpret a migration target that uses the primary domain as forwarding mail back to the same mailbox. Using a temporary Microsoft 365 subdomain avoids this conflict during batch completion.
Sign in to the Exchange admin center at admin.exchange.microsoft.com with an Exchange Online administrator account.
Go to Recipients > Migration and open the G Suite migration batch that failed during completion.
Check the target delivery domain configured for the migration batch. If it uses the primary G Suite domain, plan to replace it with a temporary Microsoft 365 subdomain such as migration.contoso.com.
Create a new migration batch and set the target delivery domain to the temporary Microsoft 365 subdomain instead of the primary domain.
Start the new migration batch and monitor it until the batch completes successfully without forwardingAddresses API errors.

Create and Start a Migration Batch Through Exchange Online PowerShell
Use this method when you need more control over provisioning settings or when the Exchange admin center batch continues to fail.
Use WPS Office for Everyday Document Work After Exchange Online Migration
WPS Office is a free, lightweight Office alternative that opens, edits, and saves Microsoft Word, Excel, and PowerPoint files with strong format compatibility. It offers a familiar ribbon interface and works well alongside Microsoft 365 workflows, making it a practical option for users and administrators who need reliable document tools during or after a G Suite to Exchange Online migration.

Frequently Asked Questions
Why does the G Suite migration fail only during batch completion with forwardingAddresses API errors?
Mail items may transfer successfully, but batch completion can fail when Google interprets the primary domain as forwarding mail back to the same mailbox. Changing the target delivery domain to a temporary Microsoft 365 subdomain usually resolves this behavior.
How do I create a temporary Microsoft 365 subdomain for the migration target?
In the Microsoft 365 admin center or Exchange admin center, add and verify an accepted domain using a subdomain such as migration.contoso.com, then select that subdomain as the target delivery domain when creating the migration batch.
Can I keep using the primary domain if I change Gmail forwarding settings?
It is not recommended for this error. Google may still treat the primary domain as the same mailbox target. The Microsoft 365 subdomain approach is the safer workaround for batch completion errors.
How do I create a new migration batch through Exchange Online PowerShell?
Connect to Exchange Online PowerShell with Connect-ExchangeOnline, verify provisioning with Mail and proxyAddresses attributes, then use New-MigrationBatch with -TargetDeliveryDomain set to a temporary subdomain and Start-MigrationBatch to start it.
Will recreating the migration batch create duplicate mail in the destination mailbox?
A new migration batch can reprocess or sync mail for the affected users. Before starting it, verify the destination mailbox state and provisioning settings to avoid creating unnecessary duplicate items.




