Migrate from Cordial to HighLevel

Cordial Contacts map directly to GoHighLevel Contacts. The email address serves as the dedupe key. All standard Cordial fields (first_name, last_name, phone) map to GoHighLevel's equivalent contact fields. We export every custom contact attribute by key name and type, creating GoHighLevel custom fields during schema discovery. Array-typed attributes (e.g. favorite_colors stored as JSON arrays) are normalized to comma-separated strings or to separate tag assignments depending on the attribute semantics agreed with the customer during scoping.

Cordial supports unlimited custom contact attributes of types string, number, geo, and array. We map each by its key name and preserve the data type where GoHighLevel supports an equivalent (text, number, date, phone). Array-type attributes are flagged during discovery and normalized to string fields or GoHighLevel tags. Geo-type attributes split into separate street, city, state, and zip fields to match GoHighLevel's address field structure. Any Cordial attribute with no GoHighLevel equivalent is documented as a custom field to be created before import.

Cordial Lists are static sub-collections within the Contact collection. We export list membership as a boolean flag per list and also create GoHighLevel tags for each list name. Each contact receives a tag per list it belongs to, preserving the segmentation logic in a form GoHighLevel's workflow triggers can reference. If the customer uses Cordial lists as suppression lists, we create GoHighLevel suppression tags with a naming convention agreed upon during scoping.

Cordial stores channel opt-in status (email, SMS) as sub-attributes on contacts. We export these as GoHighLevel contact-level boolean fields (email_opt_in, sms_opt_in) or as the built-in contact subscription fields. Any non-standard channel types (e.g. push, web push) are documented as custom fields to configure in GoHighLevel before migration.

Cordial Products store variants as nested JSON arrays under a single product record with fields productID, productName, price, and a variants array containing SKU and attribute pairs (color, size). GoHighLevel Products treat each variant as a separate product row or as attribute fields on a single product record. We unpacks the variant array and generate one GoHighLevel product record per SKU, preserving the parent Cordial product ID as a custom reference field parent_product_id__c to maintain the relationship. Price migrates directly; variant-level pricing differences are handled as separate product rows.

Cordial Segments are dynamic rule-based audiences built from contact attributes and event conditions. The Segment Export API provides the rule definitions but not the live membership list. We export the full contact list and compute membership for each segment at migration time, assigning GoHighLevel tags to matching contacts. We also deliver a written summary of each segment's rule logic (attribute conditions, event conditions, time windows) with recommended GoHighLevel Smart List or tag-based equivalent for the customer's admin to rebuild.

Cordial contact activities represent behavioral events (opens, clicks, purchases, custom events) stored with timestamps. GoHighLevel Activity Log supports custom activities. We export activity data via the Contact Activity Export API with time-range filtering and create GoHighLevel custom activity type records. Each activity type in Cordial (e.g. purchase, abandoned_cart) maps to a GoHighLevel activity category. High-volume event streams (e.g. page views, email opens) are summarized rather than row-by-row migrated unless the customer explicitly requires full behavioral history.

Orders are not a native first-class object in Cordial's core schema; they are typically stored as custom attributes on contacts or as behavioral events. We identify order-related attributes during schema discovery, map them to GoHighLevel custom fields on Contact, and flag any order data that should become GoHighLevel Opportunities if the customer wants to track deal flow alongside contact-level order history. We agree on the order data strategy with the customer before import.