Migrate from Cordial to monday CRM

Cordial contact records map to Monday.com items within a Contacts board. Standard fields (email, first name, last name, phone) map to typed columns (email, text, text, phone). Each custom contact attribute becomes a custom column on the board, with Cordial's attribute type (string, number, geo) mapped to the nearest Monday column type. Array-type attributes (e.g., tag lists, behavioral history) are normalized to delimited text columns because Monday.com does not support native array columns. We agree on a delimiter strategy (comma, semicolon) during scoping.

Cordial Lists are static sub-collections within the Contact collection. We export list membership as a boolean column per list (e.g., List_PremiumMember = true/false) or as a tag-style group membership. If a contact belongs to multiple lists, all relevant boolean flags are set. The customer chooses between per-list boolean columns or a consolidated Tags text column during scoping based on reporting needs.

Cordial products store variants as nested JSON arrays under a single product record. Monday.com has no native variant concept, so we unpack each variant into a separate item row. The parent Cordial product ID is preserved as a text column (parent_product_id) to maintain the relationship. Variant attributes (color, size, SKU) become separate text columns on each item. Product price from the parent record is copied to each variant row unless the variant carries its own price override.

Cordial Channels store email, SMS, and other channel opt-in preferences as sub-attributes on contacts. We map each channel to a Monday.com status or checkbox column (e.g., Email Opt-In = Checked, SMS Opt-In = Unchecked). Non-standard channels are mapped to additional status columns. The channel-specific preference data is preserved in separate columns per channel rather than consolidated.

Cordial does not have a native Companies collection, but companies are often stored as custom attributes on contacts (e.g., company_name, company_id). We map company data to a separate Companies board where appropriate, or consolidate it as contact-level columns. If the customer uses company-level grouping in Cordial, we create a dedicated Companies board with one item per unique company and link contacts via a company reference column.

Cordial Deals, if stored as custom attributes or linked records, map to Monday.com items in a Deals board. Deal stage maps to a Status column with values corresponding to the original stages. Deal value maps to a Numbers column formatted as currency. We flag any deal records stored as custom fields rather than native objects during discovery, as they may require a custom objects board in Monday.com CRM.

Cordial contact activities (opens, clicks, purchases, custom events) are available via the Contact Activity Export API with time-range filtering. We map these as items in an Activity History board linked to the contact item, or as custom columns on the contact item for recent events. High-volume event data (thousands per contact) may be summarized as a count column per event type rather than one item per event to avoid board bloat.

Cordial segments are dynamic rule-based audiences built from contact attributes and event conditions. We export segment definitions as rule summaries in a documentation sheet and flag which contacts currently match each segment. In Monday.com, matching contacts are grouped via a Group or identified via a Saved Filter (board filter). Active segment membership does not auto-sync; it reflects the state at migration time. The customer's admin rebuilds segment logic as Saved Filters or Groups post-migration.