User Community Feedback

Hi, customer admins can use the Events API to scan all messages owned by their org. The events with messages include the roomId, and the customer can also use the rooms and memberships APIs to decide how to organize the messages.

Is this available yet? We need to give our space owners clear documentation on how to export their entire spaces (messages, content and links) to other chat systems like MS Teams.

Please update this request as the ability to export. The Problem statement has been replied to 364 days ago.

User ability to retain data beyond Teams retention period or if leaving space:

1. We have selected a 15 month retention period for the messages within spaces and only certain regulated groups are archived. The ability for a space member to export the chat record to .txt or other format would provide the ability for them to maintain a record beyond the 15 months.

2. When a space reaches the end of its purpose, the participants may leave. There may have been important discussions and decisions made during its lifetime. The ability to export would allow the space lead to maintain a record.

In the example of moving the org, this would allow for users to be requested to save the contents of their critical spaces on the chance of data loss during migration. My vote was based on the retention period or leaving space scenario.

I can't believe this is NOT an option already. Jabber gives us the ability to save chats to email. Why does Webex Teams not do the same? This is critical for litigation purposes.

Cisco need to provide a way to export content so that the users can take their data to a stable platform! They're going to move anyway, just let them take their data!

I'll vote for this as well. For nearly a year I have used our corporate instance of WE Teams as my technical and business operations repository, dropping notes, links, whiteboards, and files, along with message content. Now the corporation is moving us to another platform, without a migration capability. WE Teams absolutely needs to provide a way for the user to export their personally-created teams, spaces, and their content AT A MINIMUM, and preferably all teams/message/content history I have access to.

Even if there was an external utility that would use my local client / WE Teams access to get to the data, that would be fine.

Why is this such an issue? It feels like a major gap in basic user experience / enablement.

Where are the following:
right-click team >>select spaces (or select all)>> export >> <select format: html / json / csv>

Take note:

https://slack.com/help/articles/201658943-Export-your-workspace-data

https://slack.com/help/articles/220556107-How-to-read-Slack-data-exports

Shame on you Cisco/WebEx... please fix it.

Hi Cisco Team - is there an update on this? More information was provided but this has been in the same state since June. Thank you.

I'll let Luca expand on the idea he submitted but I am going to share problem statements for why I voted for this.

User ability to retain data beyond Teams retention period or if leaving space:

1. We have selected a 15 month retention period for the messages within spaces and only certain regulated groups are archived. The ability for a space member to export the chat record to .txt or other format would provide the ability for them to maintain a record beyond the 15 months.

2. When a space reaches the end of its purpose, the participants may leave. There may have been important discussions and decisions made during its lifetime. The ability to export would allow the space lead to maintain a record.

In the example of moving the org, this would allow for users to be requested to save the contents of their critical spaces on the chance of data loss during migration. My vote was based on the retention period or leaving space scenario.

Financial responsibility. We place insurance for multiyear terms, and have a 7 year searchability requirement on top of that. All client placement discussions must be findable by that and no web platform other than the corporate LAN is guaranteed to last 12 years or more. The ability to take a pertinent conversation and archive monthly to a pdf or some equivalent is needed to use the platform for anything more than Where are we going to lunch today?

I had wanted the ability to email the text content of a space to all participants. This is even more elaborate but work for us. Given our fiduciary responsibilities the need to have such discoverable also helps.

I agree: Teams should offer an Admin-Feature to "backup" all Teams-Data of either people, spaces or whole teams.
May it be to comply with Data-Retention-policies or Audit Trail etc.


The Teams-Client needs to be able to

1. handle/open these Backups ..

2. ...completely offline