Error: UserAlreadyBeingMigratedException - Public Folder to Office 365 Group Migration failure

Matt Pollock 251 Reputation points
2022-06-30T20:03:00.557+00:00

Hi,

I've been trying to migrate a couple of on prem public folders to Exchange Online to test the process and see how it works.

I've followed the MS docs guidance, but my first attempt at the migration failed because of having more than two PF's mapped to the same O365 Group.

Since the first attempt however I keep receiving the following error when subsequent batches run and then eventually fail.

216580-image.png

A bit of research online and all advice I've found advises to ensure all move requests and batch migrations are removed - even if the batch is deleted from the EAC
I've run both Remove-MoveRequest and Remove-MigrationBatch in both on prem and Exchange online environments and there are no requests or batches to remove.

Any one able to help shed any light on this issue please?

Many Thanks

Matt

Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
2,219 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. KyleXu-MSFT 26,291 Reputation points
    2022-07-01T03:03:51.253+00:00

    @Matt Pollock

    Do you try to connect to Exchange online then use the command below? Which contained in this part: Prerequisite steps in Exchange Online I would suggest follow this part have a check on your Exchange online:

    Get-MigrationBatch | ?{$_.MigrationType.ToString() -eq "PublicFolder"}  
    

    If you cannot find the failed migrated request, you could open a service request(for free) to Office 365 team help you check whether is there exist invisible failed migration request.

    You can also try to change the Office 365 group email address, then check whether could migrate successfully.

    I also want to confirm with you that did you try to use a new batch migration name for new created migration request?


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    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.



  2. Amit Singh 5,071 Reputation points
    2022-07-01T11:05:32.88+00:00

    Look at the move requests on your on-prem server. Perhaps there is a move request for that user already. If so, remove the job.

    You can also check this article for more insight - How to Solve Source Mailbox Already BeingMovedPermanentException Error?


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.