Move from Customer.io to Bento.

Export your Customer.io data, bring it into Bento, and rebuild what matters while Customer.io keeps sending. Cancel only when Bento is ready.

Start free trial Plan your switch

Import from Customer.ioMedium migration

CSVcustomer-io-contacts.csv12,400 rows, mapped

SubscribersImports directly
TagsImports directly
Custom fieldsImports directly
AutomationsRebuild in Bento
TemplatesRebuild in Bento
Commerce dataPartly moves
Email historyStays behind

3 of 7kinds of data import directly

Laravel News
Examine
Less Annoying CRM
Geocodio
Authority Hacker
HeadshotPro
QuickMail

4.8/5 on G2

5/5 on Capterra

SOC 2 Type II, zero exceptions

Customer.io to Bento, at a glance.

From Bento's Customer.io migration guide. Still deciding? Read Bento vs Customer.io.

Medium

Migration difficulty

Varies by data model, channels, and workflows.

3 of 7

Kinds of data that import directly

The rest you rebuild in Bento or leave behind.

Export steps in Customer.io

Each one is written out below, with tips.

Your time depends on list size and how many flows you rebuild.

Four steps off Customer.io.

Customer.io keeps sending the whole time. You cancel only after Bento carries your mail.

Export from Customer.io.
4 steps in Customer.io, in the order below. Nothing changes for your subscribers yet.
Export from Customer.io4 steps
1Log in to Customer.ioGo to Customer.io and log in.
2Export PeopleGo to People > Segments. Export your main segments.
3Document CampaignsScreenshot campaign triggers, messages, and logic.
4Update Event TrackingPlan to update your event tracking code to Bento.
Keep Customer.io sending while you export.
Import into Bento.
Upload the CSV and map each column to a Bento field or tag. Suppressions go in first, so nobody who left gets mail.
AAcme
Settings
PeopleImportscustomer-io-contacts.csv
Start import
CSV columnBento fieldType
emailEmailIdentity
first_nameFirst nameField
last_nameLast nameField
tagsTagsTags
planplanCustom field
last_order_atlast_order_atCustom field
Rows
12,400
Before sending
Suppressions imported first
Unsubscribes kept unsubscribed
Tags created from the tags column
Test, then switch.
Authenticate your sending domain, rebuild the flow that earns the most, and send a seed test while Customer.io keeps sending.
Launch checklist4 of 5
Sending domain authenticated in Bento
Suppressions moved from Customer.io
Seed test sent and checked
Highest-revenue flow rebuilt and tested
Switch sending to BentoNext
Warm up with your most engaged subscribers first.
Cancel Customer.io last.
Warm up with your most engaged subscribers, move the rest of your sending, and cancel Customer.io only once Bento carries it.
Sending, by phase
PhaseCustomer.ioBento
ExportSendingNot yet
ImportSendingImporting
Rebuild and testSendingTesting
Warm upSendingWarming
Cancel Customer.ioOffSending
No gap in sending at any phase.

Export from Customer.io4 steps

1Log in to Customer.ioGo to Customer.io and log in.
2Export PeopleGo to People > Segments. Export your main segments.
3Document CampaignsScreenshot campaign triggers, messages, and logic.
4Update Event TrackingPlan to update your event tracking code to Bento.

Keep Customer.io sending while you export.

Export your Customer.io data.

Run these in Customer.io before you change anything there. Keep the files somewhere safe until Bento is sending.

1
Log in to Customer.io
Go to Customer.io and log in.
2
Export People
Go to People > Segments. Export your main segments.
3
Document Campaigns
Screenshot campaign triggers, messages, and logic.
4
Update Event Tracking
Plan to update your event tracking code to Bento.

What comes with you.

3 of 7 kinds of data import directly. The rest you rebuild in Bento or leave behind.

Your import checklist

Import from Customer.io3 of 7 direct

SubscribersImports directly
TagsImports directly
Custom fieldsImports directly
AutomationsRebuild in Bento
TemplatesRebuild in Bento
Commerce dataPartly moves
Email historyStays behind

Same ideas, new names

Customer.ioBento

PersonPersonSame concept
SegmentSegmentSame concept
CampaignAutomationTriggered workflows
NewsletterBroadcastOne-time sends
AttributeFieldCustom data

Before you cancel Customer.io

Map Customer.io profile identifiers and event properties before importing data
Document each trigger, condition, delay, and exit rule before rebuilding

In-app messaging features don't transfer
Event tracking code needs updating

Get a person to plan the move.

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.

Plan your switch Get a migration quote

A migration request

you@example.comMigration quote

We are on Customer.io with 12,400 contacts. We need to keep subscribers, tags, and suppressions.

Bento teamReplied

Thanks. Start with suppressions, then your list, then the flows that make money. We can review your domain setup before you send.

Teams switch for deliverability and stay for the support.

“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.

Questions about leaving Customer.io.

Will I lose my Customer.io data and campaigns when I switch?

Customer.io can export profiles, selected attributes, filtered groups, and object relationships to CSV. Campaign logic and templates need to be rebuilt, and event tracking or API calls need to point at Bento. Export required history and suppression data before closing the old account.

Will switching hurt my email deliverability?

No provider can guarantee inbox placement. Preserve suppressions, authenticate the sending domain, validate tracking links, and warm up with recent engaged recipients. Bento includes reputation monitoring and controls for batching or pausing sends.

How long does a Customer.io migration take?

Timing depends on the number of profiles, objects, channels, integrations, templates, and active journeys. Updating event tracking and rebuilding cross-channel workflows usually takes longer than importing profile data.

Will there be downtime?

No. Keep Customer.io running while you import, test, authenticate your sending domain, and warm up. Once Bento is ready, move your sending and phase out Customer.io.

Can the Bento team help if I get stuck?

Yes. The team can review your current setup, help you decide what to move first, and advise on deliverability, data mapping, and launch order.