Migrate from Zixflow Marketing Automation to Pipedrive

Zixflow Contact records map directly to Pipedrive Person. Standard fields (name, email, phone) map cleanly. We resolve duplicate Contacts by email dedupe key during import. Custom AI enrichment fields (custom contact properties) map to Pipedrive custom fields; we infer field type from the property value format (text, number, date, or picklist) and create the Pipedrive custom field in the destination before migration. Contact owner resolves by email match to Pipedrive User.

Zixflow Collections are list/grouping objects where a single Contact can belong to multiple Collections. Pipedrive Lists are membership-based but do not natively support multi-list overlap in the same way. We map each Collection to a Pipedrive List, then apply a parallel tag (Collection name as tag value) to Contacts that belong to multiple Collections. This preserves full membership history and enables multi-dimensional segmentation in Pipedrive. If the customer prefers Lists only, we document the multi-collection overlap for manual reassignment.

Zixflow Company records (if present) map to Pipedrive Organization. Organization is created before Person import so that the org_id relationship is satisfied at the moment of Person insert. The company domain maps to Organization's Website field. We use Organization name as the dedupe key during import.

Zixflow Forms capture leads and feed data into Contacts and Collections. We export form field definitions and map them to Pipedrive custom fields on Person. Form submission history migrates as Person records with field values populated from the submission data. We flag any Zixflow form fields that lack an equivalent Pipedrive field type for manual configuration.

Zixflow Inbox aggregates multichannel conversations (WhatsApp, SMS, Email, RCS). Message threads and metadata export via API and map to Pipedrive Activity records. Each conversation thread becomes a single Activity with the channel type (call, email, message) in ActivityType and the full thread content in the notes field. Thread association to Person requires re-linking in Pipedrive because conversation IDs are destination-system IDs; we resolve the Person contact by email at migration time. Delivery status (sent/delivered/open) is Zixflow-internal tracking and does not map to Pipedrive's Activity model.

Zixflow WhatsApp Subscribers (opt-in status and tag data) export and map to Pipedrive Person with List membership added for any WhatsApp-specific Pipedrive List and a tag applied for WhatsApp opt-in status. Zixflow's default 500 WhatsApp subscriber cap is a billing constraint on the source platform and does not impose any limit in Pipedrive. We flag subscriber volume post-migration if it approaches any Pipedrive messaging add-on limits.

Zixflow custom contact properties including AI-generated enrichment fields export as flat key-value pairs. We match each property to a Pipedrive custom field by name and inferred type. For multi-value or JSON-structured enrichment fields, we flatten to comma-separated strings or map to Pipedrive multi-select picklists where applicable. Any property without an exact Pipedrive field type equivalent is flagged for manual configuration before migration runs.

Zixflow Flows are visual workflow definitions built in a proprietary builder format. Automation logic cannot be exported or transferred to Pipedrive Automations because they use different trigger-event-action models. We export a documentation snapshot of each Flow: name, trigger type, step summary, and action list. This document is handed off to the customer so their admin can rebuild equivalent Pipedrive Automations post-migration. Pipedrive Automations require the Growth plan or higher.

Flow credit usage history is a billing metric, not a customer data record. It does not migrate. We note the current credit balance as a reference for the team to reallocate spend or purchase decisions in Pipedrive Automations.

Messaging credits in the Zixflow Wallet are a financial balance, not customer data. Wallet balance is excluded from migration scope. We recommend the team drains or forfeits remaining credits before closing the Zixflow account. Pipedrive does not have an equivalent messaging credit model.

Zixflow does not have a native Deal object; sales pipeline data in Zixflow is typically stored in custom contact fields or tracked externally. We audit Zixflow custom fields for any that represent deal value, stage, or close date and map them to Pipedrive Deal fields (title, value, stage, expected_close_date) during migration. Pipedrive Deal creation is configured in the destination org before migration runs.