Migrate from Salesflo Engage to Microsoft Dynamics 365 Sales

Salesflo Engage team members map directly to Dynamics 365 systemuser records. Owner resolution uses email matching against the destination user list — unmatched owners are flagged before migration so their records land with a fallback owner. This ensures referential integrity and prevents orphaned records in the destination system.

Scheduled visits translate to Dynamics 365 Appointment records with visit start time mapped to ScheduledStart, end time to ScheduledEnd, and status values (completed, cancelled, no-show) mapped to StateCode and StatusCode. Original timestamps are preserved in custom datetime fields on the appointment record for historical reference.

Unscheduled visits and general field activity records become Dynamics 365 Task entities. A custom flag field (Unscheduled_Visit__c) distinguishes them from routine tasks, and visit outcome and notes map to the Description field. Owner resolves by email match to systemuser for accurate assignment tracking.

Salesflo Engage location and store records map to Dynamics 365 Account records. Store name maps to Account.Name, full address splits into Address1 fields. GPS latitude and longitude are preserved as custom decimal fields (Location_Latitude__c and Location_Longitude__c) since Dataverse has no native location entity.

Dynamics 365 has no native form or survey entity. Each Salesflo Engage form becomes a custom Dataverse table named FormSubmission with fields for Form_Name__c (text), Submitted_At__c (datetime), Submitted_By__c (lookup to systemuser), and Response_Data__c (multitext storing the full JSON response payload for queryable reference.

Salesflo Engage workflow definitions do not migrate to Dynamics 365. We export each workflow as a structured JSON document describing its steps, triggers, and assignments — your Dynamics admin uses this as a reference to rebuild equivalent flows in Power Automate. Workflows are always disclosed as a manual-rebuild item in our migration plan.

Salesflo Engage team structure and role assignments map to Dynamics 365 Security Roles. Each Salesflo team becomes a corresponding D365 security role; you define which entities and fields each role can read, write, or delete. Page layout assignments are a separate destination-side configuration step.

Notes and file attachments attached to Salesflo Engage visit records migrate as Dynamics 365 Annotations (note records). Files re-upload to SharePoint or Dataverse storage depending on your D365 configuration. Inline images in notes are downloaded and rehosted in the destination document library.

Individual form submissions become rows in the custom FormSubmission Dataverse table. The Submitted_At__c field preserves the original submission timestamp. Response_Data__c stores the complete JSON payload so the full survey context is queryable in D365 even though there is no native form builder.

GPS coordinates captured at visit time map to Location_Latitude__c and Location_Longitude__c on the parent Account record, and to Visit_Latitude__c and Visit_Longitude__c on the Task record. This enables proximity searches and map-based reporting in Dynamics 365 using Power Apps or third-party map components without native location entities.