Migrate from Cronberry to Nutshell

Cronberry Contact records map to Nutshell People. We preserve name fields, email, phone, and address data directly. Cronberry tags and segment memberships map to Nutshell People Tags. Repeat-contact deduplication is applied during scoping: we match on email, name, and phone, generate a deduplication report for the customer to approve, and suppress or merge duplicates before import. Cronberry's custom contact fields map to Nutshell custom fields on Person, which are available from the Foundation tier onward.

Cronberry Company-level data (where present) maps to Nutshell Company records. Field-level mapping is required because Cronberry's company schema varies by implementation and may include custom properties. Company names and domains migrate directly; any custom fields require a Nutshell custom field created before the import phase begins.

Cronberry Campaign records carry channel information (Email, SMS, Push, WhatsApp), timing rules, and target segment assignments. We extract campaign names, status, start and end dates, and channel type. Campaign performance metrics (open rates, click rates, send volumes) migrate to Nutshell Campaign custom fields because Nutshell's standard Campaign object tracks cost, status, and type without native performance metrics beyond members. Segment associations are documented separately for rebuild in Nutshell's list builder.

Cronberry Smart Segments are built from conditional rules against contact field values. These rules are not exported as a reusable schema. We reverse-engineer each segment by querying which contacts belong to it, then document the implied conditions so they can be reconstructed manually in Nutshell using its People Tags and filter-based list feature. The customer receives a written segment map with field names, operators, and values per original Cronberry Smart Segment.

Cronberry Form definitions including field structure, conditional logic, and submission targets are extractable as a field schema. We map form field labels and types to Nutshell form fields. Visual drag-and-drop layout and conditional branching rules cannot be preserved 1:1 and must be rebuilt manually in Nutshell's form builder. The customer receives a field inventory per original form to guide the rebuild.

Cronberry User and agent records map to Nutshell Users. We match by email address and migrate display name, role, and basic identity. Cronberry's permission and role structures differ significantly from Nutshell's user roles (Admin, Manager, Standard), so we migrate identity only and defer permission configuration to the customer during Nutshell setup.

Cronberry tracks behavioral events (email opens, clicks, push interactions, SMS replies) against contact records. We map these to Nutshell Activities with the event type recorded in the Activity description or a custom field. Nutshell Activities appear in the Person and Company timelines. Event schema may require field mapping because Cronberry's behavioral event properties do not map directly to Nutshell's Activity object fields; we document the mapping per event type during scoping.

Message templates with personalization variables are migratable from Cronberry. We extract template content and variable placeholders, then map them to Nutshell's Email Template format or Sequence Step content depending on the intended use. Rich formatting and HTML structure may require adjustment because the two platforms use different rendering engines. The customer reviews template output in Nutshell's preview before finalizing.

Cronberry's multi-channel setup stores channel credentials and sender configurations (API keys, sender IDs, verified domains). These credentials cannot be transferred to Nutshell. We document the original channel configuration as a checklist so the customer's admin can re-register sender domains, verify email sending domains in Nutshell, and reconfigure SMS sender IDs through Nutshell's Twilio integration or their own SMS provider. This is a manual reconfiguration step outside the data migration scope.