Migrate from Zixflow to Microsoft Dynamics 365 Sales

Zixflow Contacts map to either Salesforce Lead (unqualified) or Contact (qualified) depending on the contact's lifecycle stage or collection membership. We assess the source schema during discovery: if Zixflow records carry a sales-qualified flag or belong to a sales-oriented Collection, we route them as Contacts with a parent Account lookup. Contacts without an Account assignment are created as Contacts with a placeholder Account for admin resolution post-migration.

Zixflow Collections are list groupings that have no direct Microsoft Dynamics 365 Sales equivalent. We generate a Collection membership mapping table (Contact email to Collection name) during export and offer two destination strategies: create a multi-select picklist custom field on Contact for small Collection counts, or build a separate Contact List entity via a Power Apps canvas app for larger or more dynamic groupings.

Zixflow custom fields (including AI-generated custom fields) on Contacts map to typed Microsoft Dynamics 365 Sales fields. We inspect the Zixflow field schema via API during scoping, map text to Single Line of Text, number to Whole Number or Decimal, date to Date field, and multi-select to Option Set. Custom field creation happens in the destination Dataverse environment before Contact migration begins.

Zixflow Inbox threads (across WhatsApp, SMS, Email, and RCS) migrate as Activity logs. Each message becomes a Note or Task record with the channel type preserved in a custom field, the sender/recipient mapped to the Contact lookup, and the timestamp preserved. Thread ordering is maintained by ActivityDate. The threaded conversation view does not replicate in Dynamics 365; it surfaces as a reverse-chronological activity timeline.

Zixflow Form submissions are captured as Contact field values (for known form fields that map to existing Contact fields) and as a Note record for any raw submission payload. The form builder itself does not migrate; we recommend Dynamics 365 Forms or Power Apps portals as the replacement for web-based lead capture.

Zixflow User records map to Dynamics 365 User accounts by email address. Active Zixflow users who are not yet provisioned in the destination Dynamics 365 org are queued for admin provisioning before Contact migration begins. Role and permission structures in Zixflow are documented for manual recreation because Zixflow role definitions are not exported as portable data.

Zixflow Flows are visual node-graph automation definitions that do not export as portable code. We inspect every active Flow during scoping, document its trigger conditions, conditional branches, and action sequences in a structured runbook, and deliver it to the customer's admin team for rebuild in Microsoft Dynamics 365 Sales (using Sales Automation features or Power Automate if cross-application triggers are needed). This is documentation only, not data migration.

Analytics outputs (open rates, click rates, delivery metrics) are aggregated reporting artifacts generated at query time from raw event data. They are not stored as discrete records in Zixflow and cannot be exported as structured data. We flag this gap during scoping and recommend rebuilding reporting in Microsoft Dynamics 365 Sales or Power BI from the migrated Contact and Activity data post-migration.