ONLINE
Bento
Mandrill logo
toBentoMigration path

Migration Guide

Move from Mandrill to Bento with zero guesswork.

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.

mediummigration2-4 hours0 core transfers ready
G2 LeaderCapterra ShortlistSOC-2 Compliant

Migration Flow

A practical migration plan from Mandrill to Bento

This guide follows a simple sequence: export cleanly, map data correctly, then validate before cutover. No generic product pitch, just the steps your team needs.

1Export from Mandrill
2Transfer and map in Bento
3Validate and launch

Stage 1

Export checklist

  1. 1Review 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. 2Export 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. 3Capture 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.

  4. 4Document webhooks and metadata

    Go to the webhooks section and record each endpoint URL, the events it listens for, and any custom metadata or headers you set in Mandrill.

  5. 5Plan API changes and test traffic

    Identify where your app calls Mandrill's API or SMTP, map those calls to Bento's API or SMTP, then test in a staging environment with a small slice of traffic before full cutover.

Export Steps
Export checklistMandrill → Bento
1
Review how you use Mandrill today
2
Export and copy your templates
3
Capture sending domains and DNS settings
0 of 5 steps complete
Data Transfer
Migration coverageMandrill → Bento
Subscribers
Pending
Tags
Pending
Custom Fields
Pending
Automations
Pending
Templates
Pending
Commerce Data
Pending
Transferring data from Mandrill...

Stage 2

Data portability map

Know in advance what imports directly and what may require a rebuild.

SubscribersNot portable
TagsNot portable
Custom fieldsNot portable
AutomationsNot portable
TemplatesRebuild in Bento
Email historyNot portable
Commerce dataNot portable

Stage 3

Validate and cut over

Treat cutover like launch QA. Validate your highest-risk paths first, then move sending traffic.

Send a seed-list test from Bento and verify rendering, links, and tracking.
Compare list and segment counts against Mandrill before your first live send.
Rebuild high-value automations first, then test each trigger path before cutover.
Keep Mandrill running for a short overlap while you monitor deliverability in Bento.
Migration Process
White‑glove migrationETA: 24–48 hours
0%
Bento
Contacts & TagsPending
Custom FieldsPending
AutomationsPending
24-48 hour white-glove migration
Migration

Switching from Mandrill can be done in one focused session

We help you map lists, rebuild key automations, and validate deliverability before cutover so your first week on Bento is smooth.

Your current ESP
BentoBento
Progress0%
Contacts and attributesPending
Lists and segmentsPending
Templates and flowsPending
Sending setupPending
Migration complete! Ready to send.

Operator Notes

Mandrill to Bento language map

Keep this open while rebuilding flows. It maps terminology and highlights what to do first during migration QA.

Mandrill→Bento
  • Transactional MessageTransactional Email

    One to one email triggered by an event in your app.

  • SubaccountSite

    Separate project or environment for a product or brand.

  • TagTag

    Label that groups emails or people for reporting and segmentation.

  • Merge VarField or Liquid variable

    Dynamic data that personalizes content inside a template.

  • WebhookEvent Webhook

    HTTP callback that notifies your app about deliveries, opens, clicks, and bounces.

  • Sending DomainVerified Domain

    Domain you send from with SPF and DKIM set up.

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.

Watchouts

  • 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.

Keep Exploring

Other migration playbooks

Browse full directory

Ready to leave Mandrill?

Move with confidence: export cleanly, import safely, and launch on Bento with migration support from our team.

Free30-day trial·No credit card required·Book a demo