Migration Assessment Scan: Checked-out files

Learn about issues with checked-out files during data migration.


Migration reads the source SharePoint farm using an account that has Full Read access to the environment. If a file is checked out by a user, the migration tooling is not able to read the checked out file. However, the migration tooling will see the last checked in version of the file instead. To avoid losing data, users should check-in their files prior to their site migrating.

Data Migration

Only checked-in content will be migrated. To avoid any potential data loss, encourage users to check in their files prior to migration. A site administrator can check-in a file for a user, however only the content that was saved to SharePoint by the user would be migrated – if a user downloaded the file and was working on it outside of SharePoint, those changes would not appear post check-in.

Important: Any site that is configured as “No Access” (locked), in SharePoint will be skipped. To see a list of locked site collections see the Locked Sites scan output.

Preparing for Migration

Users should ensure that their content is checked-in prior to the migration date provided.

Post Migration

Site owners performing user acceptance testing (UAT) on their content should validate that their sites migrated correctly.

Scan Result Reports

The following table describes the columns in the CheckedOutFiles.csv report.

This scan report provides a view of the files that are checked out and which user has the files checked out at the time the scan was executed.




URL tothe site collection.


Site collection owner.


File that is chekced out.


User that has the file checked out.

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!