Migrate from Bento to Pipedrive

Bento Contacts map 1:1 to Pipedrive People. Standard properties (email, first name, last name, phone, created_at, updated_at) map directly to Pipedrive Person fields. We use email as the dedupe key during import to prevent duplicate Person records. Custom fields migrate as custom Person fields in Pipedrive, preserving data type (string, number, date, boolean, choice). Choice-type custom fields become Pipedrive drop-down options. Bento's contact creation timestamp migrates as a custom Person field since Pipedrive People do not have a native created_at equivalent.

Bento's unsubscribed list requires separate handling before active contacts import. We export unsubscribes as a dedicated CSV, then set the duplicate Detection flag on matching Pipedrive Person records (using email as the match key) before activating the full contact set. This prevents accidentally reactivating suppressed addresses during migration and protects sender reputation at the destination. The original unsubscribe timestamp is preserved in a custom Person field.

Bounced addresses export from Bento as a separate suppression CSV. We apply the same duplicate Detection logic in Pipedrive, flagging bounced addresses so they cannot be reactivated for sending. Pipedrive does not have a dedicated bounced-status field equivalent to Bento's bounce flag; we simulate it using a custom Person field bounce_status and a duplicate Detection record that prevents the address from being imported as an active contact. Bounced addresses are held in a separate Pipedrive list for periodic review.

Bento tags are flat label strings attached to contacts. We export the full tag taxonomy as a comma-separated property and re-apply them as Pipedrive Labels during import. Tags with hierarchical nesting (if any) are flattened to a label convention (e.g., source_region_usa, product_tier_premium) to match Pipedrive's flat label model. The original tag count and distribution are documented so the Pipedrive admin can audit label coverage post-migration.

Bento Segments are dynamic filter rules built from contact properties and Custom Events. Pipedrive has no equivalent dynamic segment engine; dynamic segments cannot be migrated as live filters. We export each Bento Segment definition as a structured rule document (property conditions, event conditions, AND/OR logic, time windows) and recreate them as Pipedrive Filters and static Lists. The filter logic is preserved in documentation for the customer's admin to validate and adjust based on Pipedrive's filter expression syntax. Segments with Custom Event conditions require additional scoping because Pipedrive does not track behavioral events natively.

Bento Custom Events define behavioral signals with specific property schemas that drive segment membership and automation triggers. Pipedrive does not have a Custom Event equivalent. We export the full event schema (event names, property names, property data types) as a schema brief. The brief is used to configure Pipedrive custom Activity types or custom Person fields that capture equivalent data points. Behavioral event logs per contact are not importable into Pipedrive's activity model; they are documented as background context for the sales team and referenced in the handoff brief for any future behavioral tracking setup.

Bento Campaigns represent one-time sends with subject, content, send history, and performance stats (opens, clicks, unsubscribes). Pipedrive has no campaign object. We export campaign metadata (name, subject, send date, recipient count, open rate, click rate, bounce count) as structured records in a Campaign_History__c custom object in Pipedrive. The HTML content is exported and delivered as a separate file for use in rebuilding email templates in Pipedrive's email tool or a dedicated email marketing platform. Performance stats are preserved as reference data for the admin to use in reporting.

Bento Automations are behavioral trigger flows with conditions, delays, and action nodes built in a visual editor. Pipedrive Workflows are deal-stage-triggered automations with a different action model and no email journey builder. We export each Bento Automation as a structured migration brief including trigger conditions, delay settings, conditional branches, action types (send email, add tag, update field, trigger event), and screenshots of the visual flow. These briefs are delivered to the customer's admin as the specification for rebuilding equivalent logic in Pipedrive Automation or an external email marketing tool. Functional migration of automations is out of scope per FlitStack AI standard policy.

Bento's transactional email uses drop-in SDKs (Rails, Laravel, Node, Python, Go, PHP) with API credentials, template IDs, sending domain configuration, and event webhooks. Pipedrive does not include transactional email sending. We export the full configuration (API keys, template IDs, sending domain, DKIM/SPF records, event webhook URLs) as a structured brief. The customer's engineering team uses this brief to re-establish the transactional email integration with their chosen replacement service (such as Postmark, SendGrid, or Amazon SES) post-migration. SDK code references are documented with the original Bento SDK language for accurate migration.

Bento integrations (Shopify, WooCommerce, Zapier, WordPress, etc.) are listed in a configuration export that documents which integrations are active, what data they sync, and what the connection credentials are. Pipedrive has its own integration ecosystem (Salesforce, HubSpot, Zapier, Slack, Zoom, etc.) with different connection models. We deliver an Integration Handoff Brief that maps each active Bento integration to its Pipedrive equivalent or a Zapier-based alternative. The customer's admin uses this brief to re-establish integrations in Pipedrive. Active data sync connections do not transfer automatically between platforms.

Bento's analytics dashboards (open rates, click rates, bounce rates, revenue attribution, campaign performance) contain aggregate data that is not exportable at the record level. We preserve report screenshots as image archives and export summary statistics (aggregate open rate, click rate, bounce rate per campaign, overall list growth over time) as a CSV. These are delivered to the customer as reference data for reporting and for use in setting baseline expectations in Pipedrive's reporting module or a BI tool. Pipedrive's native reporting covers pipeline and activity metrics, not email campaign performance.