Migration Assessment Scan: Master Pages

Learn how to mitigate issues with Master pages during migration.


During migration, the default master page will be set on all sites that are migrated. This ensures that the site will render once the migration is complete as the content migration will not have a dependency on any custom master pages. If you have custom master pages assigned to sites, you will need to set the Master Page property on the new site after the migration has completed.

Data Migration

The custom master page files (*.master) can be migrated to the new platform as long as they are in the Master Page Gallery in the site. However, the setting on the destination site will be set to the default master page. This process ensures the site will render after the migration.

Important: 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

Review the report and determine where you can move away from custom master pages before you migrate. Plan and understand what post migration work will be necessary to use the customized file moving forward.

Post Migration

If you decide to continue using the customized master page on the new platform, you will need to apply the master page setting and validate your customizations work on the new platform.

Scan Result Reports

MasterPages.csv    This scan report contains all the sites that have a custom master page applied.




Site title


Server relative path to the non-default master page.


Server relative path to the site that contains the non-default master page.

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!