Migration Assessment Scan: Unsupported Site Templates
Learn how to fix issues with Unsupported Site Templates during migration.
Overview
Every SharePoint site is based on a site template. In the SharePoint source environment, it was possible to create site collections using various default templates and templates deployed via Full Trust Code (FTC). However, site collections that are supported for migration are the Team Site and Personal Site templates. The Personal Site Template is used for creating Microsoft OneDrive sites.
Supported Site Templates:
| Template Friendly Name | Template | ID |
|---|---|---|
| TeamSite |
STS |
1 |
| Personal Site |
SPSPERS |
21 |
Data Migration
Any site that isn't using a Team Site or Personal Site template should be mapped to the Team Site template during migration. The content from the source environment is then copied into the new Team Site on the target.
Important
Any site that is configured as "No Access" (locked), in SharePoint would be skipped. To see a list of locked site collections see the Locked Sites scan output.
Preparing for Migration
Use the scan report for Unsupported Site Templates to identify site collections that are impacted. The impacted site's content is copied into a Team Site template during migration, but it's possible the Team Site template doesn't include the features/functionality of the source site.
Post Migration
Validate that your sites work post migration.
Scan Result Reports
UnsupportedWebTemplate-detail.csv This scan report contains a list of sites that are currently using a site template that isn't supported on the target platform.
| Column | Description |
|---|---|
| SiteId |
Unique identifier of the impacted site collection. |
| SiteURL |
URL to the impacted site collection. |
| SiteOwner |
Owner of the site collection. |
| SiteAdmins |
List of people listed as site collection administrators. |
| SiteSizeInMB |
Size of the size collection in megabytes [MB] |
| NumOfWebs |
Number of webs that exist in the site collection. |
| ContentDBName |
Name of the content database hosting the site collection. |
| ContentDBServerName |
SQL Server hosting the content database. |
| ContentDBSizeInMB |
Size of the content database hosting the site collection. |
| LastContentModifiedDate |
Date/Time the site collection had content modified. |
| TotalItemCount |
Total number of items found in the site collection. |
| Hits |
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 shows N/A. |
| DistinctUsers |
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 shows N/A. |
| DaysOfUsageData |
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. |
| FullURL |
URL to the impacted site. |
| WebID |
ID for the site that is linked to the invalid site template. |
| WebTitle |
Title for the impacted site. |
| WebTemplateID |
ID for the site template that isn't supported in the source environment. |
| WebTemplate |
Friendly name for the site template. If this is empty, it indicates that the site template is no longer registered on the source environment. |
| ScanID |
Unique identifier assigned to a specific execution of the SharePoint Migration Assessment Tool. |
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for