Migration Assessment Scan: InfoPath
Learn how to mitigate issues with InfoPath during migration.
InfoPath enables developers to build custom forms for accepting user input in a variety of locations throughout SharePoint. As part of the migration to the target environment, there are certain aspects of InfoPath forms that are not supported in the target environment.
InfoPath forms (XSN files) will be migrated, but some forms may not function without remediation.
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
XSN files that leverage the following scenarios will need to be remediated. If remediation does not occur, these forms will fail post migration. The common scenarios are as follows:
XSN or UDCX makes SOAP calls that are not supported in the target environment. These forms will need to be updated to call supported endpoints.
XSN leverages managed code that will require remediation. Managed code is not supported on the target platform.
InfoPath forms that leverage people picker fields. These fields need to be updated with the new user's identity post migration. This is because the on-premises identity (e.g. Windows claims) does not match the user's Azure AD/Office 365 identity.
Ensure the updated InfoPath forms function correctly during the migration user acceptance testing phase.
Scan Result Reports
The following table describes the columns in the InfoPath-detail.csv report.
This scan report contains InfoPath forms that will require remediation prior to migration, or at a minimum, validation on the new platform.
||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.
||Locations of the XSN.
||Unique identifier for the XSN file. Each XSN file will have a distinct URN.
||SOAP calls that are not explicitly listed as supported by the target environment.
||Number of unsupported SOAP calls found in the XSN file.
||Data connections that are not supported on the new platform.
||Number of unsupported data connections.
||True - The XSN file has managed code associated with it. False - The XSN file does not have managed code associated with it.
||ValidationRequired - Managed code may work in the target environment. It will require validation during the migration testing phase to be sure.
RemediationRequired - The form has managed code that will require remediation.
||The mode that the form was published in. For example, a mode of "Client" results in an InfoPath form that will only open in the InfoPath client. Whereas a mode of "Client Server" will open in both the browser and the InfoPath client. Forms with mode set to Client will not show up in this report.
||Number of people picker fields found in the form.
||This field is no longer used and can be ignored.
||Version of InfoPath used to publish the form.
||Unique identifier assigned to a specific execution of the SharePoint Migration Assessment Tool.