Separate four kinds of continuity
Treat membership identity, usable access, useful conversations and responsibility for the space as separate decisions. A copied member list does not establish that people can enter. A working login does not establish that their paid space is included. A complete archive does not establish that someone will answer tomorrow’s question. Write one acceptance condition for each relationship before comparing vendors.
Start with the people who already participate
List the journeys that matter today: finding the next meeting, asking a question, revisiting a reference and contacting a moderator. Observe how an ordinary member completes each journey, with permission and without collecting unnecessary personal information. Translate the result into a requirement, such as finding the next meeting from the welcome page, rather than a vague preference for a modern platform.
Keep the move smaller than the ambition
Choose which relationships must work at launch and which can wait. An archive can remain at an old address temporarily if the owner can maintain access and the terms permit it. A new paid membership or a new moderation policy is a separate change that deserves its own explanation. Combining everything into one launch makes it harder to understand why a member is stuck.
A fictional reading group
A reading group has eighty members, a monthly discussion and a useful reading archive. Its first rehearsal covers one invitation, one archive entry, one meeting and one moderator reply. It does not count eighty imported email addresses as eighty successful transitions. The group records which owner can fix each failed journey and keeps the existing meeting route available while those failures are resolved. This is a planning example, not a completed Mighty Networks migration.
Before you close this task
Before proceeding, ask a second organiser to explain the four continuity conditions in their own words. A shared understanding is more useful than an impressive migration checklist that only its author can interpret.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Mighty Networks migration FAQ — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Member purchase and access — Merchant documentation · docs.mightynetworks.com · Merchant-controlled · checked 2026-09-28