Migrate from Cronberry to Zoho CRM

Cronberry Contacts map to Zoho CRM Lead (for unqualified prospects) and Contact (for qualified contacts tied to Accounts). We use Cronberry contact field values to determine qualification: contacts with at least one associated Deal map to Zoho Contact with an Account lookup; contacts with no deal association and no explicit qualification status map to Lead. The original Cronberry contact ID and any tag associations migrate as a custom field cronberry_contact_id__c and a multi-select picklist for tags. Repeat-contact duplicates identified during scoping are flagged in a reconciliation report before import.

Cronberry Company records map to Zoho CRM Account. Company name becomes Account Name; address fields map to Mailing Street, City, State, Country, PostalCode. We use Company name and domain as the dedupe key during import. Account is created before any Contact import so the Account-Contact relationship is satisfied at insert time. Custom company properties in Cronberry map to custom Account fields that we pre-create in Zoho before migration.

Cronberry Campaigns with channel assignments (Email, SMS, Push, WhatsApp) map to Zoho CRM Campaign. Campaign Name, Status (Active/Draft/Completed), Start Date, and End Date migrate directly. Cronberry's channel assignment becomes a Zoho Campaign Type field value. Target segment membership migrates as Campaign Member records linking the relevant Leads and Contacts to the Campaign. We do not migrate campaign content assets (email bodies, SMS text, push copy) as these are template-level rather than campaign-level records.

Cronberry Smart Segments are defined by conditional rules against contact field values but these rules are not exported as a reusable schema. We reverse-engineer segment conditions by querying which contacts belong to each segment, identifying the field-value combinations that produce membership, and documenting those conditions in a written segmentation rebuild guide for Zoho CRM. Where possible, we create Zoho CRM Static Groups from the actual contact membership lists so that segment membership is preserved even if the dynamic rule is not. This is a manual rebuild step guided by our documentation.

Cronberry contact tags (stored as multi-value associations) map to Zoho CRM multi-select picklist fields on Contact and Lead. We extract all distinct tag values across the contact dataset, create a custom picklist field in Zoho with those values as allowed options, and populate the field during contact import. The customer chooses during scoping whether tags also generate Zoho CRM Tag records.

Cronberry Event Logs tracking behavioral events (email opens, link clicks, push interactions, SMS deliveries) map to Zoho CRM Task records. Event type becomes Task Subject with a prefix (e.g., Email Open:); event timestamp becomes Task Due Date and Created Time; event metadata (browser, device, URL) becomes Task Description. We bulk-import events in batches using Zoho's CSV import with subqueries resolved against the parent Contact or Lead. Behavioral event volume can reach hundreds of thousands of records; we chunk imports to Zoho's documented batch limits.

Cronberry message templates with personalization variables (e.g., {{contact.first_name}}) migrate to Zoho CRM Email Templates and SMS Templates. We extract template content and variable placeholders, map them to Zoho's {{$.field_name}} format, and deliver a template migration report listing each source template, its Zoho equivalent, and any variable mappings that require manual adjustment. Visual layout from Cronberry's drag-and-drop template editor does not transfer; plain-text and HTML content migrate but rich design assets require recreation.

Cronberry channel credentials (sender IDs, API keys, WhatsApp Business Account credentials) do not transfer because they are platform-bound. We document the channel configuration present in Cronberry (which channels are active, which sender IDs or numbers are in use) in a Channel Setup Guide so that the customer's admin can reconfigure email sending domains, SMS sender IDs, and WhatsApp Business integration in Zoho CRM's渠道 configuration section. Channel associations on contacts (e.g., preferred channel flag) migrate as a custom picklist field.

Cronberry User and Agent records map to Zoho CRM User. We match by email address. Role and permission structures in Cronberry have no direct Zoho equivalent because Zoho uses profile-based and role-based access control with a different permission model; we migrate the user's name, email, and active/inactive status, and defer permission configuration to the customer's Zoho admin during implementation. Users flagged as inactive in Cronberry migrate as inactive Zoho Users.

Cronberry form definitions including field structure and conditional logic are extractable as a schema. We deliver a Form Schema Document listing each Cronberry form's fields, data types, and conditional rules. Zoho CRM does not include a drag-and-drop form builder at the base tier; the customer either recreates forms manually in Zoho's standard Web Forms module (Professional and above) or uses Zoho Creator for custom form logic. We do not migrate form visual layouts or embedded scripts; the rebuild guidance is schema-level only.

If Cronberry's lead management module contains deal or opportunity data (deal name, amount, stage, expected close date), these map to Zoho CRM Deals. We map deal stage to Zoho Stage Name, amount to Amount, close date to Closing Date, and owner to the Zoho User resolved by email match. If Cronberry does not contain deal records, this object is excluded from the migration scope. We confirm deal presence during discovery.