Most communities do not get shut down. They get abandoned — the questions stop being answered, the renewals keep charging, and one day the owner stops opening the tab. That is the worst possible ending, and it is the default one.
Closing deliberately takes about two weeks of work. It is the last thing your members will remember about you, and it is worth doing properly.
Abandonment is a decision too
An owner who quietly stops showing up has decided to close. They have simply decided not to say so.
The cost lands on the members. Someone posts a question into a room where nobody is left to answer it. Someone renews a membership for a place that no longer exists in any meaningful sense. Someone recommends it to a friend. Every one of those is avoidable with a single announcement.
It also costs the owner more than closing would. A community that is visibly dead follows your name around; a community that ended with a clear note does not. People forgive endings. They do not forgive being left in a room and charged for the privilege.
First: is it dead, or is it just quiet?
These look identical from the inside, and they need opposite responses.
Quiet usually means the rituals lapsed and the regulars drifted — recoverable, and the playbook is in how to revive a dead community. Dead means the reason people came no longer holds: the problem got solved elsewhere, the field moved, or the thing that made it worth joining was you and you are done.
The most common real reason is hours, not interest. The community still works, the owner has run out of Tuesdays, and no amount of engagement tactics fixes that — see how much time running a community takes. If that is the reason, handing it over is usually the better move than closing it, and that option is further down.
What you owe each group
Not everyone is owed the same thing, and treating them identically is what produces the angry messages.
| Who | What they are owed | When |
|---|---|---|
| Paying members | Billing stopped immediately, and the unused part of anything prepaid returned | Before the announcement goes out, not after |
| Members mid-course or mid-cohort | A way to finish, or their money back — pick one and say which | In the announcement itself |
| Moderators and volunteers | To hear it from you privately, first, and to be thanked publicly | Days before anyone else |
| Free members | Enough notice to save anything of theirs that lives there | At least two to four weeks |
The billing one is not negotiable and it is the one people get wrong. A renewal that fires after you have announced a closure reads as a scam even when it was an oversight, and it is the single fastest way to turn a graceful exit into a public complaint. Turn off renewals before you write the announcement — the mechanics are the same ones you set up when you started charging, covered in how to price a community membership.
The announcement
One post, in the main space, under your own name. Not a banner, not a quiet footer note, not an email nobody opens.
It needs four things: that it is closing, when it closes, what happens to what people paid, and what happens to their content. Everything else is optional. Most closure notices fail because they contain feelings and omit dates.
Give a reason, briefly and honestly — "I do not have the hours to run this the way it deserves" is a complete reason and members accept it easily. What they do not accept is a vague statement that implies something happened without saying what, because the vagueness invites people to invent something worse.
Do not promise a return you are not sure about. "Pausing for now" is the most common lie in community closures, and it costs you twice: nobody saves their content because they think it is coming back, and the eventual silence confirms it was never true. If you genuinely might return, say the odds out loud.
Get the data out — theirs before yours
Two separate jobs, and the members' one is time-limited in a way yours is not.
Your member list is the thing you actually keep. It is the only asset that transfers to whatever you do next, and it exports cleanly almost everywhere. On Mateflow an admin can export members as CSV or JSON from Members, with the fields and filters you choose and a history of past exports, and a single space can export its own member list as CSV.
Post archives are a different matter and vary enormously between platforms, so check what you can actually take out before you need it rather than in the last week. If the answer is thin, the practical fallback is to save the handful of threads that were genuinely valuable rather than trying to preserve everything.
Members should be told they can take their own data, and given time to do it. On Mateflow each member can request an export of their own data from their security settings and download the archive when it is ready. Say this in the announcement rather than assuming people know, because almost nobody goes looking for that setting until something is closing.
Handing it over instead
If the community still works and only the owner has run out, closing destroys something that did not need to be destroyed.
The candidates are usually already there: the moderators and regulars who answer things without being asked. They know the culture, which is the part that cannot be transferred any other way — the same population you would draw on for volunteer moderators.
Hand over with a real transfer, not a vague blessing. Ownership of the space, the billing relationship, the domain, and a written account of how things are actually done. A handover that leaves you as the person who still has to be asked is not a handover; it is unpaid work with extra steps. If the new owner wants it somewhere else, that is a migration, not a closure.
The last two weeks
Run the ending like a small project rather than letting it trail off.
Stop billing and stop accepting new members on day one. Pin the announcement. Keep answering questions in the thread it generates, because that thread is where the goodwill is won or lost, and it will be busier than anything you have posted in months.
Then, on the last day, post once more and mean it. Thank people by name where you can, say what the community did that you are proud of, and tell them where to find you next. A closure post that ends with a working link to your newsletter or your next thing converts far better than any campaign you ever ran inside the community — and an email list you own is the one thing that survives the shutdown, which is the argument in community vs social media.
Then actually close it. Leaving a hollow, unmoderated shell online so nobody has to feel it end is the abandonment option wearing a nicer coat.
The bottom line
Decide whether it is dead or quiet, stop the billing before you say anything, and give people a date and enough notice to take their things.
An ending done well is not a failure, and members read it that way too. The people who leave a properly closed community will join the next thing you build. The people who were left in an empty room with a live subscription will not.