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.
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.
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.
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-detail.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.
||Unique identifier of the impacted site collection.
||URL to the impacted site collection.
||Owner of the site collection.
||List of people listed as site collection administrators.
||Size of the size collection in megabytes [MB]
||Number of webs that exist in the site collection.
||Name of the content database hosting the site collection.
||SQL Server hosting the content database.
||Size of the content database hosting the site collection.
||Date/Time the site collection had content modified.
||Total number of items found in the site collection.
||Number of requests logged for the site collection. Relies on data from the usage logging service. If the usage logging service is disabled this row will show N/A.
||Number of distinct users that have accessed the site collection. Relies on data from the usage logging service. If the usage logging service is disabled this row will show N/A.
||Number of days the usage logging service retains data. This provides context for Hits and DistinctUsers. For example, if this is 14 days, the Hits and DistinctUsers data is for the last 14 days.
||File that is chekced out.
||User that has the file checked out.
||Unique identifier assigned to a specific execution of the SharePoint Migration Assessment Tool.