Migrate your Cordial data

Contacts are the primary collection in Cordial, stored with a flat attribute schema. We export all standard fields (email, first name, last name, etc.) plus every custom contact attribute stored on the contact record. Contacts are exported via the Contact Activity Export API with time-range filtering and CSV/JSON output options.

Cordial supports unlimited custom contact attributes of types string, number, geo, and array. We map each attribute by its key name and preserve the type. Array-type attributes (e.g. favorite_colors as ['red','blue']) are exported as JSON arrays and flattened or kept intact depending on destination schema capability.

Lists are sub-collections within the Contact collection. We export list membership as a boolean flag per list or as a separate lookup table, preserving which contacts belong to which static lists for re-creation in the destination system.

Products are stored as JSON objects in the products collection with standard fields productID, productName, price, and a variants array containing SKU and attribute pairs (color, size). We export the full nested product structure and flatten variants into separate rows if the destination requires a flat schema.

Channels (email, SMS, etc.) are stored as sub-attributes on contacts indicating opt-in status and preferences per channel. We export channel preferences as separate boolean fields and flag any non-standard channel types that may not exist in the destination CRM.

Contact activities represent behavioral events (opens, clicks, purchases, custom events). Cordial supports custom event types. We export activity data via the Contact Activity Export API with time-range scoping, but large event histories may require pagination and multiple export jobs.

Orders are not a native first-class object in Cordial's core schema but are often stored as custom attributes or linked via event data. We identify order-related attributes and custom event types and map them to the destination's order or transaction schema.

Segments in Cordial are dynamic rules-based audiences built from contact attributes and event conditions. We export segment definitions as rule summaries and flag which contacts currently match each segment, though the segment logic itself must be rebuilt in the destination platform.

Message analytics (opens, clicks, bounces, unsubscribes) are available via the Message Analytics Export API. Experiment results are not exportable via API and must be captured manually from the UI. We export standard campaign metrics but note the experiment data limitation upfront.

Cordial's Programs organize campaigns and automation sequences. Workflow logic, triggers, and delay rules are not directly exportable via API. We document the program structure, trigger points, and step count to assist with manual rebuild planning.