Migrations, 43 curated
Switching tools is a project. Plan it.
Each guide covers why teams migrate this specific pair, the plan mapping at the entry tier, what you lose by leaving, what you gain by moving, and the pair-specific gotchas that bite during cutover. Curated, not auto-generated. Grouped below by what you're leaving.
- Guides
- 43
- Source tools covered
- 26
- Destination tools
- 23
- Multi-direction tools
- 22
Pick what you're leaving
Tools with multiple migrate destinations let you compare options side-by-side instead of locking in the first one you read.
Switching from Mailchimp 6 options
- Mailchimp → MailerLite
Mailchimp's pricing escalates fast as your contact list grows.
- Cost reduction
- Tier-ratchet escape
to MailerLite: from freeRead guide - Mailchimp → Kit
Mailchimp's Standard tier ratchets fast as a creator's list grows; at 5,000 contacts it's $75 to $100/mo before send-volume overages.
- Creator-focused
- Add commerce
to Kit: from freeRead guide - Mailchimp → beehiiv
Mailchimp is built for small-business email marketing; beehiiv is built specifically for newsletter operators.
- Newsletter-first
- Monetization built-in
to beehiiv: from freeRead guide - Mailchimp → Omnisend
Mailchimp added e-commerce features over time; Omnisend was built for e-commerce from day one.
- E-commerce native
- SMS unified
to Omnisend: from freeRead guide - Mailchimp → Flodesk
Mailchimp prices by contact count, with the Standard tier hitting $20-$100+ a month as your list grows past 5,000 contacts.
- Flat pricing
- Design-led
- Creator-focused
to Flodesk: from freeRead guide - Mailchimp → Buttondown
Mailchimp is the bigger-ecosystem default ESP; Buttondown is the privacy-first à-la-carte newsletter platform.
- Cost reduction
- À la carte pricing
- Privacy-first
to Buttondown: from freeRead guide
Switching from MailerLite 4 options
- MailerLite → Kit
Kit costs more than MailerLite at every tier ($33 Creator vs $10 Growing Business at the 1k-subscriber anchor).
- Add commerce
- Creator-focused
- Feature upgrade
to Kit: from freeRead guide - MailerLite → Mailchimp
Inverse of the long-standing mailchimp-to-mailerlite cost-driven migration path.
- Brand recognition
- Integration ecosystem
- Inverse migration
to Mailchimp: from freeRead guide - MailerLite → Flodesk
Inverse of iteration 174's flodesk-to-mailerlite path; closes the flodesk-mailerlite bidirectional pair.
- Inverse migration
- Design-led upgrade
- Volume crossover
to Flodesk: from freeRead guide - MailerLite → beehiiv
MailerLite is a generalist ESP optimized for small business and light e-commerce; beehiiv is purpose-built for newsletter operators who care about growth and revenue.
- Newsletter-native
- Growth tooling
to beehiiv: from freeRead guide
Switching from Kit 3 options
- Kit → beehiiv
Kit (formerly ConvertKit) and beehiiv target the same creator audience but solve different jobs.
- Growth tooling
- Newer product
to beehiiv: from freeRead guide - Kit → Customer.io
Kit is a creator-OS: tag-based subscribers, visual automations, built-in commerce.
- Feature upgrade
- Custom data model
- Multi-channel
to Customer.io: from $100Read guide - Kit → MailerLite
Inverse of iteration 116's mailerlite-to-kit path; closes the kit-mailerlite bidirectional pair.
- Inverse migration
- Cost reduction
- Bundled website
to MailerLite: from freeRead guide
Switching from Substack 3 options
- Substack → Kit
Substack takes 10% of paid subscription revenue plus Stripe fees forever.
- No revenue share
- Add commerce
to Kit: from freeRead guide - Substack → beehiiv
Beehiiv is the closest like-for-like Substack experience without revenue share.
- No revenue share
- Growth tooling
to beehiiv: from freeRead guide - Substack → Ghost
Substack takes 10% of paid subscription revenue forever, plus Stripe fees.
- No revenue share
- Open source
- Publisher-owned
to Ghost: from $18Read guide
Switching from Crisp 2 options
- Crisp → Help Scout
Inverse of iteration 154's help-scout-to-crisp path.
- Email-first archetype
- HIPAA on Pro
- Inverse migration
to Help Scout: from freeRead guide - Crisp → Intercom
Inverse of iteration 108's intercom-to-crisp path; closes the crisp-intercom bidirectional pair.
- Inverse migration
- Messenger depth
- Per-workspace to per-seat
to Intercom: from $29Read guide
Switching from Flodesk 2 options
- Flodesk → MailerLite
Flodesk's design-led template aesthetic is the product's signature; MailerLite is the friendly affordable ESP.
- Cost reduction
- Automation depth
- Design tradeoff
to MailerLite: from freeRead 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.
- Newsletter-native
- Add monetization
to beehiiv: from freeRead guide
Switching from Intercom 2 options
- Intercom → Help Scout
Intercom prices per seat ($29 / $85 / $132) and is built around the chat messenger as the primary UX.
- Cost reduction
- Email-first archetype
- HIPAA on Pro
to Help Scout: from freeRead guide - Intercom → Crisp
Intercom prices per seat ($29 / $85 / $132 per seat per month).
- Per-seat to flat
- Cost reduction
to Crisp: from freeRead guide
Switching from Mailgun 2 options
- Mailgun → Resend
Mailgun and Resend both ship a transactional-email API, but they target different eras of developer tooling.
- Cost reduction
- Developer DX
- Platform consolidation
to Resend: from freeRead guide - Mailgun → Postmark
Both are mature transactional-email APIs in the spine; Mailgun (owned by Sinch) is positioned around volume + deliverability tooling + dedicated-IP infrastructure, while Postmark (owned by ActiveCampaign) is positioned around the deliverability-obsession + 365-day data retention + inbound-email-parsing combo at narrower volume bands.
- Deliverability focus
- Compliance retention
- Inbound primary
to Postmark: from freeRead guide
Switching from Omnisend 2 options
- Omnisend → Mailchimp
Inverse of the iteration-95 mailchimp-to-omnisend path.
- Beyond e-commerce
- Integration ecosystem
- Inverse migration
to Mailchimp: from freeRead guide - Omnisend → beehiiv
Omnisend is built for Shopify and BigCommerce stores: pre-built abandonment flows, SMS bundled with email, contact-tier pricing tied to your customer database.
- Add monetization
- Newsletter-native
to beehiiv: from freeRead guide
Switching from beehiiv 1 option
Switching from Buttondown 1 option
Switching from Cal.com 1 option
Switching from Calendly 1 option
Switching from Customer.io 1 option
Switching from Drip 1 option
Switching from Ghost 1 option
Switching from Help Scout 1 option
Switching from Leadpages 1 option
Switching from Lemlist 1 option
Switching from Mixpanel 1 option
Switching from PostHog 1 option
Switching from Postmark 1 option
Switching from Resend 1 option
Switching from Tally 1 option
Switching from Typeform 1 option
Popular destinations
Tools that show up as the destination in two or more guides. If you're researching whether to switch TO one of these, the cluster below shows every published origin path: who came from where, with what tradeoffs.
Switching to beehiiv 9 origin paths
- Substack → beehiiv
Beehiiv is the closest like-for-like Substack experience without revenue share.
- No revenue share
- Growth tooling
from Substack: from freeRead guide - Mailchimp → beehiiv
Mailchimp is built for small-business email marketing; beehiiv is built specifically for newsletter operators.
- Newsletter-first
- Monetization built-in
from Mailchimp: from freeRead guide - Kit → beehiiv
Kit (formerly ConvertKit) and beehiiv target the same creator audience but solve different jobs.
- Growth tooling
- Newer product
from Kit: from freeRead guide - Ghost → beehiiv
Ghost gives you full editorial ownership and an open-source code base; beehiiv gives you the newsletter-growth toolkit (referrals, ad network, recommendations) out of the box.
- Open-source to managed
- Built-in growth tooling
from Ghost: from $18Read guide - MailerLite → beehiiv
MailerLite is a generalist ESP optimized for small business and light e-commerce; beehiiv is purpose-built for newsletter operators who care about growth and revenue.
- Newsletter-native
- Growth tooling
from MailerLite: from freeRead guide - Buttondown → beehiiv
Buttondown is a delight to write in: clean markdown editor, privacy-first defaults, transparent a-la-carte pricing, indie-bootstrap product cadence.
- Growth tooling
- Newsletter-native
from Buttondown: from freeRead 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.
- Newsletter-native
- Add monetization
from Flodesk: from freeRead guide - Omnisend → beehiiv
Omnisend is built for Shopify and BigCommerce stores: pre-built abandonment flows, SMS bundled with email, contact-tier pricing tied to your customer database.
- Add monetization
- Newsletter-native
from Omnisend: from freeRead guide - Drip → beehiiv
Drip is built for e-commerce stores: cart abandonment, post-purchase, browse-abandonment flows tied to Shopify/BigCommerce/WooCommerce events.
- Add monetization
- Newsletter-native
from Drip: from $39Read guide
Switching to Kit 5 origin paths
- Substack → Kit
Substack takes 10% of paid subscription revenue plus Stripe fees forever.
- No revenue share
- Add commerce
from Substack: from freeRead guide - Mailchimp → Kit
Mailchimp's Standard tier ratchets fast as a creator's list grows; at 5,000 contacts it's $75 to $100/mo before send-volume overages.
- Creator-focused
- Add commerce
from Mailchimp: from freeRead guide - MailerLite → Kit
Kit costs more than MailerLite at every tier ($33 Creator vs $10 Growing Business at the 1k-subscriber anchor).
- Add commerce
- Creator-focused
- Feature upgrade
from MailerLite: from freeRead guide - beehiiv → Kit
Inverse of the kit-to-beehiiv path.
- Add commerce
- Creator-focused
- Inverse migration
from beehiiv: from freeRead guide - Customer.io → Kit
Inverse of iteration 153's kit-to-customer-io path.
- Inverse migration
- Cost reduction
- Operational simplicity
from Customer.io: from $100Read guide
Switching to MailerLite 3 origin paths
- Mailchimp → MailerLite
Mailchimp's pricing escalates fast as your contact list grows.
- Cost reduction
- Tier-ratchet escape
from Mailchimp: from freeRead guide - Flodesk → MailerLite
Flodesk's design-led template aesthetic is the product's signature; MailerLite is the friendly affordable ESP.
- Cost reduction
- Automation depth
- Design tradeoff
from Flodesk: from freeRead guide - Kit → MailerLite
Inverse of iteration 116's mailerlite-to-kit path; closes the kit-mailerlite bidirectional pair.
- Inverse migration
- Cost reduction
- Bundled website
from Kit: from freeRead guide
Switching to Crisp 2 origin paths
- Intercom → Crisp
Intercom prices per seat ($29 / $85 / $132 per seat per month).
- Per-seat to flat
- Cost reduction
from Intercom: from $29Read guide - Help Scout → Crisp
Help Scout charges per user ($25 / $45 / $75 per user/month for Standard / Plus / Pro).
- Cost reduction
- Per-seat to flat
- Chat-first
from Help Scout: from freeRead guide
Switching to Flodesk 2 origin paths
- Mailchimp → Flodesk
Mailchimp prices by contact count, with the Standard tier hitting $20-$100+ a month as your list grows past 5,000 contacts.
- Flat pricing
- Design-led
- Creator-focused
from Mailchimp: from freeRead guide - MailerLite → Flodesk
Inverse of iteration 174's flodesk-to-mailerlite path; closes the flodesk-mailerlite bidirectional pair.
- Inverse migration
- Design-led upgrade
- Volume crossover
from MailerLite: from freeRead guide
Switching to Help Scout 2 origin paths
- Intercom → Help Scout
Intercom prices per seat ($29 / $85 / $132) and is built around the chat messenger as the primary UX.
- Cost reduction
- Email-first archetype
- HIPAA on Pro
from Intercom: from $29Read guide - Crisp → Help Scout
Inverse of iteration 154's help-scout-to-crisp path.
- Email-first archetype
- HIPAA on Pro
- Inverse migration
from Crisp: from freeRead guide
Switching to Mailchimp 2 origin paths
- Omnisend → Mailchimp
Inverse of the iteration-95 mailchimp-to-omnisend path.
- Beyond e-commerce
- Integration ecosystem
- Inverse migration
from Omnisend: from freeRead guide - MailerLite → Mailchimp
Inverse of the long-standing mailchimp-to-mailerlite cost-driven migration path.
- Brand recognition
- Integration ecosystem
- Inverse migration
from MailerLite: from freeRead guide
Switching to Postmark 2 origin paths
- Mailgun → Postmark
Both are mature transactional-email APIs in the spine; Mailgun (owned by Sinch) is positioned around volume + deliverability tooling + dedicated-IP infrastructure, while Postmark (owned by ActiveCampaign) is positioned around the deliverability-obsession + 365-day data retention + inbound-email-parsing combo at narrower volume bands.
- Deliverability focus
- Compliance retention
- Inbound primary
from Mailgun: from freeRead guide - Resend → Postmark
Resend is the developer-experience-first transactional API: clean SDK surface, React Email templates, fast onboarding.
- Deliverability
- Compliance retention
from Resend: from freeRead guide
Switching to Resend 2 origin paths
- Postmark → Resend
Postmark and Resend are both transactional email APIs, but they price differently and they ship different developer experiences.
- Volume value
- Developer DX
- Modern API
from Postmark: from freeRead guide - Mailgun → Resend
Mailgun and Resend both ship a transactional-email API, but they target different eras of developer tooling.
- Cost reduction
- Developer DX
- Platform consolidation
from Mailgun: from freeRead guide
What we cover before writing one
Every guide is hand-written. We add a new one only when the pair passes a checklist:
- Both tools are in the spine with verified pricing data, so the plan mapping section is real, not guessed.
- The migration is a real path teams actually take, not a thin "alternative" framing. We need a non-trivial reason somebody would do this.
- We can describe at least three pair-specific gotchas (data export shape, integration reconnection, billing-cycle alignment, branding continuity) that wouldn't be obvious from the standard pricing diff.
- We can be honest about who SHOULDN'T migrate. Every guide has a good-fit and bad-fit section so the answer isn't always "yes, switch."
If you'd find a guide useful that isn't here yet, email [email protected] with the from / to pair and what's driving the migration.