Overview

When using SharePoint platforms as the destination, the migration job reports may display inflated destination values, or logs may indicate the creation of additional files. Below is an explanation of the variances.

• Job Overview Report: Bytes transferred may be larger than the source due to post-processing on the destination platform.
• Job Item and Log Report: A version conflict copy of the file may be created on the destination due to post-processing on the destination platform. A conflict copy will be the same file appended with a timestamp.

SharePoint Post-Processing

SharePoint-based storage providers have a post-processing step called “property demotion,” which occurs when a file is uploaded to a Document Library. When a file is uploaded, SharePoint determines whether a parser is associated with the file type. If one is, SharePoint invokes the parser, passing it the document and a property bag object. The parser then either fills the property bag with values that need to be promoted to the list or extracts from the property bag the values that need to be demoted to the document. When demoting values to a document, the document size may change. This can result in the overall number of bytes transferred to the destination being reported as larger than the source.

Content Scan and Migration Job Discrepancies

The file and folder counts for a content scan may not match those for a migration job using the same location. This variance is because migration jobs include the root folder in the folder count, but content scans do not. Migration jobs also include ignored/filtered content in the counts for auditing purposes, but content scans do not include filtered content in the counts.