Migrate from Zixflow to Freshsales

Zixflow Contacts with a qualified lifecycle stage (deal interested, demo scheduled, proposal sent, or customer) map to Freshsales Contact attached to a corresponding Account. Contacts with an unqualified stage (subscriber, lead, unqualified) map to Freshsales Lead. We compute the split at migration time using Zixflow's lifecycle stage property, preserve the original stage in a custom field zx_original_lifecycle__c on both Lead and Contact for reporting continuity.

Some Zixflow accounts inherited deal-like records from the Sales Simplify era that have no native Deals object in current Zixflow schema. We identify these by scanning for Contacts that have deal-approximating custom field patterns (deal_amount, deal_stage, close_date fields). Each identified record generates a Freshsales Deal with the custom field values mapped to Deal fields. The original Contact is preserved as the Deal's primary Contact.

Zixflow Collections (named lists and groupings) map to Freshsales Tags. We generate a membership mapping table during export, then populate Tags on the migrated Contact or Lead records. If a Collection name conflicts with an existing Freshsales tag, we prefix with the Collection name in full to preserve semantics. Segments in Freshsales are optionally rebuilt from tag combinations post-migration.

Zixflow custom fields on Contacts (including AI-generated custom fields) map to Freshsales Contact custom fields, or Lead custom fields for records that split into Leads. We create the corresponding custom fields in Freshsales first via Admin Settings > Custom Fields, then populate values during the record import. Custom field data type mapping: text to Text, number to Number, date to Date, dropdown to Picklist.

Zixflow Inbox conversations (multi-channel message threads across WhatsApp, SMS, Email, RCS) flatten into Freshsales Tasks and Notes. Each message in a thread generates a Task record with the channel type recorded in a custom field, and the thread summary becomes a Note attached to the Contact or Lead. We preserve the original timestamp and sender attribution but do not reproduce the threaded UI model.

Form submissions from Zixflow migrate as Contact custom field values where the form field maps to an existing or new Contact field. A separate Form Submission log record is created as a Note on the Contact with the form name, submission timestamp, and field values. The visual form builder structure does not transfer; we document each form's field structure for rebuilding in Freshsales Web-to-Lead or native form builder.

Zixflow Flows define automation logic as visual node-graphs. The node-graph structure is not a portable export format. We inspect each active Flow during scoping, document its trigger conditions, branch logic, and action sequence, and deliver a structured Freshsales Workflow inventory with a recommended equivalent in Freshsales' automation builder. The customer's Freshsales admin rebuilds each Flow as a Workflow post-migration.

Zixflow user accounts map to Freshsales User records by email match. We extract owner references from Contact, Collection, and Inbox records and resolve them against the destination Freshsales User table. Users without a matching Freshsales account enter a reconciliation queue for the customer to provision before record import. Role and permission structures are not transferred and must be reconfigured in Freshsales Admin Settings.