Migrate from Zixflow to HighLevel

Zixflow Contacts migrate directly to GoHighLevel Contacts. Standard fields (first name, last name, email, phone) map cleanly. Custom fields migrate as GoHighLevel Contact custom fields with equivalent data types (text, number, date, dropdown). We resolve Contact ownership by email match against GoHighLevel Users. If a Contact has no matching User in GoHighLevel, the record migrates unassigned and the customer admin assigns ownership post-migration.

Zixflow Collections (list groupings) do not have a direct GoHighLevel equivalent. We preserve Collection membership as a tag-membership table and apply the corresponding tags to each Contact during migration. If the customer uses Collections for segmentation logic (e.g., VIP list, churned list), we document the Collection-to-Tag mapping so the segmentation logic is reproducible in GoHighLevel's Smart Lists and workflow filters.

Zixflow custom fields on Contacts migrate to GoHighLevel Contact custom fields. We pre-create the destination field definitions in GoHighLevel during schema setup, matching field types (text, number, date, checkbox, dropdown) before any records are loaded. AI-generated custom fields from Zixflow migrate as read-only text fields with their computed values carried over. Field ordering and grouping in GoHighLevel is a post-migration admin task.

Zixflow Flows define automation logic as a node-graph that is not portable to GoHighLevel's workflow builder. We inspect each active Flow during scoping, document its trigger conditions, branching logic, action sequence, and delay configuration, and deliver a structured runbook so the customer's GoHighLevel admin can rebuild the logic in the destination workflow builder. Flows with complex conditional branching may require multiple GoHighLevel Workflows to replicate.

Zixflow Inbox threads (multi-channel message history across WhatsApp, SMS, Email, and RCS) migrate as structured activity records in GoHighLevel. We flatten each conversation into a chronological series of Task records (one per message) with the channel type stored in a custom field, the message body in the Task description, and the timestamp preserved in ActivityDate. GoHighLevel's conversation view groups these by Contact after migration, but the original multi-channel threading does not reproduce identically.

Zixflow Form definitions (field structure) migrate as GoHighLevel form fields with corresponding Contact custom fields pre-created in the destination. Form submission records migrate as Contact records with the submitted field values populated into the matched custom fields, plus a Form submission log stored as a Note on the Contact. The visual form builder and styling do not transfer; the customer rebuilds form appearance in GoHighLevel's form editor.

Zixflow User accounts migrate as GoHighLevel User records with role and permission structures recreated at the destination. We map Zixflow users by email match and flag any permission gaps in the runbook. Zixflow does not expose role definitions via API, so permission reconstruction requires the customer to provide a role matrix during scoping.

Analytics data including open rates, click rates, delivery metrics, and campaign performance reports are aggregated reporting outputs generated at query time in Zixflow. They are not stored as discrete records and cannot be exported as structured data. We do not migrate this object class.