Migrate Microsoft Teams Chatrooms/Channels
Support migration of Microsoft Teams
We need to do a tenant to tenant migration of Office 365. Your tool looks like it could aid with that, but my question is about Microsoft Teams migration. Aside from the Teams content that is in SharePoint, I have not found any supported method to other content from teams such as chats and channel conversation. Is Sharegate working on this?
We have officially started working on this and are aiming at releasing this before the summer.
We will still be looking at feedback given here to ensure that the experience will suits your needs.
We have the same situation here. we are aquiring companies and need to do tenant to tenant migration and we cannot migrate chat which is a major reason we are 'promoting teams'..
Is it possible with a one step copy action, to copy a (Template) Team, with SharePoint site?
If we use the Template functionality in Teams we get a new Team with the same channels and tabs. If we use the copy SharePoint sitecollection here, we copy the settings of the site collection but not the teams. Or is there a trick to this?
(The two step method is of course, create Team with the Team template, copy the required libraries and Sitepages for the layout and extra libraries).
Feedback sent from the Migration Report view.
Anny Boudreau commented
It would be good to have the ability of migrating O365 teams without having to create the empty teams beforehand and then using mapping.
Additionally. to be able to use Powershell to do this would be ideal for bigger scale operations.
Terry Mc commented
This is going to be a 'must have' feature soon. Microsoft is all in on Teams, and many organizations are as well.
So far, from what I can find there is no supported method to move Teams from tenant to tenant. What little can be done is quite manual and misses all the channel and chat conversations.
I put in a support request in O365 and was told by MS representative that it was not possible at this time.
I've been tasked with helping to move our O365 tenant after an acquisition and have run into a brick wall with this.