This article explains how to handle failed items for Exchange or Office 365 migrations before moving to Stage 2.
Archive Shuttle uses three ingestion methods by default. If an item fails with one of the methods the rest will be used as fall back for the item.
Best practice is to have the ingest methods in this order on the System configuration screen: AIP, EWSBatch, EWSSingle
Sometimes, none of the methods are able to ingest the item as the items are corrupted in some way, or are violating the MSG format.
In this case you can use the “Allow import of corrupted messages” switch on the System Configuration page, which will allow to ingest some of the failed items. It may not allow all of the failed items to be ingested, and if after making this change there are still some failures, a Support Ticket should be opened.
This switch should be used with care, as it will change the item in some visible or non-visible ways. The item will not be identical to the source item any longer.
If an item can not be ingested into the target environment, that item will remain on disk on the Staging Area.
There are two situations where items might remain on disk:
• If an item can not be ingested into the target environment, that item will remain on disk on the Staging Area.
• If a Container Mapping is deleted from Archive Shuttle, the items which currently exist on the Staging Area will not be cleaned up, unless they are manually removed.
In this case you might need to know how to identify such items on disk (staging area) for a container mapping.
For more info please go to the link: What does the Archive Shuttle folder structure look like in the Staging Area
Issues which are under investigation:
– Object reference not set to an instance of an object
– The docfile has been corrupted. (Exception from HRESULT: 0x80030109)
– Unable to convert ole attachment to png file