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.
This feature should not only work for conversations but also for announcements and it should also be possible to forward such a message if you have not written it yourself.
Just to add on to the requirement. It will be better if after moving the original post to another channel, we can post a message that it has been moved to the 'new channel', and we can then change the original post to READ ONLY.
Our current workaround is, we copy the original post with all the replies and edit the post in the new channel, and includes the name of the person and date of the post. We also informed the 'poster' by #(Nameofposter) in the post on the new channel. It is very time-consuming.
John Smith commented
I have been facing the issue with the users starting the conversation in a wrong channel and request to move to another channel instead. This is quite a hectic issue. Recently found an interesting app that did this - Apps4pro teams migrator.
The TRY THIS INSTEAD is absolutly useless. Sometimes, when I read the Admins replys, I assume they don't use Teams themselves.
A thousand times, this! My organization (more specifically, my team within my organization) has growing pains with posting the right thing in the right place. As an administrator/owner of a team in a scenario where multiple sub-teams are used collectively by a single team, we need to be able to move a conversation that was started in the wrong place. We also need the ability to move a new thread to a reply as-needed, since it is commonplace for folks to not realize they're not replying inline.
To be able to move conversation to different Teams channel would help us alot.
Those cross posting instructions don't work when you edit existing posts; only on new posts. When he said "you can edit the message and cross-post," that is false.
@Alex Cross-posting is not a solution in any way whatsoever. The OP said "but gains importance". That means it has a bunch of replies, attachments etc. Also you cannot cross-post after a message has been posted (it doesn't make a difference though as copy and paste has the same effect)
Move conversation is different than cross-channel postings. Consider that someone just started conversation in wrong channel, we need solution how to move entire conversation with replies and attachments into other channel.
Not. Even. Close
Denis Derolez commented
On my Teams, the "Post in multiple channels" option only appears when creating a new conversation. If I modify an existing conversation or reply in the conversation thread, this option does not appear.
The "try this instead" misses completely the point of the original request. If the discussion around the original post evolves, so that the discussion gets more relevant to another channel, then it would be completely pointless and even misleading to just cross-post the top-level post to another channel...
Many thanks to @Alexander Weinhard for the viable workaround. Just tested it, it works and moves all replies, but it has not the same look as an original posting of this channel.
Try this instead doesn't work for our needs. We want this to move conversations from an old channel to a new private one.
[Deleted User] commented
This recommended solution assumes that we have the ability to "edit" messages. Our corporate IT policy is to treat Teams messages like emails, so we do not have the ability to edit them and therefore, this is not a viable workaround.
I can see that cross-posting is supported for new posts - but there doesn't seem to be any way to do this when editing an existing post. Do you mean that you plan to add that in a future update?
@Alex The cross-posting feature is not a solution whatsoever. Might as well copy and paste the message. It should be as easy as drag and dropping the conversation from one channel to another. Like grabbing it from the main pane into the left bar, just like moving a file in Windows Explorer. It comes without saying that all replies go along with it. Should only be able to move it into any channel in within the team, apart from private channel. Should be doable by the original poster or by a team owner.
As a bonus, this drag and drop feature could be extended to move a new conversation into another message as a reply. The terrible UI at the moment results in people starting new conversations when they are meant to be replies.
When you edit a message, the option to post to multiple channels doesn't appear. It only displays when you are creating a NEW message.
Admins should TEST before proposing workarounds
This is Microsoft quality most of the time, "try this and give us feedback" when they havent even try it before, shameless
Gavin Jones commented
The need for being able to move conversation threads is a must for aiding adoption for Team owners. People posting in the wrong channel should be able to have their conversation moved by the owner (or moderator) and notified that someone has done so.
The only alternative at the moment is not cross-posting (which hinders, not helps this scenario as you by definition have a split thread) but manually asking the post originator to delete their own message and re-post it in the "correct" channel. Even if they are willing, this workaround breaks down as soon as there are replies, leaving a deleted start of the thread and the replies still staying there.
Please add true functionality for owners and post creators to be able to move an entire thread to a different channel
Mark Volders commented
I understand the work-around, but it is not a valid suggestion. Users want to move the entire conversation with all of the replies. Reposting a message would also make it seem like a new conversation which is not the case.
If you want to build this right, you would have a conversation history so you would be able to see where the conversation was started and who moved it to another channel.
Yes, same here. I can only cross post when I create a new message.
Also, the point of "moving conversation" is to include all replies and assets (pictures, documents) included in the post. Moving the meta data of a post is also essential, because you do not want to lose context of when the post happened.