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.
Gordon Barr commented
I think that the 'move a channel from one team to another' is probably more useful than just moving the convo history.
Cross-posting seems like a "good enough" solution when posting in the wrong channel.
Victor Taranov commented
Ability to move conversations between channels is critical! Without this feature, MS Teams quickly turns into an annoying garbage. People tend to make mistakes, and they should be able to correct them.
Please enable this feature
Steve Digby commented
Please make this happen as soon as possible, it will make a big difference
Eric Kruger commented
It boggles my mind that Microsoft Teams has not figured out how to build in this functionality. The point of using Teams and conversations is so that project managers/moderators can create an efficient space for project related conversations and sub-conversations. Without the ability to do this the product is severely handicapped. The fact that a third-party has figured out how to do this is even more annoying since it appears that enabling a feature like this would be low hanging fruit. I am not sure how Microsoft expects its products to be adopted when they are severely handicapped
Given that renaming channels doesn't rename folders we find that we have needed to create distinct channels essentially starting from scratch. We can move most things but not conversations. This is due to the twin issue that you can't export content from a channel but also that you can't move a conversation. The pretty patronising 'try this instead' totally misses the point of what this request is about.
Cross-posting so that the conversation is on TWO channels does NOT solve the problem - especially since it does not include the full set of replies. It is critical to be able to MOVE conversations from where they are often incorrectly posted to where they need to be.
would be great if we can move post threads to different channels.
Bob Van der Kloot commented
We would really like to migrate existing ongoing chats into channels, so that they can be separated by topic rather than by membership.
Marvin Taylor commented
Another use case (if truly needed): We are aggregating business process documentation to align with new process definitions and need to move files and posts from one team/channel to another to maintain discussion as part of the overall process documentation. Copy/crosspost does not meet the needs.
Shawn Fielding commented
Right now, my "solution" is to manually copy and paste the message and all subsequent responses in the other channel with the prefix "From ***." This is so far from ideal that it is laughable. But hey, until MS gets their act together, it's all I got.
Leonard Cornelisse commented
In case you need a use case... A group of employees recently started a chat group, with multiple posts. The topic has now become a project and the members of that chat group have formed an MS Team. They would like to add additional members to the team and keep the history of the original chat. Ideally, the chat would be added as a channel to the newly formed team.
Jason Randall commented
@Alex (Teams Engineering, Microsoft Teams)
> 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.
I tried your solution to edit someone else's post but despite being a team owner, I was unable to. At most, I could delete their post. As a team owner/moderator, I need to the ability to move a post to an appropriate channel otherwise I'll need to screenshot the post then re-post it myself in the correct channel - obviously that's far from ideal.
Mike DePouw commented
>Try this instead
Hi Alex - thanks for the update but that's a HACK and not a very good one IMHO.
>but will not include the full set of replies
Please implement the original ask "move conversations", thanks! 😊
Conversations often start ad-hoc in chat among a group of developers independent of a specific team project. The majority of these reach conclusion and naturally terminate, but for some we will add an appropriate title to give the conversation focus once it's reached critical mass. But then there is no way to then move this into an appropriate team channel and preserve the genesis of the conversation. This is a critical feature to teams that brainstorm ideas or discuss a problem outside of a specific Team channel.
“Try this instead” is NOT the answer! Being able to move a conversation is....
As others have said, I often wonder whether MS employees use their own products! 😳
Re-posting in another channel is unsuitable. The entire conversation (replies/reactions etc) needs to transfer or we're talking about loss of data and decisions. This isn't just about posting in the wrong channel; you may post in the correct channel, but that piece of work grows and now needs it's own dedicated channel and the historic posts need to be transferred there.
Brigitte Peeters commented
This is really needed with the reply's because of the need for overview and mistakes are quickly made + reply's are done before the owner sees this! Please fix this asap
Dear friends, moving of messages, part of a conversation or whole conversation to another channel is the "must-have" feature for our company. It is the right step to clean up and organize our discussions and workflows.
Take the implementation of this feature high priority! Thank you!
Sorry, but the cross-post is not the same as the moving of messages, and it is not a good replacement.
So this concern was raised in - as far as I can see - Sept 2017 then backlogged until Oct 2018 when we were advised Microsoft are 'Working on it'.
We are now halfway through 2020 and in the current pandemic environment with hundreds of organisations using this platform for the first time - the need is critical.
Is there any indication for a solution to the problem and not an inefficient and unusable workaround? We would really appreciate some actual confirmation of progress and an ETA for the solution.