Migrate from Mandrill — now Mailchimp Transactional — to a European transactional stack without a marketing plan tied to it

Not while you stay on Mandrill. The Mailchimp marketing plan has been a hard requirement since April 2016 and the fall 2025 rebrand to Mailchimp Transactional did not change it. Standard at $20/mo is the cheapest path; the Essentials and Free plans remain ineligible regardless of how the rest of your stack looks. For a 100K/mo Mandrill customer running 4 blocks, the marketing-plan tax is around 20% of the bill — non-trivial but not catastrophic. For a 2M/mo customer on Premium $350 (which some enterprise sales paths push), the tax is on the same order of magnitude as a dedicated IP.

The teams we see migrating off most aggressively are the ones where the Mailchimp marketing plan is unused dead weight. If your marketing is on HubSpot, Customer.io, Klaviyo, Brevo, or built in-house, the Standard $20-Premium $350 is paying for an interface no one in your company logs into. Our model removes that line item — single-product transactional service, no marketing-plan precondition. For teams that do use Mailchimp marketing campaigns alongside transactional, the dual-subscription is genuinely a feature (unified billing, marketer-editable templates), and we will not pretend otherwise.

For pure operational use, 30 days is enough. You investigate a delivery question the same week, you tune a complaint pattern within the same campaign cycle, you do not normally need to look at a password reset from four months ago. The places this gets uncomfortable are audit, dispute resolution, regulatory inquiry, and chargeback evidence. A payment processor asking "show us the proof that you sent the order confirmation on May 14" three months later finds an empty log. A regulator asking healthcare or financial services for proof of customer notification finds the same. A chargeback dispute team needing to prove dispatch notification finds the same.

The standard workaround is to capture every send and webhook event into your own data warehouse — S3, BigQuery, Redshift, Snowflake — and treat Mandrill's dashboard as a 30-day live view rather than the system of record. Most teams that have been on Mandrill for more than 12 months have already set this up. The teams who have not, but who need long retention, are the ones for whom this argument lands hardest. On our side, 365-day retention is standard, and longer retention tiers are available for industries where seven-year audit retention is the operating norm.

Mandrill (now Mailchimp Transactional) sits inside Intuit, which is US-headquartered. Like nearly all US cloud providers serving EU customers, Mailchimp relies on the EU-US Data Privacy Framework (certified July 2023) for lawful transfer of personal data from the EEA, UK, and Switzerland to its US servers. The DPF replaced the Privacy Shield framework that the CJEU invalidated in Schrems II in 2020. In December 2025, NOYB issued a public advisory that the DPF is under serious legal pressure, citing the SCOTUS Trump v. Slaughter case challenging FTC independence — the FTC being a key pillar of the enforcement architecture the European Commission required when approving the DPF. SCOTUS oral arguments were heard in December 2025 and a ruling is widely expected in June or July 2026.

If the DPF is invalidated or materially weakened, Mailchimp's contractual fallback is the Standard Contractual Clauses, which automatically apply via the Data Processing Addendum. The problem with SCCs after Schrems II is that they require a Transfer Impact Assessment demonstrating that US surveillance laws (FISA Section 702, the CLOUD Act) do not undermine the protections — a demonstration that has become legally difficult to make after Microsoft's French subsidiary admitted under oath at the French Senate in June 2025 that it cannot guarantee data sovereignty against US authorities. None of this stops Mandrill from sending mail; it raises the procurement and DPO bar for using it lawfully under GDPR. On our side, the question does not arise — we are EU-incorporated, our servers are in Stockholm and Frankfurt, our DPA is between two EU entities.

Not directly. We do not run SMS infrastructure ourselves, and we do not plan to. The carrier relationships, the country-by-country phone-number compliance, the short-code economics, and the SMS fraud landscape are a different operational discipline from email deliverability, and the providers who do it well — MessageBird (now Bird), Sinch, Twilio — do it at a scale we would not match. For teams that need transactional email plus transactional SMS, the pattern that works is: email through us, SMS through Bird or Sinch. Both have clean transactional APIs and reasonable EU jurisdiction options if that matters to your DPO.

The unified email+SMS API that Mandrill ships post-rebrand is a real convenience for omnichannel notification flows. If that convenience is the load-bearing reason you are on Mandrill, the migration calculus changes. Most teams we talk to use SMS for password recovery or 2FA only, where the per-message cost is dominated by carrier fees and the email-side savings on our infrastructure swamp the SMS routing slightly less consolidated. We work through the math case by case.

Mostly yes, with some custom-helper review. Mandrill uses Handlebars as the base template language with a layer of custom helpers and the merge_vars personalization syntax that has been stable since the original Mandrill release. Our template engine is closer to standard Handlebars, with the same merge-variable substitution pattern and conditional block syntax. The migration script our team runs typically handles 90% of the syntax conversion automatically. The 10% that needs manual review is usually deeply nested conditionals, Mandrill-specific helpers (the {{#equal}} family in particular has subtle differences across providers), and Mailchimp-side template imports that pulled in template fragments from the marketing platform.

For teams using Mandrill stored templates via the API (messages/send-template.json), the template names and merge variables get re-created on our side during week 1. The application code typically does not need to change beyond pointing the SMTP credentials or REST endpoint at us. For teams using Handlebars rendering on the application side and Mandrill purely as a relay, even less changes.

Inbound transfers cleanly. Mandrill's inbound webhook routes parsed inbound messages to your application endpoint, typically used for reply-to-ticket creation, conversation threading, or downstream automation. We ship the same pattern: inbound webhook routing with parsed JSON payloads matching the SES/Mandrill schema closely. The MX records get switched during week 1 alongside the SPF and DKIM updates. Most inbound integrations need no application-side changes beyond updating the webhook signature verification logic to use our HMAC scheme instead of Mandrill's.

The one edge case is teams using Mandrill's Rules Engine for inbound — a feature that lets you define server-side conditions on inbound messages (e.g., route messages with a specific subject pattern to one endpoint, others to another). Our equivalent is webhook-side routing logic that you implement on your end, which is more flexible but moves the conditional logic out of the provider configuration and into your application code. The migration usually simplifies this; teams who tried to keep the Mandrill Rules Engine config inside the provider often find their own webhook router cleaner once it is centralized.

For the first 12 months and the right buyer, yes — the discount is real. The eligibility is narrow: new Mandrill customer, enrolled or enrolling in Standard/Premium/Legacy Monthly with an account created in the last 90 days, in an eligible country, no compliance holds. If you meet all of those, the 50% off on 1M+ emails for 12 months is one of the better headline offers in the transactional market. At 2M/mo (80 blocks), the discount saves roughly $640/mo for a year, which is meaningful.

What the promo does not change is what happens in month 13. The list price returns to the standard volume tier, the marketing-plan precondition remains, and any structural concerns around log retention or sovereignty are unchanged. For teams whose migration drivers are cost-only and whose volume hits the promo eligibility cleanly, sticking with Mandrill for the 12 months and migrating in month 11-12 is a legitimate strategy. We have done several migrations exactly on that schedule and we say so openly when the customer's primary driver is the headline price during the promotional window.