Migrate from Zixflow to Odoo CRM

Zixflow Contacts are the primary CRM record. We assess each Contact's qualification signals during scoping (email engagement history, Collection membership, custom field values indicating sales-readiness) and split into Odoo Lead (unqualified) and Contact (qualified, attached to an Account). Contacts that map to Odoo Contact receive the corresponding Account lookup resolved at import time. We preserve the original Zixflow Contact ID in a custom field zx_contact_id__c on both Lead and Contact for audit and cross-reference.

Zixflow Collections are list-based groupings of Contacts. We generate a Collection membership mapping table during export: each Contact-to-Collection relationship becomes a row linking the Zixflow Contact ID to the Collection name. At import, we create Odoo Tags (ir.attachment.tag records) for each Collection and generate TopicAssignment or res.partner.category records linking Contact to Tag. This preserves the segmentation logic without forcing a single Collection per Contact if a Contact belongs to multiple Collections.

Zixflow custom fields on Contacts (including AI-generated fields) migrate to Odoo custom fields on the corresponding model (crm.lead for Leads, res.partner for Contacts). We inspect the Zixflow schema during discovery to capture field type, required status, and picklist values, then pre-create the destination fields in Odoo before any record import. Picklist fields in Zixflow map to Odoo selection fields or many2one relations depending on value cardinality.

Zixflow has no native Deals object. If a customer migrated from Sales Simplify and has deal-like data stored in custom fields on Contacts (deal value, stage, close date), we extract those fields during scoping, design an Odoo Opportunity schema that maps the extracted values to name, planned_revenue, stage_id, and date_closed, and import Opportunities independently of the Contact migration. This is a configuration-heavy phase that requires customer sign-off on the deal-field mapping matrix before extraction begins.

Zixflow Flows define automation logic as a node-graph that is not portable to Odoo Workflow. We inspect each active Flow during scoping, document its trigger conditions (event type, filter criteria), action sequence (field updates, tag additions, message sends, delay nodes), and active status, then deliver a structured runbook with recommended Odoo Workflow equivalent configuration. The customer's Odoo administrator or an Odoo partner rebuilds the workflow logic post-migration.

Zixflow Inbox stores threaded message conversations across WhatsApp, SMS, Email, and RCS channels. Message content, timestamps, sender, and channel type migrate as Odoo mail.message records linked to the parent record (Lead or Contact). We flatten thread structure to a linear activity log ordered by message timestamp. Channel metadata (WhatsApp vs SMS vs Email) is preserved in a custom field message_channel__c. Attachments migrate as ir.attachment records linked to the message.

Zixflow Forms capture lead data. Form submission records migrate to Odoo as Leads with the source form name recorded in a custom field x_zixflow_form__c, submission timestamp in create_date, and field values mapped to corresponding Lead or Contact custom fields. The visual form builder structure does not migrate; we document the form field layout so Odoo administrators can reconstruct the data capture in Odoo Survey or a website form.

Zixflow Users map to Odoo Users by email match. Role and permission structures in Zixflow (admin, editor, agent roles) do not map directly to Odoo's access rights groups (Portal, User, Manager) and must be reconfigured at the destination. We extract all Zixflow user records during discovery and deliver a user-reconciliation table listing which Zixflow users have no matching Odoo account for admin provisioning before record migration.

Before any record data moves, we pre-create all destination custom field definitions in Odoo using XML data import or through the Settings interface. This includes field name (mapped from Zixflow), field type (text, integer, date, selection, many2one), and any validation rules. Odoo's technical name convention uses x_ prefix for custom fields on standard models; we enforce this during schema design to comply with Odoo's ORM conventions.

Zixflow AI-generated custom fields store enriched data (email verification status, company data, social handles). These migrate as read-only Odoo custom fields. If the customer continues using Zixflow for enrichment post-migration, we document the enrichment workflow separately; if they adopt an Odoo-native enrichment tool, we flag the field as candidate for a computed field or a scheduled enrichment action.

Zixflow Campaign analytics (open rates, click rates, delivery metrics) are aggregated reporting outputs generated at query time, not stored as discrete records. We do not migrate analytics data. We deliver a data dictionary listing which metrics were available in Zixflow and the equivalent Odoo reporting fields or dashboard widgets the customer's team should configure post-migration.

WhatsApp, SMS, Email, and RCS messaging credits are consumed billing artifacts. They reset to zero at migration and have no portability value. We flag this explicitly during scoping so the customer accounts for the wallet balance gap in their Odoo-communication cost planning. Odoo does not have a native wallet model; communication costs require separate third-party module or provider configuration.