Migrate from Zixflow Marketing Automation to HubSpot

Zixflow contacts migrate directly to HubSpot contacts. All standard properties (name, email, phone, job title, address) map to HubSpot's native contact fields. Zixflow's AI-enriched properties (inferred interests, Transflow completions) migrate as HubSpot custom properties since HubSpot has no native AI-inference field equivalent.

Zixflow companies migrate to HubSpot companies. Domain-based matching is applied — if a Zixflow contact's email domain matches an existing HubSpot company, the contact's company association auto-links. Multi-company per contact (N:N model in Zixflow) collapses to the primary company link in HubSpot with additional associations recorded in contact properties.

Zixflow deals migrate to HubSpot deals. If Zixflow uses deal stages, these map to HubSpot pipeline stages via value-mapping. Zixflow deals without pipeline association land in HubSpot's default pipeline. Stage probability and forecast category are applied based on HubSpot's default stage values unless custom mappings are specified before migration.

Zixflow's pipeline (if configured) becomes a HubSpot Sales Pipeline. Each Zixflow pipeline maps to one HubSpot pipeline. If Zixflow uses a single default pipeline, it maps to HubSpot's default Sales pipeline. Pipeline stages in Zixflow map value-by-value to HubSpot stage names within the target pipeline.

Zixflow Flows (automations) do not migrate. HubSpot Workflows use enrollment-based triggers fundamentally different from Zixflow's visual flow-action model. FlitStack exports Zixflow Flow definitions as a structured JSON reference document for your HubSpot admin to manually rebuild in HubSpot's workflow builder.

Zixflow Cadence sequences have no direct HubSpot equivalent. Sequences require manual rebuild using HubSpot Sequences (available in Sales Hub Professional and Enterprise). FlitStack exports sequence step definitions, step timing, and contact enrollment data as a reference CSV for manual sequence recreation.

Zixflow campaigns migrate to HubSpot campaigns. Campaign names, descriptions, and original create dates transfer. HubSpot campaign membership is created per contact who was part of the Zixflow campaign — enrollment history is preserved as campaign member records with original enrollment timestamps.

Zixflow engagement history (calls logged, emails sent, meetings scheduled) migrates to HubSpot's contact timeline as engagements. Each activity preserves original timestamp, owner (resolved by email match to HubSpot users), and any notes or outcome recorded in Zixflow. Ensuring audit trails remain intact.

Zixflow form submissions migrate as HubSpot engagements with type='note'. Form field names and values are preserved in the note body. HubSpot's native form submission tracking is not auto-created — your HubSpot admin can connect HubSpot forms post-migration to capture future submissions directly.

Zixflow custom properties on contacts, companies, or deals migrate as HubSpot custom properties. FlitStack creates the custom properties in HubSpot before data lands. Property type mapping: Zixflow text → HubSpot single-line text; Zixflow number → HubSpot number; Zixflow date → HubSpot date; Zixflow dropdown → HubSpot single-line text (no native dropdown equivalent for all property types).

Zixflow users resolve to HubSpot users by email match. Unmatched owners are flagged before migration — teams either pre-create HubSpot users or assign their records to a fallback owner. Deactivated Zixflow users are flagged separately; your admin decides whether to activate them in HubSpot or archive their records under a generic owner.

Zixflow's wallet-based messaging balance and credit consumption history have no HubSpot equivalent. Messaging costs and credit usage are preserved as a custom note on the associated contacts for audit purposes. Going forward, HubSpot's paid messaging add-ons handle outbound channels independently.