The worst advice anyone gives community managers is to keep the community behind closed walls, where nobody can see the value until they've signed up.
Most people don't choose it on purpose. They start on Slack because everyone's already there, and Slack keeps everything behind a login. It works in the early days. Then growth gets hard, because nobody outside can find a single answer your members have written.
If you're reading this, you've probably decided to move to a forum. If you haven't, read when to move your community off Slack, Discord or WhatsApp first.
Here's what nobody tells you before you start: what you can take with you depends on your Slack plan. Some of it you can't take at all.
There's good news too. Your Slack messages were never on Google, so you have no URLs to redirect and no rankings to lose. That's the scariest part of most migrations, and you get to skip it.
What Slack lets you export
Here's the short version by plan, from Slack's export guide as it reads in November 2026:
- Free: messages from public channels. Files come only as links, and only from the last 90 days. Data more than a year old isn't included.
- Pro: messages and file links from public channels. Private channels and direct messages aren't available.
- Business+: public channels, and owners can apply for a tool that exports private channels and direct messages too. The workspace's primary owner has to approve the application.
- Enterprise: org owners contact Slack's support team to get access to the export tools.
Only workspace owners can run the export on Free, Pro and Business+ (org owners and admins on Enterprise).
What you get is a ZIP file: a folder for each channel, and inside it one JSON file per day of messages. The files themselves aren't in it, only links to them, according to Slack's guide to reading a data export. Delete a file or the channel it was shared in, and the link stops working.
Tip: If you're on the free plan, export now. Slack limits free workspaces to the most recent 90 days of history and, since August 2024, deletes messages and files more than a year old. Every week you wait, some of your community's answers disappear.
Think twice about private channels and DMs
Even if your plan lets you export them, ask yourself whether you should.
People wrote those messages to a few people, not to the internet. Publishing them on a public forum, even with good intentions, breaks the trust that made them write honestly in the first place.
Leave private conversations behind. Move what was public, and let members bring anything else themselves.
Decide what's worth moving
A forum isn't a chat log. Import a year of Slack as it is and you get thousands of one-line posts: "thanks!", "+1", "anyone around?". Nobody will ever read them, and Google won't think much of them either.
What's worth moving is the stuff people keep asking for:
- Questions that come up again and again, with the answer that finally settled them.
- How-tos and fixes someone took the time to explain properly.
- Decisions and announcements people still point to.
- Pinned messages and the links everyone keeps sharing.
Search your Slack for the way people ask: "how do I", "anyone know", "is there a way". The same questions will show up over and over. That's your list.
Turn the best answers into threads
This is the part that makes the move worth it.
Pick the 30 to 50 questions that matter most. When I seed a new community, I aim for about 50 useful pieces. It's not about volume. It's about depth and quality.
Write each one as a proper thread: a clear title in the words people would search for, the question, and the best answer, cleaned up so it makes sense on its own.
Ask the member who wrote the answer before you publish it publicly. They wrote it in a closed room. If they agree, credit them by name. People like being recognised for being helpful, and it gives them a reason to show up on the new forum.
These threads do two jobs at once. They save your community's best answers, and they mean the forum isn't empty when your members arrive. Nobody likes to be the first one in an empty room.
Or import everything
Some forum platforms can import a Slack export directly. Discourse, for example, has a Slack import script among its official importers.
If you go that way, test it on a staging copy first and look at what a busy day of chat turns into. Then decide whether you want that on your new forum. Most of the time, the 50 threads you wrote by hand will do more for you than 50,000 imported messages.
Bring your members across
You'll need a way to reach everyone outside Slack. Check what your export and Slack's member list download actually give you before you plan around email. If you can't get email addresses, do the invite from inside Slack.
Then tell people properly: why you're moving, what they'll get and what they'll lose. Once members understand the need for a migration, they support it. I've put the full plan, with announcement and email templates, in how to prepare members for a migration.
A few Slack-specific things:
- Post the announcement in your busiest channel, not just #general, and pin it.
- Put the forum link in every channel's topic.
- Give your most active members early access, so the forum has familiar names in it when everyone else arrives.
Then decide what happens to Slack. Some communities close it. Some keep it for quick chat and send every question to the forum. Either works. What doesn't work is two places for the same questions, because people will keep asking where it's easiest.
If you're moving to Jatra
Send us your Slack export and we'll tell you what can come across and what's better rewritten as threads. We'll help with the member transition too. Jatra has real-time Rooms for quick chat alongside the forum, so you don't have to keep Slack running just for that.
Start with the free community migration planner, read how Slack compares with the alternatives, or talk to me about your migration.
Frequently asked questions
Can you export private channels and DMs from Slack?
Not on Free or Pro. On Business+, workspace owners can apply for an export tool that covers private channels and DMs, and the primary owner must approve it. On Enterprise, org owners ask Slack's support team for access.
Does a Slack export include files?
No. The export has messages in JSON files and links to files, not the files themselves. On the free plan, you only get file links from the last 90 days.
Will I lose SEO moving from Slack to a forum?
No. Slack content sits behind a login, so it was never in Google. A forum is where your community starts showing up in search.
Can I import Slack messages into a forum?
Some platforms can. Discourse has an official Slack import script. Test it on a copy first: imported chat often makes poor forum threads, and rewriting your best answers as proper threads usually works better.