Order Status & Fulfillment
Sales and customer service need visibility into where an order stands in Business Central or F&SCM without switching systems, especially once a deal has closed and operations has taken over.
Microsoft Dynamics 365 has multiple products. Dynamics 365 Sales is Microsoft’s CRM that competes directly with HubSpot. Business Central (formerly Dynamics NAV) and Finance & Supply Chain Management (formerly Dynamics AX) are the ERPs under the Dynamics 365 name.
HubSpot has built its own native connector for Dynamics 365 Sales (the CRM), and a second, separate native connector for Business Central Online. Finance & Supply Chain Management and on-premises Business Central still need a third-party connector or a custom build.
If you're on Business Central Online, the native connector already handles customer data. Everything below is what's worth adding past that, through a third-party connector or custom build, for Business Central in any deployment or for F&SCM.
Sales and customer service need visibility into where an order stands in Business Central or F&SCM without switching systems, especially once a deal has closed and operations has taken over.
A closed HubSpot deal becoming a Business Central sales order at a defined stage (not automatically at every stage change) keeps the handoff clean, matching the pattern third-party Business Central connectors already use.
Sales and account management benefit from seeing revenue and payment status on the HubSpot timeline without needing write access to financial records.
This is the kind of structural, relationship-heavy data that tends to need deliberate custom handling rather than a default mapping, on both the Dynamics 365 Sales side and the ERP side.
The first scoping question on a Dynamics 365 project is which Dynamics 365, and for Business Central, which deployment. A Dynamics 365 Sales coexistence project (keeping both HubSpot and Dynamics 365 Sales running, or migrating off one) is a CRM-to-CRM conversation, often resolved largely by the free native connector. A Business Central Online project might be partly resolved by its own free native connector, if customer data is genuinely all you need. Anything past that, on-premises Business Central, F&SCM, or operational depth beyond customer records, is a CRM-to-ERP conversation: confirm the API surface, confirm what's customized, and scope the build around the fields and objects that actually matter to the business.
Cost follows the same split. Both native connectors cost nothing beyond what's already included in HubSpot, though Business Central's custom field mappings do require at least a Data Hub Starter subscription. Past what either native connector covers, a Business Central or F&SCM integration costs what any ERP-side build costs: discovery, the build itself, and ongoing maintenance as either system's configuration changes over time.
Before any integration conversation goes further, this is the question that decides everything else: which Dynamics 365 product, and is it the CRM or the ERP?
| Product | What It Is | Built For | Integration Relevance |
|---|---|---|---|
| Dynamics 365 Sales | Microsoft’s CRM, built on Dataverse | Sales teams managing leads, contacts, accounts, and opportunities | A HubSpot Dynamics 365 Sales project is a CRM-to-CRM question, not an ERP integration |
| Business Central (Online) | SMB/mid-market ERP (formerly Dynamics NAV) cloud subscription | Finance, inventory, and operations for smaller and mid-sized companies | Has its own native HubSpot connector, scoped to customer data |
| Business Central (On-Premises) | The same ERP as above, self-hosted rather than subscribed to as a cloud service | Companies that haven't moved to Business Central Online | No native HubSpot connector; same third-party or custom path as F&SCM |
| Finance & Supply Chain Management (F&SCM) | Enterprise ERP (formerly Dynamics AX) | Large, multi-entity, global operations with complex manufacturing or distribution | ERP commonly integrated with HubSpot |
HubSpot's native Microsoft Dynamics 365 integration connects to Dynamics 365 Sales, bidirectionally, without custom code. You choose which objects to sync, and the core mapping is shown here.
The sync runs near real time, with most changes propagating within minutes, and you can connect two separate Dynamics 365 instances to one HubSpot account.
| HubSpot | Dynamics 365 | |
|---|---|---|
| Company | ⇄ | Account |
| Contact | ⇄ | Contact and Lead |
| Deal | ⇄ | Opportunity |
| Custom Objects | ⇄ | Entities |
| Product | ⇄ | Bundles and Products |
| Meetings | ⇄ | Appointments |
| Notes | ⇄ | Notes |
| Tasks | ⇄ | Tasks |
| Invoice | ⇄ | Invoice |
| Order | ⇄ | Sales Orders |
| Emails | ⇄ | Emails |
| Calls | ⇄ | Phone Calls |
A separate native app, also built and published by HubSpot, that syncs customer data bidirectionally with Business Central in real time, with default field mappings already set up and historical data syncing in on install. Custom field mappings need a HubSpot Data Hub Starter or Professional subscription, a lighter gate than the Enterprise-tier requirements some other native connectors in this series carry.
This connector only reaches Business Central Online, the cloud subscription version (Essentials, Premium, or Team Members plans). On-premises Business Central isn't covered, and neither is Finance & Supply Chain Management. If you're on either of those, the native path doesn't exist, and the rest of this page is the one that applies to you instead.
| Native HubSpot Connector | iPaaS | Power Automate | Custom API Build | |
|---|---|---|---|---|
| Best For | Dynamics 365 Sales coexistence or migration; Business Central Online customer data specifically | Companies connecting Business Central (Online or on-premises) or F&SCM alongside other systems, or wanting a managed sync beyond customer data | Teams already inside the Microsoft ecosystem who want to extend or bypass native connector limits without full custom development | Business Central On-Premises, F&SCM, or any Business Central Online need the native connector doesn't cover (orders, invoices, inventory) |
| Pros | Free, no-code, maintained by HubSpot, two separate apps for two separate products | Vendor-managed; many have purpose-built Dynamics/Business Central connectors | Native to Microsoft's own low-code platform; no separate vendor relationship if you're already licensed for Power Platform | Full control over exactly what syncs and how |
| Cons | Dynamics 365 Sales app only reaches Sales; Business Central app only reaches Online, and only customer data, not orders or invoices | Ongoing subscription that scales with usage | Still requires someone who can build and maintain flows; not a packaged connector | Requires a development team that owns it long-term |
| Our Take | Worth installing on day one for either system it actually covers, but confirm which one you need before assuming it reaches further | A reasonable default for Business Central or F&SCM once you need more than the native connector's customer-data scope | Worth considering specifically because it's unique to this ecosystem | The default for on-premises Business Central, F&SCM, or any operational depth (orders, invoicing) the native connector doesn't reach |
Everything above is what shapes the pitch and the budget. Everything here is what your Dynamics 365 admin or IT contact will actually be asked to confirm or provision before build work starts. Forward it to them directly, or walk through it together on our Integration Readiness Check.
Business Central and Finance & Supply Chain Management each expose their own API, separate from Dataverse and separate from each other.
Business Central has a documented REST API (API v2.0) and OData v4 web services built into the product. Beyond what HubSpot's own native connector covers, third parties build directly against these same endpoints for the objects it doesn't reach.
Finance & Supply Chain Management has a separately documented integration surface (built around Microsoft's Data Management Framework and OData services), distinct from Business Central's.
Microsoft Dynamics 365 is a family of business applications, not one product. Dynamics 365 Sales is Microsoft's CRM. Business Central and Finance & Supply Chain Management are separate ERPs, each with its own data model and integration surface.
Yes, through two separate native connectors. One syncs contacts, companies, deals, and other core objects bidirectionally with Dynamics 365 Sales, the CRM. A separate one syncs customer data bidirectionally with Business Central Online, one of the ERPs in the family. Neither reaches Business Central On-Premises or Finance & Supply Chain Management.
Yes, both of them. HubSpot's native connectors for Dynamics 365 Sales and for Business Central Online are included on HubSpot's plans with no separate license required, though Business Central's custom field mappings do need at least a Data Hub Starter subscription. The bigger cost in most Dynamics 365 projects comes from what neither native connector reaches: Business Central On-Premises, Finance & Supply Chain Management, or operational depth (orders, invoices) beyond customer data.
Depends on which one. HubSpot's documentation lists Dynamics 365 Sales custom entities as syncable to HubSpot custom objects.
The Business Central connector supports custom field mappings, gated behind Data Hub Starter or Professional, but that's custom fields on the objects it already syncs, not new custom objects.
Yes, for the objects it covers, with some one-directional exceptions. Tasks associated with a Dynamics 365 Lead, for example, only sync from Dynamics 365 to HubSpot, not back.
Yes, and HubSpot has its own native connector for it, separate from the Dynamics 365 Sales one. The catch is it only reaches Business Central Online, and only syncs customer data. On-premises Business Central, or anything past customer data on Business Central Online (orders, invoices, inventory), needs a third-party connector or a custom API built against Business Central's own REST and OData v4 endpoints.
Yes, though it's a less common pairing than Business Central. Finance & Supply Chain Management has its own integration surface, separate from Business Central's. No native HubSpot connector reaches it, so a third-party build or custom API work against F&SCM's own services is the realistic path, the same shape as Business Central.
It can, specifically within the Microsoft ecosystem. Power Automate can extend what the native Dynamics 365 Sales connector supports, or build flows the native connector doesn't cover, without a full custom API build. It isn't a path into Business Central or F&SCM by itself, but it's a genuinely different option from what exists for the other ERPs in this series.
It depends almost entirely on which Dynamics 365 product is involved. Turning on the native Dynamics 365 Sales connector can happen in a day. A Business Central or F&SCM integration is a larger scoped build.
The native Dynamics 365 Sales connector costs nothing beyond HubSpot's own subscription. A Business Central or F&SCM integration costs what any ERP-side build costs, depending on the API surface, the objects involved, and whether a third-party connector already covers the need.
Before you scope a Dynamics 365 integration, find out whether you're working with the CRM, the ERP, or both, and which path reaches the system you need connected. Our ERP Integration Readiness Check starts with that question.