Getting Slack messages out when the export button is not yours

What an export actually contains, by plan

This matters before you ask anyone for anything, because half the requests people make are for something their workspace cannot produce. From Slack's own documentation on exporting workspace data:

• Free and Pro. A standard export covers messages and file links from public channels, in JSON. Private channels and direct messages are not included at all. On Free, file links only go back through the visible history window.
• Business+. Public channels as above, and Workspace Owners can apply for a self-serve tool that also covers private channels and direct messages. The application is a separate approval step, not a checkbox.
• Enterprise Grid. Org Owners can export by conversation type, by member, or for a single workspace, including everything for one person.

The short version for most people: if your workplace is on Free or Pro, nobody can export your DMs, including the owner. That is a Slack limit and no tool works around it.

Asking an owner, in a way that gets a yes

A vague request gets ignored. A specific one takes them five minutes.

Tell them which channels, over which dates, and that you are asking for a standard export of public channel data, which is the one available on every plan. Say what it is for. If you are leaving and you want a record of your own project work, say that, because it is a normal request and sounds like one when stated plainly.

Be ready for the answer to be no, and for it to be a policy no rather than a personal one. Plenty of companies treat workspace data as company data on purpose. If that is the answer, the next two sections are what is left.

Saving conversations by hand before access ends

Unglamorous, and it works, and it is the only route that is entirely in your hands. Do it while you can still log in, because the moment your account is deactivated the scrollback is gone from your side.

• Open Slack in a browser rather than the app. Scroll the channel or DM up until the whole stretch you want has loaded, then print the page and choose Save as PDF. Long threads need patience and several passes, and threaded replies do not always come out in a sensible place, but the words are preserved with their dates.
• Copy and paste into a document. Ugly, quick, reliable. Paste as plain text or you will inherit Slack's formatting.
• Download the files you need one at a time. Files live in Slack, not on your machine. A link to a file you can no longer open is not a record of anything.
• Do the DMs first. Public channels are the part an admin can export for you later. Your DMs, on most plans, are not.

What I would not do is run a scraping script against your employer's workspace. It is usually against the acceptable use rules you agreed to, and getting caught doing it in your last week is a bad trade for a transcript.

If you are in the EU or the UK, there is a formal route

Under the GDPR, and the UK version of it, you can ask an organisation for a copy of the personal data it holds about you, and in some cases to have it provided in a structured, commonly used, machine-readable format. The organisation has one month to respond, which it can extend by a further two months for complex requests as long as it tells you inside the first month.

Two things worth knowing before you fire one off. The request goes to your employer or whoever runs the workspace, not to Slack, because they are the ones who decide what happens to the data. And a request for your personal data is not the same as a request for a full copy of every channel, so be specific about what you want and why.

Whether any of this applies depends on where you and the organisation are. Plenty of countries have an equivalent, plenty do not, and I am not in a position to tell you which rules cover your situation.

The clock on a free workspace

If the workspace in question is a free one, whether that is a community, a side project or a small company, there are two deadlines running whether anyone is watching or not.

Slack hides messages and files older than 90 days on the free plan. They are hidden rather than deleted, and they come back if the workspace upgrades. The harder one is that Slack says messages and files more than one year old will be permanently deleted, and that since 26 August 2024 data older than a year may be removed on a rolling basis from free workspaces.

So a free workspace is not an archive. If there is something in one that matters to you, get it out on a date you choose rather than on the one the deletion schedule chooses.

When you do get the export, it will not be readable

A Slack export is a ZIP with users.json at the top and one folder per channel, and inside each folder one JSON file per day. It is complete and it is close to unreadable, for three specific reasons.

Every author is stored as an account ID like U024BE7LH, with the names kept in the separate users.json file. Every mention inside a message is written the same way, so a sentence arrives as text with a code in the middle of it. And replies are flattened into the day file with a pointer back to their parent, so a thread interleaves with everything else in the channel and the conversation stops making sense.

Joining those back up is scriptable if you write code. If you do not, that is what the tool below does.

If you have already lost access

Then your options narrow to one: ask someone who still has access. A colleague can copy a thread to you. An owner can run an export of public channels if they are willing.

What is gone is anything private to your account. Slack will not hand a former member a copy of their DMs, and no third-party tool can reach a workspace you cannot log into. If someone is selling you one, they are selling you nothing.

The lesson is only useful in advance, but it is worth writing down for next time: the week you hear the word offboarding is the week to save what you need.

Questions, answered.