Move from Mandrill to Bento.

Export your Mandrill data, bring it into Bento, and rebuild what matters while Mandrill keeps sending. Cancel only when Bento is ready.

Import from MandrillMedium migration
CSVmandrill-suppressions.csvSuppressions and templates
  • SubscribersStays behind
  • TagsStays behind
  • Custom fieldsStays behind
  • AutomationsStays behind
  • TemplatesRebuild in Bento
  • Commerce dataStays behind
  • Email historyStays behind
0 of 7kinds of data import directly
  • Laravel News
  • Examine
  • Less Annoying CRM
  • Geocodio
  • Authority Hacker
  • HeadshotPro
  • QuickMail

Mandrill to Bento, at a glance.

From Bento's Mandrill migration guide. Still deciding? Read Bento vs Mandrill.

Medium

Migration difficulty

Varies by integration scope.

0 of 7

Kinds of data that import directly

The rest you rebuild in Bento or leave behind.

5

Export steps in Mandrill

Each one is written out below, with tips.

Your time depends on list size and how many flows you rebuild.

Four steps off Mandrill.

Mandrill keeps sending the whole time. You cancel only after Bento carries your mail.

  1. Export from Mandrill.

    5 steps in Mandrill, in the order below. Nothing changes for your subscribers yet.

    Export from Mandrill5 steps
    1. 1Review how you use Mandrill todayLog 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 templatesIn 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 settingsFrom 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 metadataGo 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 trafficIdentify 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.
    Keep Mandrill sending while you export.
  2. Point your app at Bento.

    Rebuild your templates in Bento, import suppressions, then swap your API or SMTP settings.

    TransactionalSetup guide

    .env

    - EMAIL_PROVIDER=mandrill

    + EMAIL_PROVIDER=bento

    • Templates rebuilt in Bento
    • Suppressions imported
    • Sending domain authenticated
  3. Test, then switch.

    Authenticate your sending domain, rebuild the flow that earns the most, and send a seed test while Mandrill keeps sending.

    Launch checklist4 of 5
    • Sending domain authenticated in Bento
    • Suppressions moved from Mandrill
    • Seed test sent and checked
    • Highest-revenue flow rebuilt and tested
    • Switch sending to BentoNext
    Warm up with your most engaged subscribers first.
  4. Cancel Mandrill last.

    Warm up with your most engaged subscribers, move the rest of your sending, and cancel Mandrill only once Bento carries it.

    Sending, by phase
    PhaseMandrillBento
    1. ExportSendingNot yet
    2. ImportSendingImporting
    3. Rebuild and testSendingTesting
    4. Warm upSendingWarming
    5. Cancel MandrillOffSending
    No gap in sending at any phase.

Export your Mandrill data.

Run these in Mandrill before you change anything there. Keep the files somewhere safe until Bento is sending.

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

    TipThis inventory keeps your migration focused on real flows instead of unused configs.

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

    TipYou will recreate these in Bento's template editor so focus on structure and variables, not pixel perfect layout.

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

    TipYou will add similar records for Bento so keep this next to access for your domain registrar.

  4. 4

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

    TipYou will recreate the same coverage with Bento events and webhooks.

  5. 5

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

    TipRun both providers in parallel briefly so you can compare delivery and logs.

What comes with you.

0 of 7 kinds of data import directly. The rest you rebuild in Bento or leave behind.

Your import checklist

Import from Mandrill0 of 7 direct
  • SubscribersStays behind
  • TagsStays behind
  • Custom fieldsStays behind
  • AutomationsStays behind
  • TemplatesRebuild in Bento
  • Commerce dataStays behind
  • Email historyStays behind

Same ideas, new names

MandrillBento
  • Transactional MessageTransactional EmailOne to one email triggered by an event in your app.
  • SubaccountSiteSeparate project or environment for a product or brand.
  • TagTagLabel that groups emails or people for reporting and segmentation.
  • Merge VarField or Liquid variableDynamic data that personalizes content inside a template.
  • WebhookEvent WebhookHTTP callback that notifies your app about deliveries, opens, clicks, and bounces.
  • Sending DomainVerified DomainDomain you send from with SPF and DKIM set up.

Before you cancel Mandrill

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

Get a person to plan the move.

Tell us your current provider, list size, and what you need to keep. We map the order to move things and review your domain setup before you send.

A migration request

you@example.comMigration quote

We are on Mandrill with 12,400 contacts. We need to keep templates and suppressions.

Bento teamReplied

Thanks. Start with suppressions, then your list, then the flows that make money. We can review your domain setup before you send.

Teams switch for deliverability and stay for the support.

“Moving to Bento was the best thing I ever did for my list and its profitability”
Iliane L.G2
“I love how easy it is to use to design SaaS emailing sequences. You can also see rapidly which campaigns are the money makers. But what I love the most is undoubtedly the deliverability that you have once you've set up custom domain tracking”
Arnaud B.G2
“The support and community within Bento is hands down the best I've ever seen from any company, ever.”
Luke J.G2

Questions about leaving Mandrill.

What happens to my existing Mandrill templates?
You will copy or export the HTML from Mandrill, then recreate templates in Bento. Many teams use this chance to simplify layouts and move personalization into Bento events and fields.
Will my deliverability change when I switch from Mandrill?
Deliverability can change during any provider migration. Plan domain authentication, warmup for high-volume sends, suppression list imports, and staged traffic before you cut over fully. Compare bounce and complaint rates on matched flows rather than assuming inbox placement stays identical.
How long does a typical Mandrill migration to Bento take?
Timing varies by integration scope. A single app with a few templates may finish in an afternoon. Many subaccounts, inbound routes, webhook dependencies, and parallel environments can take longer. DNS propagation and staged testing often add calendar time beyond the initial API swap.
Will there be downtime?
No. Keep Mandrill running while you import, test, authenticate your sending domain, and warm up. Once Bento is ready, move your sending and phase out Mandrill.
Can the Bento team help if I get stuck?
Yes. The team can review your current setup, help you decide what to move first, and advise on deliverability, data mapping, and launch order.

Other migration guides.

Start your move from Mandrill.

Free for 30 days. We help you move your lists, flows, and templates.