Migrate from Cordial to Nutshell

Cordial Contact records map to Nutshell People. We export all standard fields (email, first_name, last_name, phone) plus every custom contact attribute stored on the contact. Cordial's flexible JSON attribute schema requires type inference (string, number, boolean) and mapping to Nutshell's custom field types via the custom_fields configuration. Array-type attributes (tags, behavioral lists, preference arrays) are normalized to delimited strings or held in a separate lookup table for reconciliation with the customer before import.

Cordial unlimited custom contact attributes map to Nutshell custom fields on the Person object. During discovery we export the full attribute key list, infer data types, and configure matching field types in Nutshell before migration. Array-type attributes require a normalization decision (delimited string vs lookup table) agreed upon with the customer. Fields that cannot map to any Nutshell field type are flagged for manual review.

Cordial Lists store static contact memberships as boolean flags or separate membership records. We export list membership per contact and map each list to a Nutshell Person Tag. Contacts belonging to multiple lists receive multiple tags. If the customer prefers a field-based approach, we create a multi-select custom field with list names as picklist values instead.

Cordial Products store variants as nested JSON arrays under a single product record. Nutshell's product model has no native variant concept. We unpack each variant (color, size, SKU) into a separate Product row, preserving the parent product ID as a custom reference field (parent_product_id__c) to maintain the relationship. Product name, price, and SKU map directly from Cordial fields to Nutshell Product fields.

Cordial Channels (email, SMS, push) store opt-in status and preference data as sub-attributes on contacts. We export channel preferences as separate boolean fields (email_opt_in, sms_opt_in) and map them to Nutshell Person contact preferences. Any non-standard channel types (WhatsApp, voice) are flagged for manual mapping with the customer.

Cordial behavioral events (opens, clicks, purchases, custom events) map to Nutshell Activity records. Standard event types (email_open, email_click, purchase) are mapped to their nearest Nutshell Activity equivalent (Email, Task). Custom event types are mapped to Task records with a custom event_type field preserving the original Cordial event name. Event timestamps migrate as Activity dates for timeline ordering. Large event volumes (over 200,000 records) are chunked and batched to respect API rate limits.

Orders are not a native first-class object in Cordial; they are stored as custom attributes or linked via event data. We identify order-related attributes and custom event types during schema discovery, then map order data to Deal Line Items in Nutshell if the customer uses Deals, or to a custom order object if Deals are not the primary workflow. Order totals, dates, and product references are preserved as custom fields on the target record.

Cordial Segments are dynamic rule-based audiences that evaluate in real time against contact attributes. Nutshell does not have a live segment engine. We export segment definitions as rule summaries (a text description of the segment criteria) and flag which contacts currently match each segment using tag-based flags on the Person record. The customer can use Nutshell's static lists and tags for manual segmentation post-migration.