Migrate from Zixflow to monday CRM

Zixflow Contact records map directly to Monday.com People Items. Standard fields (name, email, phone, address) map to the corresponding People field types. Custom fields on Zixflow Contacts map to Monday.com column types (text, number, date, dropdown, checkbox) on the People board. We resolve the email address as the dedupe key during import to prevent duplicate Person records.

Zixflow Collections are list-grouping constructs that assign Contacts to segments. We preserve Collection membership by creating a Tag on each Person record or by creating a dedicated Group within the People board. The customer chooses the strategy during scoping: Tags work well for contacts belonging to multiple Collections; Groups work well for mutually exclusive segments. We generate a Collection membership mapping table alongside the primary Contact export.

Zixflow custom fields on Contacts (including AI-generated custom fields) map to Monday.com column types on the destination board. We inspect the Zixflow field schema during discovery to determine types: text fields map to Text columns, numeric fields map to Number columns, date fields map to Date columns, multi-select fields map to Dropdown or Tags columns. The column is created on the destination board before any Person records are imported.

Zixflow Inbox threads are flattened to structured activity logs in Monday.com. Each incoming message becomes a Status Update or Pulse log entry on the Person item with timestamp, channel (WhatsApp, SMS, Email, RCS), direction (inbound/outbound), and message content preserved. We do not preserve the threaded conversation structure because Monday.com does not have an equivalent multi-channel inbox construct; the flattened log preserves the interaction history in a searchable format on the Person item.

Form definitions (field structure) and submission records migrate as Person custom field values plus a Form submission log board. Form field values populate the corresponding custom fields on the Person record. The visual form builder structure does not transfer; we document the form fields and logic so the customer can rebuild the form in Monday.com Forms or a third-party form tool.

Zixflow User accounts map to Monday.com User accounts by email match. Role and permission structures must be recreated at the destination because Zixflow role definitions do not export as structured data. We require customers to provision Monday.com User accounts for every active Zixflow user before the Person import phase begins so that Owner assignment can be resolved.

Zixflow Flows define automation logic as a node-graph inside the platform. The visual builder structure is not exported as a portable format. We inspect each active Flow during scoping, document its trigger conditions, action sequence, and condition branches in a structured runbook, and deliver it to the customer so their Monday.com admin can rebuild the logic in Monday.com Automations. Flows with complex branching or third-party action steps may require a separate rebuild scope.

Zixflow does not have a native Deals object. Pipeline-related data may exist as custom fields on Contacts or as Collections with deal-amount and deal-stage metadata. During scoping we identify all Zixflow records that function as deals, extract deal fields (amount, stage, close date, owner), and create Monday.com Deal Items on a Deals board. Each Deal Item is linked to the corresponding Person (buyer) via a Connect Board or Person column. Closed-won and closed-lost stages from Zixflow custom fields map to Monday.com Deal stage values.