Leave Skool
Leaving is the product.
An assisted migration with the limits written down before you move.
- billing transition scoped first
- timeline agreed after review
- export path documented
Three steps. No surprises.
Data, billing, and launch risks are mapped before the community is asked to move.
- step_01
Map your permitted export
We review what your current platform can export, map it to community.io, and document every gap before anything moves.
- step_02
Rebuild and verify
We rebuild the community structure, tiers, and permitted content with you in an invite-only workspace.
- step_03
Choose the cutover
You approve the member communication, billing transition, and launch date. Nothing changes until the checklist is complete.
What you keep. What changes.
You keep
- A written billing-transition plan — including where members may need to take action
- Permitted data identified in your export before the rebuild
- An approved map of courses, posts, events, and access rules
- Your approved terms — price and support scope confirmed before launch
What changes
- Your URL and domain plan — scheduled only after the launch checklist passes
- Your billing — V1 uses creator-owned payments; provider costs and member actions are confirmed before cutover
- One documented operating plan — not a surprise after your members have moved
- Your export — specified, tested, and available before we claim it is complete
Honest limit: we import what Skool lets out. Anything its export holds back is documented with you during the migration — we don’t promise what we can’t port.
- Data mapevery imported field and known omission recorded before the rebuild
- Cutovercreator-approved member, billing, and launch communication plan
- Exporta testable exit path is a release requirement, not a slogan
Verified against live pricing pages · July 7, 2026 · run your own numbers in the Skool fee calculator →
Founding 100 · applications open
The Founding 100
A hundred spots, because that’s how many migrations we can do personally.
Founding access
You get direct product access, a written launch plan, and pricing confirmed before your invite — no surprise migration fees.
White-glove migration
We scope your permitted export, rebuild the agreed structure, and validate the launch checklist with you.
Transparent terms before launch
Payment, pricing, export, and member-transition terms are written down before your community is invited to move.
A direct line to the founder
Founding migrations are done personally. You get the direct line, not the ticket queue.
No countdown, no “12 spots left” — spots are confirmed by reply, in order. And if we’re ever not better, leaving us is one click too: read the anti-lock-in pledge →
The migration ledger
Real numbers only — members moved, hours taken, fees before and after.
Case studies land here as founding migrations complete. Nothing is published until a real community has moved — and nothing on this page is invented.
Before you ask
- How does member billing move?
- We do not promise card or subscription portability. We document the provider-supported billing transition and member communication plan before you commit to a cutover.
- How long does a migration take?
- Timing depends on the data you can export, the community structure, and the payment transition. We agree a timeline only after reviewing those inputs.
- What if community.io isn’t better?
- Then you keep control of the data you provided. Our launch pledge commits us to a documented export path and no exit penalty; it becomes a live guarantee only when the export is implemented and tested.
The anti-lock-in pledge
- Export scope documented
- Exit terms before launch
- Support commitments documented
- No unverified promises