Migrate from Zixflow to Twenty CRM

Zixflow Contacts are the primary CRM record and map directly to Twenty People. We extract all standard fields (name, email, phone) and custom fields from the Contact schema. The email address serves as the dedupe key during import. If the contact was created from a Sales Simplify-era export and includes deal-related metadata, we preserve that data in a custom text field deal_metadata__c on the People record rather than assuming a native Deals object exists in Zixflow.

Zixflow Collections are list or grouping constructs that associate Contacts. We preserve Collection membership by creating a group-tag mapping table during export: for each Collection, we generate a list of contact IDs belonging to it. During import into Twenty, we create a custom select field collection_memberships__c on People and populate it with the Collection names, or we create a separate Group object with a membership relationship depending on the customer's preference. The mapping table is delivered as a CSV alongside the primary import.

Zixflow supports custom fields including AI-generated custom fields on Contacts. We document the full custom field schema (field name, field type, picklist options if applicable) and create equivalent fields in Twenty via Settings -> Data Model before import. Text fields map to TEXT, number fields to NUMBER, date fields to DATE, picklist fields to SELECT with the same options. Fields must exist in Twenty before the CSV import runs.

Zixflow Inbox stores threaded message conversations across WhatsApp, SMS, Email, and RCS channels. The conversation threading model varies by channel, so we flatten each thread into a time-ordered sequence of Task records (one Task per message with TaskSubtype=Email, Call, or Custom, and Subject set to the channel and timestamp) and a Note record (body containing the full thread text). We set ActivityDate on each Task to the original message timestamp to preserve chronological ordering in Twenty's timeline view.

Zixflow Forms capture lead data. Form field values populate corresponding Contact custom fields during import. Form submission metadata (submission date, form name, UTM parameters if present) migrate as a Note attached to the People record with the form name as the Note title and submission details in the body. The visual form builder and form design do not transfer.

Zixflow Flows define automation logic as a visual node graph. The node structure is not a portable format and does not map to Twenty's workflow builder. We inspect each active Flow during scoping, document its trigger conditions (event-based or schedule-based), condition branches, and action sequence in a written runbook. The customer's admin rebuilds the logic in Twenty's workflow builder using the runbook as a specification. Flow documentation is delivered before migration cutover so rebuild work can begin in parallel.

Zixflow User records represent seats. During migration we map Zixflow user email addresses to Twenty user accounts. We resolve by email match. Users must exist in Twenty before importing any records that reference them as owners or assignees. We flag any Zixflow user without a matching Twenty user for the customer to provision before record import resumes.

Zixflow does not have a native Company object separate from Contact, but some accounts created during the Sales Simplify era may have company-related fields or groupings. If a Zixflow export includes company name or domain data, we create Twenty Company records from that data and link People records to them via the workEmail域 or a domain-match lookup. If no company data exists, we skip this object.

Wallet-based messaging credits are a Zixflow billing artifact with no data portability value. WhatsApp, SMS, Email, and RCS credit balances reset to zero at the destination and are not migrated. We note this in the migration scope so the customer does not expect a balance transfer.

Zixflow analytics including open rates, click rates, and delivery metrics are aggregated reporting outputs generated at query time. They are not stored as discrete records and cannot be exported as structured data. Campaign performance data does not migrate. We recommend the customer export any required reports as PDF or CSV from Zixflow before the migration window and store them externally.