Migrate from Bento to Mailchimp

Bento Contacts map 1:1 to Mailchimp Audience Members. Standard properties (email, first name, last name) map directly to the corresponding Mailchimp merge fields (EMAIL, FNAME, LNAME). Custom Fields with string, number, date, boolean, or choice data types map to Mailchimp Merge Fields with the appropriate field type. We export the full Bento custom field schema including data types and apply Mailchimp-compatible type mapping during import to avoid field-type rejection at the destination.

Bento Tags are flat label strings attached to contacts and map directly to Mailchimp Tags. We export tags as a comma-separated list per contact and re-apply them as Mailchimp Tags during import. The full tag taxonomy migrates including nested or hierarchical tag patterns if used. Mailchimp Tags are not hierarchical (flat only), so any Bento tag hierarchy flattens into a single-level tag namespace.

Bento Segments are dynamic filter rules built from contact properties and behavioral events. We export each segment definition as a structured rule document that describes the filter conditions, operators, and event criteria. Mailchimp Segments use different filter syntax and operator naming. We document the Bento segment logic in a Mailchimp-compatible format and provide the customer with a rebuild guide for each segment. Segments are not migrated as executable rules because Bento and Mailchimp filter builders are not compatible.

Bento Custom Events track behavioral signals with typed property schemas on each contact. Mailchimp Events API accepts event names and key-value properties but uses a different property typing model. We export the full Bento event schema (event name, property names, property data types) and map compatible types to Mailchimp Events. Events with complex nested property structures or unsupported data types are flagged during scoping for manual resolution before migration.

Bento Campaigns (one-time sends with subject, content, and send history) migrate as Mailchimp Campaigns with metadata preserved. The HTML content exports and can be used to recreate the email body in Mailchimp's template builder. Campaign performance stats (open rates, click rates) do not migrate because Mailchimp tracks these against its own sending infrastructure. We provide campaign screenshots and metadata so the customer can identify which campaigns to rebuild in Mailchimp.

Bento Automations are visual behavioral flows with trigger conditions, delay nodes, and action steps. Mailchimp Customer Journeys use a different trigger model, action library, and delay syntax. We do not migrate automations as executable rules. We export each Bento automation as structured JSON metadata plus screenshots documenting the visual flow, and deliver a rebuild brief for each automation that describes the trigger, conditions, delays, and actions in Mailchimp Customer Journey terminology. The customer's admin rebuilds the journeys in Mailchimp using the brief as a specification.

Bento's unsubscribed contact list migrates to a Mailchimp Suppression List imported before any active contacts are activated. This is a compliance requirement at both platforms. Mailchimp requires suppression list import via CSV in the Suppressions settings. We export unsubscribed contacts from Bento as a separate CSV and apply it to the destination audience before importing active contacts to prevent re-activation of suppressed addresses.

Bento's bounced contact list migrates to a Mailchimp Suppression List. Bounced addresses are exported separately from active contacts to prevent re-sending to known invalid addresses and protect sender reputation at the destination. We carry forward the bounced list and import it as a suppression entry in Mailchimp. Mailchimp tracks its own bounce status per email address; the imported suppression list prevents the address from entering the active audience at all.