Migrate from Zixflow to HubSpot

Direct map. Zixflow contact fields (firstname, lastname, email, phone, jobtitle) map to HubSpot's native Contact properties. Company association routes to a HubSpot Company record via domain lookup, with unmatched domains saved as a custom property for later review. Owner resolved by email match against HubSpot users; unmatched owners are flagged for assignment before the load phase.

Zixflow has no native lifecycle_stage equivalent. We derive lifecycle context from Zixflow Flow enrollment status and WhatsApp opt‑in state, then write these as a custom lifecyclestage property (Subscriber, Lead, MQL, SQL, Opportunity, Customer, Evangelist) on each HubSpot contact. If a contact is enrolled in multiple Flows, the most recent active Flow determines the stage; contacts without Flow data default to Subscriber and are flagged for manual review.

Direct map. Zixflow company fields (name, domain, industry, numberofemployees, annualrevenue) map to HubSpot Company properties. Parent‑child company hierarchies map to HubSpot's parent company association, with the top‑level company set as primary. Industry values are matched value‑by‑value to HubSpot's pick‑list; unmapped values are stored as free‑text for later enrichment. Multi‑company contacts collapse to one primary Company link, while additional associations are retained as secondary links.

Direct map. Zixflow deals (dealname, amount, dealstage, closedate) map to HubSpot Deals, with each Zixflow pipeline creating a native HubSpot Deal Pipeline and stage names mapped value‑by‑value to HubSpot dealstage pick‑list values. Zixflow's engagement score attached to a deal migrates as a custom deal property (deal_engagement_score__c) for reporting continuity. Historical stage changes are retained as a custom audit log on the deal record.

Zixflow's pipeline structure becomes a HubSpot native Deal Pipeline. Each Zixflow pipeline name creates a named HubSpot pipeline; stage names map value-by-value to HubSpot dealstage pick-list values. Zixflow engagement scoring per deal is preserved as a custom number field on the deal.

Zixflow call records (duration, outcome, direction, owner, timestamp) map to HubSpot engagement call records, preserving the original call date and time as the engagement timestamp. Call subject, duration in minutes, direction (inbound/outbound), and outcome (connected, voicemail, no answer) are stored as engagement metadata on the associated contact timeline. Owner is matched by email to a HubSpot user; unmatched owners are recorded as a custom property for later assignment.

Zixflow email engagement (subject, body, status: sent, delivered, opened, bounced, owner) maps to HubSpot email engagement records attached to the contact, preserving the original send timestamp as the engagement date. Email direction (inbound/outbound) is recorded as a custom property, and open or click tracking data is stored in HubSpot's engagement metadata, with bounced statuses flagged for review.

Zixflow's multi‑channel message history has no native HubSpot equivalent, so WhatsApp, RCS, and SMS conversations are logged as HubSpot timeline engagement notes. Each note captures the message body, direction (sent/received), channel type (WhatsApp/RCS/SMS), delivery status, and original timestamp stored in custom contact properties. Any messages lacking a timestamp receive the Zixflow export date as a fallback.

Zixflow Flows (automation workflows) do not migrate directly and must be rebuilt in HubSpot's Workflows tool. We export a detailed Flow definition summary that lists trigger conditions, action steps, credit consumption estimates, and any conditional branching logic. This document serves as a rebuild reference for your HubSpot admin or a FlitStack consultant, and we recommend a testing phase in a sandbox before activating the new workflows in production.

Zixflow Cadences (outbound messaging sequences) do not migrate and must be rebuilt in HubSpot Sequences. We export cadence step definitions that capture step order, channel (email, WhatsApp, SMS), delay between steps, template content, and any personalization tokens. This export serves as a rebuild guide for your HubSpot admin or a FlitStack consultant, with a recommended testing period in a non‑production environment before launching the sequences live.

Zixflow's centralized Inbox view (multi-channel conversation threads) has no direct HubSpot equivalent. Message threads are split by contact and logged as engagement notes; assignee and conversation status are preserved as custom contact or ticket properties if a service ticket workflow is set up post-migration.

Zixflow contact custom properties migrate as HubSpot contact custom properties. Field type parity is assessed: text maps to string, number to number, picklist to dropdown, date to date, and multi‑select picklists are converted to HubSpot's checkbox or multi‑checkbox type where supported. Properties with Zixflow‑specific type definitions are created as HubSpot custom properties with type‑aware mapping, and any unsupported types are stored as text for later re‑evaluation.