Migrate your Bento data

Contacts are the core object in Bento. Standard properties (email, name, timestamps) map 1:1 to any destination CRM. Custom fields are preserved as-is during migration but may require manual mapping if the destination uses different property naming conventions.

Tags in Bento are flat label strings attached to contacts. We export them as a comma-separated property and re-apply them as tags at the destination, preserving the full tag taxonomy including any nested or hierarchical conventions used in Bento.

Segments are dynamic filter rules built from contact properties and behavioral events. We export segment definitions as structured rule documents and rebuild equivalent segments at the destination using that platform's native segmentation logic, as rule syntax is not transferable directly.

Custom fields are first-class properties on contacts with explicit data types (string, number, date, boolean, choice). We map field names and data types 1:1 during export; destination systems with same-named fields of compatible types require no transformation.

Campaigns represent one-time sends with subject, content, and send history. We preserve campaign metadata and performance stats; the HTML content is exported for use in rebuilding at the destination, as campaign records cannot be transferred between platforms.

Automations are triggered behavioral flows built with a visual builder using conditions, delays, and action nodes. We export automation definitions as structured screenshots and JSON metadata. Rebuilding at the destination requires manual recreation of the flow logic, as trigger conditions vary by platform.

Custom Events are behavioral signals Bento tracks on contacts for segmentation and automation triggers. We export the event schema (event name, property structure) and the full event log per contact to preserve behavioral history at the destination.

Bento maintains a suppression list of unsubscribed contacts. We export this as a separate CSV and import it as a suppression list at the destination to maintain compliance during and after migration.

Bounced addresses are exported separately from active contacts. We carry forward the bounced list to the destination's suppression system to prevent re-sending to known invalid addresses and protect sender reputation.

Bento's transactional email uses drop-in SDKs (Rails, Laravel, Node, Python, Go, PHP). API credentials, template IDs, and sending domain configuration are documented in a configuration export for re-establishing transactional sending at the destination.

Connected integrations (Shopify, WooCommerce, Zapier, etc.) are listed in a configuration export. We document which integrations are active and what data they sync so the destination's equivalent integrations can be configured to maintain data flow continuity.

Bento's analytics dashboards contain aggregate performance data (open rates, click rates, revenue attribution) that is not exportable at the record level. We preserve report screenshots and export summary statistics as reference documents; historical analytics are not transferred as live data.