Migrate from Zixflow Marketing Automation to Twenty CRM

Zixflow Contacts map to Twenty Person records via the GraphQL API. Standard fields (name, email, phone) map directly. Zixflow's custom AI-generated enrichment fields export as flat key-value pairs and must be matched to Twenty custom fields created before import. We audit every unique custom property on Contact records, create matching custom fields in Twenty via the metadata API, then run the import with field-level type mapping (text, number, date, select, multi-select). Contact ownership resolves to Twenty workspace users matched by email.

Zixflow Companies map to Twenty Company records. Collections (Zixflow list/grouping objects) do not map to a direct Twenty standard object; instead, we create a custom field contacts_in_collections__c on the Person object using multi-select picklist to store Collection membership, or we create a custom Collection object with a linking table if the customer needs many-to-many relationship tracking. The strategy is chosen during scoping based on how heavily the team relies on Collection-based segmentation.

Zixflow Collections preserve contact grouping logic through multi-value custom fields on the Person record or through a custom Collection object we create in Twenty. Contacts may belong to multiple Collections; we handle this with a comma-separated custom field or with a separate linking table depending on the customer's segmentation complexity. The mapping preserves all Collection names and membership dates.

Zixflow Forms capture leads and feed data into Contacts and Collections. We export form field definitions and map them to equivalent custom fields on the Twenty Person object. Submission history migrates as Contact records with the form submission timestamp preserved in a custom field form_source__c. The form structure itself (layout, conditional logic, styling) does not migrate; we deliver a field-level inventory so the customer can recreate forms in their preferred form tool or as Twenty custom pages.

Zixflow WhatsApp Subscribers export with opt-in status and tag data. We map these to Twenty Person records with a whatsapp_optin__c boolean and a whatsapp_tags__c multi-select field. Zixflow's default subscriber cap of 500 is a source-side billing artifact; we flag the actual subscriber count during scoping so the customer can plan their WhatsApp Business configuration post-migration. Subscriber credits do not transfer.

Zixflow Inbox threads export via API with message content, timestamps, and channel metadata. We map thread metadata to Twenty Note records linked to the Person record, with channel type (WhatsApp, SMS, Email, RCS) stored in a custom field channel_type__c. Message body content maps to the Note body. Thread-level associations to Contacts resolve by email lookup in Twenty. Message delivery status (sent/delivered/open) is Zixflow internal tracking and does not map to a Twenty equivalent.

Message logs export with contact association, timestamp, direction (inbound/outbound), and channel type. We map each message to a Note record in Twenty linked to the Person record, with a custom field message_direction__c and channel_type__c. For high-volume message history (over 50k records), we batch via the GraphQL API with exponential backoff to stay within Twenty's rate limits. Delivery status metrics are exported as separate reporting artifacts and delivered as a CSV for the customer's analytics team.

Zixflow custom contact properties including AI-generated enrichment fields export as flat key-value pairs. This is the most time-intensive part of the migration because Twenty's standard Person object has minimal default fields (GitHub issue #13953). We pre-create every unique custom field discovered during the audit in Twenty via the GraphQL metadata API before running any data import. Field types are matched: text strings to text fields, numbers to number fields, dates to date fields, and multi-value arrays to multi-select fields. Fields without an exact equivalent are flagged for the customer's admin to review during scoping.

Zixflow Owners referenced on Contacts, Companies, Deals, and Inbox threads map to Twenty workspace users matched by email address. Any Zixflow Owner without a matching Twenty user goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Zixflow users are mapped to inactive Twenty users if historical attribution is required.

Zixflow Flows are built in a proprietary visual builder format that cannot be exported or transferred. We do not migrate Flows as code. Instead, we export a documentation snapshot of each Flow including its name, trigger type (form submission, contact property change, schedule), step summary (each action with its configuration), and active/inactive status. This inventory is delivered as a written document for the customer's admin to reference when rebuilding automations in Twenty's workflow builder. Flow credit usage history is a billing metric and is excluded from migration scope.

Zixflow's wallet-based messaging credits and automation credit balances are billing artifacts, not customer data. Wallet balance does not migrate and should be drained or forfeited before closing the Zixflow account. Automation credit history is excluded. We flag both balances during scoping and recommend the customer review their Zixflow billing dashboard before migration day.