®
Migration Journey
This path is for teams moving from Mailchimp, Klaviyo, ConvertKit, ActiveCampaign, Drip, WordPress transactional sending, or another email platform.
Goal
Move useful contacts, consent state, and sending workflows into Bento without importing stale risk or accidentally emailing people who opted out.
The riskiest migration mistake is importing every address as active. Preserve unsubscribes, bounces, complaints, and suppression state.
Recommended Path
- Read Contacts And Consent.
- Export active contacts, unsubscribers, bounces, complaints, tags, and key fields.
- Use the provider-specific migration guide where available.
- Import a clean active list with Import Contacts.
- Rebuild only the automations you still need.
- Send first to recently engaged contacts.
What To Preserve
Preserve:
- Active subscriber status.
- Unsubscribe status.
- Bounces and complaints.
- Purchase or lifecycle tags.
- Essential custom fields.
- Preference center data.
- Suppression lists.
Defer old campaign history unless you need it for reporting or compliance.
Cutover Checklist
- Old provider exports are archived.
- Unsubscribers are excluded from active imports.
- DNS is configured for Bento.
- First send uses a conservative audience.
- Old automations are paused only after Bento equivalents are tested.
- Support can find the migration source for any disputed subscriber.