BentoMigrate from Loops to Bento
Move from Loops to Bento without losing your SaaS email data. This Loops migration guide covers exports, imports, automations, and deliverability checks.
Migration Steps and Data Transfer
DATA TRANSFER
What transfers from Loops?
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 Loops
Follow these steps to export your data and prepare for migration.
1. Review your Loops workspace and clean data
Sign in to Loops, open your workspace, and review segments, workflows, and user properties so you know what needs to move.
2. Export contacts and properties from Loops
From the people or users view in Loops, apply any segment filters you want to keep, then use the export option to download a CSV with contacts and custom properties.
3. Export unsubscribes and suppressed contacts
Filter your Loops contacts for unsubscribed, bounced, or suppressed statuses and export a separate CSV so those contacts can be added to Bento suppression lists.
WHY SWITCH
Why migrate from Loops?
Here's why teams are making the switch to Bento.
Reason 1
Value based pricing that charges for emails you send instead of contacts you store, which usually lowers costs as your list grows.
Reason 2
All features including automation, deliverability tooling, shared inboxes, and validation available from day one without upgrades.
Reason 3
Operator friendly platform that combines product, marketing, transactional email, live chat, and a strong community in one tool.
TERMINOLOGY & MIGRATION GUIDE
Loops → Bento Translation
Different platforms use different terms. Here's how Loops concepts map to Bento, plus tips for a smooth migration.
Loops uses workspaces to group a project or environment. In Bento you typically map this to an account that represents your product or site.
Loops workflows are event driven sequences. In Bento you recreate them as automations with triggers and steps.
A broadcast in Loops is a one off send to a group of users. In Bento this is called a campaign.
Loops tracks users based on events. In Bento those users become contacts with timelines of events and messages.
Both platforms attach properties to events, such as plan name or feature used, which you can use for segmentation and triggers.
Segments in Loops map to saved filters or dynamic segments in Bento based on contact fields and events.
Migration Tips
- Audit your Loops events and properties first so you only bring fields that you will actually use in Bento.
- Migrate active workflows in small batches and run them in parallel with Loops until you are confident everything behaves as expected.
- Use Bento office hours if you want help mapping Loops events and traits into a clean contact model.
- Tag imported contacts with a migration source field so you can filter them later if needed.
- Schedule the final cutover during a low traffic window so you have time to test without pressure.
Watch Out For
- Loops workflows do not import directly, so plan time to rebuild and test key journeys inside Bento.
- Historical event logs from Loops may not be fully portable, so focus on bringing the fields you need for current segmentation.
- Check DNS and authentication before disabling Loops so transactional email continues without interruption.
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