BentoMigrate from Plunk to Bento
Move from Plunk to Bento without losing your key email data. This Plunk migration guide covers exports, imports, workflows, and deliverability checks.
Migration Steps and Data Transfer
DATA TRANSFER
What transfers from Plunk?
Here's what data we can migrate from your current platform to Bento.
Contacts & Segments
All your subscribers, tags, and custom fields transfer seamlessly.
Email History
Email history transfers partially based on platform limitations.
Commerce Data
Commerce data may require reconnection to your store.
STEP-BY-STEP
Export from Plunk
Follow these steps to export your data and prepare for migration.
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.
2. Export active contacts from Plunk
From the contacts or audience area in Plunk, filter for active subscribers you want to keep and use the export option to download a CSV including email, name, and key properties.
3. Export unsubscribed and bounced contacts
Locate the view that shows unsubscribed, bounced, or suppressed contacts in Plunk and export them as a separate CSV file.
WHY SWITCH
Why migrate from Plunk?
Here's why teams are making the switch to Bento.
Reason 1
Simple per user pricing for all users with unlimited emails, which is often cheaper as you scale and you can reach out to our team for help on pricing anytime.
Reason 2
All features including automations, deliverability tooling, live chat, shared inboxes, and validation available on every plan without upgrade tiers.
Reason 3
Operator friendly platform that combines product, marketing, and transactional email with strong community support, office hours, and sending controls like batching and pausing.
TERMINOLOGY & MIGRATION GUIDE
Plunk → Bento Translation
Different platforms use different terms. Here's how Plunk concepts map to Bento, plus tips for a smooth migration.
A Plunk project typically represents one product or app. In Bento this maps to an account that groups your events, contacts, and messages.
Both platforms store people with email addresses and properties that you can target in campaigns and automations.
Plunk flows are automated sequences of emails. In Bento you recreate them as automations with triggers, delays, and actions.
A one time send to a segment in Plunk is similar to a broadcast or campaign in Bento.
Custom data stored on a user in Plunk maps to fields on a person in Bento.
Both tools track events like signups, logins, or feature usage that you can use to trigger automations and build segments.
Dynamic groups in Plunk correspond to saved filters or segments in Bento based on fields and events.
Migration Tips
- 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.
- Use Bento office hours or 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.
Watch Out For
- 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.
We've been building Bento for 7 years and 310 days.
Come help us build the next generation of email marketing and automation software. We'll see you inside.
30-Day Trial • Fast Setup
Other Migration Guides
Explore guides for other platforms