Migrate from Sales Flow Technologies to Microsoft Dynamics 365 Sales

Sales Flow Contacts with no sequence enrollment or with lifecycle stage indicating unqualified prospect status map to Microsoft Microsoft Dynamics 365 Sales Lead. Contacts actively enrolled in multi-step Sequences or marked as sales-qualified map to Microsoft Dynamics 365 Sales Contact. We preserve the original Sales Flow contact ID in a custom field sft_contact_id__c for audit and cross-reference. Email address is the dedupe key for Contact insert; duplicate detection runs against the Dynamics 365 email index before each batch commits.

Sales Flow Prospect Lists are named groupings of Contacts. We export list membership as a CSV with one row per Contact-List relationship, then recreate list membership in Microsoft Dynamics 365 Sales as Tags on the Contact record. If the customer uses more than 10 named lists, we recommend a custom Prospect List custom entity or a Power Apps canvas app to maintain the grouping hierarchy rather than flattening it entirely into Tags.

Sales Flow Sequences define multi-step cadences across LinkedIn, Email, and InMail. The sequence step order, channel, template name, and delay between steps migrate as a JSON blob stored in a custom field sft_sequence_data__c on the Contact record. Microsoft Dynamics 365 Sales has a native Sequence feature that supports similar cadence modeling; the customer's admin uses the Workflow Migration Summary to rebuild sequence logic in the Dynamics native Sequence builder. Step-level completion timestamps are partial in standard CSV export; we request the Advanced Analytics CSV to supplement missing timestamps where available.

Sales Flow Campaigns bundle multiple Sequences under a single objective. Campaign names and associated sequence counts migrate as a custom entity or as a tagged grouping on the relevant Contacts. Channel routing logic and A/B testing configurations in Sales Flow do not map directly to Dynamics 365; we document these in the Workflow Migration Summary for rebuild as Power Automate flows or Marketing Cloud Customer Journeys.

Sales Flow User accounts (Admin and Standard roles) map to Microsoft Dynamics 365 Sales User records by email match. We resolve Hub Owner IDs on Contact and Sequence records to the corresponding Dynamics 365 OwnerId. Any Sales Flow user without a matching Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision before Contact migration begins.

Sales Flow provides per-sequence open rates, reply rates, and connection acceptance rates as structured CSV exports. These metrics migrate as read-only custom fields on the Contact record (sft_open_rate__c, sft_reply_rate__c, sft_connection_acceptance_rate__c) for historical reference. Microsoft Dynamics 365 Sales native reporting and Power BI integration can surface these as custom report types; the migration does not include Power BI dashboard construction.

Inbox messages represent the conversation thread between the rep and the prospect across LinkedIn and email. These are stored in LinkedIn's infrastructure and are not accessible via Sales Flow export. We flag this limitation explicitly in the migration scope and advise the customer that rep-level inbox context will not transfer. This is a Sales Flow platform limitation, not a pair-specific gotcha.

Sales Flow Workflows define conditional branching logic (e.g., if no reply after 3 days, send template B) that lives in the application state and is not exposed via CSV or API. We do not migrate Workflows as code. We produce a detailed Workflow Migration Summary documenting every conditional rule, step order, timing logic, and branch condition so the customer's admin can reconstruct it in Power Automate or the Dynamics 365 native Sequence builder. This document is the most critical deliverable for post-migration continuity of automated follow-up sequences.