Fix Exchange Impersonation Errors During Microsoft 365 to Google Workspace Migration
Question details
The user needs to resolve an Exchange impersonation error that prevents a Microsoft 365-to-Google Workspace email migration because the migration account cannot open target mailboxes through Exchange impersonation.

- Product
- Microsoft 365 Exchange Online and Google Workspace migration service
- Device & OS
- not provided
- Scenario
- An administrator is migrating mailboxes from Microsoft 365 to Google Workspace and has configured a migration account, but the migration fails when the account attempts to access target mailboxes through Exchange impersonation.
- Observed behavior
- The email migration fails with an error that the migration account cannot open the target mailbox through Exchange impersonation.
Confirm that you have Exchange Online administrator access and know which migration account is used in the Google Workspace migration settings. Also check whether that account is already a member of an ApplicationImpersonation role group before creating a new one.
Grant ApplicationImpersonation to the Migration Account in Exchange Online
Use this solution first when the migration account cannot open target mailboxes through Exchange impersonation because it lacks the required ApplicationImpersonation role.
Exchange Online uses role-based access control. The migration account must be a member of a role group that includes the ApplicationImpersonation role or it cannot impersonate mailboxes during the migration.
Sign in to the Microsoft 365 admin center, select Admin centers, and then select Exchange to open the Exchange admin center.
Go to Roles > Admin roles, click Add role group, enter a name such as Google Workspace Migration Impersonation, and click Next.
Under Roles, search for ApplicationImpersonation, select it, and click Next.
Under Members, add the migration administrator or service account that Google Workspace uses for migration, then click Next and Finish.
Return to the Google Workspace migration console and retry the migration or re-run the affected migration batch.

Verify Migration Endpoint, Authentication, and Mailbox Permissions
Use this when ApplicationImpersonation is already granted but the migration still fails because of incorrect endpoint or mailbox access settings.
Use WPS Office as a Free Microsoft Office Alternative While You Resolve Exchange Migration Issues
WPS Office does not change Exchange Online impersonation permissions, but if you need a free, lightweight Office suite while you work through Microsoft 365 migration issues, WPS Office opens and saves Microsoft Word, Excel, PowerPoint, and PDF files with a familiar interface and no subscription.
- 1. Download WPS Office: Go to the official WPS Office website and click Download WPS Office Free to install the latest version on your Windows or macOS device.
- 2. Open an existing Microsoft Office file: Launch WPS Office, select Open, and browse to a Word, Excel, or PowerPoint file to continue working while you troubleshoot the migration.
- 3. Save in Microsoft Office formats: Use File > Save As and choose the corresponding Microsoft Word, Excel, or PowerPoint format to keep files compatible with Microsoft 365 and Google Workspace workflows.

Frequently Asked Questions
Do MX records cause Exchange impersonation failures during Google Workspace migration?
No. MX records control mail routing, not Exchange impersonation. If you see an impersonation error, check the migration account's ApplicationImpersonation role membership, mailbox permissions, migration endpoint, and authentication settings instead of changing MX records.
How long does ApplicationImpersonation permission take to take effect in Exchange Online?
In most Microsoft 365 tenants, the permission takes effect within a few minutes, but propagation can occasionally take longer. Wait a short time and then retry the Google Workspace migration batch.
Which Exchange role group must the migration account be added to?
The migration account must be a member of a role group that includes the ApplicationImpersonation role. You can create a new role group in Exchange admin center or add the account to an existing group that already has this role.
Why does Google Workspace migration say the migration account cannot open the mailbox?
This typically means the account lacks Exchange impersonation permissions, the migration endpoint is incorrect, or authentication is blocked. Grant ApplicationImpersonation, verify the endpoint URL and credentials, and check for conditional access or MFA issues.
Can WPS Office fix Exchange impersonation errors?
No. WPS Office cannot change Exchange Online permissions or resolve Google Workspace migration impersonation errors. However, it can open, edit, and save Microsoft Office files while you continue troubleshooting the migration in Microsoft 365 and Google Workspace.




