Move from Plunk to Bento.

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

Start free trial Plan your switch

Import from PlunkMedium migration

CSVplunk-contacts.csv12,400 rows, mapped

SubscribersImports directly
TagsImports directly
Custom fieldsImports directly
AutomationsRebuild in Bento
TemplatesPartly moves
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

Plunk to Bento, at a glance.

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

Medium

Migration difficulty

Varies by contacts, workflows, and hosting model.

3 of 7

Kinds of data that import directly

The rest you rebuild in Bento or leave behind.

Export steps in Plunk

Each one is written out below, with tips.

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

Four steps off Plunk.

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

Export from Plunk.
6 steps in Plunk, in the order below. Nothing changes for your subscribers yet.
Export from Plunk6 steps
1Review your Plunk workspace and clean dataSign in to your Plunk dashboard and review contacts, segments, and automations so you know what needs to move to Bento.
2Extract active contacts from PlunkUse the contact-listing API or the data access available to your self-hosted deployment to extract subscribed contacts with their email addresses and custom fields.
3Preserve unsubscribed, bounced, and complained contactsCollect subscription state and delivery-failure records through the Plunk API, activity data, or your self-hosted database, then keep them separate from active contacts.
4Document key segments and filtersRecord the conditions behind each important Plunk segment and preserve the contact fields and events those conditions reference.
5Copy important templates and flowsOpen your key Plunk campaigns and flows, copy the email HTML or content, and store them in a document or files that you will use to recreate templates and automations in Bento.
6Import data into Bento and recreate automationsUse Bento CSV importers to bring in contacts, custom fields, and suppression lists, then rebuild your core flows as Bento automations and send test messages before going live.
Keep Plunk 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
PeopleImportsplunk-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 Plunk keeps sending.
Launch checklist4 of 5
Sending domain authenticated in Bento
Suppressions moved from Plunk
Seed test sent and checked
Highest-revenue flow rebuilt and tested
Switch sending to BentoNext
Warm up with your most engaged subscribers first.
Cancel Plunk last.
Warm up with your most engaged subscribers, move the rest of your sending, and cancel Plunk only once Bento carries it.
Sending, by phase
PhasePlunkBento
ExportSendingNot yet
ImportSendingImporting
Rebuild and testSendingTesting
Warm upSendingWarming
Cancel PlunkOffSending
No gap in sending at any phase.

Export from Plunk6 steps

1Review your Plunk workspace and clean dataSign in to your Plunk dashboard and review contacts, segments, and automations so you know what needs to move to Bento.
2Extract active contacts from PlunkUse the contact-listing API or the data access available to your self-hosted deployment to extract subscribed contacts with their email addresses and custom fields.
3Preserve unsubscribed, bounced, and complained contactsCollect subscription state and delivery-failure records through the Plunk API, activity data, or your self-hosted database, then keep them separate from active contacts.
4Document key segments and filtersRecord the conditions behind each important Plunk segment and preserve the contact fields and events those conditions reference.
5Copy important templates and flowsOpen your key Plunk campaigns and flows, copy the email HTML or content, and store them in a document or files that you will use to recreate templates and automations in Bento.
6Import data into Bento and recreate automationsUse Bento CSV importers to bring in contacts, custom fields, and suppression lists, then rebuild your core flows as Bento automations and send test messages before going live.

Keep Plunk sending while you export.

Export your Plunk data.

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

1
Review your Plunk workspace and clean data
Sign in to your Plunk dashboard and review contacts, segments, and automations so you know what needs to move to Bento.
TipArchive test projects and remove old segments so you do not import noise into your new account.
2
Extract active contacts from Plunk
Use the contact-listing API or the data access available to your self-hosted deployment to extract subscribed contacts with their email addresses and custom fields.
TipPlunk documents cursor-paginated contact listing but not a CSV export endpoint, so confirm your extraction method before the cutover.
3
Preserve unsubscribed, bounced, and complained contacts
Collect subscription state and delivery-failure records through the Plunk API, activity data, or your self-hosted database, then keep them separate from active contacts.
TipImport these records into Bento suppression before any campaign sends.
4
Document key segments and filters
Record the conditions behind each important Plunk segment and preserve the contact fields and events those conditions reference.
TipRecreate the logic in Bento instead of treating current segment membership as permanent.
5
Copy important templates and flows
Open your key Plunk campaigns and flows, copy the email HTML or content, and store them in a document or files that you will use to recreate templates and automations in Bento.
TipPrioritize onboarding, trial, and upgrade sequences first so your most important journeys are rebuilt quickly.
6
Import data into Bento and recreate automations
Use Bento CSV importers to bring in contacts, custom fields, and suppression lists, then rebuild your core flows as Bento automations and send test messages before going live.
TipTag imported contacts with a Plunk source field so you can track performance for users who came from your previous platform.

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 Plunk3 of 7 direct

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

Same ideas, new names

PlunkBento

ProjectAccountA Plunk project typically represents one product or app. In Bento this maps to an account that groups your events, contacts, and messages.
Audience or contactsPeople or contactsBoth platforms store people with email addresses and properties that you can target in campaigns and automations.
FlowAutomationPlunk flows are automated sequences of emails. In Bento you recreate them as automations with triggers, delays, and actions.
CampaignBroadcast or campaignA one time send to a segment in Plunk is similar to a broadcast or campaign in Bento.
PropertyFieldCustom data stored on a user in Plunk maps to fields on a person in Bento.
EventEventBoth tools track events like signups, logins, or feature usage that you can use to trigger automations and build segments.
SegmentSegment or filterDynamic groups in Plunk correspond to saved filters or segments in Bento based on fields and events.

Before you cancel Plunk

Start by migrating a small test segment from Plunk to Bento so you can verify imports and automations before moving your full audience.
Keep Plunk active during the transition so you can fall back if needed while you verify Bento sending and tracking.
Ask Bento support if you want help mapping Plunk events, properties, and segments into a clean contact model.
Warm up your sending domain with smaller campaigns in Bento before turning off Plunk completely.
Document your most important flows in Plunk first so rebuilding them in Bento is straightforward.

Automations and flows from Plunk do not import automatically into Bento so plan time to rebuild and test your key journeys.
Email history and detailed engagement logs typically stay in Plunk, so expect to start fresh with reporting inside Bento.
Confirm that unsubscribed and bounced contacts are imported into Bento suppression lists before you send any large campaigns.

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

Will I lose data when moving from Plunk to Bento?

Your contacts, custom fields, tags, and suppression lists can move over via CSV exports from Plunk and imports into Bento, but automations and detailed email history do not migrate automatically and are usually rebuilt.

How long does a typical Plunk to Bento migration take?

The timeline depends on contact extraction, suppression history, workflow count, templates, API integrations, and whether Plunk is hosted or self-hosted. Confirm the export path and rebuild one critical journey before setting a cutover date.

Can I reuse my Plunk templates in Bento?

You can copy the HTML or content from Plunk templates into Bento and then adapt them using Bento components, which is usually faster than designing everything from scratch.

Will there be downtime?

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

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.