# Switch from Circle to Fanful: migration guide

A practical migration checklist for creators evaluating Fanful as a Circle alternative.

## Migration posture

Treat community continuity as the main risk. Fanful should start with new member rooms and access rules before attempting to move full discussion archives, moderation history, events, courses, or engagement workflows.

## Migration stages

### 1. Inventory the current stack
List what Circle currently owns before changing any live fan-facing path.

- Audit spaces, channels, posts, events, courses, members, roles, moderation needs, payments, and engagement loops.
- Decide whether existing community archives need to move or whether Fanful should start with new rooms and member experiences.

### 2. Map fan jobs into Fanful
Decide which jobs should become native Fanful surfaces and which should remain linked or temporarily external.

- Creators who want community to be connected to their public site, shop, media, live rooms, and memberships.
- Separate content, commerce, membership, community, lesson, live, email, and analytics needs so each one has an owner.

### 3. Run in parallel before cutover
Keep the source platform live while the Fanful destination is checked by humans and agents.

- Map roles and paid access to Fanful memberships before inviting members into a new community surface.
- Keep Circle live until Fanful can cover the community rhythms that members rely on every week.

## Data map

| Source data | Fanful destination | Handling note |
| --- | --- | --- |
| Spaces, posts, events, courses, and member roles | Community rooms, live moments, lessons, and memberships | Start with active spaces and role mapping before archive migration. |
| Members, segments, payments, and access groups | Fan profiles and membership access | Validate every paid/community role against Fanful access rules. |
| Moderation history, pinned resources, and onboarding | Community operations checklist | Keep moderation context documented even when archives stay behind. |
| Community homepage and invite flows | Owned site and member entry points | Run both communities in parallel until members know where to post. |

## Cutover checks

- The Fanful comparison page for Circle still describes the tradeoff honestly.
- Every migrated fan path has a fallback link to the old platform during the transition.
- Paid access, export rights, and email consent are documented before any audience import.
- The markdown guide mirrors the browser guide so agents can audit the migration plan.

## Related pages

- [Fanful vs Circle](/compare/circle-alternative.md)
- [Fanful compare hub](/compare.md)
- [Fanful roadmap](https://fanful.net/roadmap)

## Source links

- [Circle homepage](https://circle.so/)
- [Circle courses](https://circle.so/platform/courses)
- [Circle professional communities](https://circle.so/platform/professional-communities)