Migrate from Cronberry to Pipedrive

Cronberry Contacts map to Pipedrive People. We extract name, email, phone, custom field values, segment membership, and tag associations. Cronberry's repeat-contact deduplication is unreliable, so we run a dedupe pass matching on email (primary), phone (secondary), and normalized name as a tiebreaker before import. Dedupe results are presented in a reconciliation report for the customer to confirm before we load into Pipedrive. Segment membership is stored as a custom field or Pipedrive Activity note, since Pipedrive does not have a native segment object equivalent.

Cronberry Company records map to Pipedrive Organization. We extract company name, domain, address, and custom properties. Pipedrive People are linked to Organizations via the org_id field, which we resolve at import time. If a Cronberry Contact has a company association, we create the Organization record first so the relationship is satisfied during Person import. Cronberry's company schema varies by implementation and may include custom properties that map to Pipedrive custom fields.

Cronberry Campaigns with channel assignments (Email, SMS, Push, WhatsApp) and target segments map to Pipedrive Deals. The Cronberry campaign name and status map to Pipedrive Deal title and status. Pipeline and stage mapping requires configuration: we create Pipedrive pipelines matching the Cronberry campaign structure, with one pipeline per major campaign grouping. Campaign timing rules (scheduled send, trigger) do not map directly to Pipedrive; these are documented for manual rebuild in Pipedrive Automation rules.

Cronberry Smart Segments are defined by conditional rules against contact field values, but these rules are not exported as a reusable schema. We reverse-engineer segment membership by querying which contacts belong to each segment and inferring the conditions from the contact data. We deliver a written segment rebuild guide for each Smart Segment with the implied field-value conditions so the customer's Pipedrive admin can recreate them using Pipedrive Filters. Native Pipedrive Filters support field-value conditions and combined filter logic but do not replicate every Cronberry segment operator; we flag any gaps during scoping.

Cronberry User and Agent records map to Pipedrive Users. We extract user name, email, and role. Cronberry role and permission structures differ significantly from Pipedrive's user permission model, so we migrate basic user identity and defer role and permission configuration to the customer's Pipedrive admin during workspace setup. Owner assignment on Deals and People is resolved via email match against the Pipedrive User table.

Cronberry behavioral events (opens, clicks, push interactions, SMS replies) map to Pipedrive Activities. Each event type maps to a corresponding Pipedrive Activity type (email, call, meeting, task) or is stored as a note on the Person record. Event timestamps are preserved in the Activity date fields. Cronberry's event schema varies by implementation and campaign type; we document the field mapping per event category during scoping.

Cronberry message templates with personalization variables migrate to Pipedrive Templates. We extract template content, subject line, and variable placeholders. Rich formatting (HTML, inline images) may require reformatting for Pipedrive's template renderer. Email templates map to Pipedrive email templates; SMS templates map to a custom field or Pipedrive external tool note since Pipedrive does not have a native SMS template object without an add-on.

Cronberry's multi-channel setup stores channel credentials and sender IDs (Email, SMS, Push, WhatsApp) per contact or campaign. These channel associations migrate as custom fields on the Person record (e.g., sms_opt_in, push_enabled, whatsapp_consent). Channel authentication credentials (API keys, sender IDs) must be reconfigured in Pipedrive or a connected sending tool; we document the reconfiguration steps for each channel in the handoff document.

Cronberry form definitions including field structure and conditional logic are extractable as a schema. We map the form fields to Pipedrive Person or Organization custom fields. Visual layout and conditional branching cannot be preserved; the form schema is delivered as a field list for the customer to recreate using Pipedrive's form builder or a third-party form tool integrated with Pipedrive. Form submissions stored as contact records migrate with the Contact mapping.

Cronberry Landing Pages are rendered platform assets with no standard API export. We do not migrate Landing Pages. Page content must be recreated manually in the destination platform or using a landing page tool that integrates with Pipedrive. We deliver a page inventory noting each Cronberry Landing Page URL so the customer's team can recreate or redirect them.