Migrate from Zixflow Marketing Automation to Microsoft Dynamics 365 Sales

Zixflow Contacts with engagement history and sales qualification signals map to Dynamics 365 Contact attached to an Account. Zixflow Contacts without qualification signals that represent early-stage prospects map to Dynamics 365 Lead. We apply the split using Zixflow's last_activity_date, lifecyclestage, and Collection membership as the qualification criteria, with the customer's admin confirming the threshold during scoping. The original Zixflow contact ID migrates as a custom field zixflow_contact_id__c on both Lead and Contact for cross-system audit.

Zixflow Collections are list grouping objects that Contacts belong to. We map Collections to Dynamics 365 Marketing Segments (available with Dynamics 365 Customer Insights - Journeys add-on) or to a multi-select custom field on Account and Contact holding Collection membership names. The customer chooses the target during scoping based on whether they license the Marketing module. Collection membership is preserved as a comma-separated list in the custom field when the Marketing Segments path is not available.

Zixflow custom contact properties, including AI-generated enrichment fields, export as flat key-value pairs and map to typed Dynamics 365 custom fields on Contact and Account. We match by property name with type inference: text to Single Line of Text, numeric to Number, date to Date field, boolean to Two Options. Any enrichment field with no direct equivalent is flagged as a custom field to create in the destination before migration runs.

Message logs from Zixflow's Inbox export with contact association, timestamp, channel type, and message body. We map these to Dynamics 365 Note records (for conversation history) or EmailMessage records (for email threads) linked to the parent Contact via the Regarding field. Channel type (WhatsApp, SMS, Email, RCS) is preserved in a custom field message_channel__c. Delivery status (sent/delivered/open) is Zixflow-internal and migrates as a read-only custom field rather than a native Dynamics 365 status because Microsoft Dynamics 365 Sales does not track WhatsApp delivery receipts natively.

Zixflow Form field definitions export and map to Dynamics 365 custom fields on Contact or Lead. Form submission history (lead capture records) migrates as Contact or Lead records with the form name preserved in a custom field form_source__c. Zixflow Forms themselves do not migrate; we recommend Dynamics 365 Marketing forms or a third-party form tool as the replacement for lead capture post-migration.

Zixflow Inbox threads export with message content, participant metadata, and contact reference. We resolve the contact reference to the migrated Dynamics 365 Contact record ID and re-link each thread to the Contact's activity timeline. Thread-level metadata (thread ID, message count) is preserved in a custom field on the first message record of each thread. Threads with no matching migrated Contact are held in a queue for admin resolution before the final delta import.

Zixflow WhatsApp Subscribers export with opt-in status, subscriber tags, and subscription date. We map opt-in status to a custom field whatsapp_opt_in__c on Dynamics 365 Contact and preserve tags in a multi-select custom field. Zixflow's default subscriber cap of 500 does not apply to the Dynamics 365 side, but the customer should confirm their WhatsApp Business account has sufficient message capacity for the migrated contact volume.

Zixflow Flows are built in a proprietary visual builder and cannot be exported as transferable automation logic. We extract the Flow name, trigger type, step count, and action summary for each active Flow and deliver this as a written specification document. The customer's Dynamics 365 admin or a Microsoft partner rebuilds equivalent logic using Dynamics 365 Workflows, Power Automate, or Power Apps. Flows do not migrate as code.

Zixflow Owners map to Dynamics 365 User records matched by email address. Any Zixflow Owner without a matching Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision the User before record import resumes. Owner assignments on message logs and Contact records update to the resolved Dynamics 365 OwnerId during migration.