The Exit Plan You Hope Never to Use: Portable Member Lists for UK Community Groups

Every community group I've spoken to this year has the same story, told slightly differently. A Facebook group for a Sheffield allotment society. A Discord for a Bristol makers' collective. A Slack that a Manchester co-working space uses for its 400-odd members. In each case, the community lived somewhere rented, and nobody had asked what happens when the landlord changes the terms.

Then it does change. The free tier shrinks. The pricing page updates quietly on a Tuesday. A moderation policy gets rewritten and suddenly your Tuesday-night thread is against the rules. Or the platform simply goes the way of everything else and announces a shutdown date with six weeks' notice.

Rented is fine, until it isn't

Let's be fair to the platforms. Running a community is expensive, and the free-tier era was never going to last forever. Nobody is owed infinite storage and zero ads. But there's a difference between paying for a service and being locked into one.

If you cannot take your membership elsewhere, you don't have a community platform. You have a tenancy with no break clause.

What portability actually means in practice

The word gets used loosely, so let's pin it down. A genuinely portable setup has three parts: a contact route you're allowed to use, a list you can export in a readable format, and a shared archive of the stuff the group has produced together.

That last one gets forgotten constantly. People remember the names and forget the twelve pinned documents, the resources thread, the carefully maintained FAQ that took someone three weekends to write.

Consented routes beat scraped spreadsheets

This is where UK groups need to be careful, because "just in case" data hoarding is exactly what the ICO isn't keen on.

Under UK GDPR, you need a lawful basis for holding someone's details — typically consent, or legitimate interests for a members' association with a proper legitimate interests assessment on file. You also need to honour the right to data portability under Article 20, which applies where processing is based on consent or contract and is carried out by automated means. In plain English: if a member asks for their data in a machine-readable format, they're entitled to it.

So the sensible pattern is this: at sign-up, ask for an email address and explicitly say what it's for. Something like "we'll use this to send you meeting dates and the monthly bulletin, and to contact you if the group moves platforms." That last clause is the whole ballgame, and it costs you one sentence.

Don't scrape, don't guess, don't harvest. A list of 300 people who actively said yes is worth more than 3,000 you've quietly compiled, and it's considerably less of a headache if anyone ever asks how you got it.

The pinned post problem

Ownership of collaborative resources is genuinely messy. If a volunteer wrote the group's code of conduct inside a platform's document tool, who owns it? If the platform folds, does anyone have a copy?

A workable rule: anything the group would be annoyed to lose should live in a space the group controls, even if it's just a shared drive with a link posted in the chat. The chat is where the conversation happens. It shouldn't be the only copy of the constitution.

A portability checklist you can run this week

Nothing here needs a consultant or a budget.

1. Find the export. Go looking for the member export function before you need it. Note whether it gives you email addresses, or just usernames. The second one is a warning sign.
2. Check the format. CSV or JSON is fine. A PDF of a member directory is not an export, it's a souvenir.
3. Confirm the lawful basis. Write down, in one sentence, why you're holding each category of data. If you can't, you probably shouldn't be holding it.
4. Draft the move message. A short paragraph explaining that the group may relocate and that contact details will only be used for group admin. Test it on the committee before you need it in a hurry.
5. Set a retention rule. Delete people who've left, and say so in your privacy notice. Under UK GDPR you shouldn't keep data indefinitely just because it's easier.
6. Back up the archive. Code of conduct, FAQ, event history, moderation policy. Once a quarter, someone checks it's current.
7. Name a custodian. One person, plus a deputy, who holds the master list and knows where the backups live. Two people, never one.
8. Test the exit. Move a small sub-group to a new tool once, purely as a drill. You'll learn more in an afternoon than in a year of planning.

The point isn't leaving

None of this is an argument for jumping ship. Most groups should stay put — the platform is where the people are, and that matters more than sovereignty in the abstract.

But the ability to leave changes the relationship. A group with a working export button negotiates from a position of calm. It can say no to a bad policy change without losing its entire membership. It can move in a week rather than a panic.

Portability isn't paranoia. It's just good manners to your future self.