Some of you may have noticed that more migrations might be failing due to encountering 'too many bad items'. Upon closer review, you may notice that the migration report contains entries referencing ...
Updated Jul 01, 2019
Version 2.0
Blog Post
8 MIN READ
TooManyBadItemsPermanentException error when migrating to Exchange Online?
Ben, I have just gone through a long and painful PST import process just recently, having to clean up after a botched migration.
There was a clean PST export from the on-prem Ex2010 mailboxes, followed by an import to O365 of those PST files. Many of the imports failed with hundreds of "bad items".
To the best of my knowledge, bad items don't make their way into the PST file during an export. So why that many bad items? Surprise #1.
Moreover, unlike migration logs, the PST import logs failed to identify the invalid items, or these items were deemed "bad". Surprise #2.
I opened a case with Microsoft support. They were unable to give me a satisfying answer. "Dunno. Can't tell." was the answer. Surprise #3.
Are there any plans to document how to identify what failed in a PST import, or whether those failures can be ignored or should be investigated?
Thanks.