Migrate from Salesflare to Microsoft Dynamics 365 Sales

Discovery and schema scoping

We audit the source Salesflare account: object counts (Accounts, Contacts, Opportunities), pipeline and stage definitions, custom property schema per object, active email sequences, user list, tag usage, and attachment volume. We map this to a Microsoft Dynamics 365 Sales edition decision: Sales Professional ($65/user) covers standard account-contact-opportunity migrations; Sales Enterprise ($105/user) is required for complex multi-pipeline, territory, or product-line routing; Sales Premium ($150+/user) if the customer needs Copilot for Sales and Sales Accelerator sequences. The discovery output is a written scope document with object counts, field mapping draft, and pipeline-to-Record-Type plan.

Dynamics schema design and Record Type configuration

We design the destination schema in the Dynamics 365 target environment. This includes creating custom fields (sf_ prefix) for Salesflare native fields that have no Dynamics equivalent, configuring Record Types and Sales Processes for each Salesflare pipeline, and setting up the Contact.AccountId Lookup relationship model. Schema is deployed into a Sandbox environment first for validation before any production migration runs.

Sandbox migration and reconciliation

We run a full migration into the Dynamics Sandbox using production-like data volume. The customer's RevOps or admin lead spot-checks 25-50 records per object against the Salesflare source, validates that Account-Contact relationships resolved correctly, confirms stage names mapped to the right Sales Process, and signs off before production migration begins. Mapping corrections happen in Sandbox, not production.

Owner and User provisioning

We extract every distinct Salesflare Owner referenced on Opportunities and Contacts and match by email against the Dynamics target org's User table. Owners without a matching Dynamics User are held in a reconciliation queue; the customer's admin provisions missing Users before migration resumes. OwnerId is a required field on Opportunity in most Dynamics configurations, so this step gates the Opportunity import phase.

Production migration in dependency order

We run production migration in dependency order: Accounts first (as parent records), Contacts second (with AccountId resolved from the Account import), Opportunities third (with OwnerId, AccountId, and RecordTypeId resolved), Activity history fourth (Tasks, Emails, Appointments via Dataverse API with parent-record lookup), Tags fifth (as pipe-delimited text or Category records), and Custom Properties last (as custom fields appended to each object). Each phase emits a row-count reconciliation report before the next begins.

Cutover, validation, and sequence rebuild handoff

We freeze writes in Salesflare during cutover, run a final delta migration for any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record. We deliver the email sequence inventory document with step-by-step definitions and recommended Dynamics Sales Accelerator or Power Automate equivalents to the customer's admin team. We provide a one-week hypercare window for reconciliation issues. We do not rebuild sequences as Power Automate flows inside the migration scope; that is a separate engagement or internal admin task.