
Salesforce Sales CloudDynamics 365 Sales
Salesforce Sales Cloud to Dynamics 365 Sales migration
Migration specialists move your accounts, contacts, opportunities and open leads into Dynamics 365 Sales, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated November 2026 · 12 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Salesforce Sales Cloud to Dynamics 365 Sales at a glance
A Salesforce to Dynamics 365 Sales migration moves Accounts, Contacts, Leads and Opportunities into Dataverse tables, and turns each Task, Event and email into an activity whose people are activity parties. The hard parts are closed deals, which Dynamics closes through its own messages, files above the attachment limit, and ownership by business unit. Salesforce stays live until the final delta sync.
- Objects mapped
- 12
- in this route's mapping
- Typical timeline
- About 10 business days end to end
- 3 phases
- Free sample
- 100 records
- checked by your team first
- Quote
- Fixed
- within 24 hours
- Who it is for
- Sales teams moving from Salesforce Sales Cloud onto Microsoft Dynamics 365 Sales, usually because the company already runs on Microsoft, and the Microsoft partners running those projects.
- What does not move
- Flows, Process Builder, workflow rules, Apex, validation rules, formula fields, record types, page layouts and reports. We document each one so it can be rebuilt in Dynamics 365 Sales.
- What sets the scope
- Object volumes, archived activities, closed deals, files above the Dataverse attachment limit, the business unit design, and the custom tables Dataverse needs before the load.
What moves
What moves from Salesforce Sales Cloud to Dynamics 365 Sales
Accounts, Contacts, open Leads, Opportunities, Tasks, Events, emails, notes, Files, users and custom objects move into their Dataverse tables, with the people on every activity stored as activity parties and every file as a note or email attachment.
- 12 included
| Salesforce Sales Cloud | maps to | Dynamics 365 Sales | Status |
|---|---|---|---|
| Accounts | AccountsUpserted on the Salesforce Account ID in an alternate key. Parent accounts are linked through ParentAccountId once both rows exist. | Included | |
| Contacts | ContactsCompany Name (ParentCustomerId) points at the contact's main Salesforce Account. | Included | |
| Open Leads | LeadsLoaded with their owner and source fields before any opportunity. | Included | |
| Opportunities | OpportunitiesCustomerId points at the Account. Won and lost deals load open, then close through WinOpportunity or LoseOpportunity. | Included | |
| Tasks | Tasks or phone callsCall-type Tasks can become phone call activities; the rest stay tasks, linked through Regarding. | Included | |
| Events | AppointmentsAttendees become activity parties on the appointment, archived Events included. | Included | |
| Emails (EmailMessage) | EmailsSender, to, cc and bcc become activity parties, Regarding points at the Account or Opportunity, and attachments become activity attachments. | Included | |
| Notes and enhanced notes | NotesBody into NoteText, with the parent record set through Regarding. | Included | |
| Files on records | Notes with files5 MB per file by default, configurable up to 128 MB. Larger files are scoped with you during the free sample. | Included | |
| Users | UsersEach user is placed in one business unit. People who have left become disabled users, so their records keep an owner. | Included | |
| Queues and roles | Teams and business unitsDesigned with you on the scoping call, with security roles assigned to each owner team. | Included | |
| Custom objects | Custom tablesTables, columns and relationships are created in Dataverse before the load. | Included |
- AccountsAccounts
Upserted on the Salesforce Account ID in an alternate key. Parent accounts are linked through ParentAccountId once both rows exist.
- ContactsContacts
Company Name (ParentCustomerId) points at the contact's main Salesforce Account.
- Open LeadsLeads
Loaded with their owner and source fields before any opportunity.
- OpportunitiesOpportunities
CustomerId points at the Account. Won and lost deals load open, then close through WinOpportunity or LoseOpportunity.
- TasksTasks or phone calls
Call-type Tasks can become phone call activities; the rest stay tasks, linked through Regarding.
- EventsAppointments
Attendees become activity parties on the appointment, archived Events included.
- Emails (EmailMessage)Emails
Sender, to, cc and bcc become activity parties, Regarding points at the Account or Opportunity, and attachments become activity attachments.
- Notes and enhanced notesNotes
Body into NoteText, with the parent record set through Regarding.
- Files on recordsNotes with files
5 MB per file by default, configurable up to 128 MB. Larger files are scoped with you during the free sample.
- UsersUsers
Each user is placed in one business unit. People who have left become disabled users, so their records keep an owner.
- Queues and rolesTeams and business units
Designed with you on the scoping call, with security roles assigned to each owner team.
- Custom objectsCustom tables
Tables, columns and relationships are created in Dataverse before the load.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
What does not move from Salesforce Sales Cloud to Dynamics 365 Sales as-is
Flows, Apex, validation rules, formula fields, record types and reports are Salesforce configuration that even Microsoft's own migration application does not convert, so they are rebuilt in Dynamics 365 Sales.
- Products, price books and line itemsOn request
- In Dynamics 365 Sales: Products, price lists and opportunity productsThe catalogue loads before any deal, so each opportunity product finds its product.
- On request
- Converted LeadsOn request
- In Dynamics 365 Sales: Leads (qualified)Read-only in Salesforce once converted. They move on request, scoped with you during the free sample, and the Accounts, Contacts and Opportunities they became carry their data either way.
- On request
- AccountContactRelationOn request
- In Dynamics 365 Sales: Connection or custom relationship tableA Dynamics contact has one parent customer, so each extra account link needs a design choice.
- On request
- OpportunityContactRoleOn request
- In Dynamics 365 Sales: Connection roles or a custom tableKept when your team reports on buying roles per deal.
- On request
- Campaigns and campaign membersOn request
- In Dynamics 365 Sales: Campaigns and marketing listsDepends on your Dynamics 365 marketing licence, confirmed during your free sample.
- On request
- Opportunity field historyOn request
- In Dynamics 365 Sales: Notes or custom columnsSalesforce History objects are read-only, so the change log moves as notes on request.
- On request
- Flows, Process Builder, workflow rules and ApexNot migrated
- In Dynamics 365 Sales: Power Automate flows and plug-insMicrosoft's own migration application assesses them without converting them. We hand over a list of each one with what it does.
- Not migrated
- Validation, duplicate and assignment rulesNot migrated
- In Dynamics 365 Sales: Business rules, duplicate detection rules and routingRebuilt by your admin or partner from the conditions we document.
- Not migrated
- Formula and roll-up summary fieldsNot migrated
- In Dynamics 365 Sales: Calculated and rollup columnsRecreated as columns Dataverse computes. Today's values can move into plain columns on request.
- Not migrated
- Record types, page layouts, profiles and sharing rulesNot migrated
- In Dynamics 365 Sales: Forms, business process flows, security roles and teamsConfiguration, designed with you before the first load.
- Not migrated
- Reports, dashboards and list viewsNot migrated
- In Dynamics 365 Sales: Views, charts and dashboardsRebuilt on the migrated columns.
- Not migrated
- Big Objects and External ObjectsNot migrated
- Left out even by Microsoft's own migration application. Scoped on a call when they hold data you need.
- Not migrated
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
Salesforce Sales Cloud to Dynamics 365 Sales migration timeline
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayWe agree which objects move, whether converted Leads and field history come across, how Salesforce roles map to business units, and what happens to files above the attachment limit.
Connect both sides
You0.5 dayYou create a read-only Salesforce integration user and a Dataverse application user with the override and bypass privileges. The first loads go into a Dynamics 365 sandbox environment.
Tables, columns and keys
Both1 dayCustom tables and columns are created, alternate keys are added for Salesforce IDs, and picklist values, stages and owners are mapped. Your admin lists the plug-ins and flows to bypass.
Migration
Day 3-7
Free sample in the sandbox
MigrateX1 day100 of your records, picked for closed deals, long activity histories, large files and leavers' records, loaded end to end into the sandbox environment.
You review the sample
You1 dayYour team opens accounts and deals as a sales rep and a manager, and checks owners, created dates, won and lost status, activity parties and files.
Full load into production
MigrateX2-3 daysUsers, teams and business units first, then accounts, contacts, leads and the product catalogue, then opportunities, activities, notes and files, paced to the Dataverse limits.
Delta sync
MigrateX0.5 daySalesforce records changed since the full load are upserted on their alternate keys, so nothing is created twice.
Validation
Day 8-10
Reconciliation report
MigrateX1 daySalesforce counts against Dataverse counts per object, owner and year, won and lost deals against closed opportunities, and every file listed as moved or held back.
Spot checks and sign-off
You1-2 daysYour leads check a random sample, the bypassed plug-ins and flows go back on, and Salesforce stays read-only with a rollback plan ready until you sign off.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
Known risks
Every known risk on this route, with how we handle it
- 1 solved
- 6 handled
- 01HandledMost critical
Won and lost Salesforce deals cannot be created closed
The problem
Dynamics 365 Sales makes won and lost opportunities read-only and closes them through the WinOpportunity and LoseOpportunity messages. Microsoft does not document setting the original actual close date that way, so a Salesforce CloseDate on a closed deal has no confirmed native home.
How we handle it
Closed Salesforce Opportunities load open, with their products, contact roles and activities, then close through WinOpportunity or LoseOpportunity. The original CloseDate is kept in a custom column until the free sample shows whether the native close date can carry it.
Source: Microsoft Learn, checked 15 Nov 2026
- 02Handled
Salesforce files above the Dataverse upload limit
The problem
Dataverse caps note and email attachments at 5 MB by default and 128 MB at most, while Salesforce files can be far larger. Microsoft's own Salesforce migration application, Dynamics 365 Activate, skips files that exceed the Dataverse maximum upload size.
How we handle it
Every Salesforce file over your limit is listed during export. Your admin can raise MaxUploadFileSize up to 128 MB, and what happens to files above that is scoped with you during the free sample. Nothing is skipped without your sign-off.
Source: Microsoft Learn, checked 15 Nov 2026
- 03Solved
Dynamics plug-ins and flows can fire for every migrated row
The problem
Plug-ins registered on Create still run for each record sent through CreateMultiple. BypassBusinessLogicExecution skips plug-ins and classic workflows but not Power Automate flows, which create system jobs unless SuppressCallbackRegistrationExpanderJob is passed.
How we handle it
The load runs as a user holding prvBypassCustomBusinessLogic, with BypassBusinessLogicExecution on each request and SuppressCallbackRegistrationExpanderJob for flows. Your admin names any plug-in that must still run, and we test the list on the free sample.
Source: Microsoft Learn, checked 15 Nov 2026
- 04Handled
Dataverse will not catch duplicate Salesforce records on its own
The problem
Duplicate detection is suppressed by default for rows created through the Dataverse Web API, and Dynamics 365 Sales ships default duplicate detection rules for accounts and contacts only. Salesforce duplicates load as duplicates unless they are found first.
How we handle it
How duplicate Salesforce Accounts, Contacts and Leads are found and resolved before the load is scoped with you during the free sample. Each row is upserted on its Salesforce ID, so a re-run never adds the same record twice.
Source: Microsoft Learn, checked 15 Nov 2026
- 05Handled
Salesforce roles and sharing have no direct Dynamics equivalent
The problem
Salesforce controls who sees a record through roles, profiles and sharing rules. Dynamics 365 Sales assigns every user to one and only one business unit, and each team belongs to exactly one business unit, so access has to be redesigned rather than copied.
How we handle it
On the scoping call we map Salesforce roles to business units, owner teams and security roles. Owners who have left become disabled users, which Dynamics 365 accepts as record owners, and ownership is checked on the free sample before the full load.
Source: Microsoft Learn, checked 15 Nov 2026
- 06Handled
The lead behind each deal has to be set on the first insert
The problem
In Dynamics 365 Sales an opportunity's OriginatingLeadId is read-only once the opportunity exists. If deals load before the leads they came from, the lead-to-deal link can never be added afterwards.
How we handle it
Whether converted Salesforce Leads move is scoped with you during the free sample. If they do, they load before any Opportunity, so each deal is created with its originating lead set; if not, the Salesforce Lead ID is kept in a custom column on the deal.
Source: Microsoft Learn, checked 15 Nov 2026
- 07Handled
The created-date override is documented for imports, not the API
The problem
Microsoft describes mapping a source date to overriddencreatedon on its Run data import page. Microsoft does not state that a Web API or bulk-message create with overriddencreatedon sets createdon the same way.
How we handle it
The free sample writes overriddencreatedon through the API on every table in scope and checks createdon on each row. If a table does not take it, the Salesforce CreatedDate goes into a custom column, and you hear about it before the full load.
Source: Microsoft Learn, checked 15 Nov 2026
Technical profile
What makes this route technical
Salesforce paces the export through your org's daily API allocation, and Dataverse paces the load through per-user limits in five-minute windows, a daily tenant request pool and a default 5 MB attachment limit.
- Exporting from Salesforce: one daily allocation for every integration
- On Enterprise Edition, Salesforce allows 100,000 API calls a day plus 1,000 per Salesforce licence, and calls from installed managed packages count against the same total. MigrateX reads the large Salesforce tables through Bulk API 2.0 so the export leaves room for your live integrations.
Source: Salesforce developer documentation, checked 15 Nov 2026
- Exporting from Salesforce: archived activities need their own query
- Salesforce archives Events that ended more than 365 days ago and closed Tasks due more than 365 days ago, and leaves archived activities out of reports. A report-based Salesforce export misses years of calls and meetings, so MigrateX queries archived Tasks and Events directly.
Source: Salesforce Help, checked 15 Nov 2026
- Exporting from Salesforce: a file version can reach 2 GB
- Salesforce accepts up to 2 GB per ContentVersion through a multipart REST request. MigrateX records the size of every Salesforce file during export, so the files that exceed your Dataverse attachment limit are known before the first load.
Source: Salesforce developer documentation, checked 14 Nov 2026
- Importing into Dynamics 365 Sales: created dates go through overriddencreatedon
- Dataverse writes a row's createdon from the overriddencreatedon column, which needs the prvOverrideCreatedOnCreatedBy privilege. Dataverse cannot import createdby, modifiedby or modifiedon, so the Salesforce creator and last-modified values land in custom columns.
Source: Microsoft Learn, checked 15 Nov 2026
- Importing into Dynamics 365 Sales: limits per user and web server
- Dataverse allows 6,000 requests and 20 minutes of execution time per user, per web server, in any five-minute sliding window, with 52 concurrent requests. Past that, Dataverse answers 429 with a Retry-After header, and the load waits that many seconds before it goes on.
Source: Microsoft Learn, checked 15 Nov 2026
- Importing into Dynamics 365 Sales: an application user draws on the tenant pool
- A load that runs as an application user draws on a tenant pool of 500,000 requests a day plus 5,000 per Dynamics 365 Enterprise or Professional licence, up to 10,000,000. Microsoft names a background process that migrates data between databases as an example of this kind of work.
Source: Microsoft Learn, checked 15 Nov 2026
- Importing into Dynamics 365 Sales: bulk messages work table by table
- CreateMultiple, UpdateMultiple and UpsertMultiple write many rows of one table per request, and one error rolls back the whole request. Microsoft says not every table supports them, and on 15 November 2026 the Email and Note references did not list them, so emails and notes load in Web API batch requests.
Source: Microsoft Learn, checked 15 Nov 2026
- Importing into Dynamics 365 Sales: Salesforce IDs become alternate keys
- Dataverse allows up to ten alternate keys per table, each up to 900 bytes and 16 columns. Each Salesforce record ID goes into a key column, so the delta sync and any re-run update the same Dynamics row instead of creating a second one.
Source: Microsoft Learn, checked 15 Nov 2026
Facts checked 15 Nov 2026 against Salesforce and Microsoft documentation. Each fact links its source.
Salesforce Sales Cloud to Dynamics 365 Sales questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
What moves from Salesforce to Dynamics 365 Sales?
Accounts, Contacts, open Leads and Opportunities move into their Dataverse tables, with owners mapped to users, teams and business units. Tasks, Events and emails become activities with their people as activity parties, notes become notes, and files become notes with attachments. Products, contact roles, campaigns and field history move on request.
How long does a Salesforce to Dynamics 365 Sales migration take?
The default plan for this route is about 10 business days end to end. Here the export is paced by your Salesforce org's daily API allocation, and the load by Dataverse limits per user and web server in five-minute windows. Files above the attachment limit and the business unit design are settled in the first two days, and the free sample shows the real pace.
Should we use Microsoft's Dynamics 365 Activate or a managed migration?
Dynamics 365 Activate is Microsoft's preview application for moving Salesforce orgs into Dynamics 365 Sales, and Microsoft says preview features are not meant for production use. It assesses flows and Apex without converting them, skips files over the upload limit and excludes Big Objects and External Objects. MigrateX runs the move as a managed service on its own AI migration platform, starting with a free sample of 100 of your records and ending with a reconciliation report.
Will our Salesforce created dates and record owners survive the move?
Owners do: people who have left become disabled users, which Dynamics 365 Sales accepts as record owners. Original Salesforce created dates go through overriddencreatedon, which your free sample tests table by table, and the Salesforce creator and last editor go into custom columns.
How do won and lost Salesforce opportunities come across?
They load open, with their products, contact roles and activities, and are then closed through WinOpportunity or LoseOpportunity, because Dynamics 365 Sales makes won and lost deals read-only. The original Salesforce CloseDate sits in a custom column until the free sample settles the native close date.
What happens to Salesforce files larger than the Dynamics attachment limit?
They are listed before the load and never dropped silently. Your admin can raise the Dataverse attachment limit from its 5 MB default to as much as 128 MB, and how Salesforce files above that are handled is scoped with you during the free sample.
How do Salesforce roles and sharing map to business units and security roles?
By design, not by copy. We draft Dynamics 365 Sales business units, owner teams and security roles from your Salesforce roles with your admin, then check on the free sample that each rep sees the right accounts and deals. A business unit owns its users' records by default.
Do Salesforce flows and Apex triggers convert to Power Automate?
No, they are rebuilt. Neither MigrateX nor Microsoft's own migration application converts Salesforce flows, Process Builder, workflow rules or Apex. We hand your admin or partner a list of each one, with the object it runs on and what it does, so it can be rebuilt as a Power Automate flow, a business rule or a plug-in.
Can we rehearse in a Salesforce sandbox and a Dynamics sandbox environment first?
On the Dynamics side, yes: the free sample loads into a Dynamics 365 sandbox environment. On the Salesforce side, a sandbox is a weaker source, because Salesforce does not copy archived activities into new or refreshed sandboxes. MigrateX reads the sample from production through a read-only integration user, so old calls and meetings are part of the test.
What does a Salesforce to Dynamics 365 Sales migration cost?
The cost of a Salesforce to Dynamics 365 Sales migration follows Salesforce object volumes, archived activities, closed deals, files above the attachment limit, and how many custom tables and business units Dynamics 365 Sales needs. MigrateX first migrates 100 of your records free as a sample, then sends a fixed quote within 24 hours.
How it compares
Four ways to run Salesforce Sales Cloud to Dynamics 365 Sales
The same data, moved four different ways. This is what changes between them.
Object coverage (accounts, contacts, deals, activities, files)
MigrateX
Every object in the mapping on this page, plus the ones you ask for during scoping.
Automated migration software
Contacts and accounts are covered. Deals, activities and their links often are not.
Vendor CSV import
One object per file, and only the fields the export template exposes.
In-house scripts
Whatever you have time to build before the cutover date.
Activities and notes on each record
MigrateX
Each email, call, meeting and note is loaded on its own and linked to the records it belongs to.
Automated migration software
Activities usually arrive, but their links to contacts, deals and owners can be lost.
Vendor CSV import
Notes collapse into one field on the record, if they come across at all.
In-house scripts
Possible, but it is the part teams most often run out of time for.
Files and attachments
MigrateX
Uploaded and linked to the record they belong to. How files over the Dynamics 365 Sales size limit are handled is confirmed during your free sample.
Automated migration software
Supported up to the destination's file size limit. Larger files are skipped.
Vendor CSV import
Not carried by a CSV import.
In-house scripts
Needs its own download, retry and upload pipeline.
Original IDs cross-referenced
MigrateX
Every source id is stored on the destination record and handed back as a map.
Automated migration software
Often kept as a tag or a single text field.
Vendor CSV import
Lost once the file is imported.
In-house scripts
Only if you design the mapping table up front.
Delta sync before cutover
MigrateX
Included. Anything created or changed during the bulk pass is synced at cutover.
Automated migration software
Usually a paid upgrade on the top tier.
Vendor CSV import
You would re-export and re-import by hand.
In-house scripts
Requires change tracking and idempotent writes on both sides.
Rate-limit handling
MigrateX
Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.
Automated migration software
Backs off, but a long run can still stall and leave partial records.
Vendor CSV import
Not applicable, and the file size limits bite instead.
In-house scripts
The most common reason a home-grown run dies overnight.
Validation report
MigrateX
Counts per object and per status on both sides, with every default and placeholder listed.
Automated migration software
A run log and an error list, rather than a reconciliation.
Vendor CSV import
Row counts in a spreadsheet.
In-house scripts
You write the reconciliation queries yourself.
Rollback plan
MigrateX
Every write is tagged, so a batch can be reversed without touching your own records.
Automated migration software
Some approaches can clear a migration, some cannot.
Vendor CSV import
Manual cleanup of everything the import created.
In-house scripts
Only if you built the tagging in from the start.
Who does the work
MigrateX
A MigrateX engineer runs it and stays on the cutover call.
Automated migration software
You run the software. The vendor's support team answers questions.
Vendor CSV import
Your admins, one file at a time.
In-house scripts
Your engineers, instead of your roadmap.
Guides
Guides for a Salesforce Sales Cloud to Dynamics 365 Sales migration
Related routes
Other routes we run
Built for your security review, from the first call.
Read how we handle your data
SOC 2 Type II
Independently audited controls over how we handle your data.
GDPR compliant
Data processing agreement available.
HIPAA compliant
Business associate agreement available.

Start your Dynamics 365 Sales move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.



