This article lists the variables for site complexity and explains what determines the complexity of the site.
When a site contains at least one of the findings in these categories below, then it is categorized accordingly.
For Example: If a site contains just one Workflow it will be categorized as Complex. As Workflows are categorized as high severity.
Simple
| Rule | Description | Severity |
| Site has unique permissions | Sites with unique permissions (broken inheritance) are not allowed in the target environment" | Information |
| List has unique permissions | Lists with unique permissions (broken inheritance) are not allowed in the target environment. | Information |
Moderate
| Rule | Description | Severity |
| WebApplication has permissive BrowserFileHandling | The Browser File Handling settings on the Web Applications in SharePoint impact how you can browse certain file types. | Warning |
| WebApplication uses policies to grant or deny blanket-level permissions | SharePoint On Premise allows the use of web application policies to grant or deny blanket-level permissions to entire web applications. These permissions override any permissions set at the site collection, site, list/library, or item level. | Warning |
| Site has subsites | Warning | |
| List has too many unique role assignments | Lists can contain too many unique role assignments (e.g.> 5000) which impacts performance | Warning |
| Site contains custom list | Site contains a list with a custom list definition | Crictical Warning |
| Site has custom permission level | Some migration tools have problems moving custom permission levels to SharePoint Online | Crictical Warning |
| Site is larger than 500GB | Sites with more than 500GB might take a longer period of time to migrate | Crictical Warning |
| Web has specific language template | In SharePoint it is possible to install language packs and create sites leveraging multiple languages. During a migration, additional planning is required to validate sites that are not using a language familiar to the migration team. | Crictical Warning |
Complex
| Rule | Description | Severity |
| Site contains large list | Site contains a list with more than 5000 items | Error |
| Site uses Report Viewer WebParts | A page in the site contain a webpart for Report Viewer | Error |
| Site uses Excel Services WebParts | A page in the site contain a webpart for Excel Services | Error |
| List has IRM enabled | IRM settings associated with lists and libraries are not migrated. | Critical Error |
| List is external list | External lists are those lists that were created from a Business Catalogs Services [BCS] application. These are lists that appear to be SharePoint Lists, but are actually backed by an external datasource. | Critical Error |
| List has email alias enabled | On the source environment it is possible to configure lists that can accept incoming email. This feature is not available on the target environment. | Critical Error |
| List has large list view | Any list views containing over 12 lookup columns may also be throttled and require remediation. | Critical Error |
| List has running workflow | Workflow definitions will migrate, however in progress workflow information will not be migrated. | Critical Error |
| List has checked out files | 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. | Critical Error |
| List has files with many versions | Versions have historically impacted the length of a migration for a given site in a linear fashion. The more versions you have, the longer it will take to migrate a given site. | Critical Error |
| Web has running workflow | Workflow definitions will migrate, however in progress workflow information will not be migrated. | Critical Error |
| Site uses Sandboxed Solution with Code | Critical Error | |
| Site contains SharePoint Designer workflow | SharePoint Designer Workflows are still supported in the new platform, but to avoid efforts for migration of them unused workflows should be removed. | Critical Error |
| Site contains custom master page | Critical Error | |
| Site contains Nintex workflow | Nintex Workflow may not be supported on the target environment and must be removed. | Critical Error |
| Site contains modified custom master page | Critical Error | |
| Site contains InfoPath Form | InfoPath Forms are still supported in the new platform, but to avoid efforts for migration of them unused forms should be removed. | Critical Error |
| Site uses SiteMailbox feature | The site mail box feature is activated in the site | Critical Error |
Note: Sites gain the severity rating for the highest level rule encountered.