Commercial connection disclosure: beehiiv is the only option in this comparison that Visionnment may monetize through a partner relationship. Visionnment has not enrolled or installed a tracking link at this fact-check date, so all three vendor links are ordinary, non-affiliate links. Kit and Substack do not compensate Visionnment. Every option is evaluated with the same criteria.
November 17, 2026 source recheck: The Kit USD fee definition and the three linked ownership procedures have been rechecked. Other feature and plan snapshots retain their stated earlier dates. No account, payment or ownership-transfer test was performed.
The short answer
Choose beehiiv when you want a newsletter-first operating system with integrated growth and monetization, subscriber and post exports, and a documented support-assisted publication ownership transfer.
Choose Kit when the newsletter is part of a broader creator business that needs tagging, automations, sequences, forms, digital products, and a verified sending domain. Its subscriber data exports well, but the asset handover is more account-oriented than publication-oriented.
Choose Substack when the priority is low-friction publishing, paid subscriptions, network discovery, and a simple documented publication ownership transfer. The trade-offs include a 10% platform fee on paid subscription revenue and less sender-domain control: a custom web domain does not change the Substack sending address.
This comparison is source-reviewed as of October 22, 2026 for plan/fee facts (other feature research was checked October 20). Visionnment did not create accounts, send campaigns, test inbox placement, earn revenue, migrate paid subscribers, contact support, or transfer ownership on any platform.
Side-by-side comparison
The same dated criteria are applied to all three platforms.
| Criterion | beehiiv | Kit | Substack |
|---|---|---|---|
| Core model | Newsletter, website, growth, automation, monetization, and ad ecosystem | Creator email marketing, automations, forms, products, recommendations, and newsletter site | Publishing, paid subscriptions, network, app, Notes, chat, and community |
| Subscriber export | Basic and Full CSV exports; Full includes additional fields/statistics | CSV with email, status, tags, location, attribution, custom fields, and more | CSV with all or visible columns; current export omits subscriber full names |
| Content portability | Post CSV export includes published, archived, and draft posts | Subscriber and report exports are documented; templates/automations need an explicit migration inventory | Post and list export tools exist; verify archive format and migration parity before closing |
| Ownership handover | Support-assisted publication/workspace transfer with both owners' confirmation | Account owner can change login email; team roles and exports support an account-level handover | Self-service publication ownership transfer requiring both parties to confirm |
| Sending-domain control | Custom sending/domain authentication workflow; DMARC required for custom-domain users | Verified sending domain supports SPF, DKIM, and DMARC alignment | Custom web domain is optional, but newsletters still send from a substack.com address |
| Team access | Owner, Admin, Member, Contributor; plan-based seat limits | Admin and Editor; paid tiers add seats, Pro lists unlimited users | Admin, Contributor, and Byline roles |
| Paid-subscription economics | Vendor advertises 0% platform take on qualifying paid plans; processor fees remain | Kit Commerce in USD: inclusive 3.5% plus $0.30 per transaction; other currencies use their schedule | 10% of subscription revenue plus Stripe processing and billing fees |
| Current entry model | Free up to 2,500 active subscribers; Lite and Pro prices vary by billing and subscriber tier | Free up to 10,000; paid price scales by subscriber count and plan | Free publishing regardless of list size; revenue share begins with paid subscriptions |
| Best fit | Newsletter business optimizing growth, monetization, and formal transfer | Creator business needing automation and commerce around email | Writer/publisher prioritizing simple publishing and network participation |
What “transferable newsletter” actually means
A newsletter is not only an email list. A buyer needs a defensible right and working path to control:
- subscriber records, status, consent, source, and suppression history;
- content archive, drafts, templates, media, and brand assets;
- custom domain, DNS, authentication, and sending identity;
- automations, segments, tags, forms, integrations, webhooks, and API keys;
- Stripe, paid subscriptions, refunds, tax records, ads, recommendations, and payouts;
- staff roles, contractors, operating procedures, and support history;
- analytics definitions and off-platform financial evidence.
The platform should support that process. The sale agreement, privacy obligations, payment provider, domain registrar, and other vendors still determine what can lawfully and operationally transfer.
Use the newsletter valuation framework to evaluate audience quality and economics before choosing a platform based on list size alone.
Export and audience control
beehiiv: strong list and post exports
beehiiv documents Basic and Full subscriber CSV exports on all plans. Both include email, status, and tier; the Full version adds custom fields and statistics. Its post export includes published, archived, and draft content. Download links currently expire after 24 hours, so store the resulting files securely outside the platform.
That is a strong starting point for diligence and backup. A CSV does not reproduce automations, domain state, ad balances, Stripe configuration, website design, or API integrations. Export on a schedule and maintain a separate system map.
Kit: detailed subscriber export, but rebuild the system around it
Kit lets an owner or authorized team member export all or selected subscribers by bulk action. Its September 2026 guide says the CSV contains first name, email, creation time, status, tags, location, attribution data, and custom fields. The export link expires after five days and is also sent to the account owner.
Kit's migration guidance treats forms, landing pages, templates, sequences, and visual automations as separate work that may need recreation. For a sale, inventory each item instead of assuming the subscriber CSV is a full account backup. Export transaction and relevant report data separately where the product supports it.
Substack: useful list export with one notable field limit
Substack currently lets publishers export all subscribers or a selected group as CSV, with all available columns or only visible columns. Its help center says subscriber full names are not currently included in the email-list export.
Substack also provides publication import/export controls and explicitly directs publishers to export posts and their email list before deletion. Before a sale or migration, inspect the exact post archive, media, paywall state, comments/community data, podcast assets, and paid-subscription records rather than relying on an undocumented assumption of parity.
Portability decision: beehiiv publishes the clearest combined subscriber-and-post export path. Kit has a detailed subscriber export but needs a broader automation/content inventory. Substack's list and publication tools are practical, with current export-field and ecosystem limits to document.
Ownership transfer and buyer handover
beehiiv has the most explicit acquisition workflow
beehiiv's formal ownership-transfer guide, rechecked November 17, 2026, covers changing the Owner within a workspace, moving a publication between workspaces with the same owner, and transferring a publication between different owners in a sale.
Support collects confirmation from the relevant owner email addresses. It also checks outstanding paid subscriptions, paid recommendations, Ad Network earnings, and payouts. The destination workspace's plan and active-subscriber tier apply after transfer. Publication-level team roles move, while workspace team members do not and must be invited again.
This is a meaningful advantage for a newsletter intended to be sold. It also creates closing dependencies: both owners, support, monetary balances, destination capacity, billing, and workspace permissions need a scheduled plan.
Kit provides an account-owner change, not a publication sale workflow
Kit's account-owner and team guide, rechecked November 17, 2026, says changing the account owner is done by updating the login email. Paid Creator accounts can add one team member; adding more than one requires Pro. Roles include Admin, with broad access, and Editor, with content access but more limited settings control.
That can support a whole-account handover, but it is less granular than transferring one publication between buyer and seller workspaces. Before changing the owner email, separate unrelated assets, update billing, remove personal integrations, inventory products and automations, rotate credentials, and confirm the buyer controls the new address and recovery methods.
Substack offers direct publication ownership transfer
Substack's publication ownership-transfer procedure, updated March 2026 and rechecked November 17, starts in the publication's Danger Zone. The seller sends a request to the buyer's email; both parties confirm; the recipient's acceptance link expires after six hours. After completion, the new owner has administrative control over settings, subscribers, and billing.
That is a clear closing primitive. It does not automatically settle domain registration, Stripe identity and tax obligations, rights to content, contractor agreements, social accounts, or external analytics.
Ownership decision: beehiiv has the most detailed support-assisted transaction path. Substack has the simplest direct publication-transfer control. Kit can transfer an account through an owner-email change but needs more pre-closing separation when the seller's account contains other business assets.
Deliverability controls
No platform can guarantee inbox placement. Mailbox providers consider authentication, sender and IP reputation, engagement, complaints, bounces, content, volume changes, and recipient behavior.
beehiiv
beehiiv supports custom domains and describes a Smart Warming process of roughly four to eight weeks. It requires DMARC for custom-domain users and reserves dedicated IP options for Enterprise. During ownership or domain changes, preserve sending history, authentication, suppression data, volume, and complaint monitoring.
Kit
Kit's verified sending domain workflow supports SPF, DKIM, and DMARC alignment under the operator's domain. The vendor warns that changing sending identity can cause mailbox providers to recalculate reputation and that open rates may temporarily change. Pro currently includes deliverability reporting.
Substack
Substack makes the sender identity simpler but less portable. Its custom-domain documentation says a custom domain applies to the publication website; newsletters still send from a substack.com address. A buyer should not assume the publication's web domain carries an independent email-sending reputation to another provider.
Deliverability decision: beehiiv and Kit expose more custom sender-domain control. Substack reduces setup but concentrates sending identity in its platform. In every case, audit consent, authentication, complaints, bounces, engagement, and send cadence before a buyer changes ownership or volume.
Monetization and fees
beehiiv: integrated revenue products with a fixed platform subscription
beehiiv combines paid subscriptions, an ad network, paid recommendations, digital products, referrals, and other growth tools on eligible plans. It advertises a 0% platform take on paid subscriptions, excluding payment-processor fees. Revenue availability and results depend on niche, geography, engagement, eligibility, demand, and account health.
This can make the platform attractive to a newsletter business, but it also creates platform concentration. Reconcile each revenue stream to payout and payment records and distinguish recurring subscriber revenue from opportunistic ads or recommendations.
Kit: creator commerce and automation with a smaller transaction fee
Kit supports paid newsletters, products, subscriptions, tips, recommendations, ads, and automation. Its Commerce fee FAQ, checked November 4, 2026, states an inclusive 3.5% plus $0.30 per USD transaction. Do not add a second processing percentage to that combined fee; other currencies require their applicable schedule. Plan cost also scales by subscriber count and features.
Kit can be attractive when the newsletter feeds courses, products, launches, and sequences. The buyer must determine which products, payment accounts, files, automations, and customer obligations are included.
Substack: no subscription fee, but 10% of paid revenue
Substack is free to publish regardless of subscriber count. When paid subscriptions are enabled, its September 2026 fee guide says Substack keeps 10% of subscription revenue. For a US Stripe account it also lists 2.9% plus $0.30 card processing and a 0.7% recurring billing fee; local methods and countries differ. A custom domain costs a one-time $50.
That model has low fixed cost and rising variable cost. At meaningful paid revenue, compare the 10% share against beehiiv or Kit subscription and transaction economics. Include the value of Substack's network and the cost of replacing its discovery/community features—not only fees.
Current pricing without false precision
beehiiv now lists Free, Lite, and Pro
The current pricing page and official October 1 announcement now agree on Free, Lite, Pro, and Enterprise for new customers. At the 1,000-subscriber setting with yearly billing selected on October 22, Lite showed $49 per month and Pro $95 per month; monthly billing and larger lists differ. The former Launch, Scale, and Max customer plans map to Free, Lite, and Pro, with existing customers moving at their first renewal on or after November 1.
Free supports up to 2,500 subscribers, Lite up to 100,000, and Pro up to 250,000. Retain a live price quote for the buyer's actual active-subscriber count, billing interval, seats and publication count with the acquisition model.
Kit scales by subscriber count
Kit's current clean pricing page showed Free at $0 up to 10,000 subscribers, Creator at $33 per month effective on annual billing for 1,000 subscribers, and Pro at a $66 standard monthly figure with a temporary $50 first-year offer and $593 first-year annual bill. The page says the discount applies only to the first year. Verify renewal and the price at the real list size.
Substack scales with paid revenue
Substack's core platform has no fixed publishing subscription. The economic meter is paid revenue: 10% to Substack plus payment fees. That can be efficient for a free or early publication and expensive for a mature paid newsletter.
Team access and control
beehiiv distinguishes Owner, Admin, Member, and Contributor. Admins can access sensitive subscriber, wallet, and settings areas; Members cannot change billing/domains or export data; Contributors focus on content and cannot publish. Seat limits depend on the active plan.
Kit offers Admin and Editor roles. The current pricing page lists one user on Free, two on Creator, and unlimited users on Pro. Confirm whether an Admin's broad access is appropriate for contractors and whether sensitive exports trigger owner notification.
Substack provides Admin, Contributor, and Byline roles. Admins have full settings access; Contributors can draft, edit, and publish but cannot see some growth/revenue data or settings; Byline access can attribute authorship without dashboard access.
For all three, use named accounts and least privilege. Before closing, export the role list, remove former contractors, replace recovery methods, rotate API and integration credentials, and record buyer acceptance.
Compare inclusive transaction costs with renewal pricing
Use the actual subscriber tier, billing interval and renewal quotation for each platform. On November 4, 2026, beehiiv's pricing selector displays Lite at $49 and Pro at $95 per month for the shown 1,000-subscriber annual-billing setting. Kit's selector shows Creator at $33 effective monthly on annual billing, plus a temporary Pro introductory offer. A first-year discount is not the continuing price.
For Kit Commerce in USD, its current fee FAQ states an inclusive 3.5% plus $0.30 transaction charge. Do not add a second standard card-processing percentage to that stated combined fee. Other currencies and arrangements need their applicable terms.
For a hypothetical $10 USD payment, that stated transaction fee is $0.65, leaving $9.35 before platform subscription cost, refunds, taxes and other expenses. At 100 such payments it is $65. The fixed fee matters more on small payments, while a platform subscription needs to be allocated separately. Use the same price, transaction count, currency and included service when comparing platforms.
Keep the supported ownership paths above separate from the fee arithmetic. A cheaper payment model does not resolve consent, external accounts, content rights or buyer-controlled recovery.
A safer newsletter transfer plan
Before signing
- Reconcile active, free, paid, gifted, suppressed, bounced, and unsubscribed records.
- Trace major acquisition cohorts and confirm consent evidence.
- Export subscribers, content, transactions, payouts, reports, and current roles.
- Inventory domain/DNS, sending authentication, Stripe, taxes, apps, webhooks, API keys, ads, recommendations, products, and automations.
- Confirm which platform-native balances, subscriptions, and relationships transfer.
At closing
Use the platform's supported ownership path. Do not exchange a shared password as the transfer. Coordinate payment release with accepted ownership, buyer-controlled recovery, documented monetary balances, and a test of publishing, sending, subscription checkout, refunds, and payouts.
After closing
Avoid a simultaneous domain, sender identity, platform, content strategy, and volume change. Verify DNS/authentication, warm or stabilize sending as needed, monitor bounces and complaints, reinvite staff under least privilege, and store a fresh encrypted export.
Use the broader website handover checklist for connected systems; confirm recovery, MFA, and token access separately with each account owner.
Which should you choose?
Choose beehiiv when:
- the newsletter itself is the primary business asset;
- native growth, ads, recommendations, and paid subscriptions matter;
- post/list exports and a formal sale workflow are priorities;
- a fixed/tiered platform bill is preferable to a 10% revenue share;
- the buyer can govern platform concentration.
Choose Kit when:
- email drives a broader creator business and product funnel;
- tagging, sequences, automations, and commerce integrations are central;
- verified sending-domain control matters;
- an account-level handover is acceptable;
- the team will document and rebuild any non-exportable workflow.
Choose Substack when:
- speed and simplicity of publishing matter most;
- the network, app, Notes, and paid-community model are strategically valuable;
- no fixed platform subscription is attractive at the current stage;
- the team accepts the 10% paid-revenue share;
- a
substack.comsending identity and platform dependence fit the risk model.
Frequently asked questions
Which platform is easiest to sell with a newsletter?
beehiiv documents the most detailed support-assisted publication/workspace transfer. Substack offers a direct publication ownership control. Kit can change account ownership by login email but requires careful separation if the account contains other assets.
Which has the lowest paid-newsletter fee?
beehiiv advertises a 0% platform take on qualifying paid plans; Kit Commerce states an inclusive 3.5% plus $0.30 per USD transaction; Substack charges a 10% platform fee plus processing. Do not add another standard processing percentage to Kit's stated combined USD fee. Fixed plan prices, list size, features, network value, and payment costs must be included.
Can subscribers be exported from all three?
Yes. The fields and surrounding assets differ. beehiiv offers Basic/Full subscriber exports, Kit includes tags and custom fields, and Substack offers all/visible-column exports but currently omits subscriber full names.
Does a custom domain make the audience portable?
It helps brand and web continuity but is not enough. Export consent-aware subscriber data, preserve content and economics, document authentication, and use supported ownership transfer. On Substack, the custom web domain does not change the sending address.
Verdict
For a newsletter built explicitly as a transferable asset, beehiiv has the strongest documented combination of export, monetization, roles, and formal ownership transfer. Kit is the better fit when email is the automation layer for a wider creator business. Substack is the simplest publishing-and-network route, with a clear transfer control but materially different revenue economics and sender-domain dependence.
The platform does not make the asset transferable by itself. A clean sale requires consent-aware audience evidence, a custom domain strategy, off-platform exports, reconciled revenue, role discipline, supported ownership change, and an acceptance-tested handover.

