Migrate from Cronberry to HighLevel

Cronberry Contacts map directly to GoHighLevel Contacts. Standard fields (first name, last name, email, phone) map to their GoHighLevel equivalents. Custom fields on Cronberry Contacts migrate as custom fields on the GoHighLevel Contact object. We apply deduplication during import by matching on email address as the primary key, with name and phone as secondary match criteria for records where email is absent. Cronberry's contact naming conventions are unreliable per reviewer reports, so we normalize capitalization and remove formatting artifacts before insert.

Cronberry Company records map to GoHighLevel Account. Field-level mapping is required because Cronberry's company schema varies by implementation and may include custom properties that do not map to standard GoHighLevel Account fields. We create custom fields in GoHighLevel for any unmatched Cronberry company properties. The Account is created before Contact import so that the Contact-Account relationship is resolved at insert time. If Cronberry did not store company data separately from contacts, we derive Account records from the contact domain field.

Cronberry Smart Segments are built from conditional field-value rules with no export schema. We reverse-engineer each segment by querying which contacts belong to it, inferring the conditional logic from the contact data distribution, and documenting the resulting rule. In GoHighLevel, we recreate segment membership as Tags on Contacts and as Contact Lists based on tag combinations. The customer reviews and approves the inferred segment logic during sandbox validation. This is a manual reconstruction step, not an automated schema import.

Cronberry Campaigns carry channel routing (Email, SMS, Push, WhatsApp), timing rules, and target segment assignments. GoHighLevel Workflows use a different trigger and action model. We extract campaign metadata including channel type, target segment, timing conditions, and message content from Cronberry exports, then document each campaign as a written specification for GoHighLevel Workflow rebuild. Active campaigns are not migrated as running automations; they are handed off as rebuild documentation for the customer's GoHighLevel admin.

Cronberry message templates with personalization variables are extractable from exports. We map template content to GoHighLevel's Email Template and SMS Template objects, preserving personalization variable placeholders. Rich formatting (HTML email styling, embedded images) migrates as-is where Cronberry's export format supports it. GoHighLevel uses double-brace syntax ({{contact.first_name}}) for personalization variables, which differs from Cronberry's variable format; we transform variable syntax during import.

Cronberry User and Agent records map to GoHighLevel Users. We match by email address. Role and permission structures differ significantly between platforms, so we migrate basic user identity (name, email, active status) and defer permission configuration to the customer's GoHighLevel admin. Any Cronberry user without a matching GoHighLevel User is held in a reconciliation queue for manual provisioning before the Contact import phase begins.

Cronberry tracks behavioral events including opens, clicks, push interactions, and custom event types. We map these to GoHighLevel Activity records (Call, Email, Meeting, or generic Activity depending on event type). Cronberry's event schema differs from GoHighLevel's Activity schema, so we extract the available fields and map them to custom Activity fields in GoHighLevel where needed. GoHighLevel does not have a native behavioral event stream comparable to Cronberry's event log, so the richness of behavioral history in the destination depends on what Cronberry's export includes. We flag any behavioral fields that cannot map to GoHighLevel Activity records during scoping.

Cronberry form definitions including field structure and submission targets are extractable. We document the form schema (field names, field types, conditional logic conditions) in a written form inventory. Visual layout and drag-and-drop positioning cannot be preserved 1:1. The customer rebuilds forms in GoHighLevel's Form builder using the documented field schema as a specification. We do not migrate forms as live GoHighLevel form assets; that work requires the GoHighLevel admin to recreate the visual builder layout.