Mailchimp Transactional (Mandrill) is winding down. Here's the migration path

Mandrill (Mailchimp Transactional) has spent the last few years narrowing who can actually use it: tighter coupling to a paid Mailchimp account, less standalone availability, and less investment relative to newer transactional-only providers. If you're on Mandrill and reading this, you probably already know why you're looking, this isn't news to you. The migration itself is fairly contained, since Mandrill's core sending API is a simple JSON POST, not a complex integration surface.

The sending call

Mandrill's messages/send endpoint takes a message object with html, text, subject, from_email, from_name, and a to array of {email, name, type} objects. The shape is close enough to Envello's from/to/subject/html/text fields that this is a mapping exercise, not a rewrite:

• from_email + from_name combine into Envello's single from field ("Name <email>" format)
• to array of objects becomes a plain array of addresses or a single string
• html and text map directly
• merge_vars (Mandrill's per-recipient template variables) don't have a direct Envello equivalent for batch personalization; render each recipient's content in your own code before sending if you were relying on this

What honestly doesn't carry over

Mandrill grew up alongside Mailchimp's marketing tooling, so some accounts lean on features (detailed engagement analytics tied into Mailchimp's broader reporting, certain template-management workflows) that don't have a one-to-one match in a focused transactional API like Envello's. If your usage is genuinely transactional, plain sends with logging and webhooks, this won't matter. If you were using Mandrill as a lighter-weight extension of your Mailchimp marketing setup, budget time to figure out which parts of that setup need a different home entirely.

Cutover

Same shape as any provider switch: add Envello's SPF, DKIM, and DMARC records alongside your existing ones, swap the API key, and route a small percentage of traffic first while watching Envello's log search (90 days of history by default) before widening the rollout.