Substack and Beehiiv want different things from a newsletter creator. Substack wants you to grow inside its network, Beehiiv wants to give you the tools to grow on your own, and the right choice depends on whether your audience already lives on Substack or still needs finding. This guide shows how to switch Substack to Beehiiv newsletter creators by newsletter creators, moving subscribers, archives, and paid memberships without a gap in publishing.
The publishing gap is the danger nobody plans for. A migration that pauses the newsletter for two weeks loses readers who never notice the return issue. The safe sequence imports subscribers, republishes archives, tests a paid post, and only then flips the sending domain, so readers see one uninterrupted newsletter instead of a move.
The Case for Moving, Stated Plainly
Teams usually reach this decision after months of small frustrations rather than one dramatic failure. The old tool still works, but every workaround added to it makes the next change harder, and the team slowly spends more time managing the tool than doing the work it was bought for. That slow drift is easy to ignore, because no single week looks bad enough to justify a project, yet the total cost across a year is often larger than the migration itself.
The second reason teams move is control. A newsletter creators that can explain its own structure, its sharing rules and its review dates keeps the benefit of any tool long after the initial enthusiasm fades. A team that relies on memory or on one enthusiastic person loses it when that person is busy or leaves. Written standards are dull, but they are what turn a good week into a good year, and they cost almost nothing to create compared with redoing work that was never recorded.
Timing matters as much as tool choice. Starting during a quiet period, with a small pilot and a clear review date, gives the team room to fix problems without pressure. Starting during the busiest period, with everything moving at once, turns small mapping errors into visible failures. Choose the pilot carefully, protect the review date, and let the pilot result decide the pace of the wider rollout rather than a calendar deadline set before anyone saw the real data.
There are several ways to carry out the work, and the right one depends on size, data quality and how much time the team can give it. The table below compares the realistic options, including what each one suits best. Judge each option against your own volume and skill, not against a sales claim, and run the cheapest option that still passes a trial with real work. A method that works on a sample but fails on real data is not a method, it is a demo.
| Option | What it involves | Best for |
|---|---|---|
| Built in or native importer | the Beehiiv Substack importer plus the Stripe customer migration flow in Subscribers Import | A team with a standard Substack setup |
| CSV export and manual import | A manual export cleaned in a spreadsheet before import, giving control over assignment | A team that needs to restructure during the move |
| Assisted or third party migration | A specialist service that handles mapping, batches and validation | A team with compliance, volume or deadline pressure |
Check the current plan details on substack.com and beehiiv.com before you commit, since pricing, limits and importer availability change. Vendor pages are the only reliable source for prices at decision time, and any figure quoted elsewhere, including in this guide, should be treated as a prompt to verify, not as a quote.
The honest limit to name early is this. Comments, Notes, video posts in some formats and exact paywall placement do not transfer cleanly. Welcome emails must be rebuilt as automations, and any chat or community feature needs a separate plan, since Beehiiv has no matching social layer. Accepting that limit in week one lets you schedule the rebuild work properly, while discovering it in launch week turns it into a crisis. Put the rebuild items on the project plan with owners and dates, and treat them as launch criteria, not as follow up tasks.
Mapping Every Item Before You Import
Work through the table below row by row as you switch Substack to Beehiiv newsletter creators with your own data, and mark each row as moves cleanly, needs rebuilding or needs a decision. Rows marked needs a decision are the ones to resolve before import, since deciding them afterwards means rework. Keep the completed table as the project record, because it answers most questions the team will ask during rollout, and it prevents the same decision being debated three times by three different people.
| Item | Where it goes | What to check |
|---|---|---|
| Free subscribers | Beehiiv free subscribers by CSV import | Verify counts and suppression lists match after import |
| Paid subscribers | Beehiiv paid tiers with Stripe migration | Recreate each subscription at the same price and billing cycle |
| Subscription tiers | Beehiiv pricing tiers | Mirror Substack tiers before starting the Stripe transfer |
| Post archive | Beehiiv posts by importer | Check paywalled posts, images and links on a sample |
| Custom domain | Beehiiv custom domain settings | Move DNS only after the new site is tested |
| Welcome email | Beehiiv automation | Rebuild the welcome sequence as an automation |
| Comments and Notes | No direct equivalent | Export or screenshot valued discussions before cutover |
| Video posts and chats | Rebuilt or dropped | Decide per item, since some formats have no match |
Two rows in that table usually cause the most trouble, and they are worth naming plainly. The first is anything involving permissions or sharing, since a wrong share can expose sensitive work or block a colleague at a critical moment. The second is anything involving history, since history that arrives flattened or unattributed looks complete but misleads anyone who relies on it. Test both rows in the pilot with real examples, and do not accept a vendor assurance in place of a test result.
Once the mapping is settled, the order of work matters as much as the mapping itself. Move the smallest meaningful slice first, verify it completely, and only then widen the move. That order limits the damage from any error, gives the team confidence from a real success, and creates a repeatable routine for the remaining slices. Teams that move everything at once rarely get that confidence, and they often spend the savings from speed on fixing errors that a pilot would have caught.
Running the Migration in Order
Follow the steps below in order, because each one builds on a finished earlier step. Skipping ahead to the import before the mapping is settled creates work that has to be redone, while following the order means the import itself is the easy part. Print the list for switch Substack to Beehiiv newsletter creators, tick each step off, and do not move on until the current step works with real data from the team.
- Export everything from Substack first. Export subscribers, posts and any other data Substack offers, and store the files safely. Exports are your fallback if an import step fails, and they also give you the counts you will compare against after import.
- Mirror tiers in Beehiiv before touching Stripe. Create Beehiiv pricing tiers that match Substack tiers exactly, including price and billing interval. The Stripe migration maps paid subscribers onto these tiers, so a tier created afterwards cannot receive them cleanly.
- Import free subscribers and check counts. Import the subscriber CSV, then compare total counts, paid counts and suppressed addresses against Substack. Investigate every gap now, since a missing subscriber is much harder to explain after the first issue goes out.
- Run the Stripe customer migration. Follow the Beehiiv Stripe migration flow, copying customers from the Substack connected Stripe account to the Beehiiv connected account and accepting the transfer. Most transfers complete quickly, but Stripe notes it can take up to three days, so start early.
- Recreate paid subscriptions and pause Substack billing. Once customers land in the new Stripe account, recreate their subscriptions at the same prices, then pause billing on Substack so nobody is charged twice. Double charging is the one error readers will not forgive, so verify a sample subscription before pausing the rest.
- Import the post archive and fix links. Import posts, then check paywall placement, images and internal links on the most read posts first. Beehiiv uses a similar post URL structure, which helps, but only if your custom domain moves across correctly.
- Warm up the new sending domain. Connect your domain, authenticate sending, and send the first issues to your most engaged readers before the full list. That order protects inbox placement on a new sending domain far better than blasting the whole list on day one.
- Announce the move and set the cutover issue. Tell readers the sender address is changing, what stays the same, and where to find the archive. Pick one issue as the first Beehiiv issue, and keep Substack live as an archive until that issue has landed cleanly.
Pre Cutover Checks
Use this checklist as the gate before you complete switch Substack to Beehiiv newsletter creators, not as an afterthought. Every item should have a name beside it and a date, since a checklist without owners is a wish list. Run through it with the people who will live with the result, not only with the person who set it up, because the people who use the system daily spot problems that the setup person cannot see. If an item fails, fix it and rerun the checklist, rather than waiving it under time pressure.
| Check | What good looks like |
|---|---|
| Tier mirror verified | Every Substack tier has a matching Beehiiv tier at the same price |
| Subscriber counts match | Free, paid and suppressed counts agree after import |
| Stripe transfer accepted | Customers visible in the Beehiiv connected Stripe account |
| No double billing risk | Substack billing paused only after subscriptions are recreated |
| Archive links tested | Top posts open correctly with paywalls in the right place |
| First issue sent to engaged readers | Warm up send completed before the full list send |
The rollback note deserves emphasis, because it is the item most plans skip. A rollback plan is not pessimism, it is professionalism. It states what triggers a pause, who decides, how the team returns to the old system, and how long that return stays possible. Writing it before cutover costs an hour. Needing it without having written it costs days of confusion, and it is usually needed on the one migration where nobody expected trouble.
Beehiiv takes no share of paid subscription revenue beyond Stripe processing fees, while Substack takes 10 percent plus Stripe fees. Beehiiv charges a plan fee instead, with a free tier up to 2,500 subscribers. Check both pricing pages, since the break even point depends on your paid count.
Also budget for the domain and deliverability work. A custom domain, authenticated sending and a warm up sequence cost time rather than money, but skipping them costs readers. Treat the first two issues as part of the migration budget, not as normal publishing, and measure opens and spam complaints on both.
Also check what happens when you stop paying. Your data, your history and your templates should stay yours in a usable form, and the export route should be tested before you depend on it. A system that holds data hostage is not a bargain at any price, and the time to discover that is before migration, not during an exit years later when the data matters most. When you switch Substack to Beehiiv newsletter creators, you are choosing a home for work that will outlive the project itself, so exit terms deserve the same attention as entry price.
Where Migrations Usually Go Wrong
The mistakes below are common because each one feels reasonable at the time. Read the list with the team, agree which mistake your setup is most likely to make, and put one guard in place against it, since a named mistake is far easier to avoid than a vague warning to be careful. The team that can name its likely mistake before starting has already avoided half of it, and the guard you put in place now is cheaper than the fix you will need later when you switch Substack to Beehiiv newsletter creators under deadline pressure.
- Starting Stripe before mirroring tiers. Paid subscribers need matching tiers to land on. Create tiers first, or the migration stalls halfway and readers sit in limbo while you fix pricing.
- Forgetting to pause Substack billing. Two active billing systems charge readers twice. Pause Substack billing only after new subscriptions are verified, and check a sample account end to end.
- Blasting the full list on a new domain. A new sending domain with no warm up lands in spam for a share of readers. Send to engaged readers first, watch delivery, then widen the send.
- Assuming comments and chats transfer. Comments, Notes and some video formats have no direct equivalent. Decide what to preserve before cutover, and tell readers honestly what changes.
- Moving DNS before testing. Pointing the domain at an untested site breaks archive links at the worst moment. Test on the Beehiiv domain first, then move DNS last.
Checking the Move Worked
Pick four numbers and track them monthly, because evidence beats feeling when judging whether switch Substack to Beehiiv newsletter creators is working. Choose numbers you can collect without extra admin, such as time saved, errors, completion rates or satisfaction, and record them in one place on the same day each month. A trend over three months tells you far more than a single good or bad week, which may reflect holidays, deadlines or one unusual event.
Compare the new numbers with the baseline recorded before the change, and be honest about what they say. If a number improves, keep doing what caused it and say so to the team, since people repeat work that is praised. If a number gets worse, change one thing, not five, so you can tell what helped. Changing five things at once leaves you guessing, even when the numbers improve.
Set a review date now, ninety days from launch, and put it in the calendar with the name of the person who owns the review. Without a named owner and a date, reviews slip, and a slipped review means a system that slowly stops matching the work. The review itself need not take long, since one hour with the four numbers and the user answers is enough to decide what to keep, what to change and what to stop.
One more consideration is how the team handles exceptions, because every workflow meets a case that does not fit the template. Decide in advance what happens then, whether the exception is handled by hand, escalated to a named person, or logged for a later template change. A workflow without an exception rule either breaks on the first odd case or gets quietly bypassed, and bypassed workflows teach people that the routine is optional. Write the exception rule beside the template, keep it to two sentences, and review it when exceptions start to repeat, since a repeated exception is really a missing step.
Training deserves a note of its own, because a workflow is only as good as the least confident person using it. Train in short sessions with real examples from your own work, let people practise with a colleague before they face a real task, and write the three most common questions and answers where everyone can see them. People who feel confident use the system, while people who feel unsure avoid it and fall back on old habits, which quietly recreates the very problem the workflow was meant to solve.
What to Watch After Go Live
The first two weeks after cutover decide whether the new system sticks or quietly loses to old habits. Staff will hit the first unfamiliar screen, the first missing shortcut and the first report that looks different, and each of those moments is a small decision point. If help is quick and the answer is written down, the new habit forms. If help is slow and the answer lives only in one person’s head, the old habit returns, and it returns without anyone announcing it. Plan the first two weeks as carefully as the migration itself, with named helpers, office hours and a visible list of known issues.
Start with a daily check in for the first five working days, kept to fifteen minutes and focused on blockers only. Ask each team what failed, what felt slow and what they worked around, and fix the workarounds first, since a workaround that survives a week becomes a permanent shadow process. Log every issue with its fix, and share the log where the whole team can read it, because the same question asked by five people costs five times as much as the same question answered once in public. Close each check in with one decision, even a small one, so the team sees progress rather than a growing list.
- Watch the first real task end to end in the new tool, not a demo task, and note every click that felt unnecessary or confusing.
- Check the most used report, queue or dashboard daily for the first week, and compare it with the old system until the numbers agree.
- Ask new joiners and occasional users first, since confident daily users hide problems that occasional users hit immediately.
- Review permissions and access requests weekly at first, because access problems are the fastest way to lose trust in a new system.
- Record every workaround the team invents, and turn the repeated ones into proper fixes or documented steps within the fortnight.
By the end of the second week, the questions should change character. Early questions are about where things live and how to do familiar tasks, while later questions are about edge cases, reporting and improvements. That shift is the signal that adoption is working, and it is worth naming in the review, since teams that expect questions to vanish entirely misread normal learning as failure. If questions have not shifted by week three, the problem is usually training or mapping, not attitude, and it deserves a focused fix rather than a reminder to try harder.
The ninety day review should then judge the move on the numbers chosen before launch, not on how people felt in launch week. Bring the four tracked numbers, the issue log and the list of rebuild items that were deferred, and decide what to keep, what to change and what to stop. Deferred rebuild items need dates at this review, or they drift forever, and the team should hear explicitly which deferred items are being dropped and why. A review that ends with dated decisions is a project closed properly, while a review that ends with general satisfaction is a project that will be reopened the next time someone asks why a report looks odd.
Support coverage during those first weeks deserves its own rota, not just good intentions. Name two people who can answer questions each day, rotate the role so it does not burn out one enthusiast, and give the rota holders time in their week to actually help. A rota that exists only on paper helps nobody, while a rota with protected time turns early confusion into quick answers and quick answers into confidence. Thank the rota holders publicly at the review, since visible thanks is what makes people volunteer for the next change.
Measure support volume as well as task outcomes during the first fortnight, since a falling question count with steady output is a better sign than either number alone. If questions stay high while output falls, the team is stuck rather than learning, and that pattern calls for more training or a mapping fix. If questions fall but output also falls, the team may have quietly stopped using the new tool, and that pattern calls for a direct conversation, not another tutorial. Numbers do not replace talking to people, but they tell you which conversations to have first.
Finally, write the one page handover that the next person will need. It should name the system owner, the review date, the mapping decisions that matter, the known gaps and where the exports and backups live. One page is enough, and one page will actually be read, while a long manual will not. Keep it beside the system, not in a personal drive, and update it at each review. That single habit is what turns a migration project into a system that survives staff changes, busy periods and the next tool decision, whenever that comes.
More Reading on Stratilyze
For the systems around this one, Stratilyze also covers a related Stratilyze guide a related Stratilyze guide a related Stratilyze guide Read the guide that matches your next bottleneck first, because fixing the biggest bottleneck next gives a larger gain than polishing a part of the work that already runs well.
Communication around the change matters as much as the setup itself. Tell the team what is changing, why it is changing, when it takes effect and where to get help, and say it in the channel they already read rather than in a new tool they have not adopted yet. A change announced once in one place will be missed by half the audience, so repeat the message at the pilot, at cutover and at the first review, and keep the wording consistent each time.
Finally, resist the urge to add features in the first month. The first month is for proving the core workflow with real work, fixing the mapping errors the pilot missed, and letting habits form. New features added during that period confuse the measurement, since you can no longer tell whether a change in the numbers came from the workflow or from the feature. Freeze the scope for ninety days, log feature requests for the review, and judge them then against the numbers rather than against enthusiasm.
Frequently Asked Questions
Do paid subscribers need to resubscribe on Beehiiv?
No, when the Stripe migration is done correctly. Customers are copied between Stripe accounts and their subscriptions are recreated at the same price, so readers keep access without signing up again. The step that protects this is mirroring tiers first and verifying a sample subscription before pausing Substack billing.
What does Beehiiv charge compared with Substack?
Substack takes 10 percent of paid revenue plus Stripe fees and charges no plan fee, while Beehiiv takes no share beyond Stripe fees but charges a plan fee. Small paid lists often cost less on Substack, while larger paid lists usually save money on Beehiiv. Run the maths on your own paid count before deciding.
Do my old post links keep working?
Usually yes, because Beehiiv uses a similar post URL structure and your custom domain moves across. Test the most linked posts after the domain move, and fix any paywall placement that shifted during import, since that is the part most likely to change.
What does not transfer from Substack?
Comments, Notes, some video posts and exact paywall placement do not carry over cleanly. Export or preserve anything you value before cutover, and rebuild welcome emails as Beehiiv automations rather than expecting them to import.
How long does the switch take?
A typical migration takes under a day for a small list, while a large archive or a big paid list deserves an afternoon or more. The Stripe step is the long pole, since Stripe notes transfers can take up to three days, so start it early and do not schedule cutover on the same day.
Will readers notice the sender change?
Yes, and that is why you announce it. Tell readers before the first Beehiiv issue that the sender address is changing, confirm the new address, and ask them to check spam if the first issue does not arrive. A short honest note prevents most support mail.
Making the Switch Stick
Start with the mapping table and the pilot, then the checklist, then the closure date, and do those three things before any wider rollout, because a wider rollout without them is how a promising move becomes a lingering parallel system. The team that runs a simple, written routine well will get more from the new tool than a team with a fancier setup and no routine, and that advantage grows every month the routine runs.
Pick the first step today, test it with real work tomorrow, and let the numbers over the next ninety days tell you what to improve next. That disciplined approach is what makes this kind of change pay, rather than becoming another project that starts with enthusiasm and fades within a month.
