Migration errors: Exchange error+mover.io error+ account in migration batch suspended

Question

We are doing migration from Google Workspace to Microsoft 365. Below are errors we encountered. Would appreciate your urgent assistance and advice to fix these errors.

**1)Exchange Error: “**The subscription for the migration user couldn't be loaded. The followingerror was encountered: A subscription wasn't found for this user.”

In classic Exchange Admin Center (EAC),  when we click “recipients” and then “Migration” tab at top menu and then click a batch and then “View Details” , we get this error message below and can no longer view details of the batch like data migrated, dates etc

All batches (synced, syncing) have this error message

In New EAC, details of users in batches no longer show details like data migrated, dates etc

2)mover.io error  : "Request hasbeen terminated Possible causes: the network is offline, Origin is not allowedby Access-Control-Allow-Origin, the page is being unloaded, etc.: Unable toretrieve schedules for migration"
We get above error when we try to migrate and setup connectors to migrate GDrive data from gsuite/ Google Workspace to Microsoft 365

3)Migration batch suspended at PercentageComplete 70%
In one migration batch (with 2 users) to migrate gmail from gsuite to Microsoft 365 -1st user (80GB size) synced while 2nd user (75GB size) syncing forever. Logs show 2^nd^ user suspended.
This looks like throttle issue

___________________________________________________________

Thank you

Answer 1

Thanks Oliver

We have gone live with Microsoft 365.

But problem now is we cannot log into Outlook using mobile apps like Outlook and Gmail. We have no problem logging in on desktop and mobile web browser. Have posted question at

https://answers.microsoft.com/en-us/msoffice/forum/msoffice\_o365admin-mso\_dep365-mso\_o365b/cannot-log-into-outlook-using-outlook-app-or-gmail/a17cad99-47bd-4a16-a867-8de1c0eb1834?tm=1619165901283

Would appreciate your advice and help. Thanks

Answer 2

Hello John,

Thanks again for your reply with patience.

Based on the article and the screenshots you provided above, you have tried to perform the approval request via powershell commands for the skipped items.  Generally the Migration batches in Microsoft 365 keep changes there for about 24 hours, so after you performed the skipped items approval request, please wait for some more time with patience to make it provisioned in Microsoft 365 backend.

On another hand, if it still stuck on investigate after 24 hours past, for this issue, it need to be escalate to Microsoft 365 backend team and help you check it from the backend, for some more information, I will send you a Private Message (PM), please check it at your convenience, thanks.

Best Regards,

Oliver

Answer 3

Hello John,

First, I am glad to hear the first problem has been resolved, and thanks for your sharing

For the other two problems you are facing, the second error you got when you tried to migrate GDrive data to Microsoft 365 with connectors established,  as we are mainly focusing on Exchange Online for Business, for the GDrive we have limited Official resource on it for migration, could you please share some reference or pictures like how you create the connectors to migrate the GDrive data to Microosft 365 at your convenience, thanks.

For your last problem, the user mailbox migration pending on 70% for the second user, please double check if that user has any email item larger than 35MB, as Microsoft 365 has the per email item no more than 35 MB by default, if you have large item in the resource mailbox (Gsutie mailbox), it may cause the migration on a pending status.  Also I need to check the your current migration batch status, please try to connect to  Exchange Online Powershell and run command Get-MigrationStatistics  Get-MigrationBatch  for the migration request then share the full results here.

Best Regards,

Oliver

Thanks Oliver

We resolved item 2.

For item 3 (suspended migration ), we re-migrate the suspended/stopped acc. It worked and all 100% synced. BUT (there is always a but  :) ) Data Consistency Score shows "Investigate"

Looked at log and it says "1 missing item in Target"

So we follow this https://docs.microsoft.com/en-us/exchange/mailbox-migration/track-prevent-data-loss-dcs and went ahead to "Approve Migration Batch"

After 1 hours, Data Consistency Score still shows "Investigate"  and the "Approve Migration Batch" option is still there

Is it because it takes some time for it to update the Data Consistency Score? Do we have to wait for Data Consistency Score to change to "Perfect" before we can Complete the batch?

Looks like Data Migrated to Outlook even though Data Consistency Score shows "Investigate"

Thanks

Answer 4

Hello John,

First, I am glad to hear the first problem has been resolved, and thanks for your sharing

For the other two problems you are facing, the second error you got when you tried to migrate GDrive data to Microsoft 365 with connectors established,  as we are mainly focusing on Exchange Online for Business, for the GDrive we have limited Official resource on it for migration, could you please share some reference or pictures like how you create the connectors to migrate the GDrive data to Microosft 365 at your convenience, thanks.

For your last problem, the user mailbox migration pending on 70% for the second user, please double check if that user has any email item larger than 35MB, as Microsoft 365 has the per email item no more than 35 MB by default, if you have large item in the resource mailbox (Gsutie mailbox), it may cause the migration on a pending status.  Also I need to check the your current migration batch status, please try to connect to  Exchange Online Powershell and run command Get-MigrationStatistics  Get-MigrationBatch  for the migration request then share the full results here.

Best Regards,

Oliver

Answer 5

Hi

First item is resolved 1)Exchange Error: “The subscription for the migration user couldn't be loaded. The following error was encountered: A subscription wasn't found for this user.”

We just followed these steps to fix it  https://docs.microsoft.com/en-us/exchange/troubleshoot/migration/subscription-wasnt-found-for-user-error

Cheers