A HubSpot Elite Solutions Partner built to help organizations unify strategy, systems, and execution. We design HubSpot systems that scale.

See how we've solved complex HubSpot challenges across migrations, integrations, CMS, automation, and optimization.

Join a team building smarter HubSpot systems. We value strategic thinkers who move proactively, care about quality, and want to do meaningful work.

Integration

HubSpot <> Dynamics 365 Business Central Integration

Powered by Commercient
Integration Assessment
Integration Assessment · ERP

Dynamics 365 Business Central × HubSpot

How customers, items, quotes, sales orders, posted invoices and payment status in Microsoft Dynamics 365 Business Central can reach HubSpot, so sales and service teams see the full quote-to-cash picture without logging in to the ERP.

Business Central API v2.0OData v4 web servicesWebhook subscriptionsMicrosoft Entra ID (OAuth 2.0)HubSpot's Business Central appCustom build for the full quote-to-cash
Platform ownerMicrosoft
Integration typeHubSpot app + custom extension
Primary directionTwo-way, ERP owns finance
FeasibilityBuildable, well documented
API accessOpen API
01 — Summary

Does Dynamics 365 Business Central integrate with HubSpot?

Business Central is Microsoft's ERP for small and mid-sized companies. It holds the customer master, items and prices, sales documents, posted invoices and receivables. HubSpot holds the people, the pipeline and the conversations. This assessment shows how the two meet.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. API v2.0 is documented publicly. The client's administrator registers a Microsoft Entra application and assigns permission sets.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

Business Central has an open, documented API, so HubSpot can carry the whole quote-to-cash record, not just contacts and products.

Campaign Creators assessment

Microsoft publishes a standard REST API (v2.0) and OData v4 web services for Business Central, with webhook subscriptions for change notifications and Microsoft Entra ID for service-to-service authentication. HubSpot's own Business Central app is the natural starting point: it syncs customers to contacts, items to products, opportunities to deals and sales orders to orders. The custom build extends it with companies, posted invoices, invoice lines, payment status, dimensions and more than one Business Central company.

Scorecard
Data richnessHigh
API accessOpen
Public docsExtensive
Build complexityModerate

Ratings are CC judgments from Microsoft's public documentation. Per-tenant settings, custom fields and extensions are confirmed in discovery.

Strength

A standard, documented API

Customers, contacts, items, sales quotes, sales orders, sales invoices, customer payments and dimensions all have documented v2.0 endpoints, and most support webhook subscriptions.

Plan for

Customers are companies, not people

In Business Central a customer is usually a business. HubSpot needs that customer as a Company, with its people as associated Contacts. The custom build adds the company layer and the association rules.

Gate

Entra app and permissions first

An administrator registers a Microsoft Entra application, adds it on the Business Central Microsoft Entra Applications page, and assigns permission sets. Nothing syncs until that is done.

02 — API modules

Which Dynamics 365 Business Central APIs does the integration use?

Seven areas matter to a HubSpot build. Four carry quote-to-cash, two support it, and one is a scope decision made at the start. Every call is scoped to one Business Central company.

Core

Customers & contacts

customers · contacts · contactsInformation

The customer master: name, address, salesperson, currency, payment terms, credit limit, balance due and blocked status, plus the contact people linked to each customer.

  • Customer becomes a HubSpot Company
  • Contact people become associated HubSpot Contacts
  • balanceDue and creditLimit are read-only in HubSpot
Core

Items & prices

items · itemCategories · unitsOfMeasure

The product catalog sellers quote from. Business Central owns item numbers, descriptions, units and unit prices.

  • Items become HubSpot Products
  • Item number is the shared SKU
  • Webhook on items keeps prices current
Core

Sales quotes & orders

salesQuotes · salesOrders · lines

Quotes with status Draft, Sent, Accepted or Expired, and sales orders with lines, totals, requested delivery date and shipping status.

  • A won HubSpot deal can create a sales quote or order
  • Order status and fullyShipped flow back to the deal
  • makeOrder converts an accepted quote
Core

Sales invoices & payments

salesInvoices · salesInvoiceLines · customerPayments

Invoices with status (Draft, Open, Paid, Canceled, Corrective), due date, totals and remaining amount. Payment status comes from the invoice itself.

  • Posted invoices become HubSpot Invoices
  • remainingAmount and status show what is unpaid
  • Customer payment journal lines are optional detail
Structure

Dimensions & companies

dimensions · dimensionSetLines · companies

