Microsoft Dynamics 365 Sales to HubSpot
Microsoft's CRM sales application, built on Dataverse.
Microsoft Dynamics 365 Sales data can move into HubSpot, landing mainly in Sales Hub. 3 of 8 mapped objects move directly (Contacts, Accounts and Opportunities); 4 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Microsoft Dynamics 365 Sales
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<25k
Standard objects only.
Mid migration
25k-250k
A guide cites 3-8 weeks for typical projects.
Large migration
250k+
Custom tables, heavy activity history and many flows.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Microsoft Dynamics 365 Sales: what you need to get in, what lands in HubSpot, and what will not.
Dataverse Web API (OData REST), plus SDK
Read permission on each synced record type is required for the native connector.
Per user, per web server, over a 5-minute window: 6,000 requests, 20 minutes of combined execution time and 52 concurrent requests. Exceeding them returns HTTP 429 with a Retry-After header.
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from Microsoft Dynamics 365 Sales.
- You need: To confirm
- Permission: Read permission on each synced record type is required for the native connector.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- CSV export from views and Advanced Find, which community posts describe as capped at 50 rows
- Dataverse Web API extraction
- Power Platform dataflows (Power Query)
- Third-party connectors
Limits: Per user, per web server, over a 5-minute window: 6,000 requests, 20 minutes of combined execution time and 52 concurrent requests. Exceeding them returns HTTP 429 with a Retry-After header.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Microsoft Dynamics 365 Sales
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts | Contacts | yes | Both the native sync and CSV export/import carry contacts; Dynamics FullName must be split into first and last name. |
| Accounts | Companies | yes | Parent-child hierarchies become company associations. |
| Opportunities | Deals | yes | Won, lost and open stages must be mapped to HubSpot pipeline stages. |
| Activities (tasks, appointments, emails, phone calls) | Tasks, Meetings, Emails, Calls | partial | Activities become HubSpot engagements with partial fidelity, and historical timestamps need explicit handling. |
| Notes (annotations) | Notes | partial | Attached files and SharePoint links need a separate approach. |
| Users | Owners | partial | Map Dynamics user IDs to HubSpot owners, and users must exist in HubSpot first. |
| Cases | Tickets | partial | Listed as a shared object on the marketplace app listing, but no default field mappings are published. |
| Custom tables | Custom objects | partial | Custom object sync is reported to need Enterprise. |
What to expect
No Dataverse export represents this logic, so it has to be rebuilt as HubSpot workflows.
These do not transfer and must be rebuilt as build work; Power BI dashboards lose their Dynamics data source.
They do not transfer and need to be rebuilt in HubSpot's knowledge base.
Option sets and lookups need translating rather than copying.
None of these export in a form HubSpot can import.
They are references, not files.
Each integration needs to be repointed and retested.
Export with lookup GUIDs and rebuild associations through the API or imports.
Honour Retry-After, throttle requests, and consider multiple app users.
Run a sample migration and reconcile counts by activity type.
Use the Web API or dataflows instead of UI exports.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Rate limits are backed by Microsoft's Learn page and secondary sources. Object mapping and export paths rest mostly on migration guides and community posts, not HubSpot or Microsoft docs. I did not open Microsoft's Web API reference or HubSpot's connector docs directly.
Sources
Related migrations
Frequently asked questions
How do I migrate Microsoft Dynamics 365 Sales to HubSpot?
1. Inventory all tables, custom entities, fields, option sets, business rules and Power Automate flows. 2. Create an Entra app registration or dedicated API user with read access to all migrated tables. 3. Deduplicate leads, contacts and accounts, and decide how Leads map to Contacts. 4. Export a CSV backup of key tables and record counts per table.
What data can move from Microsoft Dynamics 365 Sales to HubSpot?
These objects move directly: Contacts, Accounts and Opportunities. Check the mapping table for partial and manual items.
What does not move from Microsoft Dynamics 365 Sales to HubSpot?
Power Automate flows, plugins and business rules, Reports, dashboards and permissions and Knowledge base articles. Plan to rebuild or retire these.
How long does a Microsoft Dynamics 365 Sales to HubSpot migration take?
Small (<25k): 2-4 weeks. Mid (25k-250k): 4-8 weeks. Large (250k+): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Microsoft Dynamics 365 Sales?
Read permission on each synced record type is required for the native connector.
Is there a native HubSpot connector for Microsoft Dynamics 365 Sales?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving Microsoft Dynamics 365 Sales data?
Check: Possible health, financial or minors' data depending on the customer. Agree consent, retention and access rules before exporting.
Moving Microsoft Dynamics 365 Sales into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner