Before moving a community, list what must survive the move: member access, billing, useful content, and a clear place to ask for help. A new platform is ready only when those parts work together.
Use this checklist after choosing a destination. If that choice is still open, start with the platform shortlist. This is a planning checklist, not a claim that any two platforms can transfer everything automatically.
1. Name the constraint and the owner
Write down the failure you need to fix: lessons are hard to find, permissions are difficult to manage, or the required product cannot be delivered. Assign one person to approve the move and another to handle member questions. A small team can give one person both roles.
Decide what would make you stay. Better navigation or a smaller set of channels may solve the problem without a migration.
2. Inventory the current system
| Asset | Record before moving | Check at the destination |
|---|
| Members | Identity, access level, and supported export fields | Invite or import process and permissions |
| Billing | Subscription status, renewal dates, refunds, and cancellation route | Whether payment migration is supported and who performs it |
| Learning material | Source files, URLs, attachments, and content owner | Formats, links, file access, and organization |
| Conversation | Threads worth retaining and their context | Whether history can transfer or must remain archived |
| Integrations | Bots, automations, analytics, and access rules | Replacement behavior and plan requirements |
Confirm each supported operation in the vendors' current documentation or with their support. A member CSV does not establish that subscriptions, saved payment methods, passwords, or discussion history can move with it.
3. Prove one transfer before planning all transfers
Try a small sample of material and test accounts. Record what arrived, what changed format, and what requires manual work. Keep the original source files.
For a DAO or NFT group, test wallet identity and token gating separately from email invitations. Check both entry and access removal. The existing integration may not work on the new platform.
4. Resolve billing before sending invitations
Document where a member will be charged, where they cancel, and what happens to the old subscription. If the providers offer a supported payment migration, confirm eligibility and scope directly. Otherwise, define the new signup process and prevent overlapping charges.
Do not treat exporting member contact details as permission to recreate paid subscriptions.
5. Pilot the complete member journey
Invite a small group representing the access levels you intend to support. Ask them to join, find a resource, enter an event, ask for help, and manage their membership. Test links from an ordinary member account as well as an administrator account.
Record problems and retest the fixes before opening the wider migration.
6. Publish one clear change notice
Explain the reason, what members must do, the date their routine changes, and the support contact. Link one canonical set of instructions. Keep the old community accessible for an overlap period suited to your billing and member activity; a four-week plan is not a universal requirement.
A notice can use these fields, filled in only after you confirm the details:
From [date], find lessons at [new address]. Your existing access will [confirmed change]. Your subscription will [confirmed billing action]. Complete [required step] by [date]. For help, contact [support address].
Keep the notice linked from the old community during the transition. Have someone outside the migration team read it and explain what they must do and where the next charge will happen.
7. Set the conditions for switching and a fallback
Before reducing activity in the old space, check invitations, successful access, payment problems, missing resources, and unanswered support requests. Define acceptable results for your own group before the pilot. If a critical part fails, pause the move and keep the existing member path working.
Afterward, review the first renewal cycle and fix stale links. The community-building playbook helps design the ongoing routine; the free Academy community module puts that work into a learning sequence.
References
Next, read Best Community Platforms for Creators. More in Community Building.