Designed to simplify your journey to the cloud through a free, simple, and fast solution, the SharePoint Migration Tools enables you to migrate content from on-premises SharePoint sites and shares to SharePoint, OneDrive, and Microsoft Teams in Office 365.


Content provides the center of gravity for collaboration, whether in SharePoint, OneDrive, or Microsoft Teams. 


Using the SharePoint Migration Tool, you can quickly bring your most important content to Microsoft Teams to create a more open, digital environment. 


Microsoft Teams is a chat-based workspace that brings together people, conversations, content and tools—creating a more open, digital environment. Threaded conversations make it easy to understand what each employee is referencing, and employees can co-author and collaborate on Word, Excel, PowerPoint, and OneNote documents without ever leaving the app.


Since each team in Microsoft Teams has a team site in SharePoint Online, the SharePoint Migration Tool provides a quick and simple solution to bringing your files to Microsoft Teams in Office 365.


Getting started with Microsoft Teams Migrations

Download the latest release of the SharePoint Migration Tool at https://aka.ms/SPMT.

Select the Team you would like to migrate your network shares, home directories, on-premises SharePoint or OneDrive files to in Microsoft Teams.


Select the ellipses in the Team and then select open in SharePoint.




Note the SharePoint site URL associated with the selected Microsoft Team.


Open the SharePoint Migration Tool.  When you first launch the SharePoint Migration Tool (SPMT), you will be prompted for your Office 365 username and password. The Office 365 credentials you provide will be where the files will be migrated.




Choose the location of the source files.  The SharePoint Migration Tool supports local, shared content such as network shares, home directories, etc. and SharePoint Server 2013 lists and libraries.


Enter the SharePoint site URL from the previous steps associated with the Team.




Click Next to setup and complete the migration.


NOTE The SharePoint Migration Tool user interface supports mapping migration tasks that are scoped to Document Libraries.  For scenarios in which you would like to migrate files into specific Microsoft Teams Channels folders, you can use the Windows PowerShell cmdlets and specify the appropriate relative paths.  For more information on mapping folders with SharePoint Migration Tool see also https://docs.microsoft.com/en-us/sharepointmigration/how-to-format-your-csv-file-for-data-content-mi...


Next Steps

Learn more on how to use the SharePoint Migration Tool at https://docs.microsoft.com/en-us/sharepointmigration/how-to-use-the-sharepoint-migration-tool.

Learn more about Microsoft Teams and SharePoint at https://docs.microsoft.com/en-us/MicrosoftTeams/sharepoint-onedrive-interact.

New Contributor

Why calling it a Teams Migration? When you follow these steps in the GUI you will not even see the Files in your Teams. Because you need to migrate to the "General" folder in the Document Library, Just a little NOTE at the end...

Not so good article to have a headline like "Teams Migration" and don´t even give this HINT with the General (or other Channel Folders) to the users.

Respected Contributor

When I saw the title I was expecting something to help move chats, channels, tabs and apps but none of that is supported by this tool. I agree with @André Thümmel , the title is very misleading 

Senior Member

I was wondering if there has been any further development with regards to teams and doc libraries to channels migration? We have a 2010 environment so I have been debating on a SP on prem to online migration but I want teams to be the end goal so each library would appear as a channel/   

Occasional Visitor
I like the idea to migrate SharePoint sites directly into Teams, so that the power of Teams can be made available directly or at some point after the migration. The article points out that that is possible. The migrated content is reachable in two ways: 1. Through SharePoint (lift and shift migrated content) 2. Through Teams (albeit not in channels) However, I would migrate into a new Library in Teams (e.g. Migrated documents) rather than the Teams Documents library. In that way, the Teams Document library is solely used by the channels as intended, and the migrated content seperated. This could also ease retention of unused content from the migrated library.