How to migrate from Beehiiv, in one line: the export is easy, the Stripe step is the hard part, and the math should decide whether the move is worth doing at all.
Most migration guides hand you a checklist and skip the part that matters. Beehiiv is structurally different from Substack in two ways that change the playbook, and those differences are where most paid subscribers churn if you get the sequence wrong. Here is the order to do it in, with the trap at each step.
Run the math before you run the export
Beehiiv does not take a cut of your paid subscription revenue. The fee is a flat monthly tier that steps up at 10K, 25K, 50K, and 75K subscribers, per its pricing page. Scale starts at $49/month; Max sits around $109/month. That number is what you are deciding to keep paying or stop paying. Everything else in the move is plumbing.
Compare that to what the receiving platform charges at your current list size, then add the one-time cost of the migration itself: a few hours of work, a possible spam dip on the first send, and the slice of paid subscribers who churn during the handoff. If the receiving platform charges less and bundles in something Beehiiv does not (a blog that is treated as an equal surface, automations you do not pay extra for, a sending domain reputation you actually own), the move pays for itself in the first quarter. If the gap is a rounding error against the value of Beehiiv's growth network, do not migrate yet.
What Beehiiv gives you that you should weigh
The strongest case for staying is the Boost network and the Ad Network. Boosts pay other publications to recommend you in exchange for a per-subscriber fee; the Ad Network places brand sponsorships into your sends and splits the revenue. Both are real channels that most other platforms do not have, and both depend on staying inside Beehiiv to function.
When you leave, you keep the readers who already subscribed. You lose the recommendation pipeline and the ad inventory. New growth has to come from your own social, your own SEO, and word-of-mouth that compounds slowly.
The check: in the last 90 days, what share of new subscribers came through Boosts or recommendations versus from your own pages? If Boost-sourced subscribers are under roughly a third of new growth, and your ad revenue is small compared to what a flat-rate receiving plan would save you, the network is no longer earning its keep.
Export the list and the posts
Beehiiv's export is the easy part. From the dashboard, go to Settings, then Export Data. You can choose Quick or Full: Quick gives you email, status, and tier; Full adds custom fields and engagement stats. Both arrive as a CSV by email, with a download link valid for 24 hours, per Beehiiv's own export documentation.
Take the Full export. The extra fields are what let the receiving platform recreate your segments and tags instead of treating every subscriber as a flat list. Open the CSV before you upload it anywhere, then clean the comma-in-name rows, the empty emails, and the duplicates from subscribers who signed up twice. The next platform will not do it for you.
For the posts, the receiving platform usually offers a one-click importer. Ghost documents the Beehiiv path on its migration page: you paste a Beehiiv API key, choose to import posts and members, and Ghost pulls the content. Spot-check the oldest and newest posts after the import. Image references and embedded blocks are where formatting breaks if anything does.
The Stripe handoff is structurally different from Substack
This is the step that separates a Beehiiv migration from a Substack migration, and it is where most paid subscribers churn if the sequence is wrong.
Substack uses Stripe Connect with a platform application fee, so leaving is an OAuth disconnect that keeps the underlying subscriptions alive. Beehiiv connects to your own Stripe account directly. Per Ghost's migration documentation, the Stripe account associated with a Beehiiv publication is, in practice, tied to that publication while in use; the workaround is a Stripe-to-Stripe subscription migration, which Stripe supports through a support request, as documented in their account data migration docs.
The practical sequence is: open the Stripe account for the receiving platform first. Email Stripe support and ask for a subscription migration from the old account to the new one, with the same billing dates, prices, and customers preserved. Stripe runs the move on their side, the cards do not get re-tokenized, and renewal dates do not shift. Then connect the new Stripe account to the receiving platform, confirm the imported subscriber records line up with the migrated subscriptions, and only then pause or cancel the Beehiiv plan so the old setup stops billing.
If you skip the Stripe-to-Stripe step and just import the subscriber CSV, your paid subscribers have to re-enter card details on the new platform. Expect a meaningful share of them not to bother. The 10% to 30% paid churn cited in independent migration write-ups concentrates almost entirely in this one step.
The first 30 days on the new platform
Announce four to six weeks before the cutover. Tell subscribers what is moving, when, and why. The biggest migration mistake is silence: readers who get an email from an unfamiliar sender after a quiet Beehiiv feed mark it as spam, and the new sending reputation never recovers from the first impression.
If you have been sending from Beehiiv's shared subdomain (mail.beehiiv.com) rather than a custom sending domain, your sender reputation does not travel. The new platform starts from zero and warms a new domain over the first few sends. Plan for a slightly lower inbox placement rate on the first edition. If you were on a custom sending domain, the reputation follows the domain, not the platform, which is the whole reason a custom sending domain is worth the 15-minute DNS setup in the first place. We wrote more about that in our piece on the custom sending domain.
On the cutover day, leave a goodbye post live on Beehiiv pointing readers at the new home. If you have a custom domain pointed at Beehiiv, repoint it to the receiving platform on day one. The link equity on your URL is the one piece of SEO that follows you cleanly. Send the first edition from the new sender within seven days; long gaps after a sender change train inboxes to forget you, and the new domain needs a few sends to warm.
The point of the move
A subscriber converts roughly 10× better than a follower. That number is the point of running a list at all, and it is also the point of moving the list when the platform stops earning its place. The full math is in our piece on subscribers versus followers.
Nashra is the publishing OS underneath the writing: one editor, one subscriber list as the spine, the same draft becoming an inbox send and a blog post in one motion, on your own domain. The blog and the inbox are equal surfaces, not one bolted onto the other. Import and export stay free in both directions, and the next month is something we earn every month.