Dimensions (department, region, project and so on) tag documents for reporting. One environment can hold several companies, each with its own data.

  • Global dimension codes on every sales document
  • One connector loop per Business Central company
  • Company name stamped on every HubSpot record
Starting point

HubSpot's Business Central app

Built by HubSpot · HubSpot Marketplace

HubSpot's app syncs customers to contacts, items to products, opportunities to deals and sales orders to orders, two-way, with default mappings. Custom field mappings use Data Hub.

  • Setup adds a Business Central extension and a published web service
  • Maps customers to contacts, not companies
  • The custom build adds what the app does not cover
Scope decision

Object ownership

App, custom build, or both

Each object is synced by one path only. Where the custom build takes over an object, that mapping is switched off in the app so no record is written twice.

  • Decide per object: app or custom build
  • Business Central owns finance fields; HubSpot owns pipeline
  • Record the decision in the SOW
03 — Framework

How does the Dynamics 365 Business Central HubSpot integration work?

The custom build sits beside HubSpot's app. A CC-built integration layer receives Business Central webhook notifications, reads the changed records through the v2.0 API, matches them to HubSpot records and writes in batches. Won deals travel the other way as Business Central sales quotes or orders.

Dynamics 365 Business Central
Customers & contactswebhook + v2.0 API
Itemswebhook + v2.0 API
Sales quotes & orderswebhook + v2.0 API
Sales invoicesstatus, remaining amount, lines
CC integration layer
Webhook receiverhandshake, clientState check, queue
Subscription keeperrenews each subscription before 3 days
Record matchercustomer number · email · item number
Document builderwon deal → sales quote or order
HubSpot writerbatch upserts, error replay
HubSpot
Companiesone per Business Central customer
Contactscustomer contact people
Products & line itemsitem catalog and document lines
Deals, quotes & orderspipeline through fulfillment
Invoicesposted invoices and payment status
Business Central → HubSpot (customers, items, documents, payment status)HubSpot → Business Central (new customers and won deals as quotes or orders)
Principle

Each system owns its own facts

HubSpot owns contacts, marketing and pipeline. Business Central owns customer numbers, prices, credit, orders, invoices and payments. Neither overwrites the other's fields.

Principle

Keys travel both ways

The Business Central customer number and system ID are stored on the HubSpot company, and the HubSpot record ID can be stored in Business Central, so every later update matches without guesswork.

Principle

Finance stays in the ERP

HubSpot shows invoice status and balances so sellers can act. Posting, credit memos and cash application stay in Business Central.

04 — Process

What does Dynamics 365 Business Central HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. HubSpot's app is set up first, so the custom build only adds what the app does not cover.

1

Discovery & ownership

List the Business Central companies, environments and extensions in use. Agree which system owns each object and field, and which objects stay with HubSpot's app.

Gate to next phaseSigned object ownership table
2

Access & app setup

Register the Microsoft Entra application, add it in Business Central with least-privilege permission sets, and install HubSpot's Business Central app for the objects it covers.

Gate to next phaseToken works against a sandbox company; app syncing default objects
3

HubSpot data model

Create the bc_ properties, company and contact association labels, the deal pipeline stages that trigger Business Central documents, and the invoice and order properties in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
4

Build

Build the webhook receiver, subscription renewal, record matcher, document builder and batch writer, with idempotent writes and an error replay queue.

Gate to next phaseOne Business Central company syncing end to end in sandbox
5

Backfill

Load customers, contacts, items and an agreed window of orders and posted invoices, company by company, using paged API reads.

Gate to next phaseCounts and open balances reconcile to Business Central reports
6

Workflows & reporting

Build overdue-invoice tasks, credit-hold alerts, reorder plays and revenue reports by dimension.

Gate to next phaseClient walkthrough and sign-off of each automation
7

Parallel run & launch

Run live for two weeks with outbound document creation in review mode, then switch on and add remaining companies.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Dynamics 365 Business Central HubSpot integration sync?

Business Central field names come from the API v2.0 reference. Custom fields added by extensions are confirmed in discovery and exposed through a custom API page where needed.

Business Central fieldHubSpot propertyObjectDirectionNotes
Customers & contacts
customer.numberbc_customer_numberCompany↔ BothPrimary key. Written to HubSpot on create in Business Central.
customer.idbc_customer_idCompanyBC → HSSystem ID used for API reads and webhooks.
customer.displayNamenameCompany↔ BothHubSpot creates; Business Central keeps its own on later edits.
customer.addressLine1, city, state, country, postalCodeaddress, city, state, country, zipCompany↔ BothFill blanks only after create.
customer.salespersonCodehubspot_owner_idCompanyBC → HSMapped through a salesperson-to-owner table.
customer.balanceDuebc_balance_dueCompanyBC → HSRead-only in HubSpot.
customer.creditLimitbc_credit_limitCompanyBC → HSRead-only in HubSpot.
customer.blockedbc_blockedCompanyBC → HSDrives a credit-hold flag for sellers.
contactsInformation (contact people)email, firstname, lastnameContact↔ BothAssociated to the company. Match on email.
Items & prices
item.numberhs_skuProductBC → HSShared key for products and line items.
item.displayNamenameProductBC → HS
item.unitPricepriceProductBC → HSBusiness Central owns price.
item.itemCategoryCodebc_item_categoryProductBC → HS
item.baseUnitOfMeasureCodebc_unit_of_measureProductBC → HSConfirm field name in discovery.
Quotes & orders
Deal (closed won) + line itemssalesQuote or salesOrderDealHS → BCClient chooses quote or order. Lines use item number.
salesQuote.number, statusbc_quote_number, bc_quote_statusDealBC → HSDraft, Sent, Accepted, Expired.
salesOrder.numberbc_order_numberOrderBC → HSOrder record associated to the deal and company.
salesOrder.status, fullyShippedbc_order_status, bc_fully_shippedOrderBC → HSShipping status visible to the account team.
salesOrder.totalAmountIncludingTaxhs_total_priceOrderBC → HS
salesOrderLinesLine itemsOrderBC → HSItem number, quantity, unit price.
Invoices & payments
salesInvoice.numberbc_invoice_numberInvoiceBC → HSPosted invoices only.
salesInvoice.invoiceDate, dueDatebc_invoice_date, bc_due_dateInvoiceBC → HS
salesInvoice.totalAmountIncludingTaxbc_invoice_totalInvoiceBC → HSIn invoice currency.
salesInvoice.remainingAmountbc_remaining_amountInvoiceBC → HSZero when fully paid.
salesInvoice.statusbc_invoice_statusInvoiceBC → HSOpen, Paid, Canceled, Corrective.
salesInvoice.currencyCodeInvoice currencyInvoiceBC → HSMulti-currency must be on in HubSpot.
salesInvoice.shortcutDimension1Code, 2Codebc_dimension_1, bc_dimension_2InvoiceBC → HSGlobal dimensions for reporting.
06 — Auth & API

How are authentication and API limits handled?

Business Central uses Microsoft Entra ID for service-to-service access. Limits below are Microsoft's published operational limits for Business Central online.

TopicBusiness CentralHubSpot
InterfacesAPI v2.0 (REST, OData v4 conventions) at api.businesscentral.dynamics.com/v2.0/{environment}/api/v2.0. Published OData v4 web services and custom API pages for fields the standard API lacks.REST APIs: CRM objects, commerce objects, associations, imports.
AuthenticationOAuth 2.0 client credentials through a Microsoft Entra application with the API.ReadWrite.All application permission, registered in Business Central with assigned permission sets (SUPER is not allowed).Private app access token or OAuth 2.0 public app, scoped per object.
Change notificationsWebhook subscriptions on customers, items, sales quotes, orders, invoices and more. Validation handshake on create and renew. Subscriptions expire after 3 days unless renewed.HubSpot webhooks for outbound triggers on deals and companies.
Rate limits6,000 OData requests per user in a 5-minute sliding window, 5 concurrent requests, 100 operations per batch, 20,000 entities per page. HTTP 429 when exceeded.Per-10-second burst and daily limits by subscription tier.
Company scopeEvery call names one company: companies({id})/customers. Several companies means one loop per company.One portal. Business Central company stored as a property.
Notification deliveryNotifications batch changes after about 30 seconds. Over 1,000 changes become one collection notification. Retries for about 36 hours on 408, 429 and 5xx.Writes are immediate; batch endpoints handle volume.
Plan requirementsBusiness Central Essentials or Premium. Extensions may need a custom API page for their fields.Custom properties on every paid tier. Custom objects need an Enterprise hub. Confirm order and invoice object access for the portal.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Two sync paths on the same objectHigh

HubSpot's app and the custom build must not both write the same object. The ownership table decides which path syncs each object, and the app mapping is switched off where the custom build takes over.

Companies versus contactsHigh

Business Central customers are usually businesses. Moving them from contacts to companies changes reports and lists, so plan the move and the association rules before backfill.

Webhook subscriptions expireMedium

Subscriptions last 3 days. The integration renews them on a schedule and runs a nightly reconciliation read in case a notification is missed.

Extensions and custom fieldsMedium

Fields added by extensions are not in the standard API. They need a custom API page in Business Central, which is a small AL build on the client side.

Several companies in one tenantMedium

Each Business Central company has its own customers and numbers. The matcher keys on company plus customer number so two companies never merge.

Currency and taxLow

Invoices carry their own currency and tax totals. HubSpot multi-currency is set up before backfill, and totals are shown as Business Central reports them.

Opportunities in HubSpot

Credit and balance on every accountHigh value

Sellers see balance due, credit limit and blocked status before they quote, so no one promises an order finance will hold.

Won deals become ERP documentsHigh value

Closing a deal creates the Business Central quote or order with the right customer and items, with no re-keying by sales operations.

Overdue invoices as tasksHigh value

An invoice past its due date with a remaining amount creates a task for the account owner, with the invoice attached.

Revenue reporting in HubSpotMedium value

Posted invoices and order lines let HubSpot report actual billed revenue by product, owner and dimension next to pipeline.

Reorder and upsell playsMedium value

Order history by item drives lists for customers due to reorder or ready for the next product.

Service with order contextMedium value

Service tickets show the customer's recent orders, shipping status and open invoices on the same record.

Quote-to-cash flow

One deal, from first call to paid invoice.

Each step happens in the system that owns it, and the other system sees the result. HubSpot runs the sale; Business Central runs fulfillment and finance.

  1. HubSpot: the deal, its contacts and its line items are built from Business Central products.
  2. On closed won, the integration creates the Business Central customer if needed, then a sales quote or order.
  3. Business Central ships and posts the invoice; order and invoice status return to HubSpot.
  4. Payment lowers the remaining amount to zero, the invoice shows Paid, and the account team sees it.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the bc_ prefix in a Business Central property group. Finance fields are read-only for HubSpot users.

Internal nameLabelObjectTypeSource / logic
bc_customer_numberBC Customer No.CompanySingle-line textcustomer.number; unique per BC company
bc_customer_idBC Customer IDCompanySingle-line textcustomer.id (system ID)
bc_companyBC CompanyCompanyDropdownBusiness Central company name
bc_balance_dueBalance DueCompanyNumber (currency)customer.balanceDue
bc_credit_limitCredit LimitCompanyNumber (currency)customer.creditLimit
bc_blockedBlocked StatusCompanyDropdowncustomer.blocked
bc_quote_numberBC Quote No.DealSingle-line textsalesQuote.number
bc_order_numberBC Order No.OrderSingle-line textsalesOrder.number
bc_fully_shippedFully ShippedOrderSingle checkboxsalesOrder.fullyShipped
bc_invoice_numberBC Invoice No.InvoiceSingle-line textsalesInvoice.number
bc_remaining_amountRemaining AmountInvoiceNumber (currency)salesInvoice.remainingAmount
bc_invoice_statusBC Invoice StatusInvoiceDropdownsalesInvoice.status
09 — Scope builder

Interactive scope builder

Choose the objects and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
Business Central × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Dynamics 365 Business Central HubSpot integration FAQ

Does Dynamics 365 Business Central integrate with HubSpot?

Yes. HubSpot's own Business Central app syncs customers to contacts, items to products, opportunities to deals and sales orders to orders. Campaign Creators extends it with a custom build on Business Central API v2.0 and webhook subscriptions, adding companies, posted invoices, payment status, dimensions and more than one Business Central company.

What data syncs between Business Central and HubSpot?

Business Central customers become HubSpot companies with their contacts associated, and items sync to HubSpot products. Won HubSpot deals can create Business Central sales quotes or orders. Sales orders, posted invoices, invoice lines, payment status and open balances are written back to HubSpot.

Is HubSpot's Business Central app enough on its own?

It covers customers, items, deals and sales orders with default mappings. It does not cover companies, posted invoices, payment status, dimensions or several Business Central companies. The custom build adds those, and an ownership table decides which path syncs each object so the app and the custom build never write the same record.

What does setting up the Dynamics 365 Business Central HubSpot integration involve?

Seven phases, each closed by a client sign-off: discovery and ownership, access and app setup with a Microsoft Entra application, the HubSpot data model, the build, backfill, workflows and reporting, and a two-week parallel run before outbound document creation is switched on.

How long does the integration take and what does it cost?

Timeline and cost depend on the Business Central companies, extensions and custom fields in scope, how much HubSpot's app already covers, and the history to load. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.

Ready to Get More From HubSpot?

Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.