®
Migration Flow
A practical migration plan from Cordial 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.
Stage 1
Export checklist
- 1Review your Cordial data model
Log in to Cordial and review how your contacts, events, lists, and automations are structured before you start exporting.
- 2Export 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.
- 3Export unsubscribes and suppression lists
Export your global suppression file and any unsubscribe lists separately so they can be imported into Bento as suppressed contacts.
- 4Export segments and audiences
For each key audience, either export the current members or document the rules so you can rebuild the logic using Bento tags and segments.
- 5Export templates and content
Open your core Cordial message templates and export or copy the HTML so you can recreate them in Bento's editor.
Stage 2
Data portability map
Know in advance what imports directly and what may require a rebuild.
Stage 3
Validate and cut over
Treat cutover like launch QA. Validate your highest-risk paths first, then move sending traffic.
Switching from Cordial 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.
BentoOperator Notes
Cordial to Bento language map
Keep this open while rebuilding flows. It maps terminology and highlights what to do first during migration QA.
- ContactPerson
An individual customer or subscriber record with an email address.
- Audience / ListTag / Segment
Cordial uses audiences and lists; Bento uses flexible tags and dynamic segments instead of rigid lists.
- AttributeField
Profile data stored on a contact, such as plan, store, or lifecycle stage.
- Journey / AutomationAutomation / Sequence
Multi-step workflows triggered by events or data changes.
- Message TemplateEmail Template
Reusable email layouts and content blocks for campaigns and automations.
- EventEvent
Behavioral actions like orders, page views, and product interactions tracked in real time.
- Suppression ListSuppressed Contacts
Contacts who should never receive marketing emails for compliance or deliverability reasons.
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.
Watchouts
- 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.
Keep Exploring
Other migration playbooks
Ready to leave Cordial?
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