Migrate from Cordial to HubSpot

Cordial contacts map directly to HubSpot contacts. Subscription status flags (subscribed, unsubscribed, bounced, complained) are mapped to HubSpot's email_events timeline and a custom Opt_Status__c field. Cordial's cdate and lmdate timestamps are preserved as custom datetime fields so reporting continuity is maintained.

Cordial organizations map to HubSpot companies using a direct field mapping. Cordial's domain field maps to HubSpot's domain name on the company record. Parent-child organizational hierarchies in Cordial map to HubSpot's parent company lookup where those relationships exist, preserving the organizational structure during migration. If multiple parent-child levels exist in Cordial, each level is translated to the corresponding HubSpot parent_company_id relationship.

Cordial products with nested variant arrays require flattening for HubSpot's product-variant model. Each Cordial product variant becomes a HubSpot child product linked via the parent_product_id property. Cordial product attributes map to HubSpot custom product fields; custom attributes not supported natively are stored as JSON in a custom field.

Cordial open, click, and send events migrate as HubSpot engagement records on the contact timeline. Each event type becomes a logged engagement with the original timestamp, campaign name, and UTM parameters preserved. HubSpot's timeline UI shows the latest engagement by default; full event history is stored in custom fields for reference.

Cordial lists map to HubSpot static lists. Dynamic lists in Cordial — those built with filter rules — do not automatically become HubSpot smart lists; the filter logic is exported as a reference document and the smart list criteria are rebuilt in HubSpot manually after migration.

Cordial user-defined collections map to HubSpot custom objects. Each collection name becomes a custom object type in HubSpot. Collections containing nested arrays are processed: the array field is either stored as a JSON-stringified string property or split into multiple single-value properties depending on the schema complexity — this is decided during the schema audit phase.

Cordial's granular subscription flags for multiple channels (e.g., sms_subscribed, email_subscribed, push_notifications, in_app_notifications) map to HubSpot custom contact properties. Each Cordial subscription dimension becomes a dedicated custom property on the HubSpot contact. The built-in HubSpot marketing email subscription property is set based on Cordial's primary email subscription flag. Detailed preference flags and channel-specific opt-out timestamps require custom properties created before migration begins.

Cordial channel data attached to products (e.g., channel_used: email, sms, push) maps to HubSpot product custom fields. If a Cordial product is associated with multiple channels, each association is stored as a separate custom field value on the HubSpot product record.

Cordial journey events (step entered, goal achieved, exit) are mapped to HubSpot contact engagement records. The journey name and step name are stored in engagement properties. For high-frequency event logs, the raw events are summarized and stored in a custom text field on the contact rather than as individual engagement records.

Cordial segment definitions migrate as HubSpot static lists populated with the segment's current member contacts. The segment rule logic itself — the conditions that defined membership — is exported as a JSON rule object for reference during manual rebuild of HubSpot smart lists.