Migrate from Cordial to Zoho CRM

Cordial's single flat Contacts collection maps to Zoho CRM's separate Lead and Contact modules. We apply a split rule during migration: contacts with a purchase event or lifecycle stage indicating a customer status map to Zoho Contact linked to an Account (converted from any related Company record); all other contacts map to Zoho Lead. We preserve Cordial's contact ID as a custom field cordial_id__c on both Lead and Contact for cross-reference. The split rule is defined during scoping based on the customer's Cordial attribute naming conventions and behavioral event history.

Cordial Companies map directly to Zoho CRM Accounts. The company name maps to Account Name, and domain or website maps to Website. If Cordial stores company-level revenue or employee count as custom attributes, these map to custom Account fields. Account is created before any Contact import so that the Account Name lookup is satisfied at Contact insert time.

Cordial's unlimited custom contact attributes map to Zoho CRM custom fields scoped per module. String attributes map to Zoho single-line or multi-line text fields. Number attributes map to Zoho numeric fields. Geo attributes (latitude, longitude, city) map to Zoho location fields or separate text fields. Array-type attributes (favorite_colors, tag lists, behavioral history arrays) are normalized: if the array has fewer than 30 distinct values, we map to Zoho multi-select picklist; if it has more or is unbounded, we flatten to a pipe-delimited text field. Array fields are flagged during discovery and the normalization strategy is agreed with the customer before import.

Cordial Lists represent static audience segments stored as list membership on contacts. We migrate list membership as either a checkbox field per list (if fewer than 15 lists) or as Zoho CRM Tags on the Contact or Lead record. The customer chooses the strategy during scoping. Tag migration is subject to Zoho's 10-tag limit per record and 25-character tag length limit.

Cordial products store variants as nested JSON arrays under a single product record. Zoho CRM does not support nested variant structures natively, so we unpack the variant array and generate one Product2 record per SKU. We preserve the parent Cordial product ID as a custom field parent_product_id__c on each variant record and set a custom field variant_attributes__c (e.g., color=Red, size=Medium) to carry the variant differentiators. The customer decides whether to use Zoho Inventory module (add-on, for stock tracking) or standard Products for variant rows.

Orders are not a first-class object in Cordial's core schema and are typically stored as custom contact attributes or behavioral events with order ID, total, and line items. We map order data to Zoho CRM Deals: the order total becomes Deal Amount, order date becomes Close Date, and the order ID is stored in a custom field original_order_id__c. Line items from the order migrate as Deal Line Items linked to the Deal. If the customer has a high volume of historical orders, we recommend creating a custom Orders module in Zoho CRM instead, which requires Zoho Professional tier or higher.

Cordial stores channel-level opt-in status (email, SMS, push) as sub-attributes on contacts. We map these to Zoho CRM custom fields: email_consent__c (checkbox), sms_consent__c (checkbox), push_consent__c (checkbox). Opt-in dates and source channels migrate as additional date and picklist fields. Zoho's own email compliance fields (ZC_E_email_Opt_Out) are updated in sync with the migrated consent flags.

Cordial behavioral events (opens, clicks, purchases, custom event types) migrate as Zoho CRM Tasks linked to the Contact or Lead record via WhoId. Purchase events with associated order data migrate as Deals first (see Order mapping) and then as Task records for the activity timeline. Event type maps to Task Subject, timestamp maps to Activity Date, and event properties migrate as custom Task fields. We use Zoho's Bulk API with batch chunking for large event volumes to avoid timeouts.

Cordial segments are dynamic rule-based audiences. Segment definitions (attribute conditions and event triggers) are documented as a written inventory during migration scoping. We cannot export segment rules as executable Zoho filters via API, so we deliver a segment-rebuild guide that maps each Cordial segment condition to the equivalent Zoho Advanced Filter builder syntax. The customer's Zoho admin rebuilds segments as saved views or Workflow Rule triggers post-migration.

Cordial owners map to Zoho CRM Users by email match. We extract every distinct owner referenced on Contact, Company, Deal, and Engagement record and resolve against the Zoho destination org's User table. Owners without a matching Zoho User are held in a reconciliation queue for the customer's admin to provision before record import resumes.