Migrate from Cordial to Freshsales

Cordial Contacts map to Freshsales Contact records. The Cordial email address becomes the Freshsales email field and serves as the dedupe key. All standard Cordial fields (first name, last name, phone) map to Freshsales equivalents. Custom contact attributes from Cordial's flexible JSON schema are created as Freshsales custom fields during migration, with type mapping from Cordial string/number/geo types to Freshsales Text/Number/Picklist fields. Array-type attributes (tags, behavioral lists) are normalized to delimited strings or multi-select picklists per the normalization strategy agreed during discovery.

Cordial Lists (static sub-collections within Contacts) map to Freshsales Contact Groups. List membership is preserved as a Contact Group membership record linked to each Contact. We flag any contact belonging to multiple Lists and create corresponding multiple Contact Group memberships in Freshsales.

Cordial channel preferences (email opt-in, SMS opt-in) stored as sub-attributes on contacts map to Freshsales contact-level communication preference fields. We map email subscription status to Freshsales Email Status and SMS opt-in to a custom field sms_consent__c. Any non-standard channel preferences are preserved as custom fields.

Cordial products with nested variant arrays (each containing color, size, SKU, and price attributes) are unpacked into separate Freshsales Product2 records, one per variant SKU. The parent product name is preserved in a custom field parent_product_name__c to maintain the relationship. If Freshsales Product Catalog is not enabled on the destination plan (Growth tier includes it), we flag this for customer activation before migration.

Cordial parent product records that contain variant arrays but no standalone SKU are preserved as a Freshsales Product2 entry with a custom field is_variant_parent__c set to true, serving as a grouping reference even though the primary SKU data lives in child variant records.

Cordial behavioral events (opens, clicks, purchases, custom event types) with timestamps map to Freshsales Task records linked to the Contact. Event type becomes the Task subject; event metadata (properties, values) is stored in Task description or custom fields. We preserve the original event timestamp in Task due_date and flag high-volume event migrations for batch processing to avoid Freshsales API rate limits.

Cordial does not have a native Order object; order data is typically stored as custom attributes on contacts or linked via behavioral events. We identify order-related attributes during discovery and map them to Freshsales Deal records (for sales-attributed orders) or to custom fields on the Contact (for historical purchase records). Order total, order date, and order status are preserved as Deal fields or Contact custom fields depending on the customer's data model.

All Cordial custom contact attributes are enumerated during discovery, typed (string, number, geo, array), and created as Freshsales custom fields before migration. Array-type attributes require normalization: tag lists become multi-select picklists, behavioral history arrays become delimited strings in a text field or a JSON blob in a long-text field. The customer chooses the normalization strategy during scoping. We flag any attribute exceeding Freshsales field type limits for manual review.

Cordial dynamic segments (rules-based audiences built from contact attributes and event conditions) cannot be migrated as executable logic because segment rules have no public export API. We export the segment definition as a written rule summary and identify which contacts currently match each segment. In Freshsales, we create static Contact Groups reflecting the segment membership snapshot at migration time and document the segment rules for manual rebuild as Freshsales Saved Filters or Workflow conditions.

Cordial message analytics (opens, clicks, bounces, unsubscribes) are available via the Message Analytics Export API but experiment results are explicitly excluded. We export standard message analytics to CSV and import them as Freshsales custom records or as a custom report data set. For A/B and multivariate test results, we recommend manual UI export from Cordial before cutover. Campaign attribution data is preserved in a custom report template for the customer's admin to configure in Freshsales.