Migration guide
Ghost → beehiiv
Ghost gives you full editorial ownership and an open-source code base; beehiiv gives you the newsletter-growth toolkit (referrals, ad network, recommendations) out of the box. The migration is a deliberate trade: less self-managed CMS infrastructure for more built-in monetization and growth surfaces. You'd make this move when you started on Ghost for the publisher-owned story but the DIY growth path (run your own referrals, build your own audience, sell your own ads) has stopped feeling like a feature.
Published · By the TierGauge editorial team
Moving to
beehiiv- Starting price
- Free
- Free plan
- Yes
- Plans
- 4
- Category
- Email marketing
When this migration makes sense
- You publish primarily as a newsletter rather than as a website with a newsletter sidebar; beehiiv is newsletter-first, Ghost is web-first.
- You'd use a built-in referral program and recommendations network to grow paid subscribers; on Ghost you'd build or integrate this yourself.
- You want to monetize via an ad network or sponsorship storefront in addition to (or instead of) paid subscriptions; Ghost has neither natively.
- You're paying Ghost(Pro) Publisher or Business and the per-active-member ratchet is now your dominant cost line.
- You don't need a full CMS, custom themes, or a website-shaped product around the newsletter.
When it doesn't
- You value the open-source code base and the option to self-host on your own infrastructure if you ever leave the managed product. beehiiv is closed-source SaaS.
- You publish a content-heavy website with the newsletter as a side channel; Ghost's CMS, themes, and member-portal pages are doing real work that beehiiv doesn't replicate.
- You depend on Ghost's theme ecosystem (Casper, custom themes, tier-gated content) for branded design at scale.
- You operate at high paid-subscription volume where Ghost's flat-tier model plus your direct Stripe relationship is meaningfully cheaper than beehiiv's subscriber-tier pricing. Run the math at your specific tier before assuming the move saves money.
- You rely on Ghost's Members API to sync paid status into a separate app; rebuilding against beehiiv's webhooks/API is a real engineering cost.
What you lose by leaving Ghost
- Open-source code ownership and the self-host option.
- Ghost's CMS (custom themes, structured pages, web archive at your URL, member-portal page).
- Direct Stripe relationship: revenue lands in your Stripe; on beehiiv paid-subscription revenue routes through beehiiv-managed Stripe Connect.
- The 8,000+ integration ecosystem Ghost(Pro) exposes via Zapier and webhooks.
- Staff seats and theme-driven editorial design flexibility on Publisher and above.
What you gain with beehiiv
- Built-in referral program (the standout beehiiv growth feature; on Ghost this is a separate paid integration).
- Ad network and sponsorship storefront for newsletter monetization paths Ghost doesn't natively offer.
- Recommendations network for cross-promotion with other newsletters; structural growth lever Ghost doesn't have.
- A newsletter-first product: less mental overhead than maintaining a CMS, themes, member portal, and growth integrations as separate moving parts.
- Lower operational surface area: one product to learn instead of CMS plus integration plus theme plus member-system.
Plan mapping at the entry paid tier
The lowest non-free, non-custom tier on each side. Use this for the "if I'm on $X with Ghost, what's the equivalent on beehiiv?" gut check.
| Limit | Ghost (Starter) | beehiiv (Scale) |
|---|---|---|
| Contacts | 1,000 members | 100,000 subscribers |
| Emails / month | Unlimited | Unlimited |
| Team seats | 1 | 3 |
| Campaigns | · | 3 publications |
Step-by-step migration
- 01
Export your list from Ghost
Pull a fresh CSV of every active subscriber. Capture the fields you actually use downstream: email is required, name is standard, signup date and tier (free/paid) are useful when Ghost provides them.
- 02
Provision beehiiv
Sign up, set sender identity, and verify your sending domain (DKIM, SPF, DMARC). Do this before importing the list; sending from an unverified domain is the single fastest way to land in spam at the moment of cutover.
- 03
Import the list and map fields
Upload the CSV. Map email + name + any custom fields. Decide whether to import as one list or split into segments/tags. Ghost-style organization rarely maps 1:1, so plan the split before the upload, not after.
- 04
Rebuild automations and templates
beehiiv's automation builder is structurally similar but won't import Ghost's flows directly. Rebuild only what you actively use; the move is a chance to delete the unused ones rather than lift-and-shift dead infrastructure.
- 05
Send a test broadcast
Pick a small segment and send a real broadcast (not just a preview). Verify deliverability, link clicks, and unsubscribe flow. If anything's off, you find it before the announcement, not after.
- 06
Announce the move and cut over
Send your last broadcast from Ghost announcing the new sender domain and what to expect. Cut over DNS and sending from beehiiv on the same day, not staggered. A dual-send week creates more confusion than it prevents.
Ghost-to-beehiiv specific gotchas
Universal steps cover most of the work. These are the failure modes unique to this exact pair.
-
#1
Ghost exports a JSON archive with full post content, members list, and subscription status; beehiiv import handles email plus name well, but full member metadata (subscription dates, tier names, segments) needs reconstruction. Map out which member fields are load-bearing before importing, then rebuild only those in beehiiv.
-
#2
Ghost themes do not transfer; beehiiv has its own template system. Decide before the cutover whether to maintain visual continuity (rebuild a similar look in beehiiv) or use the migration as a chance to simplify to beehiiv defaults.
-
#3
Active paid memberships on Ghost flow through your direct Stripe account; beehiiv routes paid-subscription revenue through its own Stripe Connect with disbursement to you. Subscribers must re-authorize beehiiv as a charge source on cutover, which means a clear announcement and an explicit deadline.
-
#4
Ghost's website features (custom JavaScript, page-level paywalls, theme-driven signup forms, member-only sections) are website-shaped; beehiiv emails do not render JS and beehiiv's web archive is structurally simpler. Any Ghost-only website surface that depends on theme or JS will be lost.
-
#5
Custom domain DNS: Ghost(Pro) issues SaaS-pattern records; beehiiv issues its own DKIM and SPF records. Add beehiiv's records alongside Ghost's, verify beehiiv authentication, warm beehiiv's sender for 7 to 14 days before flipping the from-address. Don't hard-cut a production sender.
-
#6
If you've staffed Ghost with multiple writer seats, plan how that maps to beehiiv. beehiiv has team seats but the role model and editorial workflow are different; document who needs to do what BEFORE the migration, not after.
Common questions
- Is beehiiv cheaper than Ghost?
- At the entry tier, yes: beehiiv starts at Free while Ghost starts at $18/mo. Pricing scales differently above that, so check the side-by-side plan grid for your specific contact count.
- Will I lose subscribers in the move?
- Email lists transfer as raw addresses; subscriber relationships transfer with you because the addresses haven't changed. What you can lose: re-engagement (some readers won't notice the new sender domain immediately), paid subscriptions if Ghost handles billing differently from beehiiv (the gotchas above call out the specific cases), and any "engagement" or warmth signals that Ghost's deliverability inferred from your sending history. Plan a clear announcement and a deliverability warm-up week.
- How long does the migration take?
- For a list under 10,000 subscribers, a clean migration is one focused week: domain setup and verification, list import, automation rebuild, test broadcast, announcement, cutover. Larger lists or complex automations can stretch to 2 or 3 weeks. The constraint is rarely the import itself; it's the deliverability warm-up and the time to rebuild flows you actually depend on.
- Are Ghost and beehiiv in the same category?
- No. Ghost is primarily a content marketing tool; beehiiv is primarily a email marketing tool. The migration involves changing both your tooling AND part of your workflow shape; the "Why migrate" and "Bad fit" sections above are honest about whether that's the right move for your team.
- Where can I see Ghost vs beehiiv side-by-side?
- The /compare/beehiiv-vs-ghost page on TierGauge shows side-by-side plans, headline pricing, included features, and limit comparison at the entry paid tier. This migration guide is the long-form decision narrative; the compare page is the data-only dashboard.
Disclosure: the "Try beehiiv" link above is an affiliate link. We may earn a commission if you sign up. Pricing is the same; this guide's recommendations and the cost math are unchanged by commercial relationships. How we rank.
Sources
- Ghost: https://ghost.org/pricing/
- beehiiv: https://www.beehiiv.com/pricing
Pricing verified . Migration mechanics are based on the public pricing pages and standard ESP migration patterns; verify destructive steps (DNS cutover, paid subscription transfer) against the vendor's current docs before executing.