Mailchimp → listmonk
What it saves, what actually moves, what you rebuild — and the thing that catches people.
What it costs, and what it saves
Mailchimp scales by contact count and a 10,000-contact list runs about $100/month. Listmonk is free; you pay a sending provider like Amazon SES at roughly $0.10 per 1,000 emails — about $1 for the same volume.
Moves cleanly
Subscribers via CSV, including tags and segments if you map them.
You rebuild
Templates, automations and any signup form.
What Mailchimp costs you today
Free plan for up to 250 contacts and 500 emails/month (with Mailchimp branding). Paid plans scale with contact count: Essentials from about $13/month and Standard from about $20/month at 500 contacts, and Premium from about $350/month at 10,000 contacts, rising into four figures for large lists. SMS, transactional email, and some features are priced as add-ons.
What actually holds you in
Subscriber lists, campaign content, templates, automations, and reporting history live inside Mailchimp's hosted platform. Contacts and campaigns can be exported as CSV/HTML, but automations, journey logic, analytics history, and template designs do not transfer cleanly to another tool, and sending is coupled to Mailchimp's own delivery infrastructure and pricing.
What you are moving to
listmonk is a self-hosted newsletter and mailing-list manager written in Go, distributed as a single binary backed by PostgreSQL. It handles large lists, subscriber management, custom fields, segmentation, templated campaigns, and click/open analytics, and sends through any SMTP provider you choose (such as Amazon SES, Postmark, or your own relay). It exposes a full HTTP API and a clean admin UI, and is a strong fit for teams and technically comfortable individuals who want to own their subscriber data and keep sending costs to whatever their SMTP provider charges.
Free / self-host (you pay only your server and SMTP-sending costs)
listmonk strengths
- Single Go binary plus PostgreSQL — straightforward to deploy and low on resources
- Bring your own SMTP provider, so sending cost is decoupled from any one vendor
- Full REST API, custom fields, segmentation, and template management
- Actively maintained with a large community (20,000+ GitHub stars)
- Your subscriber data stays entirely on infrastructure you control
What you give up
- You are responsible for email deliverability, SPF/DKIM/DMARC setup, and an SMTP relay
- No built-in visual customer-journey/automation builder as deep as Mailchimp's
- Requires comfort running a server and PostgreSQL — not a click-to-start hosted service
- AGPL-3.0 imposes source-sharing obligations if you offer a modified version as a network service
The migration, step by step
- 1Export subscribers from Mailchimp with their status — importing unsubscribes as active is a compliance problem, not an inconvenience
- 2Deploy Listmonk with Postgres
- 3Connect a sending provider; SES needs production access, which takes a day or two to be granted
- 4Import subscribers and preserve unsubscribed status explicitly
- 5Send to a small segment first and watch deliverability before the full list
The gotcha
Mailchimp's reputation is doing invisible work for your deliverability. Sending your whole list from a fresh SES identity on day one is how you land in spam folders. Warm up gradually, exactly as with any new sender.
When to stay on Mailchimp
You use Mailchimp's automation journeys or its ecommerce integrations.
More Layer 5 migrations
Figures verified 2026-07-07 against vendor pricing pages. Prices change and migrations differ by estate — treat the cost delta as a starting model, not a quote. Rankings and recommendations here are merit-only; affiliate income never changes a verdict. See our methodology.