Move from Buttondown to Bento.

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

Start free trial Plan your switch

Import from ButtondownEasy migration

CSVbuttondown-contacts.csv12,400 rows, mapped

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

Buttondown to Bento, at a glance.

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

Easy

Migration difficulty

1-2 hours.

3 of 7

Kinds of data that import directly

The rest you rebuild in Bento or leave behind.

Export steps in Buttondown

Each one is written out below, with tips.

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

Four steps off Buttondown.

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

Export from Buttondown.
6 steps in Buttondown, in the order below. Nothing changes for your subscribers yet.
Export from Buttondown6 steps
1Clean up your Buttondown listLog in to Buttondown, review your subscribers, and remove obvious test addresses or stale segments so you only migrate contacts you still care about.
2Export subscribers from ButtondownFrom the Subscribers view in Buttondown, choose the list or filter you want to export, then use the export option to generate a CSV file. Buttondown will either download the CSV directly or send you a download link by email depending on the export size.
3Collect tags and custom fieldsReview your Buttondown tags, segments, and custom fields, then note how you use them. This helps you recreate equivalent tags and properties in Bento before importing.
4Copy templates and recurring contentOpen your common newsletters and template snippets in Buttondown, then copy the HTML or markdown into new templates inside Bento.
5Rebuild drips and automations in BentoTake any Buttondown drips or scheduled sequences and recreate them as Bento automations using the visual workflow builder and event triggers.
6Import subscribers into BentoUpload your cleaned CSV to Bento, map email, name, tags, and custom fields, then run a small test import before importing the full file.
Keep Buttondown 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
PeopleImportsbuttondown-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 Buttondown keeps sending.
Launch checklist4 of 5
Sending domain authenticated in Bento
Suppressions moved from Buttondown
Seed test sent and checked
Highest-revenue flow rebuilt and tested
Switch sending to BentoNext
Warm up with your most engaged subscribers first.
Cancel Buttondown last.
Warm up with your most engaged subscribers, move the rest of your sending, and cancel Buttondown only once Bento carries it.
Sending, by phase
PhaseButtondownBento
ExportSendingNot yet
ImportSendingImporting
Rebuild and testSendingTesting
Warm upSendingWarming
Cancel ButtondownOffSending
No gap in sending at any phase.

Export from Buttondown6 steps

1Clean up your Buttondown listLog in to Buttondown, review your subscribers, and remove obvious test addresses or stale segments so you only migrate contacts you still care about.
2Export subscribers from ButtondownFrom the Subscribers view in Buttondown, choose the list or filter you want to export, then use the export option to generate a CSV file. Buttondown will either download the CSV directly or send you a download link by email depending on the export size.
3Collect tags and custom fieldsReview your Buttondown tags, segments, and custom fields, then note how you use them. This helps you recreate equivalent tags and properties in Bento before importing.
4Copy templates and recurring contentOpen your common newsletters and template snippets in Buttondown, then copy the HTML or markdown into new templates inside Bento.
5Rebuild drips and automations in BentoTake any Buttondown drips or scheduled sequences and recreate them as Bento automations using the visual workflow builder and event triggers.
6Import subscribers into BentoUpload your cleaned CSV to Bento, map email, name, tags, and custom fields, then run a small test import before importing the full file.

Keep Buttondown sending while you export.

Export your Buttondown data.

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

1
Clean up your Buttondown list
Log in to Buttondown, review your subscribers, and remove obvious test addresses or stale segments so you only migrate contacts you still care about.
TipFilter by engagement first and export only active or recently engaged subscribers to keep your new Bento account healthy.
2
Export subscribers from Buttondown
From the Subscribers view in Buttondown, choose the list or filter you want to export, then use the export option to generate a CSV file. Buttondown will either download the CSV directly or send you a download link by email depending on the export size.
TipMake sure your export includes email address, status, tags, and any custom fields you rely on.
3
Collect tags and custom fields
Review your Buttondown tags, segments, and custom fields, then note how you use them. This helps you recreate equivalent tags and properties in Bento before importing.
TipIf you use tags to track paid subscribers or cohorts, add a simple prefix like paid_ so it stays obvious after migration.
4
Copy templates and recurring content
Open your common newsletters and template snippets in Buttondown, then copy the HTML or markdown into new templates inside Bento.
TipUse this step to simplify your layouts and align them with your new brand and product emails.
5
Rebuild drips and automations in Bento
Take any Buttondown drips or scheduled sequences and recreate them as Bento automations using the visual workflow builder and event triggers.
TipThis is a good time to add behavior based steps, branching, and better segmentation that Buttondown did not support.
6
Import subscribers into Bento
Upload your cleaned CSV to Bento, map email, name, tags, and custom fields, then run a small test import before importing the full file.
TipKeep a backup of your original Buttondown export so you can fix mapping issues later if needed.

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

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

Same ideas, new names

ButtondownBento

SubscribersContactsIn Buttondown you manage subscribers to a newsletter. In Bento the same people are contacts that can receive product, marketing, and transactional email.
BroadcastsCampaignsOne off newsletters in Buttondown are broadcasts. In Bento they are campaigns that can target segments across all your data.
Drips or sequencesAutomations and flowsButtondown supports simple time based drips. In Bento you build automations and flows that react to events, behavior, and attributes.
TagsTagsBoth platforms use tags, but Bento lets you mix tags with events and properties for much richer segments.
Custom fieldsPropertiesCustom fields in Buttondown become properties on contacts and events in Bento so you can filter and personalize at a granular level.
Paid newslettersSubscriptions and billing eventsButtondown can charge for access to a newsletter directly. In Bento you track billing events from your payment stack and trigger email around them.
RSS to emailBlog and content automationsButtondown can email new posts from a feed. In Bento you trigger automations from content and product activity across your stack.

Before you cancel Buttondown

Start with a small test segment from Buttondown and send a preview campaign from Bento to confirm tracking, links, and branding look right.
Use Bento tags and properties to recreate any key segments you relied on in Buttondown before turning on automations.
Map your paid or VIP subscribers clearly during import so you can keep benefits and messaging consistent.
Turn off Buttondown welcome emails and drips only after your Bento automations are live and tested.

Historical send and open history from Buttondown will not appear in Bento, so plan your re engagement rules based on fresh engagement once you move.
If you charge for access to your newsletter through Buttondown, make sure billing and access are handled correctly in your new stack before closing your old account.
Check that unsubscribed and bounced addresses from Buttondown are not re imported as active contacts.

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

Will I lose my existing subscribers if I move from Buttondown to Bento?

No. As long as you export your subscribers as a CSV from Buttondown and import that file into Bento, your audience comes with you, including tags and key custom fields.

Can Bento replace Buttondown for a simple personal newsletter?

Yes. You can keep sending a straightforward newsletter from Bento, then layer in automation, transactional email, and product messages over time without changing tools again.

What happens to my paid Buttondown subscribers?

Buttondown processes payments directly, so you will keep that data in your billing tool or exports. In Bento you track those customers with tags and billing events so you can target them with the right onboarding and retention flows.

Does Bento support the same level of simplicity as Buttondown?

Bento is more powerful but still keeps writing and sending emails simple. You can start with basic campaigns and a few automations, then grow into more advanced workflows when you are ready.

How long does it take to migrate from Buttondown to Bento?

Most independent writers can export their Buttondown list, set up key tags and automations in Bento, and send a first campaign in one to two hours. Larger lists with complex drips may take a bit longer.

Will there be downtime?

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

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.