Salesforce to Dynamics 365 Sales Migration: Objects, Owners, History
Salesforce to Dynamics 365 Sales migration: how objects map to Dataverse tables, how owners map to users, teams and business units, and what is kept.
Published 6 min read

On this page
- Which objects map to which tables in a Salesforce to Dynamics 365 Sales migration?
- How do Salesforce owners map to Dynamics 365 users, teams and business units?
- Which Salesforce history can Dynamics 365 Sales keep?
- What should you test in the Dynamics 365 sandbox?
- Salesforce to Dynamics 365 Sales migration FAQ
- Get your Salesforce owner map and history checked first
A Salesforce to Dynamics 365 Sales migration means mapping three things. Salesforce Sales Cloud objects map onto Microsoft Dataverse tables almost one for one. Owners have to be redesigned as users, teams and business units. History is kept only where Dataverse lets a load write it: the created date can be kept, while modified dates and authors need custom columns.
This guide is for CRM owners and Microsoft partners who have chosen Dynamics 365 Sales and are deciding how the data gets there. Limits, the timeline and the full mapping are on the Salesforce to Dynamics 365 Sales migration page.
Which objects map to which tables in a Salesforce to Dynamics 365 Sales migration?
Each core sales object has a Dataverse table. What changes is how records point at each other, and that is where a load goes wrong.
The link to check for each object:
| Salesforce object | Dynamics 365 Sales table | The link that changes |
|---|---|---|
| Account | account | Parent accounts use parentaccountid. The owner can be a user or a team |
| Contact | contact | parentcustomerid points at an account or another contact, and holds one parent |
| Lead | lead | A lead is qualified into an account, contact or opportunity. Converted Salesforce Leads are read-only |
| Opportunity | opportunity | customerid points at an account or a contact. Status is Open, Won or Lost |
| OpportunityLineItem | opportunityproduct | The product catalogue has to exist before any line |
| Task | task | WhatId becomes the Regarding lookup, regardingobjectid |
| Event | appointment | Attendees become activity parties |
| EmailMessage | email | Sender and recipients become activity parties, with a direction in directioncode |
| Note and ContentNote | annotation | Text goes in notetext, and objectid names the parent record |
Activities need the most care. In Salesforce, a Task or Event points at a person through WhoId and at a record through WhatId. In Dataverse, the record goes in regardingobjectid and each person becomes an activity party with a role: sender, to, cc, bcc, organizer, or required or optional attendee.
How do Salesforce owners map to Dynamics 365 users, teams and business units?
A Salesforce owner becomes a Dataverse user or team, and every one of them sits inside a business unit. Microsoft's documentation says the ownerid column accepts a user or a team, and each team belongs to exactly one business unit. That makes ownership a design task before it is a data task.
Work through it in this order:
- List every Salesforce owner on the records in scope, including inactive users and queues.
- Design the business units. Every user belongs to exactly one.
- Create the users. For people who have left, Microsoft's Create users page says you can assign records to a disabled user, which it describes as helpful when migrating.
- Create owner teams where a group owns records. Microsoft's Teams documentation says owner teams own records and hold security roles, while access teams do not own records.
- Map each Salesforce owner ID to a user or team, then load.
One setting catches teams out. Giving a security role to a disabled user needs allowRoleAssignmentOnDisabledUsers turned on, according to Microsoft's user security page.
Which Salesforce history can Dynamics 365 Sales keep?
The original created date, the activity timeline and deal outcomes. It cannot keep who created or last modified a record in the system columns. Those go into custom columns.
What happens to each kind of history:
| History | In Salesforce | In Dynamics 365 Sales | Result |
|---|---|---|---|
| Created date | CreatedDate | Mapped to overriddencreatedon, which writes createdon | Kept. Needs the prvOverrideCreatedOnCreatedBy privilege |
| Created by | The creating user | Overriding createdby is not supported | Custom column |
| Last modified date and user | The last edit and its user | modifiedon and modifiedby cannot be imported | Custom columns |
| Old activities | Archived after 365 days, hidden from reports | task, appointment, phonecall | Kept, if read by query |
| Email dates | MessageDate on EmailMessage | email activity | Kept |
| Won and lost deals | Decided by the stage | Closed through WinOpportunity or LoseOpportunity | Loaded open, then closed |
Microsoft describes the created-date override on its Run data import page. We found no Microsoft page stating that the same column works through the Web API or bulk messages, so it is confirmed on your free sample before original dates are promised.
What should you test in the Dynamics 365 sandbox?
Five records that each prove one rule:
- An account created years ago: does
createdonshow the Salesforce date? - An opportunity owned by a former rep: is the disabled user the owner?
- A won opportunity: is it Won, with its close date held where you can report on it?
- An email with a cc and an attachment: are the parties and the file there? Microsoft's documentation says email attachments default to a 5 MB maximum, configurable up to 128 MB.
- A contact linked to two Salesforce Accounts: does the second link exist in the form you chose?
Our test migration checklist covers the wider rehearsal. Scope for each side is on the Salesforce and Dynamics 365 Sales platform pages.
Facts checked November 15, 2026 from Microsoft Learn: Run data import (Dataverse), Microsoft Learn: Create or edit business units, Microsoft Learn: Ownership-based security in Dataverse, Microsoft Learn: Teams in Dataverse, Microsoft Learn: Create users, Microsoft Learn: Configure user security in an environment, Microsoft Learn: Opportunity table reference (Dynamics 365), Microsoft Learn: Contact table reference (Dataverse), Microsoft Learn: Activity Party table reference (Dataverse), Microsoft Learn: Use file data with attachment and note records, Microsoft Learn: Dataverse auditing overview, Microsoft Learn: Work with alternate keys, Microsoft Learn: Export to an Excel static worksheet, Salesforce Help: Work with Archived Activities, Salesforce Object Reference: Task and Salesforce Object Reference: EmailMessage. No vendor paid for this article. How we research
Salesforce to Dynamics 365 Sales migration FAQ
Do Salesforce Tasks and Events older than a year move to Dynamics 365 Sales?
They can, but they have to be asked for. Salesforce archives them once an Event ended, or a closed Task was due, more than 365 days ago. Archived activities are not deleted, but Salesforce Help says they are not copied into new or refreshed sandboxes, so test old activities from production with read-only access.
Does Salesforce field history become Dynamics 365 audit history?
No. Salesforce History objects are read-only records of past changes, and Dataverse auditing records changes made inside Dataverse. We found no documented way to create audit records from another system. Stage and field history that matters is kept as a note on the record or in custom columns.
What happens to a Contact linked to several Salesforce Accounts?
It needs a decision. Salesforce links one Contact to more than one Account through AccountContactRelation, while a Dynamics contact has one parent customer. The primary Account becomes the parent, and how the other links are kept is chosen with you at mapping and shown on the sample.
Can we keep Salesforce record IDs in Dynamics 365 Sales?
Yes, as a column of their own. Dataverse alternate keys let rows be matched on a business column such as a source system ID, and Microsoft allows up to ten alternate keys per table. With the Salesforce ID as a key, a re-run updates the same row instead of creating a second one.
Is Export to Excel enough to check the migrated data?
Only for small tables. Microsoft's documentation limits an export to an Excel static worksheet to 100,000 rows at a time. For a full check, compare counts per table and per owner on both sides, then spot-check records. Our guide to data migration validation sets out the method.
Get your Salesforce owner map and history checked first
MigrateX is a managed data migration service on its own AI migration platform, SOC 2 Type II, GDPR and HIPAA compliant. Send us three things: record counts per object, your list of Salesforce owners, and the oldest date you need kept. You get 100 of your own records in Dynamics 365 Sales, free, and a fixed quote within 24 hours. Start with a free sample. Need a copy of the org first? See 4 ways to export Salesforce data.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


