Migrate from Bento to Freshsales

Bento Contacts migrate to Freshsales by qualification strategy defined during scoping. Contacts with a demonstrable sales signal (tagged with pipeline, demo-requested, or purchased) route to Freshsales Contact attached to an Account record. Contacts without a sales signal route to Freshsales Lead. We preserve Bento's standard properties (email, first_name, last_name, phone) and all Custom Fields as typed custom fields on the destination object. The original Bento contact ID is stored in a custom field bento_contact_id__c for reconciliation.

Bento tags are flat string labels on contacts. We export the full tag taxonomy, then create a Freshsales multi-select picklist field (tagged_contacts__c) with all unique values as picklist options. During contact import, each Bento tag string is parsed and mapped to the corresponding picklist value. Tags used for behavioral segmentation are also documented separately as they inform the Lead/Contact split strategy.

Bento Custom Fields (string, number, date, boolean, choice types) map 1:1 to Freshsales custom fields using equivalent data types. Choice fields become Freshsales picklist or multi-select picklist fields. Date fields preserve ISO 8601 format. Number fields with decimal precision are mapped to Freshsales number fields with matching scale. We pre-create the destination custom fields via Freshsales API before any contact import begins.

Bento Segments are dynamic filter rules against contact properties and Custom Events. Freshsales does not support dynamic segments equivalent to Bento's behavioral targeting. We export each segment definition as a structured rule document (field, operator, value, and logic tree) so the admin can recreate the logic as Freshsales static lists or Lead/Contact filters. Active segment membership at migration time is preserved as a tag.

Bento Custom Events define behavioral signals (purchase_made, page_viewed, form_submitted) with typed property schemas. Freshsales has limited native behavioral event tracking outside of its Freddy AI suite. We export the full event schema (event name, property names, property types) and event log per contact. The destination team uses this to configure equivalent event tracking in Freshsales or a paired analytics layer. Incompatible property types are flagged during scoping for manual resolution.

Bento Campaigns export as HTML content with campaign metadata (subject, send date, send count, open rate, click rate). The HTML is imported into Freshsales email templates for use in Freshsales Workflows and Sales Sequences. Campaign performance statistics are documented in a reference spreadsheet because Freshsales does not have a campaign performance analytics equivalent to Bento's sending reports.

Bento Unsubscribed contacts export as a separate CSV. We import them into Freshsales as Contact records with HasOptedOutOfEmail set to true and a custom field bento_unsubscribed__c = true to preserve the original suppression source. This prevents any email from being sent to these addresses in Freshsales and protects sender reputation during and after migration.

Bounced contacts export separately from active and unsubscribed records. We import them into Freshsales as Contacts with a custom field bento_bounced__c = true and a bounced_email__c flag. Freshsales does not have a native bounced-address suppression list separate from its email deliverability settings, so the custom field serves as the operative suppression flag for post-migration email sending rules.

Bento Automations use a visual builder with trigger conditions, delay settings, and action nodes stored in a proprietary format that cannot be exported as executable rules. We export automation definitions as structured screenshots and JSON metadata, then produce a written rebuild brief for each automation with trigger type, conditions, delay configuration, and recommended Freshsales Workflow equivalent. The customer's admin rebuilds the logic in Freshsales Workflows post-migration.