User Community Feedback

Submitted ideas will be evaluated by our product teams for upcoming releases and will be responded to so you know where things stand. For product support, please use the community forums or contact TAC.

NOTE: All Cisco employees & Channel Partners must enter Ideas through this Ideas Portal.

Ability to export Webex Teams full space content to html or JSON for members or Compliance Officer

The ability to export the content of a space directly from the space is lacking Today.
We had to migrate our ORG from US to EUR and all our users LOST their content. This had a large impact on user adoption of the product.
Jabber, for example, provides the ability to save the content of a group discussion to html.
It could be implemented as a button in the space, with a few options: save images
/save files, text/html/json, filter how many messages/how many days/full content.
The format of the content should be kept as close to the original as possible.

This ability should be available to the Compliance Officer as well, in addition to the current eDiscovery reporting feature.

Thank you for the great work :-)
Cheers
Luca Smeriglio

  • Luca Smeriglio
  • May 29 2020
  • Need more info
  • Jun 18, 2020

    Admin response

    What is the problem statement? Is it loosing data when migrating users, is it CO wanting another file format for exported data or something else?

  • John Reineke commented
    23 Jun, 2021 06:00pm

    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.

  • John Witt commented
    17 Jun, 2021 02:26pm

    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.

  • Guest commented
    11 May, 2021 08:09pm

    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.

  • Guest commented
    6 Jan, 2021 05:24am

    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!

  • Guest commented
    17 Dec, 2020 05:40pm

    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.

  • Phylane Slutzky commented
    19 Nov, 2020 08:31pm

    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.

  • John Witt commented
    18 Jun, 2020 03:40pm

    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.

  • Elena Schott commented
    18 Jun, 2020 03:19pm

    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?

  • Elena Schott commented
    5 Jun, 2020 07:08pm

    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.

  • Guest commented
    29 May, 2020 09:59am

    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