Are IPM.StickyNote and IPM.Task items producing item-level errors in MigrationWiz, without the logs clearly explaining why they are failing?

MigrationWiz does migrate IPM.StickyNote and IPM.Task, both MAPI message classes, but they tend to fail at higher rates than standard IPM.Note email items. Because each type fails in different ways, you typically need to test them separately to uncover the pattern.

IPM.StickyNote issues most commonly show up when notes were created in legacy Outlook versions that stored proprietary extended MAPI properties rather than standard schema properties. MigrationWiz can read the item, but it cannot translate the proprietary property schema into the destination mailbox format, so it logs a conversion error.

IPM.Task failures tend to cluster around task items that include file attachments. Exchange Online tasks can include attached files, but certain destination mailbox configurations or Exchange Online tenants with restrictive transport rules can block attachment write operations for task items. In those cases, MigrationWiz migrates the task body but fails on the attachment, and the item is reported as failed.

Make sure your test account pass includes at least one source account that has known IPM.StickyNote and IPM.Task content. It is better to surface the error rate during testing than to discover it after running the full production batch.

Are you including IPM.StickyNote and IPM.Task object types explicitly in your MigrationWiz test account validation?

#BitTitan #MigrationWiz