Google Workspace Migration

Fix G Suite to Exchange Online Migration Batch Completion Errors

Adam DavisAdam Davis Nov 13, 2026 869 views

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.

Fix G Suite to Exchange Online Migration Batch Completion Errors
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 you start

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.

Solution 1Recommended

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.

1
Open the Exchange admin center

Sign in to the Exchange admin center at admin.exchange.microsoft.com with an Exchange Online administrator account.

2
Locate the failing migration batch

Go to Recipients > Migration and open the G Suite migration batch that failed during completion.

3
Review the target delivery domain

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.

4
Create a new migration batch with the subdomain

Create a new migration batch and set the target delivery domain to the temporary Microsoft 365 subdomain instead of the primary domain.

5
Start and monitor the new migration batch

Start the new migration batch and monitor it until the batch completes successfully without forwardingAddresses API errors.

Switch the Migration Target Delivery Domain to a Temporary Microsoft 365 Subdomain
Expected result: This fix usually resolves the forwardingAddresses API errors because Google no longer treats the migration target as the same primary-domain mailbox.
Free Microsoft Office alternative

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.

Opens and saves Microsoft Office Word, Excel, and PowerPoint files with format compatibility.Free and lightweight Office suite for everyday document tasks without heavy licensing requirements.Familiar ribbon-style interface reduces retraining after moving from Microsoft Office or Google Workspace workflows.Works alongside Microsoft 365 and Exchange Online migration tasks for viewing and editing exported documents.Includes built-in PDF conversion and cloud integration to simplify document handling.
microsoft office alternative - wps office

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.