
Dynamics 365 Sales migration
Microsoft Dynamics 365 Sales migration
Microsoft Dynamics 365 Sales keeps its CRM data in Dataverse tables: accounts, contacts, leads and opportunities, with every email, phone call, task and appointment stored as an activity tied to its record through a Regarding lookup. We move Salesforce Sales Cloud into Dynamics 365 Sales, and scope moves out of Dynamics 365 Sales on a call.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Dynamics 365 Sales migration at a glance
- Who it is for
- Sales operations teams and Microsoft partners moving CRM history into Dynamics 365 Sales Professional, Enterprise or Premium, or out of it, and companies consolidating their CRM onto Microsoft.
- What moves
- Accounts, contacts, leads, opportunities and opportunity products, emails, phone calls, tasks and appointments with their activity parties, notes with files, and users, teams and business units.
- What does not move as-is
- Plug-ins, classic workflows, Power Automate flows, business process flows, duplicate detection rules, security roles, views, dashboards and audit history. We list each one for rebuilding.
- What sets the scope
- Rows per table, the activities and parties on each record, attachment count and size against the upload limit, the business unit design, and the custom tables and columns needed.
What moves
What moves from Dynamics 365 Sales?
MigrateX moves accounts, contacts, leads, opportunities with their products, emails, phone calls, tasks and appointments with their activity parties, notes with attachments, and the users, teams and business units that own them.
- Accounts
- Contacts
- Leads
- Opportunities
- Opportunity products
- Activities
- Notes and attachments
- Users and teams
What does not move
What does not move from Dynamics 365 Sales as-is
Configuration, not data. We list each item in scope so your team can rebuild it in the target.
- Plug-ins, classic workflows and Power Automate flows
- What we do: Platform logic, not data. We list what each one does on the account, opportunity and activity tables, and your admin or partner rebuilds it in the destination.
- Business units, security roles and teams
- What we do: Configuration, set up before any row loads, because the owner and business unit of every record depend on it.
- Duplicate detection rules
- What we do: Configuration. Dynamics 365 Sales ships defaults for accounts and contacts only, so every other rule is listed and rebuilt.
Source: Microsoft Learn, checked 15 Nov 2026
- Calculated and roll-up columns
- What we do: Editable in an Excel export but never imported back, because Dataverse computes them. The destination recalculates them from the migrated values.
Source: Microsoft Learn, checked 15 Nov 2026
- Audit history
- What we do: Rows in the Audit table cannot be deleted directly, and Microsoft documents no way to create them. Moving out, the change log can follow as notes on request; moving in, it cannot become Dataverse audit history.
Source: Microsoft Learn, checked 15 Nov 2026
- Views, dashboards, forms and business process flows
- What we do: Solution components, rebuilt in the destination or moved as a solution between Dataverse environments.
- Copilot and Sales Insights settings
- What we do: Product configuration, not data, so it is set up again after cutover.
What does a Dynamics 365 Sales migration have to handle?
A Microsoft Dynamics 365 Sales migration has to design ownership before the first row loads, close won and lost deals through their own messages, keep every email tied to its parties, stop plug-ins and flows from firing on each row, and handle duplicates itself. Each is settled with your Dynamics admin before the free sample.
- Every user sits in a business unit
- Every Dataverse environment has one root business unit, and every Dynamics 365 Sales user belongs to a business unit. By default the user's business unit owns the records that user creates; under the modernized business units model the user can pick the owning unit. Owners and units are mapped before the load.
Source: Microsoft Learn, checked 15 Nov 2026
- Won and lost are actions, not fields
- Won and lost opportunities are read-only until they are reactivated, and Dynamics 365 Sales closes deals through the WinOpportunity and LoseOpportunity messages. A closed deal from another CRM loads open with its products and activities, then closes through the matching message.
Source: Microsoft Learn, checked 15 Nov 2026
- An activity is one row plus its parties
- Every sender, recipient, caller and attendee is an ActivityParty row with a participation type. A migrated email or meeting reads correctly only when each party resolves to the right contact, lead, account or user, so people load before any activity.
Source: Microsoft Learn, checked 15 Nov 2026
- Plug-ins and flows fire on every row
- Plug-ins registered on Create still run for each record inside a CreateMultiple request. BypassBusinessLogicExecution skips plug-ins and classic workflows for a user with prvBypassCustomBusinessLogic, but Power Automate flows need SuppressCallbackRegistrationExpanderJob as well.
Source: Microsoft Learn, checked 15 Nov 2026
- Duplicate detection is off for API creates
- The Dataverse Web API suppresses duplicate detection on create unless the request asks for it, and Dynamics 365 Sales ships default rules for accounts and contacts only. How source duplicates are found and resolved before the load is scoped with you during the free sample.
Source: Microsoft Learn, checked 15 Nov 2026
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationMigration paths
Where can I move to or from Dynamics 365 Sales?
Routes we run from and into Dynamics 365 Sales. Open a route to see what migrates, or ask us about one that is not listed yet.
Into Dynamics 365 Sales
Salesforce Sales Cloud to Dynamics 365 Sales
- 12 object types mapped
- About 10 business days
191 connectors, all live
Every connector is live, so Dynamics 365 Sales can be paired with any of them. Some of the CRM platforms:
- HubSpot CRM
- Zoho CRM
- Pipedrive
- Freshsales
- monday CRM
- Zendesk Sell
- Attio
- Copper
- Close
- Insightly
Platform not listed?
We build new connectors in 2 to 3 days. Tell us what you run and we scope the route with you.
Timeline
Your Dynamics 365 Sales migration, step by step
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 dayA 30 minute call with the engineer who will run the migration, to agree the objects, date ranges and volumes in scope.
Connect both platforms
You0.5 dayYou create scoped API credentials on the source and the destination. Nothing is written until you sign off the mapping.
Field mapping review
Both1 dayWe walk through every field, pipeline stage and owner mapping with your team and note the ones that need a decision.
Migration
Day 3-7
Free sample migration of 100 records
MigrateX1 dayA sample of your real records is migrated end to end so you can see the result before the full run.
You review the sample
You1 dayYour team opens the migrated records and tells us what to adjust. We rerun the sample until it is right.
Full migration
MigrateX2-3 daysThe bulk pass runs in dependency order, paced to the destination rate limit. Your team keeps working normally.
Delta sync
MigrateX0.5 dayEverything created or changed during the bulk pass is synced at cutover so nothing falls between the two systems.
Validation
Day 8-10
Validation report
MigrateX1 dayRecord counts per object and per status on both sides, plus every record that needed a default or a placeholder.
Spot checks and sign-off
You1-2 daysYour sales managers check a random sample and sign off. We stay available for two weeks after go-live.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
See how it works in detailData model
Dynamics 365 Sales data model and limits
How Dynamics 365 Sales holds the records that move, and the vendor limits that set the pace of the migration.
How does Dynamics 365 Sales store CRM data?
Microsoft Dynamics 365 Sales stores CRM records as Dataverse tables. Accounts, contacts, leads and opportunities are tables of their own, while every email, phone call, task and appointment is also one ActivityPointer row, with its participants in ActivityParty. Notes and their files sit in the annotation table, tied to a record through its Regarding lookup.
| Object | What it holds | How it links |
|---|---|---|
| Account (account) | A company. ParentAccountId links parent and child businesses for reporting. | OwnerId targets a user (systemuser) or a team, so an account can be owned by either. Source: Microsoft Learn |
| Contact (contact) | A person. | ParentCustomerId, shown as Company Name, is a Customer lookup that can point at an account or at another contact. Source: Microsoft Learn |
| Lead (lead) | A prospect before qualification. | Qualifying a lead converts it into an account, contact or opportunity; an unqualified lead is deleted or archived. Source: Microsoft Learn |
| Opportunity (opportunity) | Potential revenue, with a status of Open, Won or Lost. | CustomerId points at an account or a contact. OriginatingLeadId is read-only once the opportunity exists. Source: Microsoft Learn |
| Opportunity Product (opportunityproduct) | One line on an opportunity: the association between that opportunity and a product. | Child of one opportunity, so the product catalogue is in place before line items load. Source: Microsoft Learn |
| Activity (activitypointer) | The base row every activity shares, which carries the activity's security. | Each email, phone call, task or appointment is represented by exactly one ActivityPointer row. Source: Microsoft Learn |
| Email (email) | An email activity, with its body in description. | Regarding can point at an account, contact, lead or opportunity. Sender and recipients are activity parties. Source: Microsoft Learn |
| Phone Call, Task and Appointment | Call, to-do and meeting activities (phonecall, task, appointment). | Tied to a record through regardingobjectid. Callers and attendees are activity parties. Source: Microsoft Learn |
| Activity Party (activityparty) | One participant in one activity. | ParticipationTypeMask holds the role: sender, to, cc, bcc, required, optional, organizer, regarding or owner. Source: Microsoft Learn |
| Note (annotation) | A note's text in NoteText and, when it carries a file, the file in DocumentBody. | ObjectId, shown as Regarding, ties the note to its parent record. Source: Microsoft Learn |
| Attachment (activitymimeattachment) | A file attached to an email or another activity, held in Body as Base64. | Child of one activity. Source: Microsoft Learn |
| User, Team and Business Unit | Owners and security boundaries (systemuser, team, businessunit). | Every user is assigned to one and only one business unit, and each team belongs to exactly one. Source: Microsoft Learn |
Account (account)
- What it holds
- A company. ParentAccountId links parent and child businesses for reporting.
- How it links
- OwnerId targets a user (systemuser) or a team, so an account can be owned by either.
Source: Microsoft Learn
Contact (contact)
- What it holds
- A person.
- How it links
- ParentCustomerId, shown as Company Name, is a Customer lookup that can point at an account or at another contact.
Source: Microsoft Learn
Lead (lead)
- What it holds
- A prospect before qualification.
- How it links
- Qualifying a lead converts it into an account, contact or opportunity; an unqualified lead is deleted or archived.
Source: Microsoft Learn
Opportunity (opportunity)
- What it holds
- Potential revenue, with a status of Open, Won or Lost.
- How it links
- CustomerId points at an account or a contact. OriginatingLeadId is read-only once the opportunity exists.
Source: Microsoft Learn
Opportunity Product (opportunityproduct)
- What it holds
- One line on an opportunity: the association between that opportunity and a product.
- How it links
- Child of one opportunity, so the product catalogue is in place before line items load.
Source: Microsoft Learn
Activity (activitypointer)
- What it holds
- The base row every activity shares, which carries the activity's security.
- How it links
- Each email, phone call, task or appointment is represented by exactly one ActivityPointer row.
Source: Microsoft Learn
Email (email)
- What it holds
- An email activity, with its body in description.
- How it links
- Regarding can point at an account, contact, lead or opportunity. Sender and recipients are activity parties.
Source: Microsoft Learn
Phone Call, Task and Appointment
- What it holds
- Call, to-do and meeting activities (phonecall, task, appointment).
- How it links
- Tied to a record through regardingobjectid. Callers and attendees are activity parties.
Source: Microsoft Learn
Activity Party (activityparty)
- What it holds
- One participant in one activity.
- How it links
- ParticipationTypeMask holds the role: sender, to, cc, bcc, required, optional, organizer, regarding or owner.
Source: Microsoft Learn
Note (annotation)
- What it holds
- A note's text in NoteText and, when it carries a file, the file in DocumentBody.
- How it links
- ObjectId, shown as Regarding, ties the note to its parent record.
Source: Microsoft Learn
Attachment (activitymimeattachment)
- What it holds
- A file attached to an email or another activity, held in Body as Base64.
- How it links
- Child of one activity.
Source: Microsoft Learn
User, Team and Business Unit
- What it holds
- Owners and security boundaries (systemuser, team, businessunit).
- How it links
- Every user is assigned to one and only one business unit, and each team belongs to exactly one.
Source: Microsoft Learn
Dynamics 365 Sales tables that hold CRM data, by Dataverse logical name, as of November 2026. Source: Microsoft Dataverse and Dynamics 365 table references on Microsoft Learn.
Which Dynamics 365 Sales limits set the pace?
Dataverse paces a load in two ways: service protection limits per user and web server over a five-minute window, and Power Platform request allowances per 24 hours. These are the limits that decide how fast accounts, opportunities, activities and notes move into or out of Microsoft Dynamics 365 Sales, and what its native import options carry.
| Limit | Allowance |
|---|---|
| Service protection | 6,000 requests and 20 minutes of execution time per user, per web server, in a five-minute sliding window, plus 52 concurrent requests. Over the limit, the Web API returns 429 with a Retry-After header. Source: Microsoft Learn |
| Web servers | Each web server enforces those limits independently, and a trial environment has only one web server. Source: Microsoft Learn |
| Requests per licence | 40,000 Power Platform requests per paid Sales Premium, Enterprise or Professional licence per 24 hours. Each requests add-on adds 50,000. Source: Microsoft Learn |
| Tenant pool for application users | 500,000 base requests plus 5,000 per Dynamics 365 Enterprise or Professional licence, up to 10,000,000 per 24 hours, for non-licensed identities such as a migration's application user. Source: Microsoft Learn |
| Bulk write messages | CreateMultiple, UpdateMultiple and UpsertMultiple write one table per request. Microsoft suggests 100 to 1,000 records each, one error rolls back the whole request, and not every table supports them. Source: Microsoft Learn |
| Batch requests | Up to 1,000 requests in one Web API batch request, which cannot contain another batch. Source: Microsoft Learn |
| Payload size | 128 MB per request and 1 GB per response; a larger response fails with 413. Source: Microsoft Learn |
| Rows per page | Up to 5,000 rows per page for standard tables and 500 for elastic tables, followed through an unchanged @odata.nextLink. Source: Microsoft Learn |
| Note and email attachments | 5 MB per file by default, configurable up to 128 MB. Large files upload in blocks of 4 MB or less. Source: Microsoft Learn |
| Import Data Wizard | Accepts .csv, XML Spreadsheet 2003, .zip or text files, up to 32 MB for a .zip and 8 MB for any other file. Source: Microsoft Learn |
| Alternate keys | Up to ten per table, each up to 900 bytes and 16 columns, so rows can be matched on a source system's ID. Source: Microsoft Learn |
Service protection
- Allowance
- 6,000 requests and 20 minutes of execution time per user, per web server, in a five-minute sliding window, plus 52 concurrent requests. Over the limit, the Web API returns 429 with a Retry-After header.
Source: Microsoft Learn
Web servers
- Allowance
- Each web server enforces those limits independently, and a trial environment has only one web server.
Source: Microsoft Learn
Requests per licence
- Allowance
- 40,000 Power Platform requests per paid Sales Premium, Enterprise or Professional licence per 24 hours. Each requests add-on adds 50,000.
Source: Microsoft Learn
Tenant pool for application users
- Allowance
- 500,000 base requests plus 5,000 per Dynamics 365 Enterprise or Professional licence, up to 10,000,000 per 24 hours, for non-licensed identities such as a migration's application user.
Source: Microsoft Learn
Bulk write messages
- Allowance
- CreateMultiple, UpdateMultiple and UpsertMultiple write one table per request. Microsoft suggests 100 to 1,000 records each, one error rolls back the whole request, and not every table supports them.
Source: Microsoft Learn
Batch requests
- Allowance
- Up to 1,000 requests in one Web API batch request, which cannot contain another batch.
Source: Microsoft Learn
Payload size
- Allowance
- 128 MB per request and 1 GB per response; a larger response fails with 413.
Source: Microsoft Learn
Rows per page
- Allowance
- Up to 5,000 rows per page for standard tables and 500 for elastic tables, followed through an unchanged @odata.nextLink.
Source: Microsoft Learn
Note and email attachments
- Allowance
- 5 MB per file by default, configurable up to 128 MB. Large files upload in blocks of 4 MB or less.
Source: Microsoft Learn
Import Data Wizard
- Allowance
- Accepts .csv, XML Spreadsheet 2003, .zip or text files, up to 32 MB for a .zip and 8 MB for any other file.
Source: Microsoft Learn
Alternate keys
- Allowance
- Up to ten per table, each up to 900 bytes and 16 columns, so rows can be matched on a source system's ID.
Source: Microsoft Learn
Dataverse and Dynamics 365 limits that shape a Dynamics 365 Sales migration, as of 15 November 2026. Source: Microsoft Learn, linked per row.
Facts checked 15 Nov 2026. Sources: Microsoft Learn.
Dynamics 365 Sales migration questions
Still unsure? Ask us on the scoping call.
What does a Microsoft Dynamics 365 Sales migration cost?
The cost of migrating Microsoft Dynamics sales data follows the Dataverse tables in scope and what hangs off each row: opportunities with their products, emails, phone calls, tasks and appointments with their parties, and notes with attachments. Business unit design and custom tables add scope. MigrateX moves a free sample of 100 of your records first and sends a fixed quote within 24 hours.
How long does a Microsoft Dynamics 365 Sales migration take?
Most Microsoft Dynamics 365 Sales migrations take about 10 business days end to end. On the Dataverse side the pace comes from service protection limits per user and web server over five-minute windows, and from the daily request pool your tenant shares with every integration. The free sample shows the pace on your own environment.
How do I migrate data to Dynamics 365 Sales?
Load parents before children through the Dataverse Web API: users, teams and business units, then accounts, contacts, leads, opportunities, activities and notes. Microsoft recommends a programmatic import over the Import Data Wizard for large volumes. MigrateX upserts each row on an alternate key holding the source ID, so a re-run or the delta sync updates the row instead of adding a second one.
How do I export data from Dynamics 365?
For a full migration, through the Dataverse Web API, table by table, with note and attachment files downloaded in blocks. Export to Excel from a view stops at 100,000 rows at a time and can time out on wide views. Change tracking, once enabled on a table, returns only rows changed since the last pass, which keeps the final delta sync short.
How do I import contacts into Dynamics 365 Sales?
Short lists go through the Import Data Wizard or an Excel workbook, and full histories through the API. Each contact's Company Name (ParentCustomerId) can point at an account or another contact, so accounts load first. Excel import ignores fields from related tables, and the wizard skips any source column that is left unmapped.
Do original created dates and owners carry over into Dynamics 365 Sales?
Owners do, and original created dates are confirmed during your free sample. Dataverse fills createdon from overriddencreatedon, an override Microsoft documents for its import feature, so we test it through the API on your sample. createdby, modifiedby and modifiedon cannot be imported and go into custom columns. Records can be assigned to disabled users, so leavers keep their deals.
Why does Dynamics 365 say a team doesn't have enough privileges to own records?
Because a team that owns records gets its access from the security roles assigned to it. In Dataverse an owner team owns records and holds security roles, while an access team owns none. When an import names a team as owner, the error points to that team's roles, so we assign them before the load and check ownership on the free sample.
Can we test the migration in a Dynamics 365 sandbox first?
Yes. An Everything copy refreshes a Dynamics 365 sandbox environment with production's data, users and customizations, and a copy can never overwrite a production environment, so a rehearsal never touches live records. Use a sandbox rather than a developer environment, since unmanaged developer environments are being suspended.
Guides
Guides for a Dynamics 365 Sales migration

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


