Migration Flow
A practical migration plan from iContact 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.
Export checklist
- 1Review your iContact account
Log in to iContact and review your lists, segments, and automations so you know what needs to move.
- 2Export contacts from iContact
Go to the contacts area, filter by list or segment, choose the contacts you want to move, then select the export option and download a CSV file with all standard and custom fields.
- 3Repeat exports for key lists or segments
If you use multiple lists or segments in iContact, export each one so you can recreate them as tags or segments in Bento.
- 4Clean your data before import
Open the CSV in a spreadsheet tool, remove obvious invalid addresses, and make sure custom field names are clear.
- 5Import contacts into Bento
Create a new import in Bento, upload your CSV, map columns to properties and tags, and choose how to handle unsubscribed contacts.
Log in to iContact and review your lists, segments, and automations so you know what needs to move.
Data portability map
Know in advance what imports directly and what may require a rebuild.
Validate and cut over
Treat cutover like launch QA. Validate your highest-risk paths first, then move sending traffic.
White-glove migration
Switching from iContact 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.
Migration coverage
Bring your whole sending setup with you.
<1 day
Typical switch window
1:1
Migration support
Zero
Forced add-ons
Operator Notes
iContact to Bento language map
Keep this open while rebuilding flows. It maps terminology and highlights what to do first during migration QA.
- ContactPerson
A single subscriber or customer in your database.
- ListTag
Bento encourages tagging people instead of locking them into fixed lists.
- SegmentSegment
Rule based groups of people built from behavior and properties.
- Autoresponder or SeriesAutomation workflow or sequence
Automated journeys that send based on rules and events.
- Custom FieldsCustom properties
Extra data you store on each person such as plan, lifecycle stage, or location.
- Suppressed or Inactive ContactsSuppressed contacts
People you should not mail, such as unsubscribed and hard bounces.
- Campaign ReportsBroadcast analytics
Performance data for one off sends like opens, clicks, and revenue.
Tips
- Export active and recently engaged contacts, plus every suppressed status needed to prevent accidental sends.
- Rebuild key journeys in Bento instead of copying every legacy autoresponder from iContact.
- Use batched and paused sending in Bento for your first campaigns while you watch engagement and deliverability.
- Add the $30/mo Bento Chat add-on only if shared inbox and live chat are part of the target setup.
Watchouts
- Do not import unsubscribed, complained, or hard bounced contacts from iContact as active subscribers.
- Automations and drip sequences do not migrate automatically and must be recreated in Bento.
- Historical open and click data from iContact will not appear in Bento reports so treat early sends as a fresh baseline.
Keep Exploring
Other migration playbooks
Ready to leave iContact?
Move with confidence: export cleanly, import safely, and launch on Bento with migration support from our team.