Migration guide
A practical migration checklist for creators evaluating Fanful as a Linktree alternative.
Migration posture
Replace the destination, not every outbound link at once. Fanful should become the first owned landing page while high-value external links stay available until native Fanful pages can cover them.
Migration stages
List what Linktree 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 |
|---|---|---|
| Link list, social destinations, campaigns, and thumbnails | Fanful homepage sections and campaign pages | Promote the most important links into native Fanful destinations first. |
| Music smart links, merch links, ticket links, and email capture | Music, shop, dates, and fan signup surfaces | Keep external links where Fanful does not yet replace the destination. |
| Click analytics and campaign tags | Fan action analytics | Track downstream actions, not only outbound clicks. |
| Profile URL and QR codes | Owned fanful.net or custom-domain entry point | Update public links only after the Fanful landing page covers the common fan jobs. |
These are the checks to pass before replacing a live Linktree path with Fanful.
The Fanful comparison page for Linktree 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