Migration guide
Migrate from Substack to Beehiiv
Substack-to-Beehiiv is one of the most common newsletter migrations in 2026. Beehiiv's superior monetization tooling, recommendations engine, and lack of revenue-share at scale pull operators across. The list migration is straightforward; the deliverability ramp is the real work.
Time: 1-2 weeks for free-list only; 3-5 weeks if migrating paid subscribers.
Migration cost: 20-60 founder hours plus $0-$84 in Beehiiv subscription during the parallel period.
Annualized cost change: For paid newsletters above 1,000 paid subscribers, the 10% Substack fee swap pays back the entire Beehiiv subscription within months. For free-only newsletters, the cost is roughly comparable.
Verified · editorial policy
Why founders make this migration
- Beehiiv keeps 100% of your subscription revenue (Substack takes 10%); the math flips for paid newsletters above 1,000 paid subscribers.
- Beehiiv's recommendation network and growth tools are more aggressive than Substack's.
- Custom-domain handling and analytics depth are stronger on Beehiiv.
When NOT to migrate
- If your Substack growth is driven primarily by the Substack network and Notes engagement, migrating cuts off that growth channel.
- If you have less than 1,000 free subscribers, the migration friction rarely pays back.
The 6-step migration
Step 1
Export the full subscriber list from Substack
Substack export includes free + paid subscriber lists with timestamps. Verify counts match the live dashboard.
Pitfall: Not exporting in the correct format — Beehiiv's importer expects specific columns; check the import spec before exporting.
Step 2
Set up the Beehiiv publication and verify the sending domain
Add SPF, DKIM, and DMARC records on your sending domain in Beehiiv. Use mail-tester to verify 9/10+ score before any subscriber-facing send.
Pitfall: Sending to the full list before the new domain is warmed. Beehiiv reuses your existing sender domain if you bring one, so warm-up may be partial — verify deliverability with a small segment first.
Step 3
Import the free subscriber list
Beehiiv import tool. Use the CSV from step 1. Verify final count matches expected.
Pitfall: Importing the paid list together with the free list. Paid subscribers need separate billing migration handled by Beehiiv support.
Step 4
Migrate paid subscribers via Beehiiv's Stripe handoff
Beehiiv's paid-subscriber migration involves transferring Stripe Customers to a new connected account. Beehiiv support handles this — coordinate the cutover date.
Pitfall: Underestimating the coordination lift. Paid subscriber migration takes 5-10 business days end-to-end.
Step 5
Send a goodbye + redirect post on Substack
One final post on Substack pointing readers at the new Beehiiv URL. Pin it. Keep Substack live for 60-90 days as a redirect layer.
Pitfall: Deleting the Substack publication immediately. Readers who bookmarked the old URL need time to update their habits.
Step 6
Set up custom-domain redirects
If you used a custom domain on Substack, move it to Beehiiv and set up Substack-URL-to-Beehiiv-URL redirects for the high-traffic posts.
Pitfall: Losing organic search traffic. Substack post URLs are indexed by Google; 301 redirects preserve the SEO.
Destination tool teardowns
Pre-decision comparisons
Related Brunson terms
Frequently asked
- Will paid subscribers be charged again during migration?
- No, Beehiiv's Stripe handoff preserves the existing subscription cycle. Subscribers should not see a charge interruption when the migration is handled through official channels.
Other migrations
After the migration, audit the funnel
Migrations preserve traffic, not conversion. The free 90-second Launch Diagnostic looks at your live page and labels what is actually broken on the new stack.