Creator acquisition
How to Move Creators and Their Patrons Off Patreon Safely
Short answer
To switch from Patreon to another platform, a creator exports whatever the old service allows, recreates tiers on the new one, and invites patrons to subscribe again, because stored payment authorizations rarely move between companies. Run both for a few weeks, announce early, and wind down the old page only after most patrons have moved.
Key takeaways
- Creators move easily; patrons move only when they re-authorize payment, so plan the migration around that step.
- Be exact with creators about what can be exported, and tell them to confirm current options in Patreon's own help center.
- Map old tiers to new tiers on paper first, and decide how existing prices and perks carry over.
- A four-week timeline of announce, overlap, switch and wind down protects the creator's income.
- Keep the message about what your platform offers; never disparage the old service.
On this page 9 sections
Moving a creator off Patreon is a campaign, not a file transfer. The creator can move quickly, because they decide where they publish. Their patrons cannot be moved for them, because the payment authorization each patron gave belongs to the old service and its payment provider. A safe plan therefore invites creators first, asks patrons to subscribe again, overlaps the two pages for a few weeks and ends the old one last.
This guide is for the operator of a new platform recruiting established creators, and it works as a practical timeline. It assumes you run a membership platform such as a white-label Patreon clone and need a process you can repeat for each creator. A note on sourcing: Patreon's own pages could not be opened when we wrote this, so we state no Patreon export option, fee or policy as fact. Tell creators to check the current options in Patreon's help center, and to read the agreement they accepted. This is general information, not legal advice.
What can and cannot be moved
Be exact with creators about this before they commit. Surprises in the middle of a migration cost trust and income.
| Item | Usually movable? | How | Check first |
|---|---|---|---|
| The creator's own posts and media | Yes, by the creator | Republish from the creator's own originals | Does the creator have the originals? Do they hold the rights? |
| Tier names, benefits and prices | Yes, recreated | Map old tiers to new ones by hand | Which perks can your platform deliver? |
| A supporter contact list | Depends on what the old service lets the creator export | Export from the old service, if allowed | The old service's current options and the supporters' consent |
| Payment authorizations (stored cards) | Generally no, by a creator | Patron re-subscribes on the new platform | Whether the processors involved offer a data transfer between companies |
| Subscription history and past payments | Not as a live relationship | Keep a record for the creator's own accounting | Tax and bookkeeping needs |
| Comments, likes and community history | Mostly no | Start fresh, or screenshot highlights | Whether it matters to the community |
Why payment cannot simply move
A patron's card is stored with the service's payment provider under a contract with that service. Stripe's documentation on migrating subscriptions says that when you migrate payment data from another processor, card data must come through a payments data import request first, and that without a default payment method on each customer, invoices cannot collect payment. That is a company-to-company process with its own requirements; an individual creator cannot start it. For an operator, the safe assumption is that every patron enters payment details again.
What your platform supports
Our ready-made Patreon clone lets creators move by invitation and republish their work. Supporters subscribe again from a creator's profile page by choosing a plan and paying by card or digital wallet. Bulk import of content or member lists depends on formats and consent and is something we set up for your build, so ask early what the old service will let creators export. Confirm the scope with us at kickoff through our contact page before you promise a creator an import.
The invitation: what a creator needs to see first
An established creator is protecting income, so the first message has to answer risk before it sells features.
- A fee comparison done fairly. Show the net payout for one invented sale, using Patreon's current published rates as the creator reads them on its pricing page and your own commission. Do not quote Patreon's numbers from memory; let the creator fill them in.
- The tools they use. Tiers, per-plan access, discounts, pay-per-view, tips and custom requests. The Patreon clone features page lists the creator-side tools.
- How and when they get paid. Creators withdraw by bank transfer, digital wallet or another configured gateway. Show the withdrawal flow in a demo; it is the question every creator asks.
- What support they get. Name a person, a reply time and an onboarding session.
- A short migration offer. For example: you will help set up the profile, price the first tier and republish the first posts, and you will give their first supporters a launch bonus. Offers must be ones you can keep.
Our guide on recruiting your first creators covers the target list and the pitch in more detail; this section assumes the creator is already an established Patreon user.
What to put in writing
- Your commission and what it covers, with a worked example.
- Payout schedule, minimum withdrawal and who bears gateway charges.
- Content rules, in plain language, before the creator moves anything.
- What the creator can export from your platform if they leave.
- Who owns the content (the creator) and what license you need to display it.
Tier mapping: old tiers to new
Do this on paper before anyone clicks. A tier map lists each old tier, its price, its perks and what it becomes on the new platform.
| Old tier (example) | Old price | Perks promised | New tier | New price | Notes |
|---|---|---|---|---|---|
| Supporter | 3 | Name in credits, update posts | Entry | 3 (kept) | Same perks; no changes needed |
| Member | 8 | All posts, early access | Core | 8 (kept for 12 months for movers) | Legacy price for movers; new price later for new patrons |
| Insider | 25 | Monthly live Q&A, capped requests | Premium | 25 | Check that live sessions and request limits are configured |
The prices are invented. The questions are not. For each row ask: can your platform deliver this perk? Will the price stay the same, and for how long? Does anything need explaining to patrons? Our post on membership tier ideas and pricing helps if the old structure has too many tiers or unfulfillable perks; a migration is the right time to clean it up, though changing too much at once confuses patrons. A good rule is to keep names, prices and perks the same for the first month, and change structure later.
A four-week migration timeline
This timeline suits a creator who publishes weekly or more. Stretch each phase for a creator who publishes monthly.
| Week | Phase | Creator does | You do |
|---|---|---|---|
| Before week 1 | Prepare | Reads the terms they accepted on the old service; picks a start date | Sets up the profile, tiers and payout method; tests a real payment; writes the invitation |
| Week 1 | Announce | Tells patrons the plan and the date, on the old page and by any channel they own | Supports the announcement with a short how-to-subscribe guide |
| Week 2 | Overlap | Posts on both; gives the new page a bonus post | Watches re-subscription numbers; answers patron questions |
| Week 3 | Switch | Moves new posts to the new platform first; reminds laggards | Sends reminders for abandoned checkouts if consent allows |
| Week 4 | Wind down | Posts a final notice on the old page; stops new posts there; may leave the page open as a pointer | Reviews first payouts; collects feedback for the next creator |
Rules for the overlap
- Do not ask patrons to pay twice for the same period. Say clearly when to cancel on the old service.
- Give a reason to move now: a bonus post, a founder's price or a first-month perk, within what you can deliver.
- Keep the old page open until most active patrons have moved, because it is where unmoved patrons will look.
- Check any notice period or term in the agreement the creator accepted on the old service before closing a page.
Supporter re-subscription
Re-subscription is where migrations succeed or fail. Every step between the invitation and the payment loses some people.
The path to measure
- Sees the announcement.
- Clicks the link to the creator's new page.
- Registers and confirms an email address.
- Chooses a plan.
- Pays by card or digital wallet.
- Sees the locked content open.
Track how many patrons reach each step. A creator with 200 patrons who sees 120 clicks and 60 payments knows where to look. These numbers are an example of the method, not a forecast.
Friction points and fixes
| Friction | Fix |
|---|---|
| Registration feels like a big commitment | Keep the form short; email confirmation only |
| Patron cannot tell which plan matches their old one | Name the new tiers the same, at least for the first month |
| Fear of double billing | Say explicitly when and how to cancel on the old service |
| Payment method not accepted | Check your gateways support the cards and wallets your patrons use before launch |
| Store app confusion | Explain web versus in-app purchase if you ship apps |
| No reason to hurry | A dated bonus or legacy price that ends |
Store billing and apps
If patrons will subscribe inside a mobile app, remember the store rules. Apple's App Review Guidelines require in-app purchase for subscriptions and premium content in guideline 3.1.1, and Google's payments policy requires its billing for digital subscriptions in Android apps, with regional exceptions. A web checkout link in the invitation is often simpler for patrons, but store rules limit how an app may point to it, so check the current text. Our post on app store rules for creator subscription apps explains where the lines are.
Messages that work
- One clear sentence on why: "I am moving my membership to a home where I set the rules and where we can talk directly."
- One clear action: "Subscribe here by this date."
- One clear reassurance: "Your price stays the same for the next twelve months."
- One clear reminder before the old page closes.
Content import
Republishing is simpler than it sounds for most creators, because they hold the originals: videos, images, posts and files. A creator who has a few hundred posts can republish the best ones in a day or two, and archive the rest.
| Scope | Approach | Effort |
|---|---|---|
| Top posts and a welcome series | Creator republishes by hand; you help in the first session | Hours |
| Full back catalog from originals | Creator or a helper uploads in batches | Days |
| Bulk import of posts or member lists from an export file | Set up for your build, around the file format and consent | 2 to 8 weeks |
Bulk import is set up per build because formats and consent differ, and it only makes sense if the old service gives creators a usable export. Ghost's help page shows what a simple member import looks like on a publishing tool: a CSV where email is the only required column, with an optional column to link a member to a customer in a connected Stripe account. That works inside one payment account. Moving between companies adds the data request step described above. If a creator needs this, we can deliver it; read about the Patreon clone development company and how tailored work is handled. Tailored changes usually take two to eight weeks depending on the work.
Rights and consent
- The creator should republish only content they own or may license.
- Patron data belongs to patrons as much as to anyone; use it only as consent and law allow.
- Substack's going-paid page is an example of a service stating that authors own their content and subscriber list; creators will ask you for the same plain statement.
What to measure and what can go wrong
A migration is easier to run when you know the numbers before it starts. Agree three figures with each creator and review them weekly.
| Measure | How to read it | Action if low |
|---|---|---|
| Share of active patrons who have re-subscribed | Moved patrons divided by patrons at the start | Simplify the path; add a dated bonus; send a reminder |
| Income compared with the month before | New plus old platform, net of fees | Extend the overlap; do not close the old page yet |
| Support questions per 100 patrons | Messages about checkout, price or access | Fix the top question in the guide; add it to the announcement |
| Failed or abandoned checkouts | Started payments that did not complete | Check gateway coverage for the patrons' cards and wallets |
An example of a first month
These figures are invented to show how to read the plan. Say a creator has 200 active patrons paying an average of 8 a month, so 1,600 comes in on the old service. After four weeks, 90 patrons have re-subscribed on the new platform at the same average price, and 80 are still paying on the old one. New-platform income is 720 and old-platform income is 640, so the combined 1,360 is about 85% of the starting figure. The creator is not failing; the move is half done, with 30 patrons unaccounted for. The next steps are to ask why those 30 have gone quiet, extend the overlap by two weeks and keep the old page open as a pointer. Compare that plan with closing the old page on day 28, which would have cut income to 720 and lost any patron who had not yet seen the notice.
Common failure points
- Closing the old page too early. Unmoved patrons lose their way and the creator loses them.
- Changing everything at once. New prices, new tiers and a new platform together raise cancellations.
- An untested subscribe flow. A broken checkout on launch day wastes the creator's best moment.
- Unclear payout timing. Creators who wait longer than expected for the first payout may stop recommending you.
- Over-promising. Features that are not live, such as an import you have not scoped, break trust faster than a missing feature does.
- Ignoring tax and records. The creator should keep records of income on both services during the overlap; ask an adviser how to report it.
Glossary
- Re-authorization: a patron entering payment details again on the new platform.
- Overlap period: the weeks when a creator posts and bills on both services.
- Legacy price: a price held for patrons who move, for a stated time.
- Tier map: a table matching each old tier to a new one.
Drop-off scenarios to test
No migration moves every patron. Treat the share that moves as an assumption to test with each creator, and plan income for the lower cases. These scenarios use invented numbers: 200 patrons paying an average of 8 a month, so 1,600 a month before the move.
| Scenario (assumed) | Patrons who move | Monthly payments after move | Change from start |
|---|---|---|---|
| Strong, warm audience | 70% (140) | 1,120 | minus 30% |
| Typical case to plan for | 50% (100) | 800 | minus 50% |
| Weak, passive audience | 30% (60) | 480 | minus 70% |
The percentages are placeholders, not findings. The point is to ask the creator whether they can absorb the middle row for a few months. If not, a longer overlap or a smaller first step, such as moving only new patrons and a new tier, is safer. A creator who sees these numbers before they decide is less likely to blame you afterward. Re-measure after each week of the plan and update the table.
Timeline with owners
| When | Task | Owner |
|---|---|---|
| Before week 1 | Review old agreement and export options | Creator |
| Before week 1 | Set up profile, tiers, payout method; test payment | Operator with creator |
| Week 1 | Announce the move and the date | Creator |
| Week 1 | Publish the how-to-subscribe guide | Operator |
| Weeks 2 to 3 | Post on both; send reminders; answer patron questions | Creator and operator support |
| Week 3 | Review re-subscription and checkout drop-offs | Operator |
| Week 4 | Decide whether to close or extend the old page | Creator |
| After week 4 | First payout review and feedback | Operator and creator |
How long should the overlap be?
| Creator type | Suggested overlap to test | Reason |
|---|---|---|
| Posts several times a week | 2 to 4 weeks | Patrons see the notice quickly |
| Posts weekly | 4 weeks | Gives each patron at least four chances |
| Posts monthly or less | 2 to 3 months | Patrons may not see a notice for weeks |
Respect the old terms
A creator stays bound by whatever they agreed to on the old service. Encouraging a move is fine; encouraging a breach is not.
- Read the old agreement. Ask creators to check notice periods, exclusivity and rules about directing patrons elsewhere. If in doubt, suggest they ask the old service's support or a lawyer.
- Do not disparage. Describe what your platform offers, with your own numbers, and leave the other service out of it. Creators will make their own comparison, and patrons dislike drama.
- Do not copy. Use your own wording, design and brand. We are not affiliated with Patreon, and a clone is software of a similar kind, not a copy of its code or look.
- Keep promises you can keep. A founder's price, a launch bonus or a support commitment must hold after the migration ends.
Operator checklist
- Write a one-page offer: fees with a worked example, payouts, support, content rules and export terms.
- Build the tier map for each creator and test every perk you promise.
- Test the subscribe flow yourself, on a phone, with a real card.
- Plan four weeks per creator, and move creators in small groups.
- Track patrons at each step: sees, clicks, registers, pays.
- Review the first payout with the creator and ask what to change before the next group.
If you do not yet run a platform, start with how to start a membership platform for creators, and compare options in sites like Patreon. For the cost and scope of your own base, see Patreon clone development cost. Patreon is a trademark of its owner and is named here only to describe the category.
Questions and answers
Can I export supporters from Patreon?
What a creator can export, and in what format, is set by the service and can change. Patreon's export options change over time, so we state no specifics here. Creators should check the current export options in Patreon's help center before promising their new platform a list, and ask only for data they are allowed to share.
Will supporters keep their price?
That is your decision as the new operator, and a good one to make explicit. Many creators offer existing patrons their old price for a set period as a thank-you for moving. State it in the invitation, in writing, and make sure your tier tools can hold a legacy price. Without that, supporters will assume the price rises.
Should creators run both for a while?
Yes, for most. An overlap protects income while patrons re-subscribe, because few people act the day they are asked. Two to four weeks of overlap is a common plan, longer if the creator publishes monthly. End the old page only after most active supporters have moved or declined.
What do creators fear most?
Losing income during the move. A close second is losing their supporters' goodwill by pushing them through a clumsy checkout. Answer the first with an overlap and a clear payout schedule, and the second by testing the new subscribe flow yourself and keeping it short.
How long until revenue recovers?
It varies with the audience, the clarity of the invitation and how many patrons are active. Plan for a dip and a gradual recovery over weeks to months, and do not promise a date. Track the number of patrons who have re-subscribed each week, not just revenue.
Can card details be transferred to the new platform?
Usually not by the creator. Stripe's migration documentation says that moving card data from another processor requires a payments data import request, which is a process between companies. Operators should assume patrons will enter payment details again on the new platform, and plan messaging for that step.
Sources
- Stripe Docs: Migrate subscriptions to Stripe Billing
- Ghost Help: Import members
- Apple App Review Guidelines
- Google Play Payments policy
- Substack: Going paid
Checked in October 2026. Rules, fees and programme terms change; confirm on the source before you rely on them.
Independence note. GetFame is an independent software company. Patreon is a trademark of its owner and is named here only to describe a category of platform. GetFame is not affiliated with, sponsored by or endorsed by Patreon.
Keep reading
How to Recruit Your First 100 Creators to a Fan Platform
How to recruit creators for a subscription platform: build an offer, pick a niche, run outreach for the first 20, onboard in a day and measure the cohort.
How to Start a Membership Platform for Creators: A Guide
How to start a membership platform for creators: pick the audience, design tiers and billing, choose rent or own, handle tax and store rules, and launch.
Sites Like Patreon: Niche Membership Platforms That Win
Sites like Patreon compared by pricing model, audience ownership and fit: general tools, niche platforms and what an operator can learn before building one.