Migrate from Zixflow Marketing Automation to Zoho CRM

Zixflow Contact records map to Zoho CRM Leads (for unqualified prospects) or Contacts (for qualified records attached to Accounts). We compute the split using Zixflow's contact properties such as lifecycle stage or tag membership, preserving any AI-generated enrichment fields as Zoho custom fields. Standard fields (First_Name, Last_Name, Email, Phone) map directly. We create any missing Zoho custom fields before import and validate field types to avoid truncation of long-text enrichment data.

Zixflow Collections map to Zoho Lists. Each Collection membership record generates a corresponding Zoho List entry for the contact. We also populate Zoho Tags with Collection names so contacts can belong to multiple groupings via tag membership. Zoho's list-to-contact assignment uses a different mechanism than Zixflow's Collection API; we resolve this by batch-assigning contacts to Lists after the primary contact import completes.

Zixflow Form field definitions export as field name and type metadata. We map each form field to a Zoho CRM custom field on the Lead or Contact module, creating the field if it does not exist. Form submission history migrates as contact records with a note capturing the original form name and submission timestamp. If the customer used form-based lead scoring, we document the scoring logic for rebuild in Zoho Scoring Rules.

Zixflow WhatsApp Subscribers migrate to Zoho CRM Contacts with the WhatsApp opt-in consent preserved in a custom field. We export subscriber status (active/inactive), opt-in date, and any subscriber tags. Zoho CRM's WhatsApp Business integration requires a separate WhatsApp Business account verification; we flag this as a pre-migration prerequisite and do not handle the WABA setup within the data migration scope.

Zixflow Inbox conversation threads export with message text, timestamps, and contact attribution. We migrate the conversation text as Notes attached to the Zoho CRM Contact record, with the conversation date preserved. Thread-level metadata (thread ID, channel source) is documented in a separate reference sheet since Zoho does not have a native conversation thread object. The customer manually re-links any critical threads if needed.

Zixflow message logs (WhatsApp, SMS, Email, RCS) export with direction (sent/received), timestamp, content, and contact association. We map each message to a Zoho CRM Task record with TaskSubtype and custom fields for channel type and delivery status. Delivery status (sent/delivered/open) is Zixflow's internal tracking and migrates as a read-only custom field; Zoho's analytics treat it as historical data rather than a live tracking metric.

Flows are visual workflow definitions stored in Zixflow's proprietary builder format. Automation logic does not export as transferable data. We export each Flow's name, trigger type, and step summary to a written inventory document. The customer's admin rebuilds each Flow in Zoho Workflow Rules, Blueprint, or Deluge scripts post-migration. This documentation handoff is included in our standard scope; we do not build the Zoho workflows themselves.

Zixflow custom contact properties including AI-generated enrichment fields export as flat key-value pairs. We match each custom property to a Zoho CRM custom field by name, creating the field if absent and validating type compatibility (text, number, date, picklist). AI enrichment fields that lack an exact Zoho equivalent are flagged during scoping and mapped to the closest available field type with a note for the customer to review post-import.

Zixflow messaging credits are a financial balance, not customer data. We exclude wallet balance from migration scope and recommend the customer drains remaining credits before closing the Zixflow account. We export the current balance as a reference figure for the customer's finance team to reconcile against the final billing cycle.

Flow automation credit usage history is a billing metric, not a customer data record. It does not migrate. We note the current monthly consumption as a reference so the customer's admin can set appropriate Workflow Rule execution limits in Zoho CRM's automation settings.