Microsoft Dynamics to HubSpot migration guide
Moving from Dynamics 365 to HubSpot: entities, Power Automate flows, Outlook habits and the integration decisions that matter.
The short answer: Moving from Dynamics 365 to HubSpot, leads and contacts become contacts, accounts become companies, opportunities become deals and cases become tickets. The biggest work is in Power Automate flows, business process flows and ERP connections, which must be rebuilt or reconnected. Dynamics moves commonly take 45 to 90 days.
Microsoft Dynamics 365 is often chosen because a company already runs on Microsoft. It’s powerful, but many sales teams find it heavy to use day to day, and changes usually need a specialist. Moving to HubSpot is a common way to get a CRM that reps adopt and marketing can share. The challenge is untangling everything Dynamics is connected to.
How Dynamics data maps to HubSpot
| Dynamics 365 | HubSpot | What to decide |
|---|---|---|
| Leads and Contacts | Contacts | Use lifecycle stage and lead status to keep the distinction |
| Accounts | Companies | Duplicates and parent/child hierarchies |
| Opportunities | Deals | Sales stages, probabilities and estimated revenue |
| Cases | Tickets | Service history and SLAs |
| Activities (phone calls, emails, appointments, tasks) | Timeline activities | Original dates and owners |
| Custom tables (entities) | Custom objects, or properties | Custom objects require HubSpot Enterprise |
Power Automate and business process flows
Dynamics automation often lives in Power Automate flows, business process flows and plugins. Some of these reach well beyond the CRM, into SharePoint, Teams, finance systems or approval chains. List every one, identify what triggers it and what it touches, then decide whether to rebuild it in HubSpot, keep it in Power Automate connected to HubSpot, or retire it. See rebuilding your automations in HubSpot.
Outlook and the Microsoft habit
Dynamics users often work from Outlook. HubSpot offers an Outlook add-in for logging emails and meetings, and connecting it before go-live keeps reps in a familiar place. Test it with real mailboxes during rehearsal, not on cutover day.
ERP and finance connections
If Dynamics CRM shares data with Dynamics finance or another ERP, for example account numbers, orders or invoices, that link has to be rebuilt between HubSpot and the ERP. Scope it early. It’s often the item that sets the go-live date.
Common mistakes
- Underestimating Power Automate flows that run outside the CRM
- Breaking the CRM-to-ERP link that finance relies on
- Recreating every custom table instead of simplifying
- Training reps on HubSpot in general instead of their own pipeline
What to expect
Dynamics moves commonly take 45 to 90 days, depending on automations, integrations and how heavily the system was customised. Our Dynamics package covers the full move, including automations, reporting and training, with a fixed price and our 30-day guarantee. Start with a free risk scan.
Sources and further reading
- Getting started with the HubSpot CRM Data Migration Service, HubSpot Academy
- Do you need HubSpot Enterprise for custom objects?, Meticulosity
- Create workflows, HubSpot Knowledge Base
Platform features and policies change. Check the vendor’s current documentation before acting on any detail in this article. This article is general information, not legal advice.