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
List what Substack currently owns before changing any live fan-facing path.
Decide which jobs should become native Fanful surfaces and which should remain linked or temporarily external.
Keep the source platform live while the Fanful destination is checked by humans and agents.
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. |
These are the checks to pass before replacing a live Substack path with Fanful.
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.
Source notes