Migrate from Bento to Nutshell

Bento Contacts with standard properties (email, first_name, last_name, phone, created_at, updated_at) map 1:1 to Nutshell People. We extract the full contact CSV from Bento, split it into active, unsubscribed, and bounced sub-sets, and import active contacts into Nutshell People using email as the dedupe key. Unsubscribe status from Bento maps to the Nutshell People opt_out property on each record. Custom fields preserve their data type (string, number, date, boolean, choice) and map to Nutshell People custom fields created during schema setup. Any Bento contacts without email are flagged as unmappable and held in a reconciliation report.

Bento does not have a native Company object, but Bento Contacts carry a company_name property on many records. We extract unique company_name values from the contact export and create Nutshell Company records for each distinct company. The company_name on the Bento Contact maps to the Nutshell People company field and links the Person to the Company record via Nutshell's foreign-key relationship. If Bento integrations (Shopify, WooCommerce) provide structured account data, we use that to build Nutshell Companies more completely.

Bento tags are flat label strings attached to contacts. We export the full tag taxonomy and re-apply them as a comma-separated text field or multi-select picklist on Nutshell People. The customer chooses whether tags become a single text field (for display) or a structured picklist (for filtering) during scoping. Tags used for behavioral segmentation are documented with their tag counts so the customer can rebuild equivalent People saved views in Nutshell.

Bento Segments are dynamic filter rules built from contact properties and behavioral events. We export each segment's rule definition as a structured JSON specification (field, operator, value, logic) and map the rule logic to Nutshell's People saved view filter builder. Segment membership counts are preserved as reference data so the customer can validate rebuilt saved views. Segments that reference Custom Events (which have no Nutshell equivalent) are flagged with the specific event property so the customer can decide whether to approximate the segment using a People custom field or skip the event condition.

Bento does not have a native Deal object, but teams migrating from Bento to Nutshell frequently manage deal records in a connected spreadsheet or another system alongside Bento contacts. If Deal data exists in a Bento-connected integration (Shopify for ecommerce, a CRM sync, or a manual export), we map those records to Nutshell Deals with Deal name, amount, stage, close date, and responsible person. If no Deal data exists in Bento, we document that the customer should begin creating Deals in Nutshell post-migration and close no historical deal data is lost.

Bento's unsubscribed contacts export as a separate suppression CSV. We import this list into Nutshell People with the opt_out flag set to true on each record before any active contacts are imported. This sequence is critical: importing active contacts first and unsubscribes second can cause Nutshell to activate suppressed addresses. We run the suppression import as the first step and validate the count matches before proceeding.

Bento's bounced address list exports separately and is imported into Nutshell People with a bounce flag. Nutshell does not have a native bounced-address field, so we set a custom boolean field bounce__c and attach a timestamped Note documenting the bounce reason (hard bounce vs soft bounce). This preserves the data for future suppression decisions and protects sender reputation at the destination.

Bento custom fields carry explicit data types (string, number, date, boolean, choice). We create equivalent Nutshell People custom fields with matching types before importing contact data. Choice fields in Bento map to Nutshell dropdown fields with the same options. Date fields in Bento map to Nutshell date fields. Boolean fields map to Nutshell checkbox fields. Any Bento custom field with a type not supported by Nutshell (for example, a complex JSON field) is flagged during scoping for the customer to resolve as a text field or to drop.

Bento automations use a visual builder with trigger conditions, delays, and action nodes. We export each automation as a structured screenshot set and JSON metadata documenting the trigger, every condition branch, each delay setting, and every action node with its configuration. Nutshell Activity Rules use a different trigger-action model (field-change or date-based triggers, action types limited to create task, update field, send email). We do not migrate automations as executable rules. The documentation package serves as the rebuild specification for the customer's admin.

Bento campaign metadata (subject, send date, recipient count, open rate, click rate, unsubscribe count) is exported as a structured summary. Campaign HTML content exports as raw markup. Nutshell's Engagement suite supports email templates but does not include a campaign send-history archive. We deliver the HTML content for the customer to use in recreating templates in Nutshell and preserve the performance summary as a CSV for reference.