Decentralised News · 2027 planning series · Sources reviewed 22 November 2026
What Matters
A creator can export thousands of contact rows and still lack a working route to the audience. Portability depends on permission, suppression records, usable identifiers, domain control, delivery configuration and paid-access continuity. DN’s Audience Portability Record measures the part of an email cohort that survives those checks while keeping technical access, marketing rights and billing obligations separate.
DN Evidence Block
2027 planning edition. Sources reviewed: 22 November 2026. The evidence consists of current Ghost and Mailchimp export/import documentation, Stripe migration guidance, Gmail sender requirements and UK ICO direct-marketing guidance. DN has not migrated a live audience or measured delivery rates for this article. The creator and counts below are an explicitly synthetic scenario. Jurisdiction-specific marketing rules require separate review.
The creator has the file. The audience has not moved yet.
Illustrative scenario: a small publication loses access to its main publishing account. Its editor has a recent backup containing 10,000 unique email records. At first, the backup appears to solve the problem. Import the file into a new service, publish an update and carry on.
A closer review changes the picture. The cohort includes 1,500 suppressed or opted-out contacts. Another 2,500 lack sufficient permission evidence for the proposed mailing or belong to a different purpose. That leaves 6,000 records eligible for the intended use under the editor’s reviewed rules. Of those, 5,400 have a verified destination mapping. The other 600 need repair or investigation.
The resulting 54% is a share of the export cohort, not a predicted email-delivery rate. It does not prove that 5,400 people will receive or read the next edition. Domain control is documented but has not been rehearsed, and the relationship between paid memberships and the new billing setup is unresolved. The backup is valuable, but the business still has work to do before service can continue.
This is the portability problem worth solving. A creator’s relationship with readers is expressed through several systems. Downloading one system’s records preserves evidence from that system. Continuity requires a documented route from those records to the promises the publication intends to fulfil.
The Signal: followers, contacts, subscribers and customers are different assets
| Record | What it may establish | What must be checked separately |
|---|---|---|
| Social follower | A relationship inside the original platform | Exportable identity, contact route and permission for a new channel |
| Email contact | An address stored in a system | Purpose, permission, opt-out status and current deliverability |
| Newsletter subscriber | A subscription state for a particular publication or list | Which lists, preferences and suppression events survive migration |
| Paid member | An entitlement or customer relationship | Billing authority, payment method, access period and cancellation state |
| Reachable reader | A delivery or access outcome observed at a stated time | Whether the same outcome continues after a system change |
Do not add these populations together. A single reader can follow on three platforms, hold two email subscriptions and pay for one membership. Without a lawful and reliable identity match, the headline sum overstates distinct people. Conversely, a customer who opted out of marketing may still have a valid paid-access relationship. Removing them from a promotional send should not silently cancel the service they bought.
1. Audit what the export actually contains
The first question is concrete: which objects and fields are in the downloadable package? Ghost’s export documentation describes separate content/settings, member, analytics, theme and routing exports. Member data includes subscription status and other fields; archived or deleted custom fields are excluded. Media handling differs between Ghost(Pro) and self-hosted sites. Those details make a content backup and a member backup distinct components.
Mailchimp’s contact-export guidance likewise distinguishes contact types and explains that email report data is not part of the contact export. An export can contain subscribed, unsubscribed, non-subscribed and cleaned records. The existence of a row therefore cannot be treated as an instruction to send a newsletter.
For your own publication, write a short export manifest: source account, export date, included objects, exclusions, unique-record count and the person who can restore it. A saved filename without those details becomes difficult to interpret months later. A folder containing several exports also needs a clear current version so an older file cannot overwrite a newer opt-out.
Keep the backup in an authorised location with access appropriate to the personal information it contains. An ordinary task brief, public repository or chatbot prompt is not a substitute for the publication’s controlled record store. DN’s calculator uses aggregate counts precisely because the decision can be explored without uploading reader addresses.
2. Carry the right to stop receiving messages
Portability must preserve readers’ choices as carefully as their addresses. Mailchimp’s contact definitions distinguish a subscriber from an unsubscribed person, a non-subscriber and a cleaned address. Those categories should retain their meaning when fields are mapped into a new destination.
The UK ICO recommends suppression records to prevent people who objected or opted out from being contacted again by mistake. It also emphasises keeping only the information needed for that purpose. This is UK guidance, not a universal legal summary; it provides a concrete reason an opt-out record can be essential operational data.
In the synthetic cohort, the 1,500 suppressed contacts stay outside the mailing segment. They are not counted as lost because of a faulty migration. Their exclusion is part of preserving the relationship correctly. The 2,500 unresolved records form another category: further evidence may clarify their permitted use, but the tool does not convert uncertainty into approval.
Keep these groups mutually exclusive. If a contact is both opted out and missing an old signup timestamp, count the record in the suppression group rather than deducting it twice. Document the classification rule. The result becomes reproducible and avoids a misleadingly low or even negative eligible count.
3. Map meaning, not just column names
An import can succeed while changing what a field means. A boolean labelled “subscribed” might apply to one newsletter in the source and to several newsletters in the destination. A membership label might represent a historical purchase rather than a current entitlement. An empty field might be treated as a default rather than as unknown.
Ghost’s import documentation illustrates the need for this check. Its email-subscription field behaves differently for new and existing members, and the handling of multiple newsletters depends on configuration. Read the current mapping rules rather than relying on what a similarly named field did in another service.
Create a small authorised test set with known states: an eligible subscriber, an opted-out contact, a member of one newsletter only, a duplicate, a paid member and a cancelled paid member. Synthetic addresses or controlled test accounts are preferable where possible. Verify the resulting states without sending marketing to real readers merely to prove that an import button works.
For each test, retain the source value, expected destination value and observed result. A successful row count answers a volume question. Correct preference and entitlement mapping answer the business question. The destination-ready count in DN’s tool should represent records whose relevant mapping has been reviewed, not every row the importer accepted.
4. Separate access rights from continuing charges
A paid audience contains two linked responsibilities: provide the promised access and handle payment correctly. A member record can move without a usable recurring-payment arrangement. Conversely, payment processing can continue while a reader is locked out of the new site.
Ghost’s member-management guidance states that bulk member deletion does not affect active Stripe subscriptions. That specific behaviour is a useful reminder that a publication database and the payment system are separate. It is not an instruction to delete either record during a migration.
Stripe’s migration guidance identifies supported customer and payment-method data and distinguishes managed payment-data migration from customer-only transfers. A normal audience CSV should therefore not be assumed to contain everything needed to transfer billing. The exact migration depends on the source, destination, payment method and account arrangement.
Use a separate paid-access register: customer identifier, current entitlement, paid-through date, billing owner, cancellation state, destination match and unresolved action. Do not place full card details or payment credentials in that register. The relevant processor’s authorised migration route owns sensitive payment data.
Consider a second synthetic example: all 400 paid-member emails map correctly, but the billing arrangement remains unknown. Calling that “100% revenue portability” would be premature. The accurate report is that member identity mapping is complete while billing continuity still needs evidence. No arbitrary percentage should average away that unresolved dependency.
5. Retain a channel you can actually operate
An owned domain can give readers a stable place to find the publication across hosting changes, provided the responsible operator can access and manage it. Record the registrar account owner, renewal responsibility, authorised recovery route and DNS administrator. Keep credentials in the appropriate secret-management system rather than inside the audience export.
Then test the specific continuity action you expect to perform. Can the authorised operator change the destination for the publication? Can they verify the change? Can they restore the previous configuration if the new service fails? Written instructions support that process; a bounded rehearsal establishes something more concrete.
Email has another dependency. Google’s current sender guidelines set authentication requirements for messages reaching personal Gmail accounts, with additional requirements for bulk senders. They also describe unsubscribe requirements. Moving the list does not automatically configure the sending domain or establish that messages satisfy the destination’s rules.
Keep delivery evidence separate from audience counts. A test delivered to a controlled address demonstrates that specific path under those conditions. It does not establish delivery to every subscriber or future inbox placement. The first real campaign, when separately authorised and properly targeted, should be reviewed for errors, bounces, complaints and unintended audience inclusion.
6. Preserve the publication that people subscribed to
An audience export without its promised content can leave paid members with a functioning login and an empty archive. Retain the content, media, access rules, important URLs, redirect mapping and subscription descriptions needed to reconstruct the service.
Prioritise the reader journey. Can an existing member find the latest edition? Can a link in an old email reach the intended article? Can a cancelled member see the access period they actually purchased? Can a new subscriber understand which publication they are joining? These tests make a restoration review more useful than simply counting restored posts.
For a research publication, this also includes downloadable assets and article tools. A restored article that links to a missing calculator or inaccessible report may no longer deliver the value that attracted the subscriber. DN’s controlled publishing workflow addresses evidence, editorial approval and maintenance. Portability adds a continuity question to that production system: can the promised research still be delivered after the original service is unavailable?
DN Audience Portability Record
Begin with one deduplicated email cohort. Enter the suppressed group, the separate unresolved-permission group and the eligible records whose destination mapping has been verified. The calculator shows the eligible total, remaining mapping gap and mapped share of the original cohort. Domain, restoration and billing evidence stay as independent states.
DN Audience Portability Record
Reconcile an aggregate, deduplicated email cohort. Keep opted-out contacts and unresolved permission separate. This tool sends no messages and stores no contact addresses.
This instrument runs locally in your browser. It does not connect to accounts, fetch evidence or submit instructions. Use aggregate values and non-sensitive references. Downloaded records contain your inputs.
Machine-readable illustrative record
An illustrative record of the example assumptions, not an observed transaction or provider test. A null calculation timestamp identifies this static example.
{
"schema_version": "1.0.0",
"article_id": "N006",
"evidence_basis": "illustrative",
"source_review_date": "2026-11-22",
"computed_at": null,
"inputs": {
"total": "10000",
"suppressed": "1500",
"unresolved": "2500",
"ready": "5400",
"domain": "documented",
"backup": "demonstrated",
"billing": "unknown"
},
"status": "Audience record reconciled; evidence remains self-reported",
"outputs": {
"total": 10000,
"suppressed": 1500,
"unresolved": 2500,
"eligible": 6000,
"mapping_gap": 600,
"destination_mapped": 5400,
"ready_fraction": 54,
"domain_evidence": "documented",
"restoration_evidence": "demonstrated",
"billing_evidence": "unknown",
"evidence_verified": false
}
}For the illustrative 10,000-record publication, eligible records equal 10,000 minus 1,500 minus 2,500, or 6,000. With 5,400 mapped, the remaining gap is 600. The mapped eligible segment represents 54% of the export cohort. The result does not certify marketing permission, verify a live delivery or establish a paid subscription’s legal transferability.
7. Run a quiet exit rehearsal before a forced exit
A useful rehearsal does not require abandoning the current platform. Freeze a recent export, choose a controlled destination and test a small representative set of record types. Disable automatic welcome messages, billing actions and live sends where the destination permits it. Confirm the test boundary before importing.
Record what another authorised operator can complete without the original builder’s private knowledge. Missing access, undocumented defaults and uncertain billing ownership are findings. They are more useful when discovered during a rehearsal than during an account suspension or service interruption.
After the test, repair the export procedure and repeat the failed portion. A new paragraph in the runbook changes the documentation state; it does not by itself demonstrate a working restoration. Retain the date, the tested version and the evidence so a later platform change can trigger a targeted retest.
For a commercial publication, attach an estimated disruption cost to the unresolved service, using transparent assumptions. For example, distinguish expected support hours, delayed editions and potentially affected paid access. Do not multiply the entire follower count by an invented customer value. That exaggerates the exposure while hiding the smaller population that actually needs immediate attention.
DN Alpha Thesis
A portable audience is an operational capability: preserve readers’ choices, reproduce their access and maintain an authorised route to deliver the publication. Contact exports are necessary evidence, but continuity depends on the relationships around them. The durable creator business knows which parts can move, which require a provider’s help and which remain untested before a forced move makes those distinctions urgent.
Methodology and limitations
DN constructed this record from documented export, import, suppression, billing and delivery mechanics. Its arithmetic is intentionally simple: eligible records equal the unique cohort less mutually exclusive suppressed and unresolved groups; the mapping gap equals eligible records less verified destination mappings. A zero-sized cohort produces no percentage.
The calculation uses self-entered classifications. It does not inspect permission records, resolve identity, migrate data, send email, transfer payments or test domain access. Documented and demonstrated evidence remain distinct. The 2027 edition describes a planning method using sources reviewed in November 2026, not measured 2027 platform performance.
Legal requirements vary with jurisdiction, sender, recipient, purpose and relationship. The cited ICO material is UK-specific. A lawful transfer of a business, a processor change and an attempt to market a different product can raise different questions. Seek context-specific advice where the proposed use is uncertain. Keep sensitive reader information out of the aggregate public worksheet.
Frequently asked questions
Does exporting an email list mean I own the audience?
It gives you a copy of specified records. Readers retain their rights and preferences, and the export does not establish a universal right to market to every address or move every paid relationship.
Should unsubscribed contacts be deleted from a migration?
Preserve the necessary suppression information through an authorised process so those people are not accidentally resubscribed. Apply the relevant retention and deletion rules; the worksheet does not decide them.
Can I turn social followers into email subscribers?
A follow on one platform does not by itself establish permission for a different channel. Use a permitted signup or other valid process rather than inferring email marketing rights from a public profile.
Why is the mapped share not a delivery rate?
It counts records whose destination mapping the operator reports as verified. Actual email delivery, inbox placement and reader engagement are different observations.
Will paid subscriptions follow a CSV import?
Do not assume that. Member access, payment credentials, recurring billing and cancellation states must be checked against the actual source and destination arrangements.
Does the DN tool contact subscribers or upload my list?
No. It uses aggregate counts and selected evidence states. It requires no subscriber addresses and makes no messaging or migration request.
Research and disclosure: DN can document one publication’s export scope, record mapping and continuity gaps under an agreed review. A review does not guarantee delivery, legal compliance or uninterrupted revenue. No publishing or email provider paid for inclusion in this article.
Primary sources and review record
- Ghost: Exporting content and data. Export object types, subscription status, media handling and exclusions for archived/deleted custom fields. Reviewed 2026-11-22.
- Ghost: Import members. Email preference import behaviour differs for new/existing members and multi-newsletter configurations. Reviewed 2026-11-22.
- Ghost: Member management. Bulk deletion of member records does not affect active Stripe subscriptions, illustrating separate membership and billing systems. Reviewed 2026-11-22.
- Mailchimp: View or export contacts. Exports contain different contact-status groups; email report data is separate. Reviewed 2026-11-22.
- Mailchimp: View unsubscribed contacts. Definitions distinguish subscribed, unsubscribed, non-subscribed and cleaned contacts. Reviewed 2026-11-22.
- ICO: Respect peoples preferences. UK guidance supports retaining minimum necessary suppression records to respect objections; jurisdiction-specific scope. Reviewed 2026-11-22.
- Stripe: Data that can be imported to a Stripe account. Managed payment-data migration and customer-only data movement have distinct routes and supported types. Reviewed 2026-11-22.
- Google: Email sender guidelines. Authentication and unsubscribe requirements for personal Gmail deliveries; different requirements for bulk senders. Reviewed 2026-11-22.