Google Workspace migration to Exchange Online worked fine but now it is failing.

Question

Google Workspace migration to Exchange Online worked fine but now it is failing.

Caro de la Torre Hdz 0

I have already successfully migrated several accounts from Google Workspace. I started another migration batch but all users failed with the following error, with user being replace with each email provided in the CVS file.

MigrationProvisioningPermanentException: The operation couldn't be performed because object 'user**@domain.com' couldn't be found on 'SA#############.****MEX########.****PROD.OUTLOOK.COM'. --> The operation couldn't be performed because object '**@domain.com' couldn't be found on 'SA#############.MEX########.PROD.OUTLOOK.COM'

All users have a valid Exchange license and I previously created the users in the Admin Center. Also some users already existed and I only assigned a valid Exchange license.

I need to finish my migration and hope to resolve this issue promptly.

Caro de la Torre Hdz 0

Thanks for the quick reply. I am actually in a hurry to continue with the migration process and fixed this situation.

Below I'll share the follow ups to some of your recommendations and provide more context.

1/ Check the CSV header and coding I have successfully completed 8 migration batches using the same CVS header and coding, just modifying the information for the users. Here is what I have been using:

SQL

EmailAddress,UserName
******@domain.com,******@domain.com

2/ Check mailbox provisioning after license assignment

I have a batch with only one user that I created on Friday and assigned a MS365 Business Standard license.

Here is the output for the PowerShell commands

PowerShell

Get-Mailbox ******@domain.com
Name   Alias           Database                       ProhibitSendQuota    ExternalDirectoryObjectId
----   -----           --------                       -----------------    -------------------------
a49... user            MEX####.PROD.OUTLOOK.COM/61... 99 GB (106,300,44... a49.....-....-....-....-...........

Get-EXORecipient ******@domain.com
ExternalDirectoryObjectId : a49.....-....-....-....-...........
Identity                  : a49.....-....-....-....-...........
Alias                     : user
EmailAddresses            : {SIP:******@domain.com, SMTP:******@domain.com}
DisplayName               : Display Name
Name                      : a49.....-....-....-....-...........
PrimarySmtpAddress        : ******@domain.com
RecipientType             : UserMailbox
RecipientTypeDetails      : UserMailbox
ExchangeVersion           : 0.20 (15.0.0.0)
DistinguishedName         : CN=a49.....-....-....-....-...........,OU=DOMAIN.onmicrosoft.com,OU=Microsoft Exchange Hosted Organizations,DC=MEX####A001,DC=PROD,DC=OUTLOOK,DC=COM
OrganizationId            : MEX####A001.PROD.OUTLOOK.COM/Microsoft Exchange Hosted 	        Organizations/DOMAIN.onmicrosoft.com - MEX####A001.PROD.OUTLOOK.COM/ConfigurationUnits/DOMAIN.onmicrosoft.com/Configuration

I have recreated several batches with the following type of users: 1)Existing users with a Apps for Business license and assigned them an MS365 Business Standard license

2)Newly created user in Admin Center

and both scenarios failed with the same error for each user.

I had a support call last Friday and I am hoping to talk to someone as I need to urgently fixed this situation to continue my migration timeline.

Thanks for all of your support.

[Moderator note: Personally Identifiable Information removed]

1 answer

Your answer

Answer 1

Hendrix-C 19,965 Microsoft External Staff Moderator

Hi Caro,

For your concern, I suggest you first double check these things:

1/ Check the CSV header and coding

Refer to Perform an automated Google Workspace migration to Microsoft 365 or Office 365 in EAC in Exchange Online, Microsoft documentation says that the required CSV header need to be EmailAddress, and it must contain the primary email address for an existing Microsoft 365/Office 365 mailbox.

For example:

EmailAddress
******@domain.com

Or, if the Google/Gmail address is different from the Microsoft 365 address:

EmailAddress	Username
******@domain.com	gmail******@domain.com

2/ Check mailbox provisioning after license assignment

If the license was just assigned, Exchange mailbox provisioning can lag. You can pick one failed user and run this PowerShell:

Get-Mailbox ******@domain.com

If it fails, please wait and retry later, or you can remove and reassign the Exchange Online service plan if needed.

You can also check whether the user is hidden or mismatched:

Get-EXORecipient ******@domain.com

If the object cannot be found by Get-EXORecipient, you should fix the mailbox provisioning/licensing first.

Hope this information would be helpful for your concern. If you have any other questions, please feel free to reach out again in the comments on this post. I'm happy to assist you further

Thank you for your understanding and cooperation. I'm looking forward to your reply.

If the answer is helpful, please click "Yes" and kindly upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Caro de la Torre Hdz 0

Thanks for the quick reply. I am actually in a hurry to continue with the migration process and fixed this situation.

Below I'll share the follow ups to some of your recommendations and provide more context.

1/ Check the CSV header and coding
I have successfully completed 8 migration batches using the same CVS header and coding, just modifying the information for the users. Here is what I have been using:

EmailAddress,UserName
******@domain.com,******@domain.com

2/ Check mailbox provisioning after license assignment

I have a batch with only one user that I created on Friday and assigned a MS365 Business Standard license.

Here is the output for the PowerShell commands

Get-Mailbox ******@domain.com
Name   Alias           Database                       ProhibitSendQuota    ExternalDirectoryObjectId
----   -----           --------                       -----------------    -------------------------
a49... user            MEX####.PROD.OUTLOOK.COM/61... 99 GB (106,300,44... a49.....-....-....-....-...........

Get-EXORecipient ******@domain.com
ExternalDirectoryObjectId : a49.....-....-....-....-...........
Identity                  : a49.....-....-....-....-...........
Alias                     : user
EmailAddresses            : {SIP:******@domain.com, SMTP:******@domain.com}
DisplayName               : Display Name
Name                      : a49.....-....-....-....-...........
PrimarySmtpAddress        : ******@domain.com
RecipientType             : UserMailbox
RecipientTypeDetails      : UserMailbox
ExchangeVersion           : 0.20 (15.0.0.0)
DistinguishedName         : CN=a49.....-....-....-....-...........,OU=DOMAIN.onmicrosoft.com,OU=Microsoft Exchange Hosted Organizations,DC=MEX####A001,DC=PROD,DC=OUTLOOK,DC=COM
OrganizationId            : MEX####A001.PROD.OUTLOOK.COM/Microsoft Exchange Hosted 	        Organizations/DOMAIN.onmicrosoft.com - MEX####A001.PROD.OUTLOOK.COM/ConfigurationUnits/DOMAIN.onmicrosoft.com/Configuration

I have recreated several batches with the following type of users:
1)Existing users with a Apps for Business license and assigned them an MS365 Business Standard license

2)Newly created user in Admin Center

and both scenarios failed with the same error for each user.

I had a support call last Friday and I am hoping to talk to someone as I need to urgently fixed this situation to continue my migration timeline.

Thanks for all of your support.

Caro de la Torre.

Hendrix-C 19,965 Reputation points Microsoft External Staff Moderator

2026-07-27T22:50:19.91+00:00
Hi Caro,

Greatly appreciate your prompt update.

If the migration still fails while both Get-Mailbox and Get-EXORecipient both succeed in returning the UserMailbox, this issue is likely a migration service/backend corruption or a stale migration object issue, not a user licensing problem anymore.

At this point, the most appropriate next step is to create a support ticket directly to Microsoft Support. This route ensures you can contact a Microsoft support engineer, who can initiate a remote session to investigate backend configurations, run advanced diagnostic tools, and, if necessary, escalate the case to specialized teams with access to internal systems and logs. These backend resources are essential for resolving issues that go beyond what’s visible in the user interface.

To create a Support ticket: sign into Microsoft 365 Admin Center > Support > Help & Support.

As community moderators, I'm here to guide you, but due to privacy and security limitations, I don’t have access to the backend tools required for a full resolution. For this reason, contacting Microsoft Support via the Admin Center is the most secure and efficient way forward.

Thank you for your cooperation and understanding during this troubleshooting process. I truly hope the issue will get resolved as soon as possible.

Kind regards.
Caro de la Torre Hdz 0 Reputation points

2026-07-28T01:45:47.4333333+00:00

Thanks for your support. I have two open support tickets but no one has reached out today. I am in a hurry to urgently resolve this issue.
Hendrix-C 19,965 Reputation points Microsoft External Staff Moderator

2026-07-28T15:32:53.77+00:00

Hi Caro,

For further assistance, I have initiated a private message asking for more information. Please check your private message when you have time.

Thank you for your cooperation and understanding.
Caro de la Torre Hdz 0 Reputation points

2026-07-28T15:37:16.77+00:00

Hi.

I have replied to the private message. I really appreciate all of your support.

Thanks.