Much like the Migration Manager which is used to migrate files, the SharePoint Migration Tool is used to migrate content from SharePoint servers to SharePoint in Microsoft 365. The first thing any organization should consider is if this tool is possible to be used in the first place. The SharePoint Migration Tool supports migration to SharePoint, One Drive, and Teams from SharePoint Servers 2010, 2013, and 2016, as well as SharePoint Foundations 2010 and 2013. As long as you meet the requirements, you can start considering use of the SharePoint Migration Tool. The SharePoint Migration Tool is capable of migrating things like files, folders and lists, user files and folder permissions, site migrations, taxonomy migrations, and more. Since it covers such a wide range of features, it can be overwhelming at first. However, Microsoft provides something called the SharePoint Migration Assessment Tool to organizations, that they can use to help assess the migration's impact beforehand.

This tool can be run in the background without affecting the environment that's being scanned and can help identify potential issues with the data plan to be migrated. Once the scan is complete, it provides logs alongside links to articles to aid you in fixing any issues that may come up during the assessment. For more information on the SharePoint Migration Assessment Tool, please refer to the documentation below. When you've determined that your environment is ready for the migration, there is a 3-step process to follow, much like the Migration Manager we spoke about in the last lecture. 

Step 1, install the SharePoint Migration Tool. Step 2, create migration tasks. And step 3, monitor and report. To install the SharePoint Migration Tool, you must download it from Microsoft site and ensure that you have proper permissions in order to use it. For example, users must have either a global or SharePoint admin privileges to migrate at the organization's level or site admin privileges to migrate at the site collection level. It also has certain requirements for the system utilizing the tool as well as the required endpoints in order to run it.

For a full list of requirements, I've provided documentation below for you to review. Once the tool is installed, you're ready to move on to step 2, which is creation of migration tasks. The tool has multiple migration types which you can process, such as a site migration; which would allow for the migrating of a single site or all sub-sites. A list and document library migration. A workflow migration which would migrate a SharePoint server workflow to Power Automate. And bulk migrations using a CSV or JSON file, which enables migration of a large number of sources which can be uploaded into this SharePoint tool. Unfortunately, I have no way of demonstrating this step. However, each of these types of migrations work similarly to the Migration Manager. When you first open SPMT, you'll be prompted for the Microsoft 365 username and password.

You'll then need to log into your SharePoint Server site credentials and direct where you want the migration to go to. Once the migration is in process, you are now into step 3, which is monitoring and reporting of the migration tasks. The tool generates logs and reports as tasks are completed to help organizations monitor their migration process. It generates a wide range of reports, which all provide additional insights into different areas of the migration process. For more information on the reports and report types, I have linked documentation below for your review.