Reader question: If a platform lets you export members or email addresses, what have you actually carried with you, and what commercial dependency remains?
Creators are often asked whether they “own” their audience. That question hides three different assets: a way to identify and contact people, a record of what those people are entitled to receive, and a channel that can still reach them. A CSV can preserve one layer while leaving the other two behind.
Current documentation makes the gap visible. Ghost separates exports for content, members, themes, and post analytics. Ghost export documentation Patreon lets creators filter member records and download a CSV, while noting that a fan can withhold an email address. Patreon Relationship Manager YouTube says subscriptions are private by default. YouTube subscription privacy Portability is a commercial design question, not a checkbox.
Start with the three-layer test
| Layer | What may travel | What the export does not prove |
|---|---|---|
| Contact | An email, name, platform ID, label, opt-in state, or other row-level field, where the platform provides it. | That every follower is identifiable, that each address is current, or that you may use it for every kind of message. |
| Entitlement | A tier, membership status, payment amount, join date, cancellation state, or billing reference. | That a paid subscription, stored payment method, access rule, refund history, or benefit obligation will transfer to a new platform. |
| Distribution | Content files, a channel or publication URL, and selected analytics if the provider exports them. | The recommendation system, accumulated trust, audience habit, inbox placement, or platform discovery that made the original channel valuable. |
Call these contact, entitlement, and distribution. They overlap in a creator’s work but should not be priced or promised as the same asset. The rest of this article is a decision framework for checking the dependencies before a platform choice, not a set of export instructions.
What a membership or email export really carries
Ghost’s export page is explicit about the handoff. It lists content and pages in JSON, members in CSV, theme files in a ZIP, and post analytics in a separate CSV. Its member export can include IDs, contact fields, email-subscription state, a Stripe customer reference, dates, and labels. Ghost says member rows can be imported to another Ghost site or reformatted for another platform. Ghost export documentation That is useful portability, but a member CSV is not a full publication backup.
Patreon’s Relationship Manager shows the same principle from a membership angle. Its documentation lists filters for member type, status, tier, dates, benefits, and subscription source. The filtered list can show tier, pledge, status, access dates, and other fields, then download those rows as a CSV. Patreon also says profile names may be anonymous and that a fan may opt out of sharing an email address. Patreon Relationship Manager Rows are not the same as fully reachable people.
What the file leaves behind
Permission is separate from possession. Patreon’s documentation for importing an email list says the contacts must already be people the creator has permission to contact. Its email-only subscribers can receive posts, but they need a Patreon account to comment, vote, join chats or livestreams, or play audio and video; they can unsubscribe, and they do not receive Patreon system emails unless they create an account. Patreon email-list import guidance An address in a spreadsheet is not a universal marketing permission or a replacement for a member identity.
Billing is not the same as an email address. Ghost’s migration guidance for Kit states that Kit-managed paid subscriptions have no direct migration path to another platform. It describes importing subscriber emails and granting access on Ghost, but that is a new access arrangement, not a transfer of the original payment relationship. Ghost migration guidance for Kit Ask who processes the payment, who owns the recurring agreement, and what happens to refunds, failed charges, taxes, and benefits before calling a membership portable.
Reach is not the same as a subscriber row. YouTube says viewers’ subscriptions are private by default; when a subscription is private, the account does not appear in a channel’s Subscribers List. YouTube subscription privacy A public subscriber count can be a useful distribution signal, but it is not an exportable contact database. The channel’s recommendation and notification systems are also platform behavior, not a file the creator can recreate by importing names.
Context is usually split across artifacts. Ghost’s separate content, member, theme, and analytics exports show why a single “backup” label is misleading. A migration may carry the people but lose history, design, source attribution, engagement data, moderation context, or entitlement logic unless those are mapped separately. That is an inference from the provider’s categories, not a claim that every platform loses every field.
Ask the dependency questions before choosing
| Dependency | Question to put in the commercial record | Evidence to request |
|---|---|---|
| Contact | Can the creator export all relevant free, paid, canceled, and opted-out states? Which fields are withheld or redacted? | A sample export schema, privacy explanation, and the stated refresh or API limits. |
| Entitlement | Can a new platform recreate tiers, access dates, benefits, and failed or refunded states without treating an email as proof of payment? | Field mapping, payment-processor terms, migration support, and a refund or chargeback path. |
| Distribution | What reach remains if recommendations, notifications, discovery, or the account itself changes? | A channel continuity plan, audience reach metrics, and the platform’s account and content rules. |
| Operations | Are content, media, themes, analytics, moderation records, and source tags separate exports? | A complete export inventory and a test import or documented mapping boundary. |
| Exit | What can be downloaded during a suspension, cancellation, or contract dispute, and how long is access available? | The terms, notice periods, support route, redirects, and any post-termination access window. |
The decision standard is not “Does this platform offer CSV export?” It is “Can we account for contact, entitlement, distribution, and exit risk in writing?” A platform can be expensive and still be a rational choice if it supplies valuable operations and a clear exit. A free platform can be commercially fragile if the creator cannot identify permissioned contacts, preserve paid access, or maintain a second route to readers.
An illustrative move between platforms
Consider a hypothetical creator with 100,000 video subscribers, 3,000 paid members, and 5,000 newsletter recipients. A membership CSV contains some rows without emails because people withheld them; the video subscriber total is not a contact list; and the new membership service cannot simply charge the old payment relationship. Keep the discovery channel running while a permissioned email relationship is established, map paid benefits, ask members to make any required new payment or account choice, preserve old and new status definitions during the overlap, and measure reactivation separately from imported rows. None of this guarantees retention; it makes dependency visible before continuity is promised.
Portability is not binary. It is a set of fields, permissions, relationships, and distribution privileges with different owners and failure modes. Keep a dated map of those layers, review the provider’s current terms before a move, and let the audience choose what follows them. The file is valuable. It is not the whole business.
Sources and limitations
- Ghost Foundation, “Exporting content and data” — checked September 2, 2026; supports Ghost’s separate content, member, theme, and post-analytics export formats, member fields, and reformatting or importing member rows. Limitation: Ghost’s export design is one provider’s implementation and does not establish what another platform exports.
- Patreon Help Center, “How to use your Relationship manager” — checked September 2, 2026; updated August 3, 2026; supports membership filters, CSV download, member fields and statuses, anonymous profile names, and missing email addresses when a fan opts out. Limitation: actual columns and visibility depend on the member record and Patreon account state.
- Patreon Help Center, “Importing your email list to Patreon (Beta)” — checked September 2, 2026; updated January 23, 2026; supports the requirement for pre-existing contact permission and the differences between email-only subscribers and Patreon accounts. Limitation: the feature is documented as early access and may change.
- Ghost Developer Docs, “Migrating from Kit” — checked September 2, 2026; supports Ghost’s statement that Kit-managed paid subscriptions have no direct migration path, while subscriber emails can be imported for a new Ghost access arrangement. Limitation: this is a Kit-to-Ghost migration boundary, not a universal rule for payment providers.
- YouTube Help, “Change your subscription privacy settings” — checked September 2, 2026; supports private subscriptions by default and the absence of private subscribers from a channel’s Subscribers List. Limitation: this page addresses subscription visibility, not every YouTube data export or analytics feature.