Move channels into other teams
We would like to move a project (channel) between groups to keep the information, or be able to sort channels to our liking.
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
I was excited when I started using MS Teams. But the moment when I realized we cant move channels across, it let me down like anything. I felt sharepoint is a much better still.
We need this feature ASAP this is letting everyone down. The workaround also doesnt work either, tried moving the sharepoint folders nothing worked for me.
Katherine Dunne commented
I've very interested in the ability to merge channels
Hopefully the roadmap update posted here
and showing a last update of 9/16 supersedes the last update from Alex. Migrating from Slack to Teams and not being able to pin the channels I care about out of a team is a BRUTAL user experience. I don't need AI to figure out what I like, I need to be able to direct the application to show what I NEED, NOW.
How can the 6th most voted request is still in backlog while other less voted ones are being worked out? Quite strange...
Nuno Marques commented
Within projects it is very common to sometimes have to create an offshoot or to reorganize the entire project. Sometimes, new project even pick up where old ones left off. The need in any case to either move or copy the channel and content to new teams is a necessity as projects are often time volatile and evolving in nature.
To see this item pushed back so many time on the backlog is disheartening. I am sure there are reasons whey something takes priority over another, but since we don't know what these reasons are, we feel a bit cheated that a feature that is in the works doesn't see any progress for close to two years while others, in our eyes less important, get implemented.
New features, implementations and ideas could maybe be voted upon for transparency's sake, by letting users add suggestions to a poll and let all users vote on this poll, so there would be a visual representation of how important our "very urgent, should be top priority" issue really is compared to what other users feel is needed. At least this way we wouldn't feel so cheated when we realize our really important issue is only ranked 20th among users with 500 votes against the number one issue, with over 25000 votes, for instance.
This is just a rant / thought. Had to get it off my chest as I have been waiting for this for a loooooooong time. The need has now become so great I have even found myself exploring alternative Project Management Software to see if it would be worth shifting over.
Taylor Pfaff commented
This is a super important feature for us when we have re-orgs! I need to be able to migrate users data from one team to another.
guys, you can´t move such an important issue to the backlog again. So far I thought MS is a customer oriented company
While I know we can copy a team, this feature "Move channels into other teams" would greatly help us doing projects. I want to setup up two channels as "Waterfall" & "Agile" project templates. My Project Managers would then be able to copy either of these template channels to a new channel to create a new project site. It also then provides me a way of seeing all active projects since they are under my "IT Project" team space.
This feature request has an immense amount of votes, why is it being delayed? - unbelievable.
That's really a shame that this got moved to the backburner again. I posted my homegrown fix last year (35 pages of comments ago...) and am reposting for the benefit of the community:
I found a workaround. By opening the SharePoint library created by Teams in Windows Explorer, I was able to drag-and-drop libraries from existing channels into the new, replacement channels.
We will lose the conversation history, which is acceptable. We will have access to the historical tasks through Planner, and any incomplete tasks will be recreated in the new channels.
It's not as clean as moving the entire channel would be, but enables us to restructure our teams and channels without losing (or manually recreating) documents and libraries. Not a bad workaround.
Andre LaRouche commented
PLEASE PLEASE PLEASE!!! We need this. We had originally organized our teams in a particular way using channels and now we need to move to a different team for each project. We dont want to start over, but this is a major hurdle for us.
When could this get resolved? It was at one point in process and now its back on the backlog.
Has this been accomplished yet? If not, do you know when it will be coming?
Is there an update on this? as we really need this copy/move channels
Chen Oren commented
this is a way for us to handle the learning curve.... doesn't need to be pretty, just working...
Brian Stewart commented
Agree that it will be useful to be able to move channels, but was wondering if it is possible to duplicate \ mirror channels within different Teams?
Mike Bielby commented
I would like this feature too. We moved some of the responsibility to another Team and they asked if we could have the Channel for that functionality so no information was lost for the new Team. I was surprised when I couldn't do it. I was expecting some "drag and drop" operation from one Team to another of the Channel. Boo!
Dariusz Kosmala commented
This would be a great feature, as will address ongoing changes to enterprise organizational structure.
This is a common need, please prioritise!
George McRobbie commented
The ability to create Private Channels and move Channels within Teams would be hugely beneficial from an organisational point of view. Our Teams become "Chapters" with Channels being projects that move across as they develop.
Is there are a workaround at all? We got very excited setting up multiple teams and now to trying to combine (to really collaborate) and having problems. Will just have to copy and lose the conversations...