Migrate from Cronberry to Freshsales

Cronberry Contacts migrate to Freshsales Leads by default, with a manual split decision during scoping: Contacts with purchase history or active campaign participation may be migrated directly as Freshsales Contacts attached to Accounts. Email, phone, name, custom field values, segment memberships, and tags all map to Freshsales Contact or Lead fields. Cronberry's tag associations migrate to Freshsales contact tags or custom multi-select fields depending on the customer's tag strategy. We flag probable duplicates by matching on email and phone and present a deduplication report before importing, since Cronberry's repeat-contact detection is unreliable.

Cronberry Company records map to Freshsales Account. Field-level mapping is required because Cronberry's company schema varies by implementation and may include custom properties that need custom fields created in Freshsales before import. Company domain from Cronberry maps to the Account Website field as a dedupe key. We create the Account record first so that Contact imports can satisfy the AccountId lookup immediately.

Cronberry Campaigns carry channel information (Email, SMS, Push, WhatsApp), timing rules, and target segment assignments. We extract these and map them to Freshsales Campaign records, preserving campaign status, start and end dates, budget, and the target segment name. Cronberry campaign channel type maps to a Freshsales custom field because Freshsales Campaign does not natively store the channel variant. Campaign content and templates migrate separately as Message Templates.

Cronberry Smart Segments are defined by conditional rules against contact field values but these rules cannot be exported as a reusable schema. We reverse-engineer segment membership by querying which contacts belong to each segment, then document the conditions implied by the contact data. The customer rebuilds these conditions in Freshsales Segmentation using the documented field-value rules. We do not automate the segment rebuild because Freshsales Segmentation rules use a different syntax and operator model than Cronberry's rule builder.

Cronberry tags attached to Contacts migrate to Freshsales Tags (a native tagging feature) or to a custom multi-select picklist field depending on how many distinct tag values exist. Tags used for lead classification migrate as tag strings; tags used for behavioral classification migrate to a dedicated custom field. We advise during scoping on which strategy preserves more reporting value.

Cronberry's channel configuration (credentials, sender IDs, WhatsApp Business Account associations) must be reconfigured in Freshsales or a connected communication tool because API keys and sender profiles cannot be exported. We migrate the channel association to contacts by setting a custom channel_preference field indicating which channels a contact has opted into, but the actual channel delivery credentials require manual reconfiguration in Freshsales Telephony or a third-party integration.

Cronberry message templates with personalization variables are extractable and migrate to Freshsales Email Templates and Sales Templates. Template subject line, body content, and personalization placeholders map to Freshsales template fields. Rich HTML formatting from Cronberry email templates may require reformatting because Freshsales template rendering handles HTML differently. SMS and push templates migrate with text content preserved; media and rich push content may not carry over.

Cronberry User and agent records map to Freshsales User records. We resolve users by email match. Role and permission structures differ significantly between platforms, so we migrate basic user identity (name, email, active status) and defer permission and team configuration to the customer's Freshsales admin. Any Cronberry user without a matching Freshsales User goes to a reconciliation queue for manual provisioning before record import begins.

Cronberry behavioral event logs (opens, clicks, push interactions, campaign engagement events) migrate to Freshsales Activity records (Tasks and Appointments) linked to the parent Contact or Account. Event schema mapping is required because Cronberry behavioral event types may not map directly to Freshsales Activity types. We use the event timestamp as the Activity Date to preserve engagement ordering. High-volume event logs (hundreds of thousands of records) require batched API insertion with exponential backoff.