How do you export Slack data for an AI data license?
Slack keeps the part of a company that never reaches a document: the quick question, the workaround, the decision made in a thread. Getting it out is a matter of plan, permissions and settings, and what you can export is often less than what people assume. This page covers what each route returns and what to check before any of it leaves.
What a Slack workspace usually holds
| Public channels | Open discussion by team or project. The easiest part to export, and the part with the fewest privacy questions. |
| Private channels | Smaller groups, often finance, hiring or management. Valuable because they show real decisions, and sensitive for the same reason. |
| Direct and group messages | One-to-one and small-group chat. Usually the most personal layer, and the one most often excluded. |
| Threads and replies | A question and the answers under it. The thread is what turns a message into a lesson. |
| Shared files and links | Documents, screenshots and links posted in chat. The message may export while the file stays behind. |
How Slack data leaves the workspace, route by route
| Tool | What an export gives you | What is missing or needs an admin |
|---|---|---|
| The standard workspace export | Messages from public channels as files organized by channel and day, with the names of the people who wrote them. | Private channels and direct messages unless your plan and the owner of the workspace allow it. File contents are links, not copies. |
| A request for private channels and direct messages | A fuller export on plans that support it, usually after the workspace owner applies and states a reason. | It can require a higher plan, a formal request and the agreement of the people involved, and it can be switched off by company policy. |
| The programming interface | A pull of channels, messages, threads and file details by a developer, shaped to the fields you want. | It needs someone who can write and run it, and your plan sets how far back the history goes and how fast it can be read. |
Tool names belong to their owners and are used only to say where records usually live. Export features change by plan and version, so check the current rules for your account.
Retention settings decide how far back you can go
A workspace can be set to delete messages after a period, and some plans only show a limited window of history. Before planning anything, find the retention setting and the oldest message you can open. If the answer is eighteen months, that is the set, whatever the company remembers.
Changing a retention setting is a business decision with its own consequences, so the owner or the team that set it should make that call, not whoever prepares the export.
Who is in the chat is the whole privacy question
A Slack export carries names, handles and sometimes phone numbers and email addresses pasted into a message. It also carries what colleagues said about customers, vendors and each other. De-identification replaces the names and the details that point to a person, and people review the result, but the first filter is deciding which channels are in scope at all.
Channels shared with outside companies need a separate look. A shared channel holds another company’s messages, and your side usually has no right to license those.
What a good export looks like to a reviewer
A reviewer wants threads kept whole, replies in order, the date and the channel name on each message, and edited or deleted messages marked, not silently dropped. A pile of loose messages with no threads shows much less than the same messages in context.
What stays out of a Slack set
| Direct messages without agreement | Private one-to-one chat stays out unless the people in it agreed in writing and your policies allow it. |
| Channels shared with other companies | Messages from partners and clients belong partly to them. They stay out unless the other side agrees. |
| Credentials and secrets | Passwords, keys and access links pasted into chat are removed or the message is dropped. |
| Channels about people and pay | Hiring, performance and compensation channels are screened out first. |
An example, invented for illustration
Take a logistics software company with 90 people and a Slack workspace that is six years old. The retention setting deletes direct messages after a year but keeps public channels, so the usable history is the public and approved private channels. The owner picks the support, engineering and release channels, leaves out hiring and finance, and removes two channels shared with customers. The set keeps every thread whole, with channel names and dates, and the owner reviews a sample before anything is exported.
Questions owners ask about this
Can we export Slack on the free or lowest plan?
Usually you can export public channels, but private channels and direct messages are limited on lower plans, and the details change. Check Slack’s current help pages for your plan before you plan around a date.
Do the files people shared come out with the messages?
Often only as links. If the file matters, it needs a separate pull while the link still works, and files are screened for personal information in their own right.
Is chat from people who left the company still ours to license?
Their messages were written as work, so the company may hold them, but your terms and local rules decide. Counsel confirms it, and many owners leave departed staff’s direct messages out regardless.
Does Slack’s own export tell people it happened?
Do not assume it. If policies promise staff that chat is private, say what is being done in a notice before the export, not after.
Didn't find your question? Ask us directly.
Keep reading
Related kinds of records
- Team chat: Slack and Teams threads, where one person must stay one person and direct messages stay out.
- Project and task history: Jira, Asana, Linear, Monday, Trello, ClickUp and Airtable comments and status changes, not task titles.
- Jira data export: How to get issues with their comments and links out of Jira, and the secrets to remove first.
Industries that keep these records
- Software companies: Tickets, postmortems and renewal threads; customers appear everywhere and code is a separate deal.