Migration guide
Mailchimp → Buttondown
Mailchimp is the bigger-ecosystem default ESP; Buttondown is the privacy-first à-la-carte newsletter platform. Move from Mailchimp to Buttondown when (a) your subscriber count is below 1,000 and Mailchimp's contact-tier ratchet is now the dominant cost, (b) you want à-la-carte feature pricing rather than the 'pay for the whole bundle even if you only want one feature' model, or (c) you want a privacy-conscious indie-tool that minimizes tracking and respects subscriber data. The migration is cost-driven at low subscriber counts and editorial-fit-driven at any scale; not a fit if Mailchimp's CRM, customer-journey builder, or integration ecosystem is load-bearing.
Published · By the TierGauge editorial team
When this migration makes sense
- Your subscriber list is under 1,000 and Mailchimp's per-contact pricing has started climbing past $20/mo. Buttondown Free covers up to 100 subscribers; the $9/mo paid tier covers small lists at a flat fee with no contact-tier ratchet.
- You want à-la-carte feature pricing. Buttondown's $9 / $29 / $79 add-on tiers let you pay only for what you use (paid subscriptions, multiple newsletters, custom domain archives, whitelabeling) rather than Mailchimp's bundled tiers where you pay for everything in the tier.
- Privacy is genuinely a value for you or your audience. Buttondown markets itself privacy-first: minimal tracking, no third-party pixel injection by default, transparent data-handling. Mailchimp's tracking is more pervasive and enabled by default.
- Your newsletter is the entire business and you don't need Mailchimp's CRM, customer-journey builder, or commerce-adjacent features. If it's a newsletter, send it; Buttondown's UX is calibrated for that one job.
- You appreciate indie-bootstrap tooling. Buttondown is a small team with a transparent product roadmap and direct founder access; Mailchimp is Intuit-owned and structurally different.
- You write in markdown or want clean RSS-to-email. Buttondown ships native markdown editing and clean RSS-to-email pipelines; Mailchimp's editor is WYSIWYG-first with markdown as a secondary option.
When it doesn't
- You depend on Mailchimp's customer-journey builder for multi-step automated flows beyond simple welcome sequences. Buttondown has automations on the $29 add-on tier but the depth and trigger taxonomy don't match Mailchimp Standard's 200-flow allowance.
- You use Mailchimp's lightweight CRM for B2B contact tracking. Buttondown is newsletter-only; no CRM equivalent.
- Your subscriber list is past 5,000 and you're already on Mailchimp Standard. Buttondown's pricing model still works at higher volumes (the add-on fees stay flat regardless of subscriber count) but the integration ecosystem and reporting depth at scale favor Mailchimp's mature product.
- You depend on Mailchimp's predictive segmentation, multivariate testing, or send-time optimization. Buttondown doesn't ship these.
- Your team uses Mailchimp's broader integration ecosystem (Salesforce, HubSpot, Shopify connectors, plus 300+ third-party apps). Buttondown's integration surface is smaller and indie-tool-shaped.
- You want Mandrill for transactional email under the same roof. Buttondown is newsletter-only; transactional email needs a separate vendor (Postmark, Resend, Mailgun).
What you lose by leaving Mailchimp
- Mailchimp's customer-journey builder for multi-step branching flows.
- Lightweight CRM for B2B contact tracking and meeting-booking.
- Predictive segmentation, multivariate testing, send-time optimization on Standard / Premium.
- 300+ integration ecosystem (Salesforce, HubSpot, Shopify, etc.).
- Mandrill for transactional email as a same-roof add-on.
- Brand-name vendor recognition for stakeholder approval.
- Mailchimp's e-commerce features and abandoned-cart automation if you use them.
What you gain with Buttondown
- Cost reduction at small subscriber counts. Buttondown $9/mo flat add-on tier vs Mailchimp Essentials $13/500 subs scaling per-contact past the 250-subscriber free tier.
- À-la-carte feature pricing model. Pay only for what you need (paid subs, multiple newsletters, custom domain archives, whitelabeling) rather than bundled tier upgrades.
- Privacy-first defaults. Minimal tracking, no third-party pixel injection by default, transparent data-handling. Real differentiator if your audience values it.
- Native markdown editing and clean RSS-to-email pipelines. Mailchimp supports markdown as a secondary option but the editor is WYSIWYG-first.
- Indie-bootstrap tooling alignment. Direct founder access, transparent product roadmap, smaller-team product cadence.
- Newsletter-focused UX. No CRM clutter, no commerce navigation, no journey-builder maze. If you send newsletters and you don't need anything else, the product surface is calibrated for that one job.
- Paid subscriptions on $9 add-on tier. Mailchimp doesn't ship native paid-subscription billing; you'd add Stripe / a separate cart.
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 Mailchimp, what's the equivalent on Buttondown?" gut check.
| Limit | Mailchimp (Essentials) | Buttondown ($9 add-ons) |
|---|---|---|
| Contacts | 500 contacts (anchor; scales up) | Custom |
| Emails / month | 5,000 sends (10x contacts) | · |
| Team seats | 3 | · |
| Automations | 4 flow steps | · |
| Campaigns | 3 audiences | · |
Step-by-step migration
- 01
Export your list from Mailchimp
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 Mailchimp provides them.
- 02
Provision Buttondown
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. Mailchimp-style organization rarely maps 1:1, so plan the split before the upload, not after.
- 04
Rebuild automations and templates
Buttondown's automation builder is structurally similar but won't import Mailchimp'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 Mailchimp announcing the new sender domain and what to expect. Cut over DNS and sending from Buttondown on the same day, not staggered. A dual-send week creates more confusion than it prevents.
Mailchimp-to-Buttondown specific gotchas
Universal steps cover most of the work. These are the failure modes unique to this exact pair.
-
#1
Audience-to-list flattening: Mailchimp's audience model (multiple audiences, each separately billed) doesn't map to Buttondown's single-list-with-tags model. If you have multiple Mailchimp audiences representing different brands or product lines, decide BEFORE importing whether they merge into one Buttondown list (with brand-tags) or whether you spin up separate Buttondown accounts. Each Buttondown account has its own billing.
-
#2
Custom-fields rebuild: Mailchimp custom merge fields don't 1:1 map to Buttondown's metadata. Audit which merge fields drive automation logic (subject-line personalization, conditional content); rebuild only the load-bearing 3-5 fields. The other 80% of merge fields are usually contact-info (name, location) that Buttondown handles via its built-in metadata.
-
#3
Customer-journey rebuild: Mailchimp's customer journeys (multi-step automation flows) don't transfer to Buttondown. If you've invested in customer-journey logic (welcome series, re-engagement, abandoned-cart on Standard's e-commerce), audit which flows are load-bearing; rebuild as Buttondown automations on the $29 add-on tier or as simple sequences. Don't expect import.
-
#4
Email-template differences: Mailchimp's drag-drop visual editor produces HTML structurally different from Buttondown's markdown-first composition. Templates that depend on specific Mailchimp-block components (image grids, button rows, structured layouts) need re-authoring in Buttondown's editor. The migration is a reasonable trigger to rationalize down to 2-3 essential templates.
-
#5
Sender-domain DNS: Mailchimp issues `mc.us<region>.list-manage.com` patterns; Buttondown issues `buttondown.email`-related DKIM and SPF records. Add Buttondown's records alongside Mailchimp's; verify Buttondown's authentication; warm Buttondown's sender for 7-14 days on a percentage of traffic before flipping the from-address. Don't hard-cut a production sender.
-
#6
Reporting model shift: Mailchimp's reports center on campaign performance dashboards with granular subscriber-engagement metrics. Buttondown's reports are simpler (open rates, click rates, growth chart). If you've built ops processes around specific Mailchimp report formats or regular dashboard exports, audit before migrating.
Compare on price across the category
This guide is Mailchimp to Buttondown 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 Buttondown cheaper than Mailchimp?
- 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 Mailchimp handles billing differently from Buttondown (the gotchas above call out the specific cases), and any "engagement" or warmth signals that Mailchimp'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 Mailchimp and Buttondown 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 Mailchimp vs Buttondown side-by-side?
- The /compare/buttondown-vs-mailchimp 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.
Sources
- Mailchimp: https://mailchimp.com/pricing/marketing/
- Buttondown: https://buttondown.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.