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.
Dear Suphatra, i found various similar requests, so I will post my comment here rather that opening a new thread. Its about moving conversation history, - chats, - from one place to another, or export/import thereof. We have started Knowledge exchange initiative in our company, using Teams. Works fine, search is fantastic, integration options are great and user acceptance is MUCH higher than classical Sharepoint. After a while, we've noticed that we created too many teams and it would make sense to merge some of those. Or to rearrange. Everything is doable manually, - files, tabs, connectors...except of chat history, - I cant find a way to move whole history of chats from one Team to another. Maybe you can recommend some technical workaround via API ? The point is, we have valuable knowledge residing in chat, announcements, statements, etc...and we dont want losing it, but a rearrangement is necessary from time to time.
I dont expect a comfortable "move" button, since I understand the complexity of this task, but f.e. an export into external file and then import in other teams channel ? With prerequisite that users on sender and recipient part are same to have a 100%match?
thanks a lot
Niklas Engblom commented
This is a really important feature in terms of findability and general maintenance. From time to time we have important conversations which are unfortunately posted to wrong channels. I'd imagine this to be even more common thing if there's more users.
Peter Sattler commented
Worthy of the front-log, not the backlog. Without the ABILITY TO SHIFT THINGS AMONG CHANNELS, the utility of channels is completely compromised. Make Teams more useful for projects that grow and need to adapt as they grow.
Abizar Vakharia commented
That sucks, this would be a really useful feature for me.
Ana Jablonski commented
Agreed! Our company has just begun using Teams and there are multiple conversations that need to be moved into other channels now that we're getting more used to the system and creating more channels.
A real shame!
Keith Davies commented
IMHO this would be a very beneficial feature as we currently have users posting chats into channels inappropriate to the conversation within it.
I would live this feature. Also, can we make a chat to be a wiki?
Needed for many reasons addressed below.
This is crucial... some conversation channels develop and flexibility to move to new channels is a "must have" ...like yesterday!
This is essential in my opinion. Any user can make the mistake of posting a message in the wrong thread. An owner/admin should be able to move a message anywhere their rights allow. Most blog/forums allow this....
Just came up for us now as well, basically share a discussion to another channel
Per Ove Sandhåland commented
We also need to move conversations to another Team. Sometimes people create multiple Teams for the same purpose. When consolidating these to one single team, we need to move the conversations also. We can move everything else, but not conversations. Being a chat centric tool, I find it essential to be able to move chats.
Definitely need this... conversations get posted in the wrong channel and need to be adjusted
James Cann commented
Yes, this would be great. We have channels that are fairly generic and some for more specific topics. Conversations often start in one channel and then need to move into the specific one.
Elan Shudnow commented
Would love this feature as well.
Often times people respond or start Conversations while having the wrong channel active. It would be great if we could grab a whole conversation and move it to the proper Channel.
Alain Moussa commented
Currently we're creating separate teams per project, which is not exactly how it's supposed to be set up, since a project is not a team. But that is the only work around for having private channels with private plans. We should be able to have a team that represents a department and separate channels that represent projects in which only certain members can access.
I do realize that "private" channels is currently being considered as an update, however, we need to know if we'll be able to consolidate teams and move channels between teams once that feature is available.
This is a very frustrating situation for us in IT, we see the potential of MS Teams, but we just cannot keep telling our users that essential features are being considered, like "Printing? multiple plans per team? private channels?" to name a few. Change and update is happening at a very slow pace, and it's sad to see that we have to invest in a different more mature solution, while we already own Office 365.
Microsoft need to step up development of such products if the plan is to provide a adequate solution to common "Team" requirements
Yes, this is a must > move and existing conversation to a another Team channel <