Migrate from Bento to HighLevel

Bento Contacts map directly to GoHighLevel Contacts. Standard properties (email, first name, last name, phone, address fields) map 1:1 to GoHighLevel contact fields. Custom fields migrate as GoHighLevel contact custom fields. We resolve duplicate contacts by email address during import and flag any conflicts for manual resolution. Created and updated timestamps migrate as custom fields since GoHighLevel's native audit fields are system-managed.

Bento tags are flat string labels attached to contacts. We export all tags per contact and import them as GoHighLevel tags, preserving the complete tag taxonomy including nested or namespaced tags. Tags appear in GoHighLevel's tag index and can be used to filter contacts and trigger workflows. The full tag list is preserved regardless of count.

Bento Segments are dynamic filter rules built from contact properties and behavioral events. We export each segment definition as a structured rule document specifying the filter conditions, operator logic, and event triggers. The customer recreates equivalent Smart Lists in GoHighLevel using the exported rule document as a specification. We validate that the destination field types support the segment logic (e.g., date-based segments require date-typed custom fields in GoHighLevel).

Bento custom fields are first-class properties with explicit data types (string, number, date, boolean, choice). We map each field name and data type 1:1 to GoHighLevel contact custom fields of equivalent type. Choice fields map to GoHighLevel picklist fields with the same options. Multi-value choice fields map to multi-select picklists. Any data type mismatches are flagged during scoping for the customer to resolve before migration.

Bento Campaigns (one-time sends with subject, content, and send history) migrate as GoHighLevel Campaigns with the HTML content preserved for recreation. Campaign metadata and performance statistics (open rate, click rate, send date) are exported as summary data. The campaign content itself is carried forward as HTML; the customer recreates the sends in GoHighLevel using the exported content and the GoHighLevel campaign builder. Send history does not carry forward as individual engagement records.

Bento Automations are visual flows with trigger conditions, delay settings, and action nodes stored in a proprietary format that cannot be exported as executable logic. We document each automation as a structured migration brief covering trigger type, conditions, delay configurations, action nodes, and Custom Event dependencies. The customer uses the brief to manually rebuild equivalent workflows in GoHighLevel's workflow builder. The migration brief is included in scope; the rebuild is a separate task.

Bento Custom Events define behavioral signals tracked on contacts (event name and property schema). GoHighLevel does not have a native Custom Event object in the same sense, but behavioral events can be modeled using custom fields (tracking a boolean flag, count, or last-occurrence date) or using GoHighLevel's Opportunities and engagement tracking. We export the full event schema and property definitions and map each Bento Custom Event to the most equivalent GoHighLevel construct based on the customer's use case.

Bento's unsubscribed contacts export as a separate suppression list and import into GoHighLevel's suppression list. We import before activating any active contacts for sending. GoHighLevel's suppression list prevents any email send to those addresses regardless of workflow or campaign settings. This is a compliance-critical step that must not be skipped.

Bounced addresses export separately from Bento as a distinct suppression list and import into GoHighLevel's suppression list alongside unsubscribed contacts. GoHighLevel does not distinguish between soft bounces, hard bounces, and unsubscribes in its suppression list interface, so we merge both Bento exports into a single suppression import and let GoHighLevel handle delivery based on its own bounce detection post-migration.