SharePoint Migration Tool (SPMT) – A Quick Look

  • Basically a GUI wrapper for PowerShell scripts to migrate content to SharePoint Online provided by Microsoft themselves
  • The PowerShell script are also able to be referenced by available cmdlet after loading the module (Import-Module Microsoft.SharePoint.MigrationTool.PowerShell )
  • Designed to be used for migrations ranging from the smallest set of files to a large scale enterprise migration
  • Officially only support SharePoint Server 2010 and 2013, also network and local file shares – Though is possible to make it work for 2016
  • Created By, Modified By, Date Created and Date Modified details will be copied where possible
  • Possible to tee up bulk migrations

Migration Tips

  • Scan source first using SharePoint Migration Assessment Tool
  • Split migrations into small chunks to improve speed (about 250MB per transfer)
  • For a larger than 100TB migration, please submit a support request

SharePoint Migration Assessment Tool – 2016 Support

  • Now you won’t get any support from Microsoft with this mod, but hey is there really any difference between 2013 and 2016
  • Open regedit.exe where you are running spmtsetup.exe and add the following
    • Create Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MigrationTool
    • New Multistring: SupportedSPVersions
    • Value: 15 16 (on separate lines)
SharePoint Migration Tool: Regedit


  • Download exe and run, Site Collection administrator is required at both sources and destination
  • Can perform full site collection or individual list/library migrations
  • Can tee up multiple jobs to run or save for later
  • Enough migration settings to manipulate to your needs
  • Option to perform a scan of content before actual migration take place
SharePoint Migration Tool: Settings
SharePoint Migration Tool – Progress

Great tool for migrating content, it won’t provide 100% coverage especially when you’re looking at classic features like master pages and the like.


Leave a Reply

Your email address will not be published. Required fields are marked *