BentoMigrate from Mandrill to Bento
Step by step guide to move from Mandrill to Bento. Learn how to export templates and settings, update APIs, and switch transactional traffic safely at your pace.
Migration Steps and Data Transfer
DATA TRANSFER
What transfers from Mandrill?
Here's what data we can migrate from your current platform to Bento.
Contacts & Segments
All your subscribers, tags, and custom fields transfer seamlessly.
Email History
Email history transfers partially based on platform limitations.
Commerce Data
Commerce data may require reconnection to your store.
STEP-BY-STEP
Export from Mandrill
Follow these steps to export your data and prepare for migration.
1. Review how you use Mandrill today
Log in to Mailchimp, open the Transactional Email or Mandrill section, and list the sending domains, API keys, templates, and webhooks you rely on.
2. Export and copy your templates
In the Mandrill templates area, open each template you still use and copy the HTML source, or use the templates API to pull them as JSON for reference.
3. Capture sending domains and DNS settings
From Mandrill or Mailchimp transactional settings, note each verified sending domain plus the SPF, DKIM, and tracking records that are currently in DNS.
WHY SWITCH
Why migrate from Mandrill?
Here's why teams are making the switch to Bento.
Reason 1
All your product, marketing, and transactional email in one app instead of a Mandrill add-on.
Reason 2
All features included from day one, including automation, transactional email, and deliverability tooling.
Reason 3
Deliverability tools, batched sending, free validation, and real human support plus community.
TERMINOLOGY & MIGRATION GUIDE
Mandrill → Bento Translation
Different platforms use different terms. Here's how Mandrill concepts map to Bento, plus tips for a smooth migration.
One to one email triggered by an event in your app.
Separate project or environment for a product or brand.
Label that groups emails or people for reporting and segmentation.
Dynamic data that personalizes content inside a template.
HTTP callback that notifies your app about deliveries, opens, clicks, and bounces.
Domain you send from with SPF and DKIM set up.
Migration Tips
- Pull your contact lists from Mailchimp or your own database, not Mandrill, since Mandrill is not a full CRM.
- Use the migration as a chance to consolidate Mandrill and Mailchimp into a single Bento account.
- Start by moving high value flows like signups, password resets, and receipts before lower priority messages.
- Warm up new Bento sending domains gradually if you send high volumes.
Watch Out For
- Mandrill does not store a complete marketing audience so do not treat it as the only source of truth for subscribers.
- API keys, webhooks, and SMTP settings are different in Bento so plan time for code changes and testing.
- Keep Mandrill active for a short overlap so you can fall back if something unexpected appears in production.
We've been building Bento for 7 years and 310 days.
Come help us build the next generation of email marketing and automation software. We'll see you inside.
30-Day Trial • Fast Setup
Other Migration Guides
Explore guides for other platforms