The short answer
  • Substack: for simplicity and a reader network.
  • Ghost: for ownership and your own site.
  • Kit: for product-led creators.
  • Sailthru or Iterable: for media companies with data teams.
  • A custom stack: for full control and custom workflows.
  • Staying put: often right when a plan upgrade or a tool built around Beehiiv solves the problem.

Why publishers look beyond Beehiiv

Beehiiv suits growth-focused newsletters well. Publishers look elsewhere when the business outgrows the shape of the platform, not usually because something broke.

  • Cost at scale. Plan pricing grows with your list. At some sizes, a different model or owning the stack costs less.
  • Ownership. Some publishers want their site, data and sending fully under their control.
  • Enterprise needs. Large media companies may need deep personalization and data integrations.
  • Custom workflows. Production pipelines and internal tools that go beyond what any platform editor offers.

First, check whether a plan change solves it

Several reasons people give for leaving are plan limits, not platform limits. Price the upgrade before you price the move.

At the time of review, creating posts through the API needs the Pro or Enterprise plan, and webhooks need a paid plan. Removing Beehiiv branding also sits on Pro and above. Dedicated IPs are Enterprise only.

The number of publications and team seats scales with the plan too. If you run several titles, check those limits before deciding Beehiiv cannot handle them.

Paid subscriptions are the other common worry. Beehiiv takes no cut of paid subscription or digital product revenue. If revenue share is your concern, it is not Beehiiv's model.

Start with how you make money

Ad-led newsletters give up the most by leaving. Beehiiv's ad network and paid recommendations are built in, and replacing that income takes direct sales or another network.

Paid-led newsletters should compare pricing models at the size they expect in two years: a plan, a revenue share or a per-sale fee.

Product-led creators may be better served by a tool that treats sequences and commerce as the core.

B2B and multi-title publishers care about one reader record across titles and data they can sync to a CRM. That points to an API-first setup, on Beehiiv or off it.

The alternatives

Substack

Who it suits. Writers who value simplicity and discovery through the Substack network over growth tools and design control.

How it charges. Free to start, then a percentage of paid subscription revenue. Cheap while small, expensive at scale.

What you gain. Recommendations, Notes and the Substack app, plus payments through your own connected Stripe account. Substack also runs a curated native sponsorship program.

What you give up. Design control, a general-purpose public API and the built-in ad network. Automation and data syncs become workarounds.

Beehiiv vs Substack, compared

Ghost

Who it suits. Publishers who want an open-source site and memberships they fully own.

How it charges. Ghost(Pro) plans scale with member count, with no percentage of revenue. You can also self-host and pay for your own server and bulk email provider.

What you gain. Full theme and site control, payments through your own Stripe account and an Admin API with webhooks. Ghost 6 added social web following through ActivityPub and native analytics.

What you give up. Beehiiv's growth and ad tools. On Ghost(Pro), the Admin API and custom themes start on the Publisher plan. Self-hosting means owning updates and backups, and sending through Mailgun, the only bulk email provider Ghost supports.

Moving from Beehiiv. Ghost has a built-in Beehiiv migrator for posts and members. Paid members are harder. Ghost's documentation says the Stripe account tied to a Beehiiv publication cannot be connected to another platform, so customer data has to be migrated between Stripe accounts.

Beehiiv vs Ghost, compared

Kit

Who it suits. Creators whose business runs on products, sequences and automations.

How it charges. Plans by subscriber count, plus a per-sale fee on Kit Commerce that includes card processing.

What you gain. Visual automations, tagging and built-in commerce. Creator Network recommendations, plus paid recommendations and Newsletter Sponsorships on paid plans at the time of review.

What you give up. Newsletter-first publishing. Kit thinks in broadcasts and sequences more than issues, websites and archives.

Moving from Beehiiv. Subscribers come across through Kit's Beehiiv importer or a CSV. For paid members, Kit's Beehiiv guide says there is no convenient way to move subscriptions with payment details, so plan for paying readers to re-subscribe.

Beehiiv vs Kit, compared

Sailthru or Iterable

Who it suits. Media companies sending at scale, with personalization needs and in-house data teams.

How it charges. Enterprise contracts rather than self-serve plans.

What you gain. Deep personalization and data integration. Sailthru is now part of Zeta Global. Iterable builds automated flows as Journeys in its Studio.

What you give up. Speed and simplicity. Both need technical people and specialist template skills to run well, and neither is a newsletter website.

Sailthru help

A custom stack (for example Resend)

Who it suits. Publishers who want to own sending, templates, data and production, with software built around them.

How it charges. You pay a sending service plus the software you build and maintain. Resend's marketing plans, for example, scale by contacts rather than emails sent.

What you gain. Full control of the pipeline, reader data and templates, with every delivery and engagement event available through webhooks.

What you give up. Everything Beehiiv bundles. Signup forms, archive, website, referrals and paywall do not exist until someone builds them. Deliverability is yours.

Newsletter infrastructure on Resend

TopicSubstackGhostKitCustom stack
How it chargesPercentage of paid subscription revenueGhost(Pro) plans by member count, or self-hostPlans by subscriber count, plus a per-sale Commerce feeSending service plus build and upkeep
OwnershipLowHighMediumFull
APINo general-purpose public APIAdmin API (Publisher plan and up on Ghost(Pro))Yes (every plan)Yours
Built-in adsCurated native sponsorship programNoneNewsletter Sponsorships (paid plans)None
Beehiiv paid membersCheck the current import processStripe data migration between accountsPlan for re-subscribesPlan for a Stripe data migration
Setup effortLowMediumLowHigh (built for you)

How they compare on what matters

Growth

Beehiiv bundles referrals, recommendations and paid recommendations. Substack offers its network and app instead. Kit has Creator Network recommendations. Ghost relies on your site, search and the social web. On a custom stack, every growth tool is something you build or buy.

Data and portability

Beehiiv's full subscriber export includes custom fields and statistics, and posts export as a CSV. Before you move, check that the destination can store every field you rely on. Engagement history rarely survives a move in usable form.

Deliverability control

On Beehiiv you can already send from your own domain on paid plans. Leaving means re-authenticating that domain on the new sender and warming it up. Substack manages sending itself. A custom stack gives you full control and full responsibility.

Teams and multiple titles

Ghost(Pro) scales staff users and newsletters by plan. Substack offers Admin, Contributor and Byline roles per publication. Kit scales team members by plan. Enterprise platforms and custom stacks can model one reader across titles, which is often the deciding factor for multi-title publishers.

Which one fits

Choose Substack if

  • You want to write, not configure
  • Discovery matters more than margin
  • You do not need an API

Choose Ghost if

  • You want your own site and members
  • Paid memberships drive revenue
  • You can handle more setup

Choose Kit if

  • Products and sequences drive revenue
  • You want commerce built into email
  • The newsletter supports a creator business

Choose a custom stack if

  • Your workflow fits no platform editor
  • Reader data is central to revenue
  • Someone will build and maintain it

When to stay on Beehiiv

Stay if a plan upgrade unlocks what you need. It is almost always cheaper than a migration.

Stay if the ad network or paid recommendations are a real line of revenue. Replacing them takes time.

Stay if the gap is production or sponsor operations. Automated drafts through the API, sponsor workflows and CRM syncs can all be built around Beehiiv while your team keeps using it.

A worked example

This publisher is fictional. It shows how the trade-offs play out, not a real result.

A small team runs a daily B2B newsletter on a mid-tier Beehiiv plan. Revenue is direct-sold sponsorships, with some ad network income. They want issues drafted automatically and reader job titles synced to their CRM.

First question: is this a plan limit? Creating posts through the API needs a higher plan. Pricing the upgrade against a migration is the first job.

Second question: what would they lose? The ad network income and the built-in website. Both need replacing if they leave.

Third question: does reader data justify owning the stack? If job title and company are what sponsors pay for, and they plan more titles, a custom stack starts to make sense.

The outcome depends on the plan. With one title, they upgrade and build the draft pipeline and CRM sync around Beehiiv. With three titles planned and a team to maintain software, they move to their own stack in stages.

A migration checklist

If moving is right, work through these before the first send on the new platform.

  • Run Beehiiv's full subscriber export, with custom fields and statistics, and export all posts. Download links expire, so save them right away.
  • Map every custom field and segment to the new platform.
  • Plan paid members as their own project, including Stripe data migration and who cancels billing in the old account.
  • Redirect every archive URL, including /p/ post paths, to its new home.
  • Settle open sponsor commitments and ad network obligations around the cutover.
  • Rebuild welcome emails, referral rewards and automations and test them.
  • Authenticate the sending domain on the new sender, then warm up with your most engaged readers.
  • Point signup forms, embeds and partner links to the new platform.
  • Tell readers, especially paying ones, what is changing.

Our migration guide walks through each step.

What most comparisons miss

Check what your plan already includes

Some features publishers leave for, such as API post creation, are available on higher Beehiiv plans. Compare the cost of upgrading with the cost of moving.

Paid members are tied to Beehiiv's Stripe setup

Beehiiv requires a Stripe account created through its own setup, and Ghost's documentation says that account cannot be connected to another platform. Budget time for moving customer data between Stripe accounts.

You lose bundled income, not just features

Ad network and paid recommendation earnings stop when you leave. Count them as a cost of moving.

Ownership is a spectrum

Moving to Ghost gives you more ownership. Moving to your own stack on a sending service gives you full ownership, and full responsibility.

Archives carry search traffic

A Beehiiv archive may rank in search. Redirect every old URL to its new home so you keep that traffic.

How we help

We build on Beehiiv through its API, and we have moved a B2B newsletter off Beehiiv onto its own Resend-based infrastructure, with its full archive on its own domain. So we can give you an honest answer on building around Beehiiv versus leaving it. See our Beehiiv work and platform migrations, or read how to choose a newsletter platform.

Not sure yet? Start with a process audit.

Platforms change their features and pricing often. Check each platform's current plans before you decide.