Migrate from Cronberry to monday CRM

Cronberry Contact records map to Monday.com People board items. We match on email address as the dedupe key and preserve first name, last name, phone, and custom field values as column data. Cronberry's tag associations and segment memberships migrate to Monday.com Labels (multi-select) and Group membership. Before import, we run deduplication matching on name, email, and phone to identify Cronberry's duplicate-contact records and present a merge report to the customer for resolution.

Cronberry Company records map to Monday.com Organizations linked to the corresponding People item. The Company name becomes the Organization name, domain becomes the Website column, and any company-level custom fields map to Organization column values. Cronberry company schema varies by implementation, so we audit custom company properties during scoping and map them to the destination Organization columns or custom columns before import.

Cronberry Deals map to Monday.com Deal board items with deal amount, stage, expected close date, and owner transferred as column values. Cronberry Deal stages map to Monday.com Status column values configured per Deal board. Owner assignment resolves by matching Cronberry agent email to Monday.com team member email. We create the Deal board with the customer's stage names during schema setup before any data loads.

Cronberry Campaigns carry channel information (Email, SMS, Push, WhatsApp), timing rules, and target segment assignments. We map these to a Monday.com Board configured with columns for Channel, Start Date, End Date, Target Segment, and Status. Campaign content and body text migrate as item updates or Document column attachments. Cronberry's campaign workflow triggers (automated sends, drip sequences) do not migrate as automation; we document the campaign logic for manual reconstruction in Monday.com Automations.

Cronberry Smart Segments are defined by conditional rules against contact field values but are not exported as reusable schema. We reverse-engineer segment membership by querying which contacts belong to each segment, inferring the implied field-value conditions, and documenting them as a condition tree. The customer rebuilds these conditions in Monday.com using Group filters and saved Filter views. We provide the documented segment logic and the list of contacts in each segment for validation after rebuild.

Cronberry message templates with personalization variables migrate as Monday.com Document column content or as items in a dedicated Templates board. We extract template body text and variable placeholders (such as {{contact.first_name}} equivalents) and map them to Monday.com column text or template item descriptions. Rich formatting may require reformatting since Cronberry's template editor and Monday.com's text handling differ. Channel-specific templates (SMS character limits, push subject lines) are flagged for channel-appropriate formatting.

Cronberry User and agent records map to Monday.com team members by email match. Role and permission structures differ significantly between Cronberry's agent model and Monday.com's workspace membership model, so we migrate basic user identity and defer permission configuration to the customer's admin. Any Cronberry agent without a matching Monday.com user is held in a reconciliation queue.

Cronberry behavioral events (opens, clicks, push interactions, channel engagement) map to Monday.com item Updates or a dedicated Activity board with columns for Event Type, Timestamp, Contact, and Campaign. Event schema varies by Cronberry implementation, so we audit the event data structure during scoping, normalize field names, and map to typed Monday.com columns. Historical event data volume can be substantial; we batch-load via Monday.com API with rate-limit handling.