Natively Export Data
Learning Objectives
After completing this unit, you’ll be able to:
- List the types of data that can be natively exported from Slack.
- Describe when to use native Slack exports instead of the Discovery API.
- Read a JSON export file.
Just Export the Data
Although DLP and eDiscovery solutions add tremendous value to Slack, they may not be the best option for every scenario. What if you simply need regularly scheduled exports to meet your compliance requirements? Or what can you do if you need to export conversations to help with data storage needs?
Slack offers native built exports on all plans.
Explore Slack Export Types
On any plan, Workspace Owners and Admins can export messages from all public channels. These exports are in JSON format and exclude files, direct messages, or messages from private channels.
Workspace Owners on the Business+ plan can apply to export data from all channels and conversations, including public channels, private channels, and direct messages (DMs). This export will not include files themselves, but will include links to the files in Slack. If a file has been deleted in Slack, it cannot be retrieved via an export link.
In addition, Business+ workspaces can schedule recurring exports, which will send a JSON file of all channels and conversations to Workspace Owners at regular intervals. This can help organizations meet data storage requirements, or allow teams to keep a file of all messages if needed for future reference. Recurring exports are a valuable alternative for workspaces that do not need a full eDiscovery solution but still have retention requirements.
On the Enterprise Grid plan, Organization Owners have the added ability to export data on a single user including private channel messages, public channel messages, and links to files posted. Single user exports are the only export type rendered in TXT format rather than JSON.
Read a JSON Export File
When you export a file from Slack, it will be in JSON format with the exception of single-user exports on Enterprise Grid mentioned above. Many people prefer to run a JSON export through a third-party converter to render it in text format. However, it's valuable to know what a JSON export file looks like so you can understand what you are reading.
Want to dive even deeper into the world of JSON? Find the comprehensive Slack guide to navigating and understanding JSON exports in the Workspace administration Help Center article.
Now you know what native export features are available in Slack and when it makes more sense to use a native export instead of a third-party solution. Next you take a look at data retention policies and the compliance features built into Slack.