1. Choose the intended outcome
  2. Announce an understandable process
  3. Handle resources and outstanding requests
  4. Close access in the right order

Choose the intended outcome

A pause, a handover and a closure have different outcomes. Write down what will stop: new messages, registrations, moderation or archive access. Check the service’s actual options before promising read-only mode or a transfer. Identify who can make the decision, then agree a date and an owner who can be reached during the transition.

Announce an understandable process

Explain the reason members need to know, the timetable and what will remain accessible. Do not promise an automatic migration of profiles or messages. A new group may require a new registration and different settings. Repeat the notice where members actually arrive: description, welcome message and reference page. Name the destination clearly and provide a route for people who do not want to move.

Handle resources and outstanding requests

List unresolved questions, announced events, shared documents and important contacts. Keep a summary of resources you are allowed to preserve rather than a full copy of every conversation. Do not publish private messages to create an archive. Give each outstanding request an owner and check that retained files are readable and include the context needed to understand them.

Close access in the right order

Keep the access needed for the transition until agreed checks are complete, then review permissions, apps and scheduled posts. Record actions actually completed and items outside your control. Closure should not leave an automatic tool posting into an abandoned space. Finally test entry links and explain the next step on a page you can maintain.

A fictional case to apply the process

Fictional example: a festival planning group closes after the event. The team publishes a summary without individual conversations, answers outstanding volunteer requests and points to the next edition’s page. It distinguishes completed backups from requests merely submitted to the service.

Template to adapt

Copy this outline into your working document without passwords or unnecessary personal data.

Decision and scope:
Announcement date:
Last planned activity:
Optional destination:
Resources to retain and permissions:
Unresolved requests:
Access and automations:
Transition contact:
Final check:

Your check before use

Checks to complete

0 / 4

Useful questions

Should every conversation be retained?

No: choose what remains useful and what you are allowed to keep. A decision summary can be more useful than a complete export.

Can you promise complete deletion?

Do not promise it without confirmation from the service and knowledge of external copies. Describe the operations you actually completed.

Sources and scope

Sources consulted on 10 October 2026 for the points specified below. The method, template and example are editorial proposals; they are not service tests.