beehiiv’s webinar, How to Migrate From Substack on Your Lunch Break, makes a compelling point: the mechanical part of a platform move can be quick. Export subscribers from Substack, upload a CSV to beehiiv, import posts, and begin publishing from a newly customized site. But for a creator or small business, the real task is not a software migration. It is an audience operations project.
That distinction matters because the asset being moved is not merely a list of email addresses. It is a collection of relationships, consent records, paid subscriptions, reader preferences, historical content, and acquisition data. A rushed switch can technically succeed while still creating avoidable churn, broken links, or a muddled welcome experience.
Start with a migration inventory—not an import button
Substack gives publishers ways to export subscriber data and publication posts. Subscriber exports are available as CSV files, while post exports can be generated from the publication’s exports area. (support.substack.com) Before importing anything, make a simple inventory of what you have:
- Free, paid, comped, gifted, and expired subscribers
- Tags, source data, interests, signup dates, and engagement fields
- Free posts, premium archives, podcasts, audio, and video
- Your sending domain and website domain
- High-traffic evergreen URLs and referral links
The webinar highlights beehiiv’s ability to map incoming subscriber fields and apply tags during import. That is more important than it sounds. A tag such as substack-migration-2025, for example, lets you compare the behavior of your legacy audience with readers acquired later through referrals, partnerships, or your website.
Don’t import every field simply because it exists. Import the data you will actually use: acquisition source, interests, subscription status, lifetime value, and a useful engagement indicator. Then build segments around decisions you expect to make—such as who should receive a paid upgrade offer, a local event invitation, or a re-engagement campaign.
Protect the reader experience during the handoff
One of the easiest mistakes is sending a generic “welcome” automation to people who have been reading for years. They are not new subscribers; they are established readers encountering a new publishing home.
Instead, create a dedicated migration email that answers four questions plainly:
- What is changing?
- What is staying the same?
- Do readers need to take any action?
- Where should they update preferences or contact you?
Use this as an opportunity to reset expectations. Tell readers whether the publishing schedule, sender address, membership benefits, or site experience will change. If the move enables a sharper editorial format, more useful automations, or a redesigned archive, say so. Platform changes feel less disruptive when framed as an investment in the reader experience rather than an administrative announcement.
Content import is useful, but verify the exceptions
beehiiv supports a Substack content-import workflow for newsletter posts, and its migration documentation recommends setting a default post template before importing so older articles inherit the intended styling. (beehiiv.com) That can save substantial cleanup time for a written archive.
Still, do not assume every format will transfer perfectly. beehiiv’s current documentation says its Content Import tool does not import Substack audio or video posts; those need to be recreated manually with native audio uploads or embeds. (beehiiv.com) Similarly, paid content and paid subscribers deserve a separate QA pass. beehiiv’s paid-subscriber import process requires an active connected Stripe account and access to the relevant prior Stripe account. (beehiiv.com)
The practical lesson: migrate free written content in bulk, then create a checklist for premium posts, podcasts, media embeds, custom pages, and purchase states. Test them as a reader would.
SEO continuity depends on your domain strategy
“Keeping SEO” is not automatic just because posts appear on a new platform. The cleanest path is to retain control of a custom domain and point it to the new site. beehiiv says that when a publication uses a custom domain, publishers can mirror that setup so backlinks and traffic to older posts redirect to the new beehiiv site. (beehiiv.com)
Before launch, identify your top pages in search and referral analytics. Confirm that their old URLs resolve correctly, that page titles and canonical settings are sensible, and that internal links in navigation and popular posts are updated. A migration is also a good moment to improve archive structure and create conversion-focused landing pages for your best topics.
The business case is larger than design freedom
The webinar positions customization, recommendations, referral programs, automations, and analytics as reasons to move. Those features may be valuable, but the economic calculation is often the clearest trigger for a paid publication. Substack says it takes 10% of each paid transaction, in addition to Stripe-related fees. (support.substack.com) beehiiv says it takes no percentage of paid subscription revenue, though Stripe processing fees still apply. (beehiiv.com)
That does not make one platform universally better. Substack’s network and product ecosystem can be meaningful advantages for some writers. But if your next stage depends on a more distinct site, more controlled lifecycle messaging, and a larger share of subscription revenue, migration can be a growth decision—not just a cost-cutting exercise.
The “lunch break” part may be true for an initial CSV import. The durable version of the move takes a little longer: audit the data, preserve the links, communicate clearly, and use the new platform’s segmentation and automation capabilities from day one.