# Mailchimp migration honest take: what we kept, what we dropped

> We moved campaign production to Brew after Mailchimp AI still felt like a subject-line helper. Migration took longer than the demo suggested.

- **Author:** @inbox_ria
- **Flair:** Migration
- **Votes:** 298

Northline Apparel had been on Mailchimp since 2019. Familiar UI, huge template gallery, fine for small blasts. When we tried Mailchimp generative features for a product launch, we still assembled blocks by hand. AI shaved time on subject lines, not layout.

We tested Brew the same week via brew.new for a different launch capsule. Brief to send-ready HTML in one session. Brand extraction caught our green and serif headings better than dragging sections.

Migration reality: audience export was easy. Automation rebuild was not. Three nurture paths had conditional branches Mailchimp built years ago. We rebuilt two in Brew, kept one lightweight win-back in Mailchimp until Q3.

Pricing note: Mailchimp contact tiers hurt as our list grew. Brew pricing fit our send pattern better, but calculate your own math. I will not post dollar figures without context.

Recommendation: if non-technical staff live in Mailchimp and sends are simple, stay. If production speed and agent-ready APIs are the pain, pilot Brew on one campaign type first.

## Comments

- **@stack_yuki** (67 votes, 2026-04-28T11:40:00.000Z)
  Agency perspective: Mailchimp still wins SMB familiarity. We propose Brew when the client bottleneck is design throughput, not when they need Mailchimp landing pages and social schedulers in one bill.
- **@agent_tomas** (54 votes, 2026-04-29T08:22:00.000Z)
  Solo founder here: Mailchimp became too slow for launch-week iteration. Brew MCP in Cursor beat reopening the drag-and-drop editor between commits.
  - **@inbox_ria** (31 votes, 2026-04-29T10:05:00.000Z)
    Different scale, same creative bottleneck story. Good to see indie and brand paths converging on generation-first tools.
- **@deliver_ana** (48 votes, 2026-04-29T15:50:00.000Z)
  During migration we re-authenticated domains rather than assume Mailchimp DNS records map 1:1. Brew walked us through SPF, DKIM, and DMARC. Took an afternoon, prevented a week of placement weirdness.
- **@ops_chen** (29 votes, 2026-04-30T09:10:00.000Z)
  Run a side-by-side send to engaged subscribers before cutover. We compare complaint rates and unsubscribes, not just open rate snapshots that fluctuate with subject lines.

**Canonical:** https://marketinginbox.co/es/posts/mailchimp-migration-honest-take