Migrate from Freshsales to Microsoft Dynamics 365 Sales

Discovery and edition selection

We audit the source Freshsales portal across plan tier (Free/Growth/Pro/Enterprise), custom field definitions, custom object schemas, pipeline count, active workflows, active sales sequences, engagement volume, and file attachment sizes. We pair this with a Microsoft Dynamics 365 Sales edition recommendation: Professional at $65/user covers most migrations without custom objects; Enterprise at $105/user is required for Copilot AI, advanced pipeline intelligence, and conversation intelligence through Teams; Premium at $150/user includes full AI surface coverage. The discovery output is a written migration scope and an edition recommendation aligned to the customer's existing Microsoft 365 licensing.

Schema design and Lead-to-Contact mapping configuration

We design the destination schema in Microsoft Dynamics 365 Sales . This includes provisioning custom fields (with typed equivalents for Freshsales custom field data types), Record Types (one per Freshsales pipeline), Sales Processes (stage value whitelist per Record Type), and the Lead-to-Contact field mapping configuration that Dynamics 365 requires for data to transfer during Lead qualification. We also configure the Contact-to-Account relationship mapping so that when Contacts are created from Freshsales data they are linked to the correct Account. Schema is deployed to a Dynamics 365 Sandbox for validation before production migration.

Sandbox migration and reconciliation

We run a full migration into a Dynamics 365 Sandbox using production-like data volume. The customer's RevOps lead reconciles record counts (Leads in, Contacts in, Accounts in, Opportunities in, Activities in), spot-checks 25-50 random records against the Freshsales source, and validates the Lead-to-Contact field mapping behavior by qualifying a test Lead in Dynamics 365. Any mapping corrections or validation rule adjustments happen in the sandbox before production migration begins.

User provisioning and owner reconciliation

We extract every distinct Freshsales Owner referenced on Contact, Account, Deal, and Activity records and match by email against the Dynamics 365 destination org's User table. Owners without a matching User go to a reconciliation queue. The customer's Dynamics 365 admin provisions any missing Users before record migration resumes. Migration cannot proceed past this step because OwnerId references are required on most standard objects in Dynamics 365.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from Freshsales Accounts, first because both Contact and Opportunity carry AccountId), Contacts (with AccountId resolved), Leads (with status and score fields), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Products and Pricebook entries, Activity history (Tasks and Events via Dynamics 365 Data Migration Manager or Bulk API), Custom field data on all objects. Each phase emits a row-count reconciliation report before the next phase begins. We sample activity records for field-level accuracy against the Freshsales source.

Cutover, validation, and workflow rebuild handoff

We freeze Freshsales writes during cutover, run a final delta migration of any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record. We deliver the Workflow and Sequence inventory document to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's sales team. We do not rebuild Freshsales Workflows as Power Automate flows inside the migration scope; that work is documented for the customer's Microsoft partner or admin team to handle as a separate engagement.