Migration guide
Flodesk → beehiiv
Flodesk is the design-first creator email tool: gorgeous templates, near-flat $25 to $54/mo pricing, and a sub-count-agnostic billing model. beehiiv is the publication-and-monetization stack: native paid subscriptions, a referral program, an opt-in cross-promotion network, and an ad marketplace. The migration motivation is structural, not aesthetic. You did not outgrow Flodesk because the product got worse; you outgrew it because the work changed. The newsletter is now the business, and you need monetization and growth surfaces Flodesk intentionally does not ship.
Published · By the TierGauge editorial team
Moving to
beehiiv- Starting price
- Free
- Free plan
- Yes
- Plans
- 4
- Category
- Email marketing
When this migration makes sense
- Your newsletter is the primary product (or you want it to be), and the bottleneck is now growth and revenue, not how the email looks. The beehiiv referral program and recommendations network are first-class growth surfaces Flodesk has no equivalent for.
- You want native paid subscriptions, sponsorship storefront access, or the beehiiv ad network. Flodesk's Everything plan ships sales pages and checkout for digital products, but it has no native recurring-subscription billing for newsletter content and no ad-revenue layer.
- You publish frequently (weekly or more) and the visual-template lock-in inside Flodesk has become a friction tax. beehiiv's block editor is faster for high-cadence text-first sends.
When it doesn't
- Flodesk's design system is core to your brand and your audience associates the look with you. beehiiv's editor is well-built but it does not produce the same visual identity Flodesk is known for. If your brand IS the design, the migration costs more than it saves.
- You sell digital products or courses through Flodesk Checkout and the integrated sales-page-plus-email funnel is doing real conversion work. beehiiv has no equivalent integrated commerce; you would need a separate cart (Stripe, Gumroad, ThriveCart) plus separate landing pages.
- Your subscriber count is large (50,000+) and Flodesk's near-flat pricing gives you a cost structure beehiiv's tier ladder cannot match. Re-run the math at your specific tier; beehiiv Scale is $43/mo but real-world send volume often pushes you to Max ($96/mo) or above.
What you lose by leaving Flodesk
- Flodesk's design-first template library and the visual identity built around it.
- Near-flat pricing across the full subscriber range; beehiiv's tier ladder costs more once you cross 2,500 subs into the Scale tier.
- Integrated checkout and sales pages on the Everything plan ($54/mo); beehiiv has no equivalent native commerce layer.
- Workflow branching off segment joins and date triggers; beehiiv automations are flatter.
What you gain with beehiiv
- Built-in referral program: two-sided rewards for subscriber-driven growth, a $300+/mo separate tool elsewhere (SparkLoop, Beacon), and the standout beehiiv growth feature.
- Recommendations network: opt-in cross-promotion with other publications for compounding subscriber growth without paid acquisition.
- Ad network access on Scale and above: optional revenue layer for newsletters that hit minimum-engagement thresholds, no separate sponsorship hustle required.
- Native paid subscriptions through Stripe Connect with 0% take rate plus the publication-shaped product surface (multi-author seats, multiple publications on Scale and Max, sponsorship storefront).
Plan mapping at the entry paid tier
The lowest non-free, non-custom tier on each side. Use this for the "if I'm on $X with Flodesk, what's the equivalent on beehiiv?" gut check.
| Limit | Flodesk (Lite) | beehiiv (Scale) |
|---|---|---|
| Contacts | 25,000 subscribers | 100,000 subscribers |
| Emails / month | · | Unlimited |
| Team seats | 1 | 3 |
| Campaigns | · | 3 publications |
Step-by-step migration
- 01
Export your list from Flodesk
Pull a fresh CSV of every active subscriber. Capture the fields you actually use downstream: email is required, name is standard, signup date and tier (free/paid) are useful when Flodesk provides them.
- 02
Provision beehiiv
Sign up, set sender identity, and verify your sending domain (DKIM, SPF, DMARC). Do this before importing the list; sending from an unverified domain is the single fastest way to land in spam at the moment of cutover.
- 03
Import the list and map fields
Upload the CSV. Map email + name + any custom fields. Decide whether to import as one list or split into segments/tags. Flodesk-style organization rarely maps 1:1, so plan the split before the upload, not after.
- 04
Rebuild automations and templates
beehiiv's automation builder is structurally similar but won't import Flodesk's flows directly. Rebuild only what you actively use; the move is a chance to delete the unused ones rather than lift-and-shift dead infrastructure.
- 05
Send a test broadcast
Pick a small segment and send a real broadcast (not just a preview). Verify deliverability, link clicks, and unsubscribe flow. If anything's off, you find it before the announcement, not after.
- 06
Announce the move and cut over
Send your last broadcast from Flodesk announcing the new sender domain and what to expect. Cut over DNS and sending from beehiiv on the same day, not staggered. A dual-send week creates more confusion than it prevents.
Flodesk-to-beehiiv specific gotchas
Universal steps cover most of the work. These are the failure modes unique to this exact pair.
-
#1
Template rebuild: Flodesk emails are visual-template-anchored; beehiiv posts are block-based and lean text-first. Your existing template library does not import. Pick 2 or 3 send formats (weekly issue, announcement, paid-only post) and rebuild them as beehiiv post templates before the cutover so you are not designing from scratch on send day.
-
#2
Workflow rebuild: Flodesk Workflows trigger off subscribe, segment join, link click, and date. beehiiv automations are simpler (subscribe / unsubscribe / engagement events) and do not replicate Flodesk's branching workflows. Flatten complex sequences into linear ones or keep a Flodesk Free workspace running for the workflow-heavy slice.
-
#3
Checkout and sales-page handoff: if you use Flodesk Everything for digital-product checkout and sales pages, beehiiv does not replace either. Decide before the cutover: keep Flodesk Everything ($54/mo) running just for the commerce layer, OR migrate the digital-product side to a dedicated tool (Stripe + a landing-page builder, Gumroad, Lemon Squeezy) before switching primary email to beehiiv.
-
#4
Custom-domain and DKIM sequencing: Flodesk handles SPF and DKIM through its own DNS records; beehiiv issues a different set. Add beehiiv's records alongside Flodesk's, verify beehiiv authentication end-to-end, then warm beehiiv's sender on a small list segment for 7 to 14 days before flipping the from-address. Do not hard-cut a production sender.
Compare on price across the category
This guide is Flodesk to beehiiv specifically. To see both side by side with every other email marketing tool we track on a single price-only table, see the email marketing pricing comparison . Useful before committing to the migration, in case a third option fits the cost-and-feature combination better than either side of this guide.
Common questions
- Is beehiiv cheaper than Flodesk?
- Both start at the same headline price (Free). The reason to migrate is the pricing model and feature scope, not the entry-tier number.
- Will I lose subscribers in the move?
- Email lists transfer as raw addresses; subscriber relationships transfer with you because the addresses haven't changed. What you can lose: re-engagement (some readers won't notice the new sender domain immediately), paid subscriptions if Flodesk handles billing differently from beehiiv (the gotchas above call out the specific cases), and any "engagement" or warmth signals that Flodesk's deliverability inferred from your sending history. Plan a clear announcement and a deliverability warm-up week.
- How long does the migration take?
- For a list under 10,000 subscribers, a clean migration is one focused week: domain setup and verification, list import, automation rebuild, test broadcast, announcement, cutover. Larger lists or complex automations can stretch to 2 or 3 weeks. The constraint is rarely the import itself; it's the deliverability warm-up and the time to rebuild flows you actually depend on.
- Are Flodesk and beehiiv direct competitors?
- Yes. Both are primarily email marketing tools, which is why this is a defensible head-to-head migration rather than a cross-category consolidation.
- Where can I see Flodesk vs beehiiv side-by-side?
- The /compare/beehiiv-vs-flodesk page on TierGauge shows side-by-side plans, headline pricing, included features, and limit comparison at the entry paid tier. This migration guide is the long-form decision narrative; the compare page is the data-only dashboard.
Disclosure: the "Try beehiiv" link above is an affiliate link. We may earn a commission if you sign up. Pricing is the same; this guide's recommendations and the cost math are unchanged by commercial relationships. How we rank.
Sources
- Flodesk: https://flodesk.com/pricing
- beehiiv: https://www.beehiiv.com/pricing
Pricing verified . Migration mechanics are based on the public pricing pages and standard ESP migration patterns; verify destructive steps (DNS cutover, paid subscription transfer) against the vendor's current docs before executing.