Every migration guide I read before actually moving a test publication off Substack described the process in the vaguest possible terms: “export your list, import it, done.” Nobody mentioned what happens to an active paid subscriber’s Stripe billing mid-migration, or that DNS propagation means your custom domain can be in limbo for a day, or that your welcome automation needs to exist before you send your first import, not after. Those are the details that turn a migration from a weekend project into a two-week headache.
I walked through beehiiv’s actual migration tooling, the CSV import flow, the Stripe billing transfer for paid subscriptions, the Entri-assisted domain connection, and the content import tool, to document exactly what the process looks like in 2026, not what a marketing page implies it looks like.
Disclosure: some links in this post are affiliate links. If you sign up through them, we may earn a commission at no extra cost to you. That never changes our verdict.
The short answer: how do you migrate from Substack to beehiiv?
You migrate from Substack to beehiiv by exporting your subscriber list as a CSV, setting up your beehiiv publication and welcome automation before importing anyone, transferring paid subscriptions through Stripe so billing continues without interruption, connecting your custom domain via beehiiv’s Entri integration, importing your content archive, and redirecting old post URLs to protect your SEO. The main reason writers make this move is economics: Substack takes 10% of paid subscription revenue forever, on top of Stripe’s standard 2.9% plus $0.30 per transaction, while beehiiv takes 0% on its Scale plan and above for a flat monthly fee starting at $43/month on annual billing. The whole process, done carefully, takes most publications a few hours of active work spread across three to five days to account for DNS propagation and Stripe transfer timing.
- Export your Substack subscriber list as CSV before doing anything else; this is the one step everything downstream depends on.
- Set up your beehiiv publication, branding, and welcome automation first, then import subscribers, not the reverse, or new subscribers land with no onboarding sequence waiting for them.
- Paid subscriptions transfer through Stripe, which is the part to get right, since billing needs to continue uninterrupted for subscribers who are actively paying.
- Custom domain migration uses beehiiv’s Entri integration to avoid manual DNS record editing, though propagation can still take up to 48 hours.
- Redirecting your old Substack post URLs (or at minimum updating internal and external links) protects the search rankings your archive already earned.
Before you touch your subscriber list, open a free beehiiv account and build your publication shell and welcome automation first. It’s free to 2,500 subscribers with no card required, and having the destination ready before you move anyone makes the whole migration smoother.
Why are Substack writers actually migrating to beehiiv in 2026?
Almost always one of two reasons, sometimes both. The first is the fee. Substack’s 10% cut of paid subscription revenue never goes away and never decreases as you grow, while beehiiv’s Scale plan charges a flat fee and takes 0%. Run the math on your own numbers: a newsletter earning $2,000 a month in paid subscriptions pays Substack roughly $200 a month, every month, forever. The same newsletter on beehiiv’s Scale plan pays a flat $43 a month on annual billing and keeps the rest. The crossover point, where beehiiv becomes cheaper than Substack’s cut alone, lands around $430 a month in paid revenue, and every dollar of growth past that point is money Substack would have kept a slice of.
The second reason is control and tooling. Writers who want a native referral program, a two-sided growth marketplace (Boosts), deeper analytics, and a website with real SEO controls find Substack’s feature set thinner in exactly those areas, since Substack optimizes for its in-app discovery network (Notes, recommendations inside the app) rather than for growth tools an operator configures directly. I compare both platforms feature by feature in beehiiv vs Substack, cover the hands-on details of actually running a publication on beehiiv in my full beehiiv review, and if you’re weighing beehiiv against the wider field before committing to the move, my ranking of the best newsletter platforms covers where each one wins.
What actually changes when you move from Substack to beehiiv?
Your content, subscribers, and (if applicable) paid billing all move. Your posts become beehiiv posts on a beehiiv-hosted or custom-domain website. Your subscriber list becomes a beehiiv audience with the same email addresses and subscription statuses, assuming the CSV export and import map correctly. Paid subscribers keep paying through the same Stripe relationship, just billed through beehiiv’s Stripe Connect integration instead of Substack’s. What does not automatically move: Substack’s Notes presence and any organic discovery you were getting from Substack’s in-app recommendation network, which is specific to Substack’s ecosystem and does not have a direct equivalent on beehiiv. Weigh that loss honestly against the fee savings and the growth tools you’re gaining; for many writers it is a clear win, but if a meaningful share of your growth genuinely comes from Notes, say so to yourself before you migrate, not after.
Step 1: Audit what you’re actually bringing over
Before touching any export tool, make a short inventory: total subscriber count, how many are paid versus free, your current Stripe setup (are you on Substack’s Stripe integration directly, and do you have admin access to that Stripe account), your custom domain (if you have one and where it’s registered), and a rough count of published posts you want to preserve. This ten-minute audit prevents the most common migration mistake, which is starting the subscriber import before realizing you don’t actually have Stripe admin access, or discovering mid-move that your domain registrar login was your business partner’s and not yours.
Step 2: Export your subscriber list from Substack
Inside your Substack dashboard, go to Subscribers and use the export function to download your full list as a CSV. This file includes email addresses and subscription status (free versus paid), which you’ll need when mapping fields during import. Do this export fresh, right before you plan to import, rather than days earlier, so the list reflects your current subscribers and not a stale snapshot missing recent signups or cancellations.
Step 3: Set up your beehiiv publication before you import anyone
This is the step most migration guides skip and the one that causes the worst first impression for new subscribers. Create your beehiiv publication, set your branding (logo, colors, publication name), write your welcome automation, and decide your posting cadence before a single subscriber lands in the system. If you import your list into an empty publication with no welcome sequence, subscribers who happen to open an early test send see an empty, unbranded shell, which reads as unprofessional at best and as a scam at worst to a subscriber who doesn’t remember signing up for a new platform. Get the welcome automation covered in Step 8 built now, even though it comes later in this sequence logically; build it before the import so it’s live the moment new subscribers arrive.
Step 4: Import your subscriber CSV into beehiiv
Inside beehiiv, use the subscriber import tool, upload the CSV you exported from Substack, and map the fields (email, subscription status, any custom fields you want to preserve) to beehiiv’s schema. beehiiv’s import accepts CSV exports from all major newsletter platforms, and the field-mapping step is where you confirm free versus paid status carries over correctly, which matters for the next step. Import free and paid subscribers together if your CSV includes both, but do not assume paid billing transfers automatically through this CSV import alone; that requires the separate Stripe step below.
Step 5: Migrate paid subscriptions through Stripe (the part to get right)
This is the delicate part of the entire migration, and it’s worth doing slowly and carefully rather than rushing. beehiiv’s migration path for paid subscriptions runs through Stripe: you connect or transfer the relevant Stripe billing relationship so that active paid subscribers continue being charged without an interruption or a duplicate charge. Because active subscriptions are real money moving on a recurring basis, confirm with beehiiv’s support (available on all plans, with priority support on Max and dedicated customer success on Enterprise) or a vetted migration specialist from beehiiv’s Experts Directory before you flip the switch on a list with meaningful paid revenue, rather than improvising this step solo. A failed or duplicated charge on a paying subscriber is the single worst thing that can happen during a migration, and it’s avoidable with a careful, verified Stripe transfer.
If your list includes paid subscribers, start with a free beehiiv account and reach out to their support before transferring Stripe billing. Getting a second set of eyes on the Stripe transfer step, especially with real recurring revenue on the line, is worth the extra day it takes.
Step 6: Migrate your content archive
Use beehiiv’s content import tool, which accepts a publication URL or an export file, to pull your Substack archive into beehiiv. Your imported posts land in a draft or review state so you can check formatting, images, and links before anything goes live, which matters because automated imports occasionally mangle embedded images or custom formatting that was specific to Substack’s editor. Spend an hour reviewing your ten or fifteen best-performing posts specifically, since those are the ones most likely to still be pulling in search traffic and worth getting exactly right.
Step 7: Point your custom domain to beehiiv
If you were using a custom domain on Substack, connecting it to beehiiv is handled through beehiiv’s Entri integration, which walks you through the connection without requiring you to manually edit DNS records at your registrar the way older migrations required. Even with Entri handling the technical steps, DNS changes can take anywhere from a few minutes to up to 48 hours to fully propagate depending on your registrar and existing DNS configuration, so plan your public announcement for after propagation is confirmed, not the moment you click connect. If you were on a substack.com subdomain rather than a custom domain, this step is simpler: you’re choosing a new domain or beehiiv-hosted address rather than migrating an existing one, but it’s worth registering a proper custom domain at this point regardless, since it’s supported even on beehiiv’s free Launch plan.
Step 8: Confirm your welcome automation is live and correct
You built this in Step 3, but confirm it before your first real send. A welcome automation should fire immediately when someone subscribes (whether through a fresh signup or, for migrated subscribers, framed as a “we’ve moved” message rather than a cold welcome), introduce what to expect, and set the cadence. For migrated subscribers specifically, the first automated message people receive from a platform switch should acknowledge the move directly: “You’re getting this because I moved [newsletter name] from Substack to beehiiv, here’s what’s changing and what isn’t.” Skipping this context is what causes a spike of confused unsubscribes and spam complaints right after a migration, since a subscriber who does not remember opting into a new platform is primed to hit report instead of read.
Step 9: Redirect old URLs to protect the SEO you already earned
Every Substack post that ranks in Google for anything is an asset you paid for with time, and losing those rankings during a migration is avoidable with proper redirects. If you’re moving to a custom domain that was already pointed at Substack, set up 301 redirects from your old post URLs to their new beehiiv equivalents wherever the URL structure differs; beehiiv’s documentation notes that for Substack migrations specifically, post URL structures often transfer automatically when the domain moves, which reduces but doesn’t eliminate the redirect work. Where automatic mapping doesn’t apply cleanly (renamed posts, restructured slugs), manually redirect your ten to twenty highest-traffic posts at minimum, checked against your old Substack analytics, since those are the ones with the most search equity at stake.
Step 10: Announce the move and send your first beehiiv issue
Once DNS has propagated, your content archive looks right, and Stripe billing is confirmed working for paid subscribers, send an announcement issue explaining the move: why you switched, what’s different for readers (usually nothing meaningful on the reading side), and what to expect going forward. Keep this first issue focused entirely on the transition and save your next regular content issue for immediately after, so subscribers get proof the newsletter itself hasn’t changed within days of the switch, not weeks.
What about Substack’s Notes and discovery network?
This is the honest tradeoff, and it’s worth stating plainly rather than glossing over. Substack’s Notes feed and in-app recommendation system genuinely surface new readers inside Substack’s own app, and that discovery channel does not transfer to beehiiv or any other platform, because it’s tied to Substack’s ecosystem specifically. If Notes is a meaningful, measurable source of your subscriber growth today, check your own analytics before you decide, not a general claim either way, since this varies enormously by niche and by how active you personally are on Notes. For most small and mid-sized publications, the honest answer is that Notes contributes less than writers assume, and beehiiv’s native referral program and Boosts marketplace replace it with a different but comparable growth mechanism. For publications where Notes really is driving significant discovery, that’s a real cost of migrating and should factor into the decision alongside the fee savings.
How much does it actually cost to migrate, and is it worth the fee difference?
The migration itself costs nothing beyond your time; beehiiv’s import, Stripe transfer, and domain connection tools are included on the Scale plan, which is the tier you need anyway to access 0% fees on paid subscriptions, priced from $43/month on annual billing ($517/year) or $96/month for Max if you want beehiiv branding removed and up to 10 publications. Compare that against what you’re currently paying Substack: nothing in platform fees, but 10% of every dollar of paid subscription revenue, forever, on top of Stripe’s standard processing cut. Run your own numbers before deciding: divide your monthly Scale plan cost by 0.10 to find your break-even point in paid monthly revenue; below that line Substack’s fee-free model can still be cheaper on paper, above it beehiiv’s flat fee wins and the gap widens every month you grow. For the complete tier-by-tier breakdown, see the beehiiv pricing breakdown, and if you’re specifically comparing Substack’s fee structure across everything it charges, I lay that out in Substack pricing explained.
If beehiiv isn’t the right fit for your specific situation after reading all this, it’s worth knowing what else is out there before you commit to any single alternative; my guide to Substack alternatives covers the wider field, including where Ghost and Kit fit for writers with different priorities than growth tooling.
Common mistakes when migrating from Substack
- Importing subscribers before the welcome automation exists. New arrivals land in a silent publication with no context for what just happened.
- Rushing the Stripe transfer on a list with real paid revenue. A failed or duplicate charge on a paying subscriber is the worst possible first impression of the new platform.
- Announcing the move before DNS has propagated. Sending readers to a custom domain that isn’t fully live yet creates broken links and confusion.
- Skipping redirects on high-traffic old posts. Search rankings you spent months earning can quietly evaporate without them.
- Not addressing the migration directly in the first send. Subscribers who don’t remember signing up for a new platform report unfamiliar senders as spam.
- Ignoring the Notes discovery question entirely. Know honestly how much of your growth came from Substack’s in-app network before you decide, not after you’ve already left.
Frequently asked questions
Will I lose my paid subscribers when I migrate from Substack to beehiiv? No, if the Stripe transfer is done correctly. Paid subscriptions transfer through Stripe so billing continues without interruption, but this is the step worth doing carefully, ideally with beehiiv support or a vetted migration specialist involved if your paid revenue is significant.
How long does migrating from Substack to beehiiv take? The active work (export, import, publication setup, welcome automation, content review) typically takes a few hours spread across two to three days, plus up to 48 hours for DNS propagation if you’re connecting a custom domain. Most publications can complete the full migration within a week.
Will I lose my SEO rankings when I switch from Substack? Not if you redirect properly. beehiiv notes that post URL structures often transfer automatically for Substack migrations when the domain moves, and manually redirecting your highest-traffic posts covers what doesn’t map automatically.
Does beehiiv charge a fee to migrate from Substack? No separate migration fee. The tools (CSV import, Stripe transfer, domain connection via Entri, content import) are included on the Scale plan, which is the tier you need for 0% fees on paid subscriptions and starts at $43/month on annual billing.
What happens to my Substack Notes presence after I migrate? It doesn’t transfer. Notes and Substack’s in-app discovery network are specific to Substack’s ecosystem, and beehiiv’s referral program and Boosts marketplace are the closest replacement, though they work differently. Check your own analytics for how much Notes actually contributes to your growth before deciding how much this matters for you.
Can I keep both Substack and beehiiv running during the transition? Yes, and it’s a reasonable way to de-risk the move. Keep your Substack publication live while you build out and test your beehiiv publication, then switch your primary sending and announce the move once everything (welcome automation, domain, Stripe transfer) is verified working.
The bottom line
Migrating from Substack to beehiiv is a well-documented process now, CSV export and import, Stripe billing transfer, Entri-assisted domain connection, and a content import tool all exist specifically to make this move manageable without a developer. The parts that actually require care are the ones involving real subscribers and real money: the welcome automation needs to exist before you import anyone, and the Stripe transfer for paid subscriptions deserves a slow, verified approach rather than a rushed one.
Do the audit first, build the destination before you move anyone into it, and treat the paid subscription transfer as the one step where “move fast” is the wrong instinct. Everything else in this guide is mechanical once those two things are handled correctly.
Start your free beehiiv publication and build the destination (branding, welcome automation, publication settings) before you export a single subscriber from Substack. It’s free to 2,500 subscribers with no card required, and having it ready first is what makes the rest of this migration go smoothly.
Pricing captured from vendor pricing pages, July 2026. Plans change, so confirm current details before you buy.
