Move conversations to different channels
If a conversation is started in one channel but gains importance to the point where the conversation deserves its own channel. Or a conversation was started in the wrong channel and needs to be moved
if you have an existing post that you want to show in a different channel, you can edit the message and cross-post. This will add the top-level post to the different channel, but will not include the full set of replies. We will keep this request in mind as we evolve the cross-posting feature in the future and update if the status changes.
Details on cross posting can be found here: https://support.office.com/article/cross-post-a-channel-conversation-in-teams-9c1252a3-67ef-498e-a7c1-dd7147b3d295.
Kyla Lacey-Davidson commented
Any update on this? The workaround doesn't really resolve the issue...
@microsoft in October 2018, Admin Suphatra flagged this as 'working on it' (a year after marking as 'under review')
presumably 'working on it' is no longer the case?
Helen Gamage commented
You suggestion isn't helpful sometimes you need to move a channel into a new Team and get rid of the channel you can move all the files but not the whole chat thread.
Mike Trantham commented
I would like to vote for this feature.
This request started in 2016 and now has over 11 000 votes and still not resolved. Microsoft please can you address this issue.
Julie McCoy commented
Admin, your response is not helpful. The tip you gave is about cross-posting a new chat/post. What is needed is the ability to move or copy an existing conversation to another channel.
Unable to vote; still need this functionality
A common task for managing an online community is pruning and cleaning the forum. The open source phpBB has been able to do this for more than a decade.
If the "cross-posted" message was kept in sync in both places. That would be a viable work-around.
Unless there is something I missed, the suggested work-around is not significantly different than copy/pasting into a new post which splits it into parallel conversations.
What's the status of this idea? It's been three years now. I can imagine that some scenario would/should not allow for this to happen, but this can easily be address with an option at the Teams/Channel level to prevent moving threads around. Privacy obviously needs to be considered, but someone could just as well copy/screenshot the content. So in the end I think this should be implemented.
Just like we can move files around between folders and shares, we should be able to move threads around from channel to channel.
@Alex, as many have mentioned, the workaround you have offered is useful for a announcement, but falls short as soon as a conversation is concerned, because of the serious weaknesses of Team's cross-posting, which is simply creating two posts with no relation to each other whatsoever.
It's hard to keep channels neat and tidy. This is just facilitating that ability. It's that simple.
Eck Dolmick commented
Why is it not possible to move conversation to another channel? This is strange.
It would be great to enable linking existing chats to team channels. Proposed actions are not satisfying that need.
+1 for this feature. And No, cross-posting does not satisfy the request.
How many votes are necessary for a such change? 10k seems to be a lot already. :-)
Estudios Katz commented
It can move, merge, copy, archive and export channels ✅
In addition, can change channels from private to public and vice versa
Also available in Microsoft Appsource
I agree with Kirk and Aslam - Cross posting is not a solution to this challenge we need to be able to move conversations and I would strongly argue chats to other channels or promote them as new channels. Please help us. Chat is great and really facilitates communication and sharing but is terrible when it comes to preserving and organizing chats to the teams they belong in. In our case we use Teams for the customer and I really would like the ability to promote a chat to a new channel and have everyone on the chat be able to continue communicating but have it linked to the new channel so we can capture the history.
Cross posting isn't the solution. I've seen this many times and we just started using Teams.
A conversation it going in one channel, but someone chimes in with a new conversation that does not at all relate to the existing channel. It should not be in both, it should be moved. People just don't always stop and think - oh, this should be in another channel, then they would need to say - hey I'm posting in this other channel.
Aslam GC commented
I tried the “try this instead” tip to use cross posting but it comes with a couple of key issues that limit the usefulness of cross-posting, and fundamentally result in it not satisfying the spirit of the initial request:
1. Replies to a cross posted thread don’t show in both channels. So now we have two streams of conversation each with only half the story. This severely limits the value of cross posting right out of the gate. The idea behind posting a single thread to two channels is so members in both channels can participate in the conversation together, even individuals who may only have access to one channel or the other.
2. The moment you turn on cross posting, the ability to attach files to the post is lost. That limits use cases where we can leverage cross posting and in many cases necessitates creating two posts.
Those two issues alone severely limit the usefulness of cross-posting to the point where it is rarely a good option. This I encourage you to fix those issues with cross-posting to make it actually useful to us.
I’m addition, the idea of cross-posting also doesn’t truly satisfy the spirit and use case of the original feature request. The request was a to move a whole conversation from one channel to another. The example given was if a conversation started in one channel but has now grown in importance enough to require its own channel. When we start the new channel, we obviously want the history of the conversation to come along with it and thus bootstrap the conversation. Cross-posting ok it’s current form doesn’t accomplish that at all because only the original post, without any of the subsequent conversation, would come along.
Thus I request you folks to take another look at allowing conversations to be moved from one channel to another.
+1 for this feature
Mike H commented
I have seen several posts on this going back to 2017 and I cannot understand why this basic functionality of being able to move conversations let alone tabs, files or even moving a channel from one team is still not available / part of MS Team core functionality.
Also it seems yet again another Microsoft UserVoice not being listened to especially as this has over 10,000 VOTES!!!!!
Please add this feature let alone the ability to copy / move a channel from one team to another. This is needed to reflect real life - people do get moved from one Team to another within an organisation everyday!