Getting Started

What Patreon members actually bring with them when you move subscriptions

Separate transferable supporter data from platform-bound benefits, payment records and membership history before announcing the move.

The store.fan teamNovember 13, 20266 min read
What Patreon members actually bring with them when you move subscriptions

You have decided to move your paid membership away from Patreon. A supporter asks whether their subscription, payment history and access will follow them. You open an export, find a list of names and email addresses, and realise the harder question is not what you can download. It is what you are allowed to use, what you can recreate, and what your members will need to do again.

Start with four different kinds of information

The word “members” hides several records. Separate them before you write an announcement. A supporter’s contact details are not the same as permission to email them. A payment record is not the same as an active subscription. A history of comments or downloads is not the same as access to your new membership.

What you may haveWhat it can help you doWhat it does not prove
Name and email addressIdentify people and explain the moveThat they consent to every type of marketing or want to continue
Tier, pledge or subscription statusMap people to a possible new offerThat the same tier, price or benefit exists on your new platform
Payment and transaction recordsReconcile income and answer support questionsThat you can charge the same card or move billing automatically
Join date and membership historyPreserve context and recognise long-standing supportersThat old comments, badges or platform access can be reproduced
Posts, comments, files and messagesIdentify content worth archiving or recreatingThat every item can be exported, republished or transferred

What supporters can usually bring

The most useful thing to bring across is a carefully checked contact list, subject to the terms and permissions that governed its collection. Keep the fields you genuinely need: name, email address, former tier, status, join date and a note about any promised benefit. You may also need an internal record of refunds, cancellations or unresolved support issues.

That record is for planning and support, not an invitation to assume every person is still an active customer. Mark people as current, cancelled, lapsed, refunded or unclear. If a field cannot be verified, leave it unclear rather than turning an assumption into a promise. A simple spreadsheet can expose gaps before your announcement does.

  1. 1Export the available supporter and transaction data from Patreon, then keep the original file unchanged as your reference copy.
  2. 2Create a working copy and remove fields you do not need for the move.
  3. 3Check each segment against your terms, privacy notice and the permissions attached to the original collection.
  4. 4Match each former tier to a specific new product, membership or next step, including any difference in price or benefits.
  5. 5Contact supporters with a deadline, a clear explanation and a way to ask questions or decline.

What does not transfer automatically

Platform-bound benefits stay platform-bound unless you deliberately rebuild them. This can include Patreon posts, comment threads, reactions, badges, private messages, platform notifications, saved payment methods and the member’s existing login. Even when you can download a file or copy text, the surrounding history may not come with it.

Billing is the sharpest boundary. You should not describe a list of Patreon supporters as a list of people whose payments will continue. In most cases, the supporter needs to review the new offer and complete the new checkout. Your migration plan should therefore include a final date for the old membership, a start date for the new one and instructions for avoiding an unwanted overlapping charge.

Rebuild the promise before you rebuild the page

Write down what each Patreon tier actually promised. Include delivery frequency, format, archive access, community participation, calls, discounts and any personal response you offered. Then decide whether each promise is continuing, changing, ending or becoming an optional extra.

  • If the promise is recurring content, prepare the first few deliveries on the new platform before inviting people over.
  • If it is a private group, decide where conversations will happen and how new members will receive access.
  • If it is a call or live session, publish the booking or attendance process rather than assuming the old workflow carries across.
  • If it is an archive, label what is available on the new platform and what will remain unavailable.
  • If the price changes, show the old and new amounts plainly and explain what has changed with them.

Give the new home a clear job

Your new storefront should make the next action obvious. With store.fan, you can create a home at store.fan/yourname for a membership offer, rather than asking supporters to reconstruct the move from several links. Its paid plans start with a 14-day trial, and store.fan takes 0% of sales; Stripe’s own processing fee still applies.

Money goes straight to your own Stripe account. That gives you a new payment relationship to explain, not an old subscription to pretend has moved. If you need to organise supporter records and follow-up, store.fan’s customer CRM can sit alongside the new storefront. Pro also adds email marketing, discount codes, flash campaigns, hosted course video and creator-run affiliate programmes.

Use the migration email to answer four practical questions: why are you moving, what changes for the supporter, what must they do and when does the old arrangement end? Link to the new checkout only after the offer is ready. If you send people to an unfinished page, you create support work before you have a working destination.

Keep a record after the move

After the announcement, record who has moved, who declined, who needs help and who has not responded. Do not treat silence as consent to a new charge. Send a reminder that repeats the date and action, then close the old membership according to the timetable you published.

Keep the original export, your cleaned working file, copies of the messages you sent and a note of decisions about tiers and benefits. Limit access to those files and retain only what you have a reason to keep. The purpose is to resolve legitimate questions and run the new membership responsibly, not to collect a permanent archive of unnecessary personal data.

Do not assume that you can. A supporter may need to choose the new offer and complete its checkout themselves. Treat the Patreon list as migration context, then give each person clear instructions for joining the new membership.

That depends on how the information was collected, the permissions given at the time and the rules that apply to your communication. Segment current, cancelled and unclear records, check your terms and privacy notice, and avoid presenting every former supporter as an active customer.

Identify the material you are entitled and able to export or republish, then decide what is worth recreating. Tell supporters which archive or history will be available on the new platform. Do not promise that comments, badges, private messages or platform notifications will come with them.

Build the new membership home first, then invite supporters to make the move on clear terms.

Start with store.fan
#memberships#migration#customer-data#patreon#digital-products

Turn your knowledge into income

Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.