# Switch from Substack to Fanful: migration guide

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

## Migration posture

Keep the newsletter relationship stable while Fanful takes over the wider fan home. The safest path is to move public pages, offers, and member context first, then decide whether paid subscriptions should remain on Substack during the transition.

## Migration stages

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

- Export publication, post, subscriber, paid-subscription, podcast, and payment setup data before changing the live reader experience.
- Decide whether existing paid subscriptions should continue on Substack while Fanful handles site, shop, media, or community first.

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

- Creators who need newsletters plus commerce, media, live, lessons, memberships, and community under their own brand.
- 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 welcome emails, referral rewards, reader segments, free subscribers, and paid subscriber benefits into a shared fan profile.
- Publish a transition note that tells readers what stays in their inbox and what moves into Fanful.

## Data map

| Source data | Fanful destination | Handling note |
| --- | --- | --- |
| Posts, podcasts, publication pages, and comments | Public posts, media, and protected member content | Decide which archive content must move versus remain linked from Substack. |
| Free and paid subscriber lists | Fan profiles, membership candidates, and email segments | Preserve paid/free status and do not change billing without explicit subscriber messaging. |
| Welcome flows, referrals, and benefits | Onboarding, offers, and member benefits | Map benefits before importing people so access rules are clear. |
| Publication identity and custom domain | Owned creator site and fan home | Redirect only after readers can still find the newsletter and paid content. |

## Cutover checks

- The Fanful comparison page for Substack 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 Substack](/compare/substack-alternative.md)
- [Fanful compare hub](/compare.md)
- [Fanful roadmap](https://fanful.net/roadmap)

## Source links

- [Substack reader guide](https://support.substack.com/hc/en-us/articles/33655200073620-A-reader-s-guide-to-Substack)
- [Substack pricing](https://support.substack.com/hc/en-us/articles/360037607131-How-much-does-Substack-cost)
- [Substack paid publication setup](https://support.substack.com/hc/en-us/articles/360037459952-How-do-I-set-up-a-paid-publication)