Every community platform says you own your data. Very few tell you what you'll actually get when you ask for it.
I learned how much that matters in 2007. CrazyEngineers got hacked, and I had no backups. The only reason the community survived is that I spent three or four sleepless days rebuilding it piece by piece. Since then, the first thing I ask about any platform is simple: if I had to leave tomorrow, what would I walk out with?
The time to find out is during the trial, not on the day you cancel. Here's how. Platform facts below come from each vendor's own documentation, checked on November 11, 2026.
What "you own your data" usually means
On most platforms, owning your data means you can download a list of your members. That's it.
Your posts, replies, accepted answers, attachments, private messages and URLs are the community. A member list is a mailing list.
Here's what each platform's official docs say you can export:
Swipe sideways to see every column.
| Platform | What you can get | How |
|---|---|---|
| Discourse | Full database backup, with uploads if you choose | Self-serve, any time |
| Higher Logic Vanilla | Database dump with posts, profiles, private messages and hashed passwords; files separately | Support ticket; free at cancellation |
| Circle | CSV files of members, spaces, posts and comments; no uploaded media | Email Circle's support |
| Bettermode | Member CSV; content only through the API | Self-serve for members |
| Mighty Networks | Member list as an Excel file | Self-serve, Launch plan and up |
| Khoros | One machine-readable export at contract end; the bulk API only returns analytics | Through your account manager |
| Slack | Messages as JSON with links to files; private channels and DMs only on Business+ | Workspace owners |
| Discord | No server-wide export in Discord's docs; each member can download only their own data | — |
Two things jump out. Only Discourse and Vanilla document a real full export. And only Vanilla says in writing that password hashes are included, which decides whether every member has to reset their password when you move.
The 14 tests
Run these during your trial, on the plan you'd actually buy. If a vendor can't show you a test live, ask them to put the answer in writing.
Getting your content out
-
Ask for a full export during the trial. Seed a test space first: 100 posts, some replies, two attachments, a few reactions, one private message. Note how long the file takes to arrive and whether you needed a sales call.
-
Open the files and check every post has its basics: ID, title, body, author, date, the thread it belongs to, and its URL or slug. If posts and replies can't be joined back together by ID, you don't have a community, you have a pile of text.
-
Check attachments. Are the files in the export, or only links to the vendor's servers? Links die when you cancel. Circle's docs say its post export doesn't include uploaded media. Slack gives links, not files.
-
Check replies, reactions and accepted answers. Do they survive, and do you know who reacted, or only how many?
-
Check private messages. Some platforms export them, some don't, and some only on higher plans.
-
Ask about password hashes, and the hashing method, in writing. If you can't move hashes, plan for every member to reset their password. That's a lot of members you'll lose at the door.
-
Export members with every custom profile field and their email consent. You'll need consent flags to email people about the move.
Keeping your search traffic
-
Run the URL test. Pick 20 live URLs: posts, profiles, categories. Can you build an old-URL to new-URL map from the export? After you move, can the new platform redirect those exact old URLs? Google says to use permanent 301 or 308 redirects and keep them for at least a year.
This one matters more than any other. When CrazyEngineers moved from vBulletin to XenForo, our URL structure changed, and traffic fell about 40% for six to seven months. Keep the URLs, or redirect every one of them. We've talked through how that works in practice in migrating from XenForo without losing traffic.
-
Check the community is on your own domain on the plan you'll buy. If it lives on the vendor's subdomain, you can't redirect anything when you leave, and the search equity was never yours. On Discourse's hosting, for example, a custom domain starts on the $100 Pro plan.
Connecting your stack
-
Pull 1,000 posts through the API with a trial key. Note which plan you need and the rate limits. Some are tight: Discourse admin keys get 60 requests a minute, Mighty Networks' Scale plan includes 5,000 requests a month, and Slack limits apps outside its Marketplace to one history request a minute.
-
Test a webhook. Create a post and check your endpoint receives the event. Not every platform has webhooks; Circle's docs don't document any.
-
Test single sign-on with your own identity provider, on the plan you'll buy. Check that existing accounts link up instead of duplicating. SSO is often a plan or two above the one in your budget.
-
Sync a test member to your CRM and back. Native HubSpot or Salesforce connectors are usually on higher plans; otherwise you're building it with webhooks or Zapier.
Reading the contract
- Get the exit terms in writing: how often you can export, whether it costs anything, how long you have to download your data after the contract ends, and that you own the content. Vanilla, for example, gives a free export at cancellation and allows up to one export a month.
What the law says (if you're in the EU)
Two EU laws come up here, and people mix them up.
GDPR Article 20 gives each member the right to get the data they provided in a machine-readable format. That's a member's right against you, the community owner. It doesn't help your business get its community out of a vendor.
The EU Data Act does. Its switching rules (Chapter VI) have applied since September 12, 2025, and the European Commission's FAQ says they cover SaaS. In short: the notice period to switch is capped at two months, the switch itself at 30 days, the vendor must let you export your data in a structured, machine-readable format, and from January 12, 2027, vendors can't charge you for switching at all.
I'm not a lawyer. If you're in the EU and your contract says otherwise, ask one.
What Jatra gives you
I build Jatra, so here's the same answer for us, plainly.
The community owner can export the whole community themselves, any time, from Settings → Data. No support ticket, no sales call. Pick what to include, click export, and you get an email with download links when it's ready. The links expire after 7 days, and you can run one full export a day.
The ZIP has:
- every published post and reply, with authors, dates, status, the thread each reply belongs to, and accepted answers
- reactions, with who reacted
- event RSVPs and messages from public rooms
- your uploaded files themselves, not links, with a list mapping each file to its post
- every member with their profile fields, roles, join date, email consent, badges and trophies, as JSON and as a CSV
- a list of every public URL with what it points to, so you can redirect each one
- your community settings, channels and tags, plus a README that explains every file and field
Two things are left out on purpose: private messages, because they belong to the people who wrote them, and password hashes and other secrets. That means members will reset their passwords if you move. I'd rather tell you that now than have you find out on moving day.
Admins can also export the member list as a CSV, and any member can download their own data.
Single sign-on isn't available yet. Your community runs on your own domain, and URLs never change once something is published.
Before you sign
Your job during a trial isn't to fall in love with the features. It's to make sure you can leave.
Run tests 1, 6 and 8 at the very least: the full export, password hashes and the URL test. If a platform fails all three, you're not buying software, you're renting your community.
If you're comparing platforms, start with how to choose a community platform and the platform comparison tool. If you're already moving, read the community migration guide and see how we handle migrations. Or book a call and run these tests on Jatra with me.
