Migration guide
A practical migration checklist for creators evaluating Fanful as a Bandcamp alternative.
Migration posture
Respect existing music buyers and collectors. Fanful can become the owned artist home while Bandcamp continues to handle historical purchases, marketplace discovery, downloads, and music-native buying habits until replacement flows are proven.
Migration stages
List what Bandcamp 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 |
|---|---|---|
| Albums, tracks, merch, artwork, and embeds | Media library, release pages, and shop offers | Keep purchase links intact while recreating the owned artist presentation. |
| Fans, supporters, messages, and mailing list exports | Fan profiles and email/community segments | Import contact context only where export rights and consent are clear. |
| Subscriptions and subscriber-only items | Membership benefits and protected media | Move benefits only after subscribers know what remains on Bandcamp. |
| Artist page links and social destinations | Artist homepage and campaign pages | Switch primary links gradually to avoid breaking existing purchases. |
These are the checks to pass before replacing a live Bandcamp path with Fanful.
The Fanful comparison page for Bandcamp 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