BentoMigrate from Cordial to Bento
Step-by-step guide to migrate from Cordial to Bento. Learn how to export contacts, templates, and suppression lists and rebuild key journeys without losing deliverability.
Migration Steps and Data Transfer
DATA TRANSFER
What transfers from Cordial?
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 Cordial
Follow these steps to export your data and prepare for migration.
1. Review your Cordial data model
Log in to Cordial and review how your contacts, events, lists, and automations are structured before you start exporting.
2. Export contacts and profile attributes
From your contacts or audience section, export all active subscribers as CSV including email, status, and key attributes you want to keep.
3. Export unsubscribes and suppression lists
Export your global suppression file and any unsubscribe lists separately so they can be imported into Bento as suppressed contacts.
WHY SWITCH
Why migrate from Cordial?
Here's why teams are making the switch to Bento.
Reason 1
Per-user pricing with unlimited emails, not per-contact or per-email charges.
Reason 2
All features included from day one, including automation, transactional email, and shared inboxes.
Reason 3
Built-in deliverability infrastructure, free email validation, and batched sending so operators stay in control.
TERMINOLOGY & MIGRATION GUIDE
Cordial → Bento Translation
Different platforms use different terms. Here's how Cordial concepts map to Bento, plus tips for a smooth migration.
An individual customer or subscriber record with an email address.
Cordial uses audiences and lists; Bento uses flexible tags and dynamic segments instead of rigid lists.
Profile data stored on a contact, such as plan, store, or lifecycle stage.
Multi-step workflows triggered by events or data changes.
Reusable email layouts and content blocks for campaigns and automations.
Behavioral actions like orders, page views, and product interactions tracked in real time.
Contacts who should never receive marketing emails for compliance or deliverability reasons.
Migration Tips
- Migrate one key journey at a time so your team can test and learn Bento's automation model.
- Use Bento's free email validation before your first big send to clean any legacy Cordial data.
- Run Bento alongside Cordial for a short overlap so you can compare performance before turning Cordial off.
- Tag imported contacts by source, such as 'from-cordial', so you can report on performance after the switch.
- Work with your data team to keep any existing CDP in place while Bento takes over messaging.
Watch Out For
- Email engagement history from Cordial will not import into Bento, so reporting will start fresh from your first sends.
- Complex cross-channel journeys with mobile or in-app steps will need to be simplified or rebuilt around email and SMS.
- Do not cancel your Cordial account until you have fully imported suppression lists and tested key flows in Bento.
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