Download Your Slack History Before Leaving

Your access ends Friday. Maybe you resigned, maybe the contract wrapped, maybe the community's Slack is shutting down — either way there's a date now, and after it the workspace goes dark for you. So do this while you still can, download the DMs, private channels and files you're authorized to keep, and check they actually saved. Once your account is switched off, you generally can't get any of it back.

Think about what's in there. The DMs where half the coordination happened. The private channel with decisions no doc ever wrote down. Files someone dropped in a thread instead of emailing. All readable right now. All gone the minute your access is. And most people picture some "download my data" button waiting on the way out — for a regular member, there isn't one.

what happens the day they switch off your account

Deactivation is quieter and more final than people expect. One day you open Slack and the workspace is just gone from your list, or it's still there but nothing loads. Your messages usually stay visible to everyone else — admins, teammates, whoever's still inside — but you can't read, search, or pull them anymore. There's no grace period you can rely on. No "you have 30 days" email as a rule.

And here's the part nobody enjoys hearing. If a message was already deleted before you got to it — by someone clearing a channel, by a retention policy, or on a free workspace where old history ages out — it's gone for everyone, and no backup tool invents it back. A copy can only save what's still there to open. If you're on a free plan, some of your older history may already be sitting past the line; I wrote about how that 90-day and one-year clock works if you want the specifics. The lesson lands the same either way. Sooner beats later.

make this list before you touch anything

When you're rushing, you grab the loud channels and forget the things you'll actually miss. So spend two minutes writing down what matters before you start clicking. Mine usually looks like this.

• Your DMs. The one-on-one threads where half the real coordination lived. Hardest to reconstruct, first thing you lose.
• Private project channels. The rooms you belonged to that outsiders never saw. Decisions, context, the "why we did it this way" no doc ever captured.
• Files and attachments. PDFs, spreadsheets, design mockups, that one screenshot of the thing that broke. People share files in Slack and nowhere else, and file links can expire.
• Links you'll need. Google Docs, tickets, dashboards, repos — the URLs buried in old messages that are your map to everything outside Slack.
• Decisions and commitments. Who agreed to what, the deadline someone promised, the scope that got cut. If it lived in a thread, it leaves with the thread.
• Contacts. Names, handles, the personal email a freelancer gave you once. You'll want to reach some of these people after you no longer share a workspace.

Save that top group first. If your access gets cut early — it happens, sometimes the calendar and reality don't match — you want the irreplaceable stuff already sitting on your disk.

what you're actually allowed to take

This is the uncomfortable paragraph, and I'd rather say it straight than bury it at the bottom. Your workplace Slack, and most of what's in it, usually belongs to the company, not to you. So before you export anything, check the policy — your contract, the employee handbook, or just ask IT. Some places are fine with you keeping your own conversations. Some are strict about anything work-related leaving the building.

The safe zone is your own stuff and the conversations you were genuinely part of and cleared to retain — your DMs, your notes, channels you belonged to. The line you don't cross is using a backup as a way around access you were never given, or walking off with confidential material you weren't authorized to keep. Personal, authorized retention. Not a workaround for permissions. Stay on that side of the line and you're fine.

your three real ways to get it out

Once you know what you're keeping and that you're allowed to keep it, there are basically three routes, and which one fits depends on whether you're an admin and how comfortable you are with a terminal. Facts as of 2026-08.

• Slack's official export. Free and first-party, but owner/admin only, and on the free plan it exports public channels as raw JSON — no DMs, no private channels. If you're a regular member walking out of a job, this one usually isn't even available to you.
• Slackdump. A free, open-source command-line tool (github.com/rusq/slackdump) that runs from your own signed-in account with no admin. It reaches the private channels and DMs you can see and writes export files you open in a separate viewer. If a terminal doesn't scare you, it's a solid free answer.
• A local archiver like Empowia for Slack. This is the one I make, so I'll be straight about its shape. It reuses the Slack session you're already logged into and copies the channels, private channels, DMs, group DMs and files your account can reach onto your own computer — no admin, no tokens. On top of the archive you get local search and AI answers with citations, using your own API key. It's free for your first 20 conversations, then a one-time purchase (around €19.90) lifts the cap. A couple of things worth knowing before you install it — it's Windows 10 and 11 only right now, with a Mac version coming, and like everything else here it can't recover a message Slack already deleted. It doesn't push anything back into Slack, either, or double as legal hold — it's a personal copy, not company recordkeeping.

None of these gives you new access. They keep a copy of what you can already open — which is the whole point when the opening is about to close.

download it, then prove to yourself it downloaded

The mistake that actually hurts happens after the export, not during it. You run the export, the progress bar fills, you feel done, and you close the laptop without checking. Then Friday comes, access is gone, and you find out the DMs didn't come through or every file is a broken link.

So don't trust the progress bar. Open the archive and look. Pick your three most important conversations and read a few messages inside them. Open a couple of the files — a PDF, an image — and confirm they're real files sitting on your disk, not links pointing back into a Slack you can no longer reach. Search for a name you know is in there and see if it comes up. Five minutes of poking now is the difference between having your history and having a folder that only looks like your history.

reading it back when you actually need it

The reason to keep any of this isn't the day you leave. It's eleven months later, when someone asks what was agreed, or you need the invoice a client sent, or you're writing your own version of events and want the exact wording. A pile of raw JSON won't help you then — you'll open it, wince, and close it again. What you want is something you can search the way you searched Slack, by name, by keyword, by the file you half-remember. Whichever tool you land on, favor the one that leaves you a readable, searchable copy over the one that leaves you an archive you'll never willingly open.

the small things that quietly ruin a rushed backup

A few that catch people in their last week:

• Backing up the loud channels and forgetting the quiet DM that held the one thing you needed.
• Grabbing messages but not the files, then finding the links dead a month later.
• Waiting for the actual last day, when access sometimes ends at midnight the night before.
• Never opening the archive to check, and trusting it blind.
• Assuming you can just ask an admin afterward. Sometimes you can. Plan as if you can't.

None of these are hard to dodge. They just need you to do the boring verification step instead of assuming it worked.

If there's a date on your calendar, don't try to save everything at once. Go back to the list you just wrote — the DMs, the private project channel, the files at the top of it — and pull those down first, while your account still works, then check they landed. That's the risky part handled. You can do it with Empowia or with anything else that saves what your account can see — the tool matters less than the timing here. The window is the thing. Get the irreplaceable stuff out while the door's still open.