Creator · Newsletter Migration
How to Move a Newsletter From Substack to Beehiiv
A step-by-step migration order that protects paid access and prevents double billing.
Affiliate disclosure: SoloClientStack may earn a commission on links on this page. Full disclosure →
You move a newsletter from Substack to Beehiiv by exporting your subscriber list and post archive from Substack, importing free and paid subscribers into Beehiiv with your paid tiers mapped correctly, and then pausing or canceling Substack billing so nobody gets charged twice. The archive comes over mostly intact, but code blocks, embeds, and Substack's recommendation network need manual rebuilding. The riskiest part of this move is not the CSV export, it's the sequencing - migrate paid access before you touch the old billing, and don't cancel anything on Substack until Beehiiv access is confirmed working.
Move to Beehiiv now if...
You already have paid subscribers and want stronger segmentation and growth tooling, your list has outgrown a simple send-and-collect setup, and you are willing to spend a few hours rebuilding recommendations and cleaning up archive formatting after the import.
Stay on Substack if...
Your newsletter is small and simple, your current monetization is already working with low operational overhead, and you do not have a specific workflow reason - audience control, revenue efficiency, better tooling - tied to the move.
Who this migration guide is for
This is written for a solo creator or small operator running a free or paid newsletter on Substack, usually somewhere between a few hundred and several thousand subscribers, with no technical team and no appetite for billing mistakes. If you are just starting a newsletter, the platform choice matters less than the habit of publishing consistently - pick one and go. This guide is for the operator who already has an audience and revenue at stake and needs a migration order that does not put either at risk.
What actually transfers from Substack to Beehiiv
Migrating a newsletter is really three separate migrations happening at once: your subscriber list, your paid billing relationship, and your content archive. Treating them as one step is where most of the risk comes from. Substack's own help documentation confirms you can export your email list from the Subscribers page and export your published posts, since anything you publish there is yours to own and take with you. Beehiiv's migration tooling is built to receive both of those exports, but it is explicit about what does not come over cleanly - notably code blocks, which import as plain text, and Substack's recommendation network, which has no direct equivalent and needs to be rebuilt inside Beehiiv's own growth features.
| Item | Migrates? | How | Caveats |
|---|---|---|---|
| Free subscriber emails | Yes | CSV export from Substack, CSV import into Beehiiv | Subscriber names may not be included in the export file |
| Paid subscribers | Partially | Beehiiv's paid import maps Stripe subscription data into your tiers | You must confirm renewal and expiration dates before mapping |
| Post archive | Mostly | Export posts from Substack, import as content into Beehiiv | Code blocks import as plain text and often need reformatting |
| Custom fields and tags | Yes | CSV column mapping during subscriber import | Only works if the fields exist in your export and in Beehiiv first |
| Cross-promotion recommendations | No | Not transferable | Rebuild manually using Beehiiv's growth and recommendation features |
Substack export checklist: pull this before you touch Beehiiv
Do the exports first, before you create anything on Beehiiv. You want raw data in hand so you can verify counts at every later step.
- Export your email list from the Subscribers page. Substack's help documentation notes that subscriber names may not be included in this file, so do not plan on personalization data carrying over automatically.
- Export your post archive from your posts dashboard. This is the content you own and can take with you.
- Pull paid subscriber detail from your Stripe dashboard - plan, price, and renewal or expiration date for each paid subscriber. Beehiiv's paid import needs this to map subscribers into the right tier without guessing.
- Write down your current free and paid subscriber counts. This is the number you will check every export and import against.
Beehiiv setup order before you import anything
The setup order matters more than the import itself. Build the destination before you pour anything into it.
- Create your Beehiiv publication and configure the basics - name, sending domain, and site settings.
- Build your paid tiers first, matching whatever pricing structure you are keeping from Substack, or deliberately changing it now while you are already restructuring.
- Set up any custom fields or tags you want subscribers organized by. These need to exist in Beehiiv before a mapped CSV import can use them.
- Only after tiers and fields exist, start importing subscribers.
How to import free subscribers
Beehiiv's subscriber import supports a CSV upload with tag and custom field mapping in one pass, so bring your Substack export in as a single file and map the columns you have rather than tagging subscribers one at a time after the fact. Once the import finishes, the first thing to check is the total subscriber count against the number you wrote down before you started. A mismatch here is easier to fix before you move on to paid subscribers than after.
How to import paid subscribers without double billing
This is the highest-risk step in the whole migration, and it is worth slowing down for. Beehiiv has a dedicated paid subscriber import flow built to map Stripe subscription data into your Beehiiv tiers. Before you run it, confirm every subscriber's renewal date from the Stripe export you pulled earlier. If the mapping is off, a subscriber either loses paid access they already paid for, or ends up being billed on both platforms at once - and double billing is the fastest way to lose the trust you are trying to keep by migrating carefully in the first place.
Substack currently charges a 10 percent creator fee on paid subscriptions plus standard Stripe processing fees (verify current terms, since platform fees change). Once your paid subscribers are confirmed active and renewing correctly inside Beehiiv, go back to Substack and pause or cancel the paid subscription there. Do this last, not first. Canceling Substack billing before Beehiiv access is verified working is how creators end up with subscribers who suddenly cannot read anything they already paid for.
What to do with the archive
Beehiiv's migration tooling can import your Substack content and subscriber data together, but plan for a manual cleanup pass, not a perfect one-click transfer. Two things break most often: code blocks, which come across as plain text and need to be reformatted by hand, and Substack's recommendation network, which does not transfer at all and has to be rebuilt using Beehiiv's own growth and recommendation tools. Everything else - standard post formatting, images, and basic layout - tends to come across in reasonable shape, but spot-check a handful of your most-read posts after import rather than assuming the whole archive is clean.
Migration order checklist
This is the sequence that keeps paid access intact and prevents billing mistakes. Do these roughly in order, verifying each step before moving to the next.
| Step | Do it before | Verification |
|---|---|---|
| Inventory current Substack assets | Anything else | Confirm free count, paid count, and archive size |
| Export free subscriber list | Any Beehiiv setup | Open the CSV and confirm email column is complete |
| Export paid subscriber data from Stripe | Creating Beehiiv tiers | Confirm renewal or expiration date recorded for each subscriber |
| Export post archive | Content import | Confirm post count matches your Substack dashboard |
| Build Beehiiv publication and paid tiers | Any subscriber import | Tiers mirror, or intentionally replace, Substack pricing |
| Import free subscribers | Paid subscriber import | Total subscriber count matches your Substack export |
| Import paid subscribers and map tiers | Canceling Substack billing | No subscriber shows access issues or duplicate charges |
| Import and clean up archive | Public relaunch | Spot-check top posts for formatting and code blocks |
| Pause or cancel Substack billing | Announcing the move | No new Substack charges appear after the switch date |
| Send a welcome or relaunch email | Nothing - this is last | Links point to Beehiiv, not old Substack URLs |
How long does a Substack to Beehiiv migration actually take?
Nobody publishes hard numbers on this, so treat the ranges below as general planning estimates based on the setup steps involved, not measured data from a specific tool. Your actual time depends heavily on archive size, how many code blocks or embeds you use, and how clean your Stripe records already are. Use this to set expectations with yourself, not as a guarantee.
| List size | Subscriber export and import | Paid tier mapping | Archive cleanup | Billing shutdown |
|---|---|---|---|---|
| Around 1,000 subscribers | Under an hour | 1 to 2 hours | 1 to 3 hours | Under 30 minutes |
| Around 10,000 subscribers | 1 to 2 hours | 2 to 4 hours | 3 to 6 hours | Under 30 minutes |
| Around 50,000 subscribers | 2 to 4 hours | Half a day or more, depending on tier complexity | Half a day or more, depending on archive depth | Under 30 minutes |
The billing shutdown step is short at every size - the time risk is almost entirely in tier mapping and archive cleanup, not in clicking cancel on Substack.
Common migration risks and fixes
| Risk | Symptom | Fix | Severity |
|---|---|---|---|
| Double billing | A subscriber is charged on both Substack and Beehiiv | Pause or cancel Substack billing only after Beehiiv paid access is confirmed active | High |
| Paid access gap | A subscriber loses access to paid content mid-migration | Migrate and verify paid subscribers before canceling any old billing | High |
| Broken code blocks or embeds | Imported posts show plain text where formatted code used to be | Manually reformat affected posts after import, before announcing the switch | Medium |
| Lost recommendation network | Cross-promotion traffic drops after the move | Rebuild recommendations using Beehiiv's own growth features | Medium |
| Missing subscriber names | Personalization fields are blank after import | Substack's export may not include names - ask subscribers to update their profile post-migration | Low |
Beehiiv vs Substack for this migration
| Workflow need | Substack | Beehiiv | Best choice |
|---|---|---|---|
| Simple send-and-collect newsletter | Strong, minimal setup required | More setup steps to get to the same simplicity | Substack |
| Paid subscriber growth tooling | Basic | Stronger segmentation and growth features | Beehiiv |
| Free subscriber tags and segmentation | Limited | CSV-based tag and custom field mapping | Beehiiv |
| Built-in migration support | Export only, no receiving tooling | Dedicated Substack migration import flow | Beehiiv |
| Cost model on paid revenue | 10 percent creator fee plus Stripe fees, verify current terms | Plan and tier pricing instead of a revenue share, verify current terms | Depends on your subscriber count and margins |
The two platforms, evaluated for this move
Beehiiv
Best for: creators who want stronger growth tools, subscriber segmentation, and a more operational newsletter stack, especially once paid subscriptions are involved.
Not best for: operators who just want the simplest possible send-and-collect setup with minimal configuration.
Key strengths: dedicated Substack migration support, CSV subscriber import with tag and custom field mapping, a paid subscriber import flow that maps Stripe data into tiers, and a growth-oriented feature set built for scaling an audience.
Limitations: more setup complexity than Substack, and pricing is tied to plan and subscriber count rather than a flat rate - verify current plan pricing and terms directly with Beehiiv before you commit to a switch date.
If you have decided the migration is worth it, review Beehiiv's current migration documentation and plan pricing before you set a launch date.
Substack
Best for: simple publishing workflows and creators whose current monetization is already working without much operational overhead.
Not best for: creators who need advanced segmentation, growth tooling, or migration flexibility as their list scales.
Key strengths: familiar publishing experience, straightforward export tools for both subscribers and posts, and a clear own-your-content posture.
Limitations: a 10 percent creator fee on paid subscriptions plus Stripe processing fees, and limited built-in tooling for migration or advanced audience operations - verify current fee terms directly with Substack before assuming today's numbers still apply.
Common mistakes to avoid
- Migrating content before subscriber data, which leaves you with a rebuilt archive and no confirmed audience to read it.
- Canceling Substack billing before verifying that paid access works correctly on Beehiiv.
- Assuming code blocks, embeds, and recommendations will transfer cleanly - they generally will not.
- Changing your pricing tiers, your sending domain, and your content format all in the same week as the platform switch, which makes it hard to isolate what broke if something does.
- Skipping the subscriber count check after each export and import step, which is the cheapest way to catch a problem early.
Get outside help if: you have a large paid list, a complex Stripe setup with multiple products or tiers, or you simply cannot tolerate a billing mistake. A few hours of paid setup help is usually cheaper than a support backlog from double-charged subscribers.
How this fits your creator operating system
A platform migration is an acquisition and onboarding decision, not a content decision - the newsletter itself does not need to change, but the systems underneath it do. If you are building out a full creator operating system rather than just swapping tools, it is worth looking at how newsletter platform choice fits alongside your broader client and audience workflow. Start at the creator hub for related setup guides, or review the operating system guide for how acquisition tools fit into a one-person business overall. If you are still deciding whether to switch at all, the comparison hub and tools hub are good next stops before you commit to a migration date.
FAQ
How do I move subscribers from Substack to Beehiiv?
Export your email list as a CSV from Substack's Subscribers page, then import that file into Beehiiv, mapping any tags or custom fields you want to keep. Verify the total subscriber count in Beehiiv matches your Substack export before you move on to paid subscribers.
Can I move paid subscribers from Substack to Beehiiv?
Yes, but it needs care. Beehiiv has a dedicated paid subscriber import that maps Stripe subscription data into your Beehiiv tiers. Confirm each subscriber's renewal or expiration date before running the import, so nobody loses access or gets billed twice.
Will my Substack archive move over to Beehiiv?
Most of it will. Beehiiv's migration tooling can import your Substack posts, but code blocks come across as plain text and need manual reformatting, and Substack's recommendation network does not transfer at all and has to be rebuilt inside Beehiiv.
Do I need to cancel Substack before switching to Beehiiv?
No, and you generally should not cancel first. Migrate your subscribers and confirm paid access is working correctly on Beehiiv, then go back and pause or cancel Substack billing. Canceling too early is how subscribers end up losing access before the new platform is verified.
What data does Substack actually let me export?
You can export your email subscriber list from the Subscribers page and export your published posts from your posts dashboard. Substack's help documentation notes that subscriber names may not be included in the email export file, so do not plan on that data carrying over automatically.
Does Beehiiv import tags and custom fields from Substack?
Yes, Beehiiv's subscriber import supports mapping CSV columns to tags and custom fields during the free subscriber import, as long as those fields exist in Beehiiv before you run the import.
What happens to my Substack recommendations after I switch?
They do not carry over. Substack's recommendation network has no direct equivalent inside Beehiiv, so you need to rebuild cross-promotion relationships manually using Beehiiv's own growth features after the move.
How long does a Substack to Beehiiv migration take?
It depends heavily on your list size, archive complexity, and how clean your Stripe records are. As a general planning estimate rather than measured data, a simple newsletter with a few thousand subscribers might take a few hours total, while a large paid list with a complex archive can take the better part of a day or more, mostly in paid tier mapping and archive cleanup.
Is Beehiiv cheaper than Substack?
It depends on your subscriber count and which plan you need. Substack currently takes a 10 percent creator fee on paid subscriptions plus Stripe fees, while Beehiiv prices by plan tier and subscriber count rather than a revenue share. Compare your specific numbers against current terms on both platforms before deciding, since pricing on both sides can change.
Can I keep my old Substack posts live after I move to Beehiiv?
Generally yes, but decide on your redirect and archive strategy before you switch rather than after. If you plan to keep the old Substack URL active, make sure your new Beehiiv links are what you promote going forward so traffic and search authority start consolidating on the new platform.
Get the Solo Consultant OS Blueprint
Map your acquisition, onboarding, delivery, and automation stack. Free for subscribers.
- CRM setup and pipeline configuration
- Client onboarding automation walkthrough
- Proposal system with AI prompts
- Make scenario templates
Free for subscribers
No spam. Unsubscribe any time.
Related resources