Migration guide
Buttondown → beehiiv
Buttondown is a delight to write in: clean markdown editor, privacy-first defaults, transparent a-la-carte pricing, indie-bootstrap product cadence. beehiiv is its growth-oriented opposite: referral program, recommendations network, ad network, native paid subscriptions, multi-author publication shape. The migration motivation is structural, not corrective. You have not outgrown Buttondown's quality; you have outgrown its deliberate-simplicity ceiling and want growth tooling Buttondown intentionally does not ship. Many Buttondown users should not make this move.
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
- Your newsletter has crossed the point where growth (not writing) is the bottleneck. You want a built-in referral program and a cross-promotion network, both of which Buttondown does not offer at any tier.
- You want to monetize via the beehiiv ad network or sponsorship storefront in addition to (or instead of) paid subscriptions. Buttondown ships paid subscriptions on the $9 add-on but has no native ad layer.
- You are evolving from a single-author indie newsletter into a publication shape (multi-author, brand-style, possibly multiple newsletters under one roof) and want a tool calibrated for that.
When it doesn't
- You love writing in Buttondown's markdown editor and the writing experience is core to why you publish. beehiiv's editor is Notion-like blocks; it is good, but it is not markdown-first and it is not the same product feel.
- Privacy-first defaults are a value for you or your audience. Buttondown markets itself on minimal tracking and transparent data handling; beehiiv ships standard newsletter analytics, opens, clicks, engagement scoring. The privacy posture is structurally different.
- Your subscriber count is under a few hundred and you are paying $9 or $29 in Buttondown add-ons. beehiiv Launch is free up to 2,500 subs, but the Scale tier at $43/mo is a real step up in cost the moment you need automations, the ad network, paid subs, or boosts.
What you lose by leaving Buttondown
- Buttondown's markdown-first editor and the writing experience built around it.
- Privacy-first defaults: minimal tracking, no third-party pixel injection by default, transparent data-handling.
- A-la-carte pricing: pay only for the features you actually use ($9 / $29 / $79 add-ons) rather than the beehiiv tier ladder where you buy the whole bundle.
- Indie-bootstrap product cadence and direct founder access; beehiiv is a venture-backed company with a different operating shape.
What you gain with beehiiv
- Built-in referral program: two-sided rewards for subscriber-driven growth, the standout beehiiv growth feature with no Buttondown equivalent.
- Recommendations network: opt-in cross-promotion with other newsletters for compounding subscriber growth without paid acquisition.
- Ad network access on Scale and above: optional revenue layer for newsletters that hit minimum-engagement thresholds.
- Publication-shaped product surface: multi-author seats, multiple publications on Scale (3) and Max (10), sponsorship storefront, audio newsletters on Max. The toolkit assumes you are a media business, not a single-author writer.
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 Buttondown, what's the equivalent on beehiiv?" gut check.
| Limit | Buttondown ($9 add-ons) | beehiiv (Scale) |
|---|---|---|
| Contacts | Custom | 100,000 subscribers |
| Emails / month | · | Unlimited |
| Team seats | · | 3 |
| Campaigns | · | 3 publications |
Step-by-step migration
- 01
Export your list from Buttondown
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 Buttondown 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. Buttondown-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 Buttondown'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 Buttondown 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.
Buttondown-to-beehiiv specific gotchas
Universal steps cover most of the work. These are the failure modes unique to this exact pair.
-
#1
Subscriber export: Buttondown exports a clean CSV with email, subscription date, and tags. beehiiv import accepts email plus name well but tag round-tripping needs reconstruction; map Buttondown tags to beehiiv segments before importing or accept a flatter list.
-
#2
Paid-subscription cutover: Buttondown's paid subs run through Buttondown-managed Stripe; 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. Plan a 30-day overlap window.
-
#3
Markdown to blocks: Buttondown posts are markdown; beehiiv posts are block-based. Past issues do not import as native beehiiv posts cleanly. Decide before the cutover whether to backfill the archive (paste-as-block per issue) or simply leave the historical archive on Buttondown's hosted archive page and start fresh on beehiiv.
-
#4
Custom-domain handoff: Buttondown handles custom-domain sending and (on $29 add-on) custom-domain archives. beehiiv issues its own DKIM and custom-domain records. Add beehiiv's records alongside Buttondown's, verify, warm the new sender for 7 to 14 days on a list segment, then flip. Do not hard-cut a production sender.
Compare on price across the category
This guide is Buttondown to beehiiv specifically. To see both side by side with every other email marketing tool we track on a single price-only table, see the email marketing pricing comparison . Useful before committing to the migration, in case a third option fits the cost-and-feature combination better than either side of this guide.
Common questions
- Is beehiiv cheaper than Buttondown?
- Both start at the same headline price (Free). The reason to migrate is the pricing model and feature scope, not the entry-tier number.
- 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 Buttondown handles billing differently from beehiiv (the gotchas above call out the specific cases), and any "engagement" or warmth signals that Buttondown'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 Buttondown and beehiiv direct competitors?
- Yes. Both are primarily email marketing tools, which is why this is a defensible head-to-head migration rather than a cross-category consolidation.
- Where can I see Buttondown vs beehiiv side-by-side?
- The /compare/beehiiv-vs-buttondown 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
- Buttondown: https://buttondown.com/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.