Leaving Substack for Beehiiv: keeping the audience, dropping the 10%

Substack's 10% take is the explicit cost. The implicit cost is that your audience lives inside their network, the recommendation engine drives where your growth comes from, and the long-term ranking is theirs not yours. Beehiiv flips both: flat monthly pricing, your own domain at the centre, your own SEO footprint. The migration is two evenings of work for a typical 10k-subscriber newsletter, the bigger commitment is the redirect strategy you choose at step 4.

What you actually move

The full email list (free and paid). The complete post archive. Your paid subscriber Stripe data. Custom domain if you have one. What stays in Substack: the recommendation network and the comments. There's no way to move either; recommendations are Substack's product, comments are tied to user accounts that don't exist anywhere else.

Step 1: get your data out of Substack

Substack ships an export from Dashboard → Settings → Export your data. The export includes a CSV of subscribers and a folder of post HTML files. It takes 5-15 minutes.

Important caveat: the subscriber CSV separates free and paid subscribers. Keep both files; you'll need them for the Stripe handover (step 3) and the deliverability warm-up (step 7).

The post HTML files include the original styling and Substack-specific embeds. They are usable but need light cleanup before importing. Beehiiv accepts HTML import.

Step 2: set up the Beehiiv publication

Create the Beehiiv account, pick a plan that covers your subscriber count (Growth tier at $49/mo for under 25k subscribers is the right starting point for most paid creators), and complete the publication setup.

Two decisions to make now:

Domain choice. If you have a custom domain on Substack (e.g., yournewsletter.com), you can point it at Beehiiv via DNS. If you're on yournewsletter.substack.com, you need to decide: spin up a new domain, or accept yournewsletter.beehiiv.com. The DNS pointing is a one-time fiddly hour; do it now, not later.

Custom email sender. Beehiiv lets you send from you@yourdomain.com instead of you@beehiiv.com. Configure SPF, DKIM, and DMARC records before importing subscribers. This is the difference between 95% inbox placement and 60% on day one.

Step 3: import the list and the archive

In Beehiiv, Subscribers → Import. Upload the free and paid CSVs separately, tagging each row with substack-migrated-2026-05 and either substack-free or substack-paid so you can address the cohorts differently in the warm-up.

For the archive, import the post HTML in chronological order from oldest to newest. Beehiiv's import has a date field; fill it in for each post so the chronology matches your Substack archive. This matters for the redirect strategy.

Step 4: handle the Stripe handover for paid subscribers

This is the step everyone gets wrong. Substack runs paid subscriptions on Substack's Stripe account. The credit cards your paid subscribers entered are not transferable to your Stripe account directly.

Two paths:

Path A: keep Substack alive for paid, run free + new paid on Beehiiv. The existing paid subscriber tier continues running in Substack until each subscription naturally renews. New paid signups go to Beehiiv. The list is split for 12 months but no one loses access. Slow but zero friction for existing subscribers.

Path B: ask paid subscribers to re-subscribe at Beehiiv. Send a one-time campaign explaining the move, offering an exclusive (a discount, a free month, a bonus) for re-subscribing during a 14-day window. Expect 60-80% to re-subscribe. You absorb the loss of the 20-40% who don't, but you're done in two weeks.

Path A is the right answer for newsletters with above $20k MRR in paid (the lost revenue from path B is significant). Path B is the right answer for everyone else.

Step 5: domain redirect strategy

If you used a custom domain on Substack, the swap is clean: change the DNS records, the domain now points at Beehiiv, every old URL resolves to Beehiiv. Done.

If you were on a *.substack.com URL, the question is what to do with the existing Substack publication. Three options:

Cleanest: Leave the Substack pub up with all the old posts. Each old post on Substack stays indexed and live. On Beehiiv, set the same posts at clean URLs on your new domain. Update internal links between posts to point at the Beehiiv versions. Eventually Beehiiv's URLs out-rank the Substack ones; for the first 6 months both work.

Bolder: Delete the Substack publication entirely. Every old URL 404s. This tanks your search traffic for 3-6 months. Only do it if you have low SEO traffic to begin with or you've already secured the redirect via a custom domain.

The cleanest option is almost always the right call.

Step 6: forms and landing pages

Wherever your Substack subscribe button lives — your website footer, your bio links, your in-article CTAs — swap the URL for the Beehiiv equivalent. Beehiiv's embed snippet is short; the styling matches Substack closely.

Don't forget Twitter/X bio, LinkedIn header, GitHub profile, Stripe page, podcast description, and any guest-post bylines you wrote in the last year. Use a search engine: "your newsletter name site:linkedin.com" finds the bylines fast.

Step 7: the warm-up week

Same principle as the Mailchimp-to-Kit migration. Don't blast your full list on day one from the new platform. Start with the most engaged 10% on day one, expand outward across a week. The Beehiiv side runs on different IPs than Substack; your domain reputation transfers but the sending IP doesn't.

For paid subscribers, prioritise their welcome. Day one: a personal email from the founder address (you) thanking them and walking them to their new login. Day three: the first regular issue at the new sending pace.

Step 8: shut down or freeze Substack

If you went with path A (Stripe handover) you keep Substack running for paid. The free side can be paused — turn off new free signups, leave the existing free list inert.

If you went with path B, Substack can be archived or deleted after 30 days. Keep the export for one year in case you need to reference old performance numbers.

What you will miss

The Substack network and the recommendations. Roughly 10-30% of newsletter growth on Substack comes from the recommendation engine and the in-app browse. Beehiiv has a similar feature (Boost), which works differently and at a smaller scale. For some creators, the network was a meaningful chunk of growth and Beehiiv will feel slower; for others, it was decorative.

The audience comments. Substack threads have a community feel that Beehiiv's commenting system doesn't replicate. If your comment threads are active, this is a real loss.

What you gain

The 10% revenue back, the SEO of your own domain, ownership of the list as a portable asset, control of the design and the brand, and a publisher rather than a feed. For most creators above $5k MRR in paid, the math is clearly in favour of moving. Below that, the decision is more about whether owning the platform is worth the migration friction.