Migration Guide
Move from Rejoiner to Bento with zero guesswork.
Step-by-step guide to migrate from Rejoiner to Bento. Export subscribers, segments, and suppression lists, then rebuild key ecommerce flows in Bento with better deliverability and control.
Migration Flow
A practical migration plan from Rejoiner 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
- 1Export your subscribers from Rejoiner
Sign in to your Rejoiner account, open the customers or subscribers area, and use the export option to download all contacts as a CSV including status and key profile fields.
- 2Export key segments and lifecycle lists
For important segments such as VIPs, high spenders, or product-specific lists, export each group as its own CSV so you can recreate them in Bento with tags and segments.
- 3Export suppression and unsubscribe data
Download a CSV of unsubscribed, bounced, and suppressed contacts from Rejoiner so you can import them into Bento's suppression list and stay compliant.
- 4Capture templates and automation logic
Open your high-value Rejoiner campaigns and lifecycle flows, save email HTML or text, and document triggers, delays, and branching so you can rebuild them in Bento.
- 5Connect Bento to your ecommerce platform
In Bento, install the Shopify, WooCommerce, or custom ecommerce integration, or add the tracking script so new orders and events start flowing into 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 Rejoiner 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.
Operator Notes
Rejoiner to Bento language map
Keep this open while rebuilding flows. It maps terminology and highlights what to do first during migration QA.
- Customer profilePerson
An individual contact with an email address and behavior history.
- CampaignBroadcast
A one-off marketing email sent to a list or segment.
- Lifecycle campaignSequence/Automation
A series of automated emails triggered by behavior, such as cart abandonment or win-back.
- SegmentSegment/Tag
A group of contacts defined by rules; in Bento you typically model these with tags plus dynamic segments.
- Cart abandonment flowCart recovery automation
A triggered automation that recovers revenue from shoppers who start checkout but don't complete it.
- Product feedProduct catalog or event data
The data source used to insert products and dynamic content into emails.
- Attribution reportAttribution & reporting
Analytics that tie orders and revenue back to specific campaigns and automations.
Tips
- Ask Rejoiner support for a complete export of subscribers and suppression lists if you cannot self-serve from the UI.
- Rebuild your highest revenue flows first in Bento, such as cart recovery, post-purchase, and win-back sequences.
- Keep Rejoiner running in parallel until Bento broadcasts and automations are fully tested.
- Use Bento's free email validation during import to clean your list and improve deliverability from day one.
- Use batched sending in Bento when you first mail your full list, especially if you change domains or DNS.
Watchouts
- Automations and lifecycle flows do not migrate automatically from Rejoiner; you need to rebuild them in Bento.
- Detailed historical email performance data will remain in Rejoiner, so export reports or screenshots before closing your account.
- Failing to import your suppression list can cause you to email unsubscribed contacts, which can hurt deliverability and compliance.
Keep Exploring
Other migration playbooks
Ready to leave Rejoiner?
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


