Migration Assessment Scan: Apps
Learn how to mitigate issues with SharePoint add-ins during migration.
Migrating SharePoint add-ins (formerly called apps) isn't supported in the target environment. The site content will be migrated, but the add-ins will not. As a result, once the site is migrated, the add-ins will need to be reinstalled. If you purchased the add-in, you will need to reclaim the license from the Add-in store.
Site content will be migrated, but add-ins will need to be installed on the destination environment. If any add-ins stored data in the SharePoint App-web, that data will be orphaned and the add-in will be reinstalled cleanly.
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
Read through the provided report.
Site owners will need to reinstall the add-in during the user acceptance testing (UAT) process. If there was an add-in that was purchased, the user who purchased the add-in will need to recover the license.
Scan Result Reports
The following table describes the columns in the Apps-detail.csv report.
This scan report provides a list of all the add-ins installed in the environment.
||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.
||Owner of the site collection. [duplicate of Site Owner column]
||Display name for the owner.
||Title of the add-in.
||This is the location the application was installed from.
||ID assigned to the add-in.
||ID or the web hosting the add-in.
||URL used to launch the add-in. If this URL is ~appWebUrl, then the add-in runs on the SharePoint environment. If the URL is not associated with the SharePoint environment, then the add-in is a provider-hosted add-in that runs outside of the environment.
||Time the add-in was installed.
||If the add-in is a provider-hosted add-in, this will contain the URL for the add-in.
||URL for the settings page associated with an add-in.
||Title of the web hosting the add-in.
||URL of the webhosting the add-in.
||If the add-in is an app part that sites on a page, this will be the URL to the page.
||Unique identifier assigned to a specific execution of the SharePoint Migration Assessment Tool.