For this case have to check move request in exchange on-prem if there are moving mailbox. if yes we need to remove all move request and resume migration.
Remove Move request
Remove-MoveRequest -Identity firstname.lastname@example.org
Get Move request status
Get-MoveRequest | fl Status, Protect, “Display Name”, Identity
When migrating mailboxes to Exchange Online in a Hybrid environment, you might encounter the following error:
PS C:\> Get-MigrationUser email@example.com | FL Identity : firstname.lastname@example.org BatchId : Pilot Migration 1 MailboxEmailAddress : email@example.com RecipientType : MailboxOrMailuser Status : Failed StatusSummary : Failed MigrationType : ExchangeRemoteMove State : Failed WorkflowStep : DataMigration WorkflowStage : Injection ErrorSummary : The onboarding move could not be created because user 'User' is already being moved.
If you have already checked all your migration batches (Get-MigrationBatch) and/or all your individual move requests (Get-MoveRequest “user”) and there is absolutely no move request associated with this user, then it is very likely you still have a move request for the user in your on-premises Exchange environment.
So, go to your on-premises environment and remove the local move request for that particular user. This should clear the msExchMailboxMoveRemoteHostName AD attribute. Other attributes related to move requests that you can also check are:
4. Let’s use PowerShell commands to get detailed migration information.
Get-MigrationBatch | fl
Get-MoveRequest | fl
Get-MigrationStatistics | fl
Get-MigrationUserStatistics -Identity *** Email address is removed for privacy *** -IncludeReport | FL
Get-MigrationUser *** Email address is removed for privacy *** | fl
Note: *** Email address is removed for privacy *** is the problematic user.