Move a project (channel) from one team to another
We would like to move a project (channel) between groups to keep the information.
This continues to be on our backlog due to prioritization of other work items. We will update when there is more to share.
Another example of Microsoft simply not caring what its customers want. This has been a top voted topic for over 3 years.
If your company really needs this feature, I would suggest looking into using AGATs solution for this
Üllar Aun commented
Topic raised from March 2017, still unsolved? It would a very and useful. It saves time in creating new channels and maintains a common structure in similar workshops in the company.
Should be logical and as default feature?
Jeff Koertzen commented
I, too, am surprised this feature is not yet available. We have people creating teams and then realizing they would be better suited as channels in another team. We would like to be able to migrate those channels into another team. We are a small organization, so I am fine if the first iteration requires the admin to process.
This is HIGHLY NEEDED by everyone who is now or will ever become a moderate teams user. Things change, organizations change, permissions change...content should be able to move between teams to flex with ever changing organizations.
Please move out of backlog and into progress.
It would save us loads of time spent moving channel content manually.
Thank you in advance :)
Ed Hansberry commented
Really need this. We are having issues just moving files from one team to another to move data related to a channel we want to move. Older XLS/DOC/PPT files often get left behind. hoping this channel move makes the whole thing better.
Would love to see this change implemented.
Herschel Salan commented
This is sitting out there for 3 years. Really. C'mon MS Teams Developers
Cassandra Stelter commented
This is definitely a critical feature moving forward. My users are drowning in teams that should be consolidated now with the improved access controls generated by private channels. Please implement ASAP- I'm in danger of being switched to a program more navigable for my users.
This is essential for us. We are heavy users but now that private channels are around we want to merge many Teams into one without losing our conversation history.
AGAT software really helps with this
This is a must have for using teams as a PM tool
Tony L Kuper commented
This would be great to get off the backlog, now that we have private channels this will makes thing much more clean and simple. Thank you.
PLEASE take this off the backlog! Now that the private channels are available it means I can finally create teams in the hierarchy I want and with the access control required. What's required now is to be able to consolidate all the disparate teams/channels that were created to get around the lack of private channel/access control.
Going to add my voice to the masses. Not sure I can imagine too many more basic need than this one... PLEASE take this off the backlog!!!
Jeremie McGaw commented
Hi, progress? The more we use Teams, the more we learn and the more we need to move things around...
Is there any progress on this functionality?
Anthony J. Guzzi commented
Personally, amazed that this feature does not already exist. Would seem like a 'Day 1' feature. In our organizations teams of people are formed with subteams (similar to channels) which may move from one team to another as experience and events dictate. So why won't that also be true of channels in MS/Teams? And just as software goes through life-cycles and major versions, wouldn't the teams used by a particular organization also go through similar life-cycles? Seems like a big hole in the product's features to me. Maybe it's not something that everyone can do but at least the product's administrators should be able to do.
Need badly as well!