Migrate from Zixflow Marketing Automation to Odoo CRM

Zixflow Contacts map directly to Odoo res.partner records with type=contact. Standard fields (name, email, phone) migrate 1:1. Custom AI-generated enrichment fields and any custom contact properties export as flat key-value pairs and map to Odoo custom res.partner fields. We verify field type compatibility during schema design — Zixflow text fields must map to Odoo char or text fields, date fields to Odoo date, and boolean fields to Odoo boolean. Multi-value properties (arrays or tags) map to Odoo tags rather than custom fields if the customer prefers tag-based segmentation.

Zixflow Companies map to Odoo res.partner records with type=company and is_company=True. The company name becomes the partner name; domain or website maps to website. Individual Contacts within a Zixflow Company are created as separate res.partner records with parent_id pointing to the company record. We resolve the company record first in migration order so the parent lookup is satisfied before child contacts insert.

Zixflow Collections are audience segments — contacts may belong to multiple Collections. We map each Collection to an Odoo Tag on the res.partner record. Because contacts can belong to multiple Collections, we use multi-tag assignment rather than a single Collection field. Tags are created in Odoo before contact migration and matched by name during the transform phase. If a contact belongs to Collection A and Collection B, it receives both tags on the res.partner record in Odoo.

Zixflow Flows are built in a proprietary visual builder. Automation logic does not export as transferable data. We export a snapshot of every Flow: name, trigger type, step summary, and conditions list. This document is delivered as the Flows Inventory and is the handoff artifact for the customer or an Odoo implementation partner to rebuild in Odoo Marketing Automation. This step has no data migration component; it is a documentation deliverable scoped separately from data transfer.

Zixflow Forms capture leads and feed data into Contacts and Collections. Form field definitions export as field names and types, and we map each to an Odoo custom field on res.partner. Form submission history does not migrate as a separate object — submissions become Contact records in Odoo with the form-specific custom fields populated. The original form name is stored in a custom field so the admin can attribute leads to the correct form source.

Zixflow Inbox aggregates multichannel conversations across WhatsApp, SMS, Email, and RCS. Odoo has no native unified conversation store. We migrate conversation threads as CRM notes attached to the related res.partner record via mail.message. Thread metadata (channel type, participant, start time) is stored in the note body so the admin can reconstruct the conversation context. Thread-to-contact association requires re-linking using the Zixflow contact ID stored in a custom field during contact migration.

Message logs export from Zixflow with contact association, channel type, content, and timestamp. We populate the Odoo res.partner message field with the log content and channel metadata. Message delivery status (sent/delivered/open) is Zixflow's internal tracking and has no Odoo equivalent, so we flag this in the reconciliation report and note that the admin should configure Odoo's email tracking separately if delivery confirmation is required.

WhatsApp subscribers in Zixflow have opt-in status and tag data that map to Odoo CRM contacts with the WhatsApp field enabled and a tag indicating the subscriber source. Subscriber migration requires that the Odoo WhatsApp Business API app is installed and configured before the migration runs; if WhatsApp is not set up in Odoo, subscriber data has no destination and we flag this before migration begins. Zixflow's default 500 WhatsApp contact cap is not an Odoo constraint — we note it as a Zixflow-specific billing artifact.

Zixflow custom contact properties including AI-generated enrichment fields export as flat key-value pairs. We pre-create the corresponding custom fields in Odoo on res.partner before contact migration, matching field names and verifying data types (char, text, integer, float, date, boolean, selection). Any Zixflow property without an exact Odoo type equivalent is flagged in the mapping document and the customer chooses between storing as text or splitting across compatible Odoo field types.

Flow automation credit usage is a Zixflow billing metric, not a data record. It does not migrate. We note the current balance as a reference for the customer to plan their Odoo automation credit or SMS gateway spend. If the customer uses Odoo SMS or a third-party SMS provider post-migration, the credit model is entirely new and unrelated to Zixflow wallet balance.

Zixflow Wallet is a financial balance for per-sent messaging. It is not customer data and does not migrate. We flag the current wallet balance for the customer to drain before closing the Zixflow account. Post-migration, the customer configures messaging via Odoo's WhatsApp Business API app, Odoo SMS, or a third-party SMS provider — each with its own credit or subscription model.

Zixflow Owners referenced on Contacts, Companies, and Deals map to Odoo Users. We resolve by email match. Any Zixflow Owner without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision the User before record import resumes. Inactive Odoo Users must be provisioned as inactive to preserve Owner attribution without granting login access.