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.
Peter van Londen commented
six months now - it would be time for an update Suphatra.
What does the microsoft team intend to do?
This feature is surely missing. So much, I am not sure if we might have to look for another solution.
We have a team already hitting the roof on channel limit. (100) for this reason we would also like to move channels to an Archive Team.
Guillaume BM commented
The product is in continuous improvement.
Today we do not have private channel, so we're building team separately if needed.
But when private channel will be possible, we would like to be able to move channel (at least basic tabs likes Chat, Files and OneNote) to another team.
This would be great
Emanuele C commented
As discussions continue its sometimes useful to move a chat to a dedicated channel so as not to confuse the current channel discussion.
I would like (for admins) to be able to select individual comments (and direct replies) to another channel.
Amer Ghafari commented
Can these votes be consolidated with the same request that was already made, called "moving channels between Teams." It already has 21 votes.
Amer Ghafari commented
Any update on this?
It would be great to have the feature to move an entire channel and its content from one place to another. It will make it flexible and efficient
PD Garaguso commented
We need this feature as part of our workflow. There should be a way to move the content from a channel (files, tabs, etc) into another team/channel.
Tuomas Kallio commented
Also important feature to our company. Now it's a big work, downloading everythinh to local tempo folder, then creating structure in another team/channel and uploading everything (20 files / time).
Keagan Pearson commented
If we could be able to export the channel content (conversations, tabs, settings) that would would be a start. We could then just upload the content to our new channel in the new team and then link the SharePoint documents folder with the new team on the back side. The documents are easy enough to do that way right now, but losing all the dialog attached to that channel is a deal breaker with being able to move a channel to a more appropriate location when it's reached a predetermined stage.
David Gibson commented
I've created a channel in a leadership aka management Team. The project has grown and I'd like to move the entire channel to a bigger Team so we can include staff members.
I recognise this would share the entire history, but this is simply an area to take care.
Tim Conroy commented
This is something we need as well, primarily to deal with shifting user responsibilities and/or business objectives.
While I can't think of a work-around that actually works, the closest approximation I can come up with is copying channel history to a document and then storing the document in the new Team's files. This would require exporting the chat, preferably with meta-data (user, time, thread), and making it searchable in the new Team.
It would be very helpful to copy content from one channel to other.
I just want to be able to set the order of channels in my team to mirror the sequence we will follow for the project. Step 1 being before Step 2, etc. Now, they are alphabetically arranged and I named them descriptively (task oriented) rather than Step 1, etc. That should be easy enough, right?
Michael van der Haven commented
Work-arounds are probably not what we're waiting for. I'm used to the option in Slack, and given the organization I'm currently in where reorganizations and relocations of sub-teams (with their own channel, where I hate the fact that private channels are not available as well), moving a channel from one-team to the other is a must.
A work-around would be to copy the complete conversation stack in the channel, but then we lose the meta-data. (and in all honesty: from a compliance perspective this simply needs to be available)
Maybe an easier way to accomplish this would be to have the option of copying a channel's content into a different channel. That way the architecture of the current channel doesn't have to be shifted, just the content. This could then be governed by existing permissions and DLP policies.It could be presented in the UI as a "move channel" and prompt for a couple variables such as:
Target Channel Options: Copy into existing channel, or even create a new channel.
How to set new permissions: maintain existing, reset based on target channel settings, no permissions (set later)
What to do with the source channel: can be hidden, archived, or deleted per many of the other top voted requests.
In essence, a wizard that mimics or even re-uses the existing new channel dialogue. Taken to the next logical stage, it becomes a part of the default new channel dialogue, so when creating a channel you're even asked if you want to start a new channel from scratch, copy and existing channel, or "migrate" an existing channel.
David Gibson commented
I need to be able to move a channel to a new team. Teams are tied to Groups and I cannot always add new members to the Group. For example, a project starts inside the leadership team and then grows to include many new members. How do I move the old channel or its contents to a new channel in a Group/Team that can include other members?
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