The Pre-check report shows you possible warnings and errors that can occur when you run your migration.
At any time, you can view and export your Pre-check reports by selecting Tasks from the menu.
- Item count
A warning indicates that to migrate the item to the destination a modification will need to be made or something will need to be left out. A common example is a list that migrates without a source field because that field is not supported in the destination environment. Warnings generally occur because something is not supported between versions.
An error indicates that the app will not able to migrate the item to the destination. Errors can be complex, and always have associated error codes and articles to help you work through why the error occurred and to indicate if there is a solution or workaround. Click the Help me solve this issue link to access the corresponding help center article.
The Pre-check report provides information on permissions, users and groups, the site architecture, and more.
In the report, select any item from the Details column for more information.
The app verifies that you have sufficient rights to run the migration. The Pre-check report will highlight any permissions that are missing. For details on what permissions are required for each type of migration, see the help center category Administrative permissions.
Users and groups
The Pre-check report will indicate if a user or a group no longer exists at the destination and how you can resolve the issue. For example, a common suggestion for resolving orphaned users is the Users and groups mappings feature or the Permission levels mappings feature.
Sites architecture - Site templates, language, navigation, web parts, and so on, are checked before the migration. A common warning is a nonexistent destination site template, which can be resolved with the Site template mappings feature.
Metadata validation - The pre-check will analyze every column, content type, and managed metadata linked to a document, a library, a list, or a site to ensure that your information architecture remains the same.
Workflows - The app will check that your workflows can be migrated to the destination. A common issue is when migrating Nintex Workflows from on-premises to Microsoft 365, in which case, the Pre-check report will list all properties that are not available at the destination for each action.
Site collection and site features - The Pre-check report will alert you when a specific feature is deprecated at the target if you are migrating to a newer version of SharePoint.
Some features need the server extension installed on both the source and destination to be supported. For example, the server extension is needed for User Alerts, and to preserve the authors and timestamps.
The Pre-check report will provide a prompt for you to install or update the server extension if it's needed for your migration. For more information, see the help center category Server extension.
The Pre-check report will list all the unsupported features.
The Item count column displays the number of items affected by the warning or message. While the pre-check is running, this number will be automatically updated.