®
Migration Flow
A practical migration plan from Plunk 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.
Stage 1
Export checklist
- 1Review 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.
- 2Export 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.
- 3Export unsubscribed and bounced contacts
Locate the view that shows unsubscribed, bounced, or suppressed contacts in Plunk and export them as a separate CSV file.
- 4Export any key segments or tags
If you rely on specific Plunk segments, export members of those segments or ensure the fields that define them are present in your contact export.
- 5Copy 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.
Stage 2
Data portability map
Know in advance what imports directly and what may require a rebuild.
Stage 3
Validate and cut over
Treat cutover like launch QA. Validate your highest-risk paths first, then move sending traffic.
Switching from Plunk 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.
BentoOperator Notes
Plunk to Bento language map
Keep this open while rebuilding flows. It maps terminology and highlights what to do first during migration QA.
- ProjectAccount
A 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 contacts
Both platforms store people with email addresses and properties that you can target in campaigns and automations.
- FlowAutomation
Plunk flows are automated sequences of emails. In Bento you recreate them as automations with triggers, delays, and actions.
- CampaignBroadcast or campaign
A one time send to a segment in Plunk is similar to a broadcast or campaign in Bento.
- PropertyField
Custom data stored on a user in Plunk maps to fields on a person in Bento.
- EventEvent
Both tools track events like signups, logins, or feature usage that you can use to trigger automations and build segments.
- SegmentSegment or filter
Dynamic groups in Plunk correspond to saved filters or segments in Bento based on fields and events.
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.
Watchouts
- 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.
Keep Exploring
Other migration playbooks
Ready to leave Plunk?
Move with confidence: export cleanly, import safely, and launch on Bento with migration support from our team.
Free30-day trial·No credit card required·Book a demo