Migrate from Cronberry to Twenty CRM

Cronberry Contact records map to Twenty's Person object, which represents individual contacts. We preserve email, phone, name fields, and custom field values. Cronberry's tag associations transfer to Twenty as custom text or multi-select fields (chosen during scoping). The critical pre-migration step is deduplication: Cronberry's unreliable repeat-contact detection means a single physical contact may exist as multiple records. We identify probable duplicates by matching on name, email, and phone, present a deduplication report to the customer, and merge before importing into Twenty to avoid contaminating the new workspace.

Cronberry Company records map directly to Twenty's Company object. Field-level mapping is required because Cronberry's company schema varies by implementation and may include custom properties. We extract company name, domain, address fields, and any custom fields, then map them to Twenty's Company fields. Company is imported before Person records so that the relationship can be resolved during Person import via company domain matching.

Cronberry Deals map to Twenty's Opportunity object. Each Opportunity receives a name, amount, close date, and stage. The stage mapping is designed during scoping based on Cronberry's deal pipeline stages. Closed-Lost and Closed-Won reasons from Cronberry custom fields migrate to Opportunity custom fields for audit and reporting continuity.

Cronberry Campaigns carry channel information (Email, SMS, Push, WhatsApp), timing rules, and target segment assignments. Twenty does not have a native Campaign object, so we map Campaigns to either a custom Campaign object (created via Twenty's custom object API) or to Opportunity groupings by campaign. Campaign-channel associations are documented in the mapping spec for the customer to configure manually in Twenty's channel setup. Campaign timing rules do not migrate as automations.

Cronberry Smart Segments are defined by conditional rules against contact field values. These rules are not exported as reusable schemas. We reverse-engineer segment membership by querying which contacts belong to each segment, then derive the implied conditions from the contact field data and document them. In Twenty, segments can be modeled as custom filter views or as tag-based groupings via the API. We deliver a written segment reconstruction guide specifying the conditions for each original Cronberry Smart Segment so the customer's admin can rebuild them in Twenty's workspace.

Cronberry tracks behavioral events (opens, clicks, push interactions) as Event Logs. These map to Twenty's Activity records with activity type, timestamp, and related Person or Company. Event schema may require field mapping because behavioral event properties differ between platforms. We extract event type, event date, and any associated contact reference, then map to Twenty Activity with the activity type field set to reflect the original Cronberry event category.

Cronberry User and agent records map to Twenty workspace members. We extract user name, email, and role where available. Role and permission structures differ significantly between platforms; we migrate basic user identity and defer permission model configuration to the customer's admin post-migration. Active/inactive status is preserved.

Message templates with personalization variables are migratable. We extract template content and variable placeholders from Cronberry's template storage. Rich formatting (HTML in email templates, character encoding in SMS templates) may require adjustment for Twenty's template format. We deliver a template migration report listing each template's content, variable placeholders, and channel type for manual import into Twenty's template system.

Cronberry's multi-channel setup stores channel credentials and API keys for Email, SMS, Push, and WhatsApp. These credentials (API keys, sender IDs, domain authentication records) cannot be exported for security reasons and must be reconfigured manually in Twenty's channel settings. We document the channel types active in Cronberry and provide a setup checklist for the customer's admin to configure in Twenty.

Cronberry form-level custom fields extend the Contact and Company schemas. These map to Twenty custom fields on the Person and Company objects. We extract the field definitions (name, type, options for picklists), create corresponding custom fields in Twenty's schema via the API, then migrate the field values during the Person or Company import phase. Custom field types are mapped to Twenty field types (text, number, date, select, multi-select) during scoping.