Salesforce to Dynamics 365 migration
We migrate Accounts, Contacts, Leads, Opportunities, and engagement history from Salesforce Sales Cloud into Microsoft Microsoft Dynamics 365 Sales with the Account-Contact relationship resolved upfront, activity records preserved through the Dataverse API, and every Salesforce object mapped to its Dynamics 365 equivalent before cutover.
FlitStack AI migrates accounts, contacts, connections, leads and opportunities from Salesforce to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 5-8 weeks.

What moves from Salesforce to Dynamics 365?
Moving from Salesforce Sales Cloud to Microsoft Microsoft Dynamics 365 Sales is a cross-platform migration that requires translating Salesforce's object model and relationship graph into Dynamics 365's Dataverse structure.
Read the full summary
The core entities map cleanly—Accounts, Contacts, Leads, Opportunities, Cases, Products, and Quotes—but the relationship topology differs: Salesforce uses a many-to-many Account Contact Relation junction table while Dynamics 365 attaches Contacts directly to Accounts, requiring a relationship-flattening step during import. We resolve parent Account hierarchies first, import Contacts with their primary AccountId, then replay any secondary Account relationships as a separate junction pass. Opportunity Team Members and Territory assignments reference User IDs that must exist in the destination tenant before the junction records can be inserted. Workflow Rules and Process Builder automations do not migrate; we deliver a written inventory of every active automation with a recommended Power Automate or Dynamics workflow equivalent for the customer's admin to rebuild post-migration.
Account → Account
Salesforce Account maps directly to Dynamics 365 Account.
How it maps
The primary key mapping uses AccountId-to-accountid with Name, Industry, AnnualRevenue, Type, and BillingAddress migrating as standard fields. Parent-Account hierarchies require a recursive import pass: we import top-level Accounts (where ParentId is null) first, then resolve parent IDs and import child Accounts. The relationship preserves the hierarchy depth up to Dynamics 365's ten-level limit, which covers the vast majority of Salesforce org hierarchies.
Contact → Contact
Salesforce Contact maps to Dynamics 365 Contact with a critical relationship difference to resolve.
How it maps
Salesforce supports many-to-many Contact-to-Account relationships via the Account Contact Relation junction object; Dynamics 365 uses a primary AccountId on Contact with the Connection entity for secondary relationships. We import Contacts with their primary AccountId set, then replay secondary Account relationships as Connection records (fromcontacts and toaccounts) in a second pass. Email, Phone, Title, and custom contact fields migrate directly.
AccountContactRelation → Connection (Contact-to-Account)
Salesforce's Account Contact Relation junction table (which enables a Contact to belong to multiple Accounts with roles) maps to the Dynamics 365 Connection entity.
How it maps
Each Account Contact Relation record becomes a Connection with Record1Id pointing to the Account and Record2Id pointing to the Contact, with a custom Connection Role reflecting the original Account Contact Relation roles field. This second-pass migration runs only after both Accounts and Contacts are committed to Dataverse.
Lead → Lead
Salesforce Lead maps directly to Dynamics 365 Lead with field-level mapping of Name, Company, Email, Phone, LeadSource, Status, Rating, and custom fields.
How it maps
Salesforce Lead Status values map to Dynamics 365 Lead Status values via a pre-migration value map. If the source org uses Lead conversion mapping to auto-create Contacts and Accounts on conversion, we map the pre-conversion Lead record to the Dynamics 365 Lead and set the converted-flag fields accordingly.
Opportunity → Opportunity
Salesforce Opportunity maps to Dynamics 365 Opportunity with Stage, Amount, CloseDate, Probability, Description, and OwnerId fields.
How it maps
The OwnerId maps to the Dynamics 365 Owner (User) entity. Opportunity Record Type maps to Dynamics 365 Opportunity Type or a custom field if multiple sales processes are in use. Multi-currency Opportunities from Salesforce with CurrencyIsoCode map to Dynamics 365 TransactionCurrency with the appropriate exchange rate context.
OpportunityContactRole → Contact (opportunitycustomeraccountcontact role)
Salesforce Opportunity Contact Role junction records map to the Contact's opportunitycustomeraccountcontact role relationship in Dynamics 365.
How it maps
The Contact's primary role on the Opportunity is set via the Role field on that relationship. If a Salesforce Opportunity has multiple Contact Roles, we set the first Contact as primary and store additional roles in a custom field or notes for the customer's admin to distribute post-migration.
- AccountAccount1:1
- ContactContact1:1
- AccountContactRelationConnectionsplit
- LeadLead1:1
- OpportunityOpportunity1:1
- OpportunityContactRoleContacttransformed
+ 10 more in the mapping below
How Salesforce and Dynamics 365 differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Salesforce | Dynamics 365 |
|---|---|---|
| Account-Contact relationship | Many-to-many via Account Contact Relation junction object | Contact attached directly to Account with primary flag; secondary relationships via connection entity |
| Lead conversion model | Lead converts to Account, Contact, and optionally Opportunity; conversion mapping configurable | Lead converts to Contact and Account; Opportunity linked separately or via lead-to-opportunity configuration |
| Pricing model | Per-seat tiers from $25 to $550/user/month with storage overages and annual uplift | Per-seat at $95/user/month for Sales Enterprise including Copilot for Sales; no storage overage billing |
| Workflow and automation | Flow (formerly Process Builder and Workflow Rules) as the automation engine | Power Automate and Dynamics 365 workflow engine with a different trigger model |
| Custom objects | Custom Objects from Professional tier ($165/user) with unlimited per org | Custom tables via Dataverse from any tier with environment storage limits |
| AI integration | Einstein AI as a layered add-on across Sales Cloud editions | Copilot for Sales natively embedded in Outlook and Teams with no per-use pricing |
| Reporting | Salesforce Reports and Dashboards with custom report types and joined reports | Dynamics 365 built-in reports plus Power BI with native Dataverse connector |
What to watch for in a Salesforce to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Account-Contact many-to-many relationship requires two-pass migration
Salesforce's Account Contact Relation junction object allows a single Contact to associate with multiple Accounts with role-specific permissions.
How we handle it
Dynamics 365 stores a Contact's primary Account as a direct lookup field and handles secondary relationships via the Connection entity. A flat single-pass import that sets only the primary AccountId will silently drop every secondary Account relationship. We import Contacts with their primary AccountId, then replay all Account Contact Relation records as Dynamics 365 Connection records in a second pass, preserving every relationship the org has built.
Workflow Rules and Process Builder do not migrate to Power Automate
Salesforce has retired Workflow Rules and is restricting Process Builder, requiring orgs to migrate to Flow.
How we handle it
Dynamics 365 uses Power Automate and the native Dynamics 365 workflow engine as its automation layer, which operates on different triggers, conditions, and actions. We do not migrate automations as code. We deliver a written inventory of every active Salesforce Workflow Rule and Process Builder process with its trigger, conditions, and actions, plus a recommended Power Automate template or Dynamics 365 workflow equivalent. The customer's admin rebuilds these post-migration.
User ID reference chain blocks junction record migration
Opportunity Team Members, Account Team Members, and Territory Account Assignments in Salesforce all reference User IDs that must exist in the destination Dynamics 365 tenant before the junction records can be inserted.
How we handle it
We audit all User IDs during the pre-migration data audit and flag any Salesforce User without a corresponding Dynamics 365 User. The customer's tenant admin provisions missing users in Dynamics 365 before we begin the junction record pass. Skipping this step causes the junction insert to fail with a foreign-key violation on the Owner field.
Salesforce Bulk API quota pacing is required for large historical imports
Salesforce limits Bulk API to 15,000 batches per day with 10,000 records per batch.
How we handle it
For orgs with millions of historical records, this quota can be exhausted in a single migration day, blocking subsequent days. We pace imports across multiple days, monitor batch consumption in real time, and switch to the REST API Composite endpoint for smaller objects when the bulk quota is exhausted. The Dataverse target side also has API request limits per environment that we observe with exponential backoff.
Salesforce Contracts field mapping XML has no Dynamics 365 equivalent out-of-box
Salesforce Contracts uses a Field Mapping XML to create and update Contract records from Opportunity, Order, Quote, or custom objects with parent-to-child and child-to-child mapping relationships.
How we handle it
Dynamics 365 Contract creation follows the standard contract entity workflow without this flexible mapping configuration. We document every active Salesforce Contract field mapping during scoping and the customer rebuilds the equivalent logic in Dynamics 365 using Power Automate or a plugin. The contract record data itself migrates; the automated creation logic does not.
How the migration runs
Discovery and source org audit
We audit the source Salesforce org across edition, active objects, record counts per object, custom object definitions, Workflow Rules and Process Builder inventory, Territory configuration, and API usage over the prior 90 days.
What this step covers
We assess the destination Dynamics 365 environment's licensing tier, existing Dataverse tables, and any Power Platform capacity constraints. The discovery output is a written migration scope document covering object-by-object mapping, volume estimates, automation inventory, and a go/no-go readiness checklist for both source and destination.
User and Owner reconciliation
We extract every distinct Salesforce User ID and Owner ID referenced across Accounts, Contacts, Leads, Opportunities, Cases, and Activities and match by email against the destination Dynamics 365 tenant's User table.
What this step covers
Users without a matching Dynamics 365 User go to a reconciliation queue for the customer's tenant admin to provision before migration begins. Owner IDs on records must resolve to valid Dynamics 365 Users or the record insert will fail on the OwnerId reference.
Dataverse schema preparation
We pre-create any custom tables (Dataverse equivalent of Salesforce Custom Objects) and custom columns in the destination Dynamics 365 environment before any data migrates.
What this step covers
This includes option set values, lookup relationships, and any calculated or rollup fields. If the destination is a Sandbox environment, we validate the schema there first before deploying to production. The Account-Contact relationship model (primary AccountId plus Connection entity for secondary relationships) is configured in Dataverse at this stage.
Sandbox migration and reconciliation
We run a full migration into the Dynamics 365 Sandbox environment using production-like data volume.
What this step covers
The customer's RevOps lead reconciles record counts across all objects (Accounts in, Contacts in, Opportunities in, Activities in), spot-checks 25-50 records against the Salesforce source, and validates that the Account-Contact relationship model preserved secondary Account connections. Schema corrections and mapping adjustments happen in Sandbox, not in production.
Production migration in dependency order
We run production migration in record-dependency sequence: Users (manually provisioned, validated by email match), Accounts (with parent Account hierarchy resolved), Contacts (with primary AccountId set), Account Contact Relations (as Connection records), Leads, Opportunities (with OwnerId and AccountId resolved), Products, Price Lists, Opportunity Products, Cases, Campaigns, Contracts, and Activity history (Tasks, Events, Notes, Attachments via Dataverse API with chunking and backoff).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, delta sync, and workflow handoff
We freeze Salesforce writes during cutover, run a final delta migration of records modified during the migration window, then enable Dynamics 365 as the system of record.
What this step covers
We deliver the Workflow Rules and Process Builder inventory document with Power Automate equivalents to the customer's admin team. We support a one-week hypercare window for reconciliation issues. We do not rebuild Salesforce automations as Power Automate flows inside the migration scope; that is a separate engagement or an internal admin task.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom object complexity, and the number of junction objects requiring multi-pass migration. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Salesforce to Dynamics 365 →Why teams move from Salesforce to Dynamics 365
- Organizations already running Microsoft 365 (Outlook, Teams, Excel, Power BI) gain immediate workflow parity by adopting Microsoft Dynamics 365 Sales . Copilot for Sales surfaces CRM insights inside Outlook email and Teams chat without context-switching, and Power BI connects to Dataverse natively for reporting without a third-party connector. Case studies from mid-market companies switching cite reduced tool sprawl and lower per-seat licensing overlap as the primary driver.
- Salesforce's per-seat pricing with storage overages, annual uplift, and add-on subscriptions (Sales Engagement, Sales Programs, Agentforce conversations) compounds to 30-40% above the sticker price. Microsoft Microsoft Dynamics 365 Sales Enterprise at $95/user/month includes Copilot for Sales with no per-use AI charges, removing the variable cost exposure that CFOs cite during Salesforce renewal negotiations.
- Microsoft Copilot integrates across Windows, Microsoft 365, Dynamics 365, and Power Platform in a single conversational interface. Reviewers on Gartner Peer Insights and Reddit discussions note that Salesforce's Einstein AI requires separate configuration and additional licensing tiers, whereas Copilot feels native to the tools sales teams already use daily, reducing adoption friction and training overhead.
- Dynamics 365 uses standard Microsoft development languages (C#, .NET, JavaScript via Power Apps component framework) for customization, making in-house development feasible without a specialist Salesforce developer. Reviewers on Capterra and G2 cite this as a differentiator for mid-market companies that lack dedicated Salesforce admins but have existing Microsoft developers on staff.
- Territory management and multi-currency support in Salesforce Enterprise require careful configuration, and territory assignments via Territory Management objects have a specific import ordering dependency that catches migration teams. Dynamics 365 territory structures use a simpler organizational hierarchy model accessible from the base Sales Enterprise license, reducing the configuration surface area for organizations managing regional or product-line sales teams.
Questions, answered
Salesforce to Dynamics 365 migration questions
How long does a Salesforce Sales Cloud to Microsoft Microsoft Dynamics 365 Sales migration take?
Most migrations land between five and eight weeks for organizations under 30,000 Accounts and 10,000 Opportunities with standard objects and no custom objects. Migrations with large engagement histories (over 500,000 activity records), custom objects, complex Account hierarchies with multiple junction table passes, Territory management, or multiple Salesforce orgs consolidated into one Dynamics 365 tenant move to twelve to eighteen weeks because of Dataverse API pacing, multi-pass junction resolution, and Power Automate workflow inventory scope.
Do Salesforce Workflow Rules, Process Builder, and Flow automations migrate to Dynamics 365?
No. Salesforce Flow, Process Builder, and Workflow Rules are platform-specific automation constructs with different trigger models, action types, and limits from Dynamics 365's Power Automate and workflow engine. We do not migrate automations as code. We deliver a written inventory of every active Salesforce Workflow Rule and Process Builder with its trigger, conditions, actions, and a recommended Power Automate template or Dynamics 365 workflow equivalent. The customer's admin or a Microsoft partner rebuilds these post-migration. Salesforce Flow rebuilds are outside the standard migration scope and constitute a separate engagement.
Will we lose historical engagement data (calls, emails, meetings, tasks)?
No. We migrate the full engagement history through the Dataverse API with batch chunking and parent-record resolution. Tasks land as Dynamics 365 Task records with Subject, Status, Priority, and ActivityDate preserved; Events land as Appointment records with StartDateTime, EndDateTime, and Location; email content migrates as a Note record attached to the related Contact or Account; and files attach as Annotation records. Activity ordering is preserved by setting the original timestamp. We do not migrate Salesforce ContentDocumentLink attachments that reference ContentDocument records without a body; we flag these for the customer to re-upload post-migration.
How does the Account-Contact relationship work after migration?
Salesforce allows a Contact to belong to multiple Accounts simultaneously via the Account Contact Relation junction object. In Dynamics 365, a Contact has a primary AccountId lookup and secondary relationships use the Connection entity. We import every Contact with its primary Account relationship, then replay every Salesforce Account Contact Relation record as a Dynamics 365 Connection in a second migration pass. The Connection entity preserves the role and any IsDirect flag from the original junction. The customer's sales team sees the full relationship graph in Dynamics 365 exactly as it appeared in Salesforce.
Can we keep Salesforce while phasing in Microsoft Dynamics 365 Sales ?
A phased cutover is possible but requires careful data synchronization planning. We do not operate a live bi-directional sync between Salesforce and Dynamics 365 as part of a standard migration scope. The typical pattern is a parallel-run period where the Salesforce org remains read-only after go-live while the customer validates data completeness in Dynamics 365, followed by a full cutover when the validation window closes. Any new records created in Salesforce during the parallel period are migrated as a final delta pass before the Salesforce org is decommissioned.
What happens to our Salesforce territory configuration during migration?
Salesforce Territory Management uses Territory objects with a hierarchy that assigns Users, Accounts, and Opportunities. Dynamics 365 uses organizational hierarchies and sales territories configured within the Sales Hub. We migrate the territory structure as documented configuration (territory names, hierarchies, and assignment rules) in the migration scope, but the customer's admin implements the equivalent in Microsoft Dynamics 365 Sales Hub territory management. Territory Account assignments (which link Accounts to specific Sales Territories) migrate as data records that the customer's admin maps into Dynamics 365's territory assignment framework.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Dynamics 365 to SalesforceThe same pair in reverse Mailchimp to Dynamics 365Mapping · history · rollbackZoho CRM to Dynamics 365Mapping · history · rollbackOdoo CRM to Dynamics 365Mapping · history · rollbackCopper to Dynamics 365Mapping · history · rollbackConvertkit to Dynamics 365Mapping · history · rollbackmonday CRM to Dynamics 365Mapping · history · rollback Salesforce to HubSpotMapping · history · rollbackSalesforce to Zoho CRMMapping · history · rollbackSalesforce to Odoo CRMMapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
Get a quote
Moving from Salesforce to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote