On this page (11 sections)
Affiliate link: OwnLetter may earn a commission if you sign up through this link, at no extra cost to you. Launch tier stays free.
Substack to Beehiiv Migration: The Real Process and the 8 Warnings Beehiiv Documents
By Arthur Brulard, Founder of OwnLetter. Cross-vendor analyst review across 11 newsletter platforms, aggregating user signals from Reddit, G2, Capterra, Trustpilot, and Hacker News. LinkedIn
Published May 28, 2026 · Updated May 28, 2026 · 11 min read
OwnLetter is supported by readers like you. When you sign up through our links, we may earn a commission that helps keep our reviews independent and free. How we make money · How we test.
Quick verdict
Beehiiv documents three distinct migration flows, not one: content migration (5-10 minutes), free subscriber CSV import, and a 30-step paid-subscriber Stripe customer transfer flow that this guide compresses to 12 operational phases (typically 5-15 minutes, up to three days for large lists). Anyone selling you a single "90-minute total" is estimating, not citing. Two things are NOT migrated: Apple in-app subscribers (tied to Substack's developer account, not yours) and Substack Notes followers. The most expensive mistake is missing two separate post-migration steps that are easy to confuse: pause Substack billing to prevent double-charging (Beehiiv documents this verbatim), and email Substack to remove the 10 percent platform cut on your old account (Paid Newsletter Playbook). Both are manual. Both are forgotten by creators.
How we testedVerified May 2026 · 4 primary sources cross-checked · methodology public
What we did: cross-checked four primary sources for this guide. (1) Beehiiv's official migration support article (beehiiv.com/support/article/14966988360215, verified May 28, 2026) for the documented step-by-step process. (2) The Paid Newsletter Playbook migration guide (paidnewsletterplaybook.com/how-to-migrate-from-substack/) for the practitioner timing recommendations and the 10 percent cut cancellation step. (3) Apple Developer auto-renewable subscriptions documentation for the structural reason Apple in-app subs cannot move. (4) The Beehiiv case study on Matt Brown of Extra Points (blog.beehiiv.com/p/case-study-extra-points) for the named migration case study.
What we did NOT do: we did not run a controlled migration test on a live paying audience (ethically constrained; see our methodology). We did not estimate a single "X-minute total" for the full process because no source documents one. We did not invent a subscriber-drop percentage. Where a claim is not in a source we cite, the guide softens or omits it rather than extrapolating.
Refresh cadence: migration process verified quarterly minimum (next refresh August 28, 2026). Re-verified if Beehiiv updates the migration article or if Substack changes export functionality. Full methodology →
Why People Migrate
Two recurring triggers show up across migration retrospectives. The first is Notes effort without proportional return: writers describe shipping work to the Substack Notes feed and watching reach plateau without a clear reason. The second is the 10 percent platform fee that becomes a material line in the newsletter P&L once paid revenue compounds.
The platform-fee math is direct. Substack takes 10 percent of paid subscription revenue plus Stripe processing fees (about 2.9 percent and $0.30 per transaction). Beehiiv Scale costs $43/mo (Scale, 1K subs) · verified May 20, 2026 on annual billing at 1,000 subs baseline with 0 percent platform fee on paid subs. Break-even sits around $430 monthly paid revenue. Above that, the flat Beehiiv fee compounds in your favor.
Matt Brown of Extra Points migrated off Substack at 2,000 paid subscribers and a $200K newsletter, per the Beehiiv case study. He describes the 10 percent cut as "hundreds of dollars a month I was giving up" before he moved. If you are under 500 paid subscribers, the cut is small enough that Substack's Notes algorithmic discovery still offsets it. The migration math turns decisive when paid revenue crosses $1,000 monthly.
What Migrates (and What Doesn't)
Beehiiv's migration support article documents the exclusions explicitly. This matters because they determine what you need to plan for or rebuild manually.
| Asset | Migrates? | Action required |
|---|---|---|
| Free subscribers | Yes (CSV upload) | Map CSV columns to Beehiiv fields; confirm opt-in status. |
| Paid subscribers | Yes (30-step Stripe transfer, 12 phases here) | Connect Stripe to Beehiiv; mirror Substack tiers; match currency; copy customer PAN; map products; preview; import. |
| Published posts (text) | Yes (5-10 min) | Standard content import via Beehiiv URL paste or export zip upload. |
| Notes followers | No | Stay on Substack. Substack Notes is a platform-side social graph, not your email list. |
| Apple in-app subscribers | No | Email them a Beehiiv signup link with a discount or trial. Apple in-app subs are tied to Substack's developer account. |
| Videos & Podcasts | No | Re-upload separately to Beehiiv (audio newsletter feature requires Max tier). |
| Comments | No | Comments are not transferred. |
| Paywall placements | No | Beehiiv documents verbatim: "the exact paywall placement is not carried over." Re-add Paywall block manually post-import. |
| Photo galleries & Embeds | No | Re-create manually. |
| Code blocks & Blockquotes | Partially | Code blocks migrate as plain text (must recreate formatting). Blockquotes migrate with visual styling differences. |
The Three Migration Flows
Beehiiv documents three distinct flows, not one unified process. Each has its own timing and dependencies. Reading them as a single "1-click migration" sets up the wrong expectations.
Flow A. Content migration (5-10 minutes)
Beehiiv documents this as "5-10 minutes, depending on number of posts." In Beehiiv Settings > Content Import, select Substack as source, paste your Substack publication URL (the importer adds the https://, so enter only the domain), and click Finish import. Monitor the Historical Imports table for Pending or Processing status, refresh to confirm Complete. For paywalled content, run a Substack export first (Settings > Import/Export > New export), download the zip, then in Beehiiv choose "Free + Paywalled" and upload the zip during the import flow.
Flow B. Free subscriber CSV import
From Substack > Subscribers, export the CSV list. In Beehiiv Settings > Subscribers Import, click "New Subscribers Import", select "Upload a CSV file", apply tags under Advanced Configuration if useful, confirm all contacts opted in, map CSV columns to Beehiiv fields, and review results. Beehiiv recommends excluding subscribers with a Substack Activity Rating of 0 for the first 2-4 weeks to protect deliverability while the audience transitions.
Flow C. Paid subscriber Stripe transfer (Beehiiv's 30-step flow, 5-15 min typical to 3 days)
This is the flow most often described inaccurately as "1-click." Beehiiv documents a 30-step paid-subscriber mapping flow in its official support article. This guide compresses those 30 steps into 12 operational phases for readability; the underlying actions are unchanged. Prerequisites: Stripe must already be connected to Beehiiv, paid tiers must already exist and mirror Substack, currency must match (you cannot remap $150 USD to €140 EUR).
- Beehiiv Settings > Subscribers Import > "Start a New Migration".
- Confirm "Start a New Migration" again.
- Log into your Substack-connected Stripe account in a separate tab.
- Navigate to Customers > "Copy > Copy all customers".
- Copy your Beehiiv Stripe account ID from the Beehiiv tab.
- Return to Stripe, paste the Beehiiv account ID, click Continue.
- Click "Confirm request" to initiate transfer.
- In the Beehiiv-connected Stripe account, click "Accept" to approve the transfer.
- Monitor transfer progress (typically 5-15 minutes, can take up to 3 days for large lists).
- Back in Beehiiv, click "I've completed these steps", then paste your Substack Stripe business account ID into Beehiiv.
- Create a restricted Stripe API key (Developers > API keys > Create restricted key). Beehiiv warns: "once the window is closed, the key cannot be retrieved."
- Map Substack products to Beehiiv tiers, generate the migration preview (2-10 minutes), download the CSV, click Start import, and monitor completion.
If you prefer hands-on help, Beehiiv lists migration specialists in their Experts Directory. The free Launch tier (2,500 subscribers, unlimited email sends) lets you test the import on a duplicate non-paying audience first.
Eight Critical Warnings Beehiiv Documents
Every item below is a verbatim warning from Beehiiv's migration support article. Missing any of these is a known failure mode, not bad luck.
1. Double-billing risk if you do not pause Substack billing
Beehiiv documents verbatim: "After migrating, you must either pause or cancel paid subscriptions in your Substack account to prevent double billing. If you don't, subscribers will be charged twice — once by Substack and once by beehiiv." Action: Substack Dashboard > Settings > Payments > "Pause subscription billing" > "Pause indefinitely."
2. Paywall placements are not preserved
Verbatim: "When paid posts are imported from Substack, the exact paywall placement is not carried over. No portion of the post will be visible to free readers by default." Action: re-add the Paywall block manually post-import on every previously-paywalled post.
3. Subscription dates reset by default
Verbatim: "By default, the subscription date in beehiiv will display as the date you import your subscribers." Preserving original dates requires manual Beehiiv Support team intervention. If subscription anniversary matters for your retention metrics or anniversary emails, request the preservation explicitly during migration.
4. Currency cannot change during migration
Verbatim: "Maintain the same currency... you cannot change the currency of subscriptions during migration." A $150 USD subscription cannot be remapped to €140 EUR for the same customer. Match the currency on the Beehiiv side before starting the Stripe transfer.
5. Safari can corrupt the export zip download
Verbatim: "By default, Safari may automatically unpack zipped files after download." The Beehiiv paywalled-content upload requires the zip format intact. Disable the "Open safe files after downloading" preference before downloading the Substack export, or use a different browser for that step.
6. The restricted Stripe API key is non-retrievable
Verbatim: "Once the window is closed, the key cannot be retrieved and you'll need to create a new one if lost." Save the key in a password manager before closing the Stripe key-creation window. Creating a replacement adds time to the migration.
7. Exclude inactive subscribers for the first 2-4 weeks
Beehiiv recommends excluding subscribers with a Substack Activity Rating of 0 from the initial import "to protect deliverability while your audience transitions." Including dead addresses spikes bounce rates on a new sender domain. Add them back gradually after the audience re-warms.
8. Create a default template before migration
Beehiiv documents: "After migration, styling can only be adjusted on a post-by-post basis." Define your default template (typography, header, footer, CTA blocks) before importing content. Otherwise every imported post inherits Beehiiv defaults and requires manual restyling.
Apple In-App Subscribers Cannot Move
The Paid Newsletter Playbook states it directly, verbatim: "due to Substack's recent integration with Apple, your Apple subscriptions cannot move." This is the most-misunderstood limitation of any Substack migration.
The structural reason is documented in Apple's auto-renewable subscriptions documentation. Multi-app subscriptions are tied to the developer account that owns the apps, and that developer account is Substack, not you. Apple does not offer an official mechanism to transfer subscribers between unrelated developer accounts. There is no "App Transfer" feature documented for this scenario.
The pragmatic step is to email Apple-billed subscribers separately during your transition sequence with a Beehiiv signup link. Offer a discount or extended trial as goodwill compensation for the friction. No source documents the typical percentage of subscribers affected; it varies by publication and audience. Some writers report negligible Apple-billed cohorts; others lose a meaningful share. Plan for the loss explicitly rather than assuming low impact.
The 10% Cut Trap: Two Separate Steps You Will Forget
Migration retrospectives in r/beehiiv and r/Substack threads consistently report two distinct mistakes, and confusing them costs creators money for months.
Mistake 1: Not pausing Substack billing post-migration (double-charge)
Beehiiv documents this verbatim: "After migrating, you must either pause or cancel paid subscriptions in your Substack account to prevent double billing. If you don't, subscribers will be charged twice — once by Substack and once by beehiiv." This is a Beehiiv-side observation about how billing routing works post-Stripe transfer. The fix is mechanical: Substack Dashboard > Settings > Payments > "Pause subscription billing" > select "Pause indefinitely." Do this immediately after the Stripe customer transfer accepts on the Beehiiv side.
Mistake 2: Forgetting to email Substack to remove the 10% cut
The Paid Newsletter Playbook covers this verbatim: "Once you've moved away, be sure you email Substack and have them remove their 10% cut." This is a separate manual request to Substack support. There is no settings toggle, no automated step, no template provided in the Playbook. It is the most-forgotten step because it happens after the noisy parts of the migration are done and the creator's attention has shifted to growing on Beehiiv.
Pragmatic email script: "Hi Substack support, I have completed my migration off Substack to a different newsletter platform on [date]. Please deactivate paid features on my account [URL] and confirm that the 10 percent platform fee will no longer apply to any residual Stripe Connect activity tied to my old account. Thanks."
Real-World Migration Cases
Two named, verifiable cases. One illustrates the writer-fatigue trigger at small scale; one illustrates the platform-fee trigger at meaningful scale.
Case 1, identity-pending: Substack-to-Beehiiv consideration at 118 subs
The typical writer-fatigue migration trigger. Posted on r/beehiiv (May 19, 2026):
"Moving over from Substack. Substack has become a bit of a grind with very little return. I've been working my ass off over there and I've got 118 subs in 4 months. Notes are a grind. I'm considering moving over to beehiiv but worried about losing the subs I have."
At 118 subscribers, the platform-fee math is irrelevant. The trigger is opportunity cost on Notes effort. Migration friction for this profile is psychological commitment rather than technical. The 1-click subscriber CSV import handles 118 subs in minutes, and at this scale the paid-subscriber Stripe transfer is either trivial or not applicable.
Case 2, Matt Brown (Extra Points): 2,000 paid subscribers, $200K newsletter
The platform-fee trigger at meaningful scale. Per the Beehiiv case study, Brown reached 2,000 paid subscribers and a $200K newsletter on Substack before migrating. He describes the 10 percent cut as "hundreds of dollars a month I was giving up," invisible at first, then a meaningful operating line as paid revenue compounded.
At Brown's scale, Beehiiv Scale at the relevant subscriber tier with 0 percent platform fee on paid subs flips the equation: the flat fee becomes a fraction of what the Substack cut was costing. His case illustrates the inflection point where the operational friction of migrating (30-step Stripe transfer compressed to 12 phases, 8 critical warnings, transition email sequence, manual 10 percent cut cancellation) becomes trivial relative to multi-year platform fee savings.
Frequently asked
Frequently Asked Questions
Will my paid Substack subscribers follow me to Beehiiv?
Mostly yes, but the process is more involved than a single click. Beehiiv's official migration support article documents a 30-step Stripe customer transfer flow for paid subscribers (this guide compresses it into 12 operational phases: copy Substack-side Stripe customers, paste Beehiiv Stripe account ID, accept transfer Beehiiv-side, map Substack products to Beehiiv tiers, generate migration preview, then import). Free subscribers move via standard CSV upload. Apple in-app subscribers do NOT transfer because Apple's billing relationship is with Substack as the developer account, not with you as the creator. The Paid Newsletter Playbook states: "your Apple subscriptions cannot move." Plan a focused half-day for the technical steps; Beehiiv documents the Stripe transfer itself typically completes in 5-15 minutes but can take up to three days for large lists.
How long does the full migration actually take?
Beehiiv documents three distinct timing brackets and does not promise a single total. Content migration takes "5-10 minutes, depending on number of posts" (verbatim). Free subscriber CSV import is also typically minutes. The Stripe customer transfer for paid subscribers is the variable step: "Most transfers complete within 5-15 minutes, depending on size of customer list" and "can take up to three days." Add time for transition email drafting (the Paid Newsletter Playbook recommends giving readers "maybe a month or less" notice and contacting them "a couple times"), Substack-side billing pause, and the easily-forgotten step of emailing Substack to remove the 10 percent cut. No source documents a single "X-minute total." Anyone publishing that number is estimating, not citing.
What if my Stripe Connect setup is complex (multi-publication, custom payouts)?
The Beehiiv migration support article does not document multi-publication or custom Stripe Connect handling. It describes the standard single-publication transfer and notes that "if you prefer hands-on help with your migration from Substack to beehiiv, you can work with a specialist from the beehiiv Experts Directory." If your Stripe setup is unusual, the honest path is to contact Beehiiv support before starting and budget extra calendar time. The free Launch tier (2,500 subscribers, unlimited email sends) lets you test the import flow on a non-paying duplicate audience first.
What is the "10% cut trap" and how do I avoid it?
Two distinct things, and confusing them costs creators money. First: Beehiiv documents a double-billing risk verbatim: "After migrating, you must either pause or cancel paid subscriptions in your Substack account to prevent double billing. If you don't, subscribers will be charged twice — once by Substack and once by beehiiv." The fix: Substack Dashboard > Settings > Payments > "Pause subscription billing" > Select "Pause indefinitely." Second: the Paid Newsletter Playbook recommends, verbatim: "Once you've moved away, be sure you email Substack and have them remove their 10% cut." These are separate steps. The double-billing pause is immediate. The 10 percent cut removal is a manual support request that creators frequently forget.
What happens to my Apple in-app subscribers?
They stay on Substack and cannot be migrated. The Paid Newsletter Playbook states verbatim: "due to Substack's recent integration with Apple, your Apple subscriptions cannot move." Apple's auto-renewable subscriptions documentation confirms the structural reason: in-app subscriptions are tied to the developer account that owns the app (Substack in this case), not to the individual creator. Apple does not offer an official transfer mechanism for moving subscribers between unrelated developer accounts. The pragmatic step is to email these subscribers a Beehiiv signup link with a discount or extended trial so they can manually re-subscribe to your newsletter on the new platform. No source documents the typical percentage of subscribers affected; it varies by publication and audience.
How We Tested This Migration Guide
OwnLetter operates as a hybrid lab analyst rather than a power-user reviewer. For this guide, we cross-checked four primary sources for every documented step: Beehiiv's official migration support article, the Paid Newsletter Playbook migration guide, Apple Developer auto-renewable subscriptions documentation, and the Beehiiv case study on Matt Brown of Extra Points. We used the OwnLetter methodology. Claims that are not in a source we cite are softened or omitted, not extrapolated.
We did not run a controlled migration test on a live paying audience because the ethical bar for that test is high. Where this guide describes timing brackets (5-10 min content, 5-15 min Stripe transfer typical, up to 3 days for large lists), the numbers come directly from Beehiiv's documentation. The paid-subscriber flow is reproduced from Beehiiv's 30-step support article and compressed into 12 operational phases for readability. The 10 percent cut cancellation step and the "Apple subscriptions cannot move" constraint come from the Paid Newsletter Playbook verbatim.
All sources verified May 28, 2026. Next refresh August 28, 2026 (quarterly cadence). Earlier refresh if Beehiiv updates the migration article or Substack changes export functionality.
Sources
- · Beehiiv Substack-to-beehiiv migration support article (verified May 28, 2026; primary source for 30-step Stripe transfer flow + 8 critical warnings)
- · Paid Newsletter Playbook: How to migrate away from Substack (verified May 28, 2026; primary source for 10% cut cancellation + Apple in-app constraint + transition email cadence)
- · Apple Developer: Auto-renewable subscriptions (verified May 28, 2026; structural reason Apple in-app subs cannot transfer)
- · Beehiiv case study: Matt Brown Extra Points (2,000 paid subscribers, $200K newsletter; named migration case)
- · Reddit r/beehiiv "Moving over from Substack" by identity-pending (May 19, 2026; small-scale writer-fatigue migration trigger verbatim)
- · Beehiiv pricing page (verified May 20, 2026)
- · Substack Going Paid documentation (verified May 20, 2026; 10 percent platform fee structure)
- · FTC Consumer Review Rule Oct 2024 (regulatory)
Final Verdict
If your paid revenue is above $430 monthly: migrate.The platform-fee math compounds in your favor every month above break-even. Block a focused half-day for the technical work (Flow A content + Flow B free subs + Flow C paid subs Stripe transfer — Beehiiv's 30-step flow compressed to 12 phases here), plan a 3-4 email transition sequence over the following weeks, and do not skip the two manual post-migration steps: pause Substack billing immediately to prevent double-charging, then email Substack to remove the 10 percent cut on your old account.
Start MY free Beehiiv account →No credit card. Launch tier stays free.
If you are under 500 paid subscribers without an existing audience: stay on Substack for now. Notes can be a useful cold-start discovery channel if it is already driving measurable subscribers for you; the 10 percent cut on trivial paid revenue is negligible at this scale. Plan the migration trigger at the 1,000+ paid subscriber mark or once paid revenue crosses $430 monthly, whichever happens first.
Reader bonus via our link: 14-day free trial + 20% off your first 3 months on Scale or Max plan (annual billing, new accounts). Applied automatically (no promo code needed). Beehiiv Launch tier remains free, no credit card required.
Want the full Substack vs Beehiiv head-to-head comparison? Read the full comparison with feature matrix, pricing scenarios, and 591 user signals aggregated.
Join the discussion
Migrated from Substack to Beehiiv yourself? Share what worked and what tripped you up, especially around the paid-subscriber Stripe transfer or the post-migration billing pause. No account required: just an email and a name. Comments are moderated to keep replies useful, specific, and migration-related.