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
Export your Mandrill data, bring it into Bento, and rebuild what matters while Mandrill keeps sending. Cancel only when Bento is ready.
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.
Mandrill keeps sending the whole time. You cancel only after Bento carries your mail.
5 steps in Mandrill, in the order below. Nothing changes for your subscribers yet.
Rebuild your templates in Bento, import suppressions, then swap your API or SMTP settings.
Authenticate your sending domain, rebuild the flow that earns the most, and send a seed test while Mandrill keeps sending.
Warm up with your most engaged subscribers, move the rest of your sending, and cancel Mandrill only once Bento carries it.
Run these in Mandrill before you change anything there. Keep the files somewhere safe until Bento is sending.
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.
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.
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.
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.
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.
0 of 7 kinds of data import directly. The rest you rebuild in Bento or leave behind.
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.
“Moving to Bento was the best thing I ever did for my list and its profitability”
Iliane L.“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.“The support and community within Bento is hands down the best I've ever seen from any company, ever.”
Luke J.Free for 30 days. We help you move your lists, flows, and templates.