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.
This is a necessity. Once private channels is available many of us will want to migrate away from the private teams/channels and move those channels and conversations into the the primary team. Not having this ability defeats the purpose.
Right now we have:
Team A with a bunch if public channels (all our team members have access)
Team B with a single private channel (select member members of the above team have access)
Team C with a single private channel (select member members of the above team have access)
When private channels are enabled we want to have one Team A setup a follows:
Private Channel (restricted to Team B folks)
Private Channel (restricted to Team C folks)
Ryan Reynolds commented
this is a crucial part when you have used ALL available channels and then you have to create a 2nd one for overflow. some are inactive but needed for archive but hogging up the real team site channels. making the limit of channels larger would be great too.
Totally want this
if we can't move now; can we set permissions within a channel?
such that a subset of team members can view the channel
James Emanuelli commented
We have a number of teams but in one case we would like the ability to move a channel from one team to the other. EG: Channel is spun up by IT Projects, once the project is completed it should be handed over to the IT Operations department and moved to their team. I believe this should be part of a channels life cycle. The alternative is to have a team per service/application which is overkill, messy and confusing.
Mathieu Remy commented
Or maybe with a kind of "inter-teams channel-dump manager"
I find the use of channels extremly useful. But as tasks and information made in the setup is finnished, and was useful there, the setup team does to longer need access to the channel. I would like to be able to transfer the channel including all information to the maintenance, or day-to-day team that will handle the future work. Is it a possibility that is planned for? Moving channels between Teams.
And of course - move Wiki - now, don't know how to do it - only copy/paste every content manually - not good.
If it can't be done as move, than maybe easier will be to do it as copy?
- Copy all conversation
- Copy all files (it can easily be done by OneDrive app)
- Copy all TAB or one TAB - now it is necessary to copy/paste links to TAB and write names of TAB once again. IT is normall that the same TAB we need to use in different Team/Channel.
Jim Brook commented
As a teacher, I want to set up channels for different aspects of a course, with documents, tabs etc, and be able to replicate those to multiple classes. I do not want the conversations to be replicated.
Seth Tanner commented
I think the main concern is retaining the chat content for a specific channel. Having the ability to export channel contents to a standard format like json and then importing that content to a new channel in an existing team would probably solve half of this issue.
Andrew Chatham commented
Is there any update on this? Other PM platforms like Asana make this very easy, and the lack of this functionality makes implementation and reorganization of work extremely cumbersome.
If moving a channel to another team is difficult is it possible to link a channel from one team to another? I'm more of a business needs person than a developer, but I think this would work for what I need.
If you could @ to another Team/Channel that might help this problem. I submitted another idea for this. We still need to be able to move these Consolidate Teams and Channels or you end up having to much noise in your environment.
Carlton Barnes commented
Move channel to another Team very important too.
Brad Friedlander commented
This could be accomplished if there was an ability to archive a channel and then restore it to a different team.
Dave Kuehling commented
In my case, we have a "Sales Pursuit" channel in a broader team site. Would be great to take all that history and move it to a new team should that sale land and become a project/client. The other thing that may work is "Closing" the original channel and link to it from the new Team. Would be even better if when closing a channel for new content/contributions you could display a banner with the name/link of the new location. For my need of moving a channel, that could be an acceptable workaround.
John W commented
People new to Teams, such as myself, create teams and channels thinking we know what we are doing and later see that organization could be better or maybe a duty previously handled by one team is now performed by another. We need to be able to move channels between teams to maintain organization.
It would be great if channels can be easily moved between teams. It will make this app more flexible.
We have just started dogfooding Teams in our Tech department before rolling out to others. A project which started in one channel, we now realise reqiuires a different set of people from the original Team it was in. The inability to copy channels, or to add guests to a specific channel only from outside the Team means I now have to add people to the Team who aren't supposed to be in the Team! This is hugely frustrating.