Hi, sorry if this subject is a bit perplexing. and if it's been answered before.

Migrating 2007 - 2013. Most mailboxes fine- slow but fine. Moved a few hundred now, more to come!

The odd mailbox- for various reasons- failed. Literally just a handful so far. So... I try to move them again, and the move completes with 0 mailboxes moved. No errors, it just hasn't moved the mailbox(es). Any idea what could be going wrong? Target database: xxx. Status: Completed. Synced Mailboxes: 0, Finalized mailboxes: 0, Failed mailboxes: 0.

There's no rhyme nor reason to this that I can see- it's almost like there's a flag set which says this mailbox can't be moved.

Any ideas gratefully received! I've just got these few causing problems on our old WS2K3/EX2007 boxes now (along with public folders), need to meet next Tuesdays deadline :)

Enter this command to see details of what happened:

Get-MoveRequest -Identity "Mailbox Name" | Get-MoveRequestStatistics -IncludeReport | FL Report

Hi,

How does you migrate mailbox to Exchange 2013? Do you have add baditemlimit parameter with New-MoveRequest? During my research, it might caused by too many bad items in mailbox. We can add this parameter to specifies the maximum number of bad items that are allowed before the request fails.

For example: New-MoveRequest user@contoso.com -baditemlimit 1050 -AcceptLargeDataLoss -TargetDatabase "DB"
Note: please run Remove-MoveRequest cmd to remove erarlier request first.

Thanks

Hi both, thanks for your answers- lots of good stuff to try here! I think the answer is going to be to remove any existing move requests, but I'm going to give Ed's command a go first (if only I could figure out what our system needs for identity, it's certainly not the UPN or email address!)

if you already have move request for that accounts, it should be deleted first and then run it again.

Enter:

Get-MoveRequest

To see whether a move request exists.  The first column will give you an identity, although you can use other forms.