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 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.
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.
Ratings are CC judgments from Microsoft's public documentation. Per-tenant settings, custom fields and extensions are confirmed in discovery.
Customers, contacts, items, sales quotes, sales orders, sales invoices, customer payments and dimensions all have documented v2.0 endpoints, and most support webhook subscriptions.
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.
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.
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.
The customer master: name, address, salesperson, currency, payment terms, credit limit, balance due and blocked status, plus the contact people linked to each customer.
balanceDue and creditLimit are read-only in HubSpotThe product catalog sellers quote from. Business Central owns item numbers, descriptions, units and unit prices.
Quotes with status Draft, Sent, Accepted or Expired, and sales orders with lines, totals, requested delivery date and shipping status.
fullyShipped flow back to the dealmakeOrder converts an accepted quoteInvoices with status (Draft, Open, Paid, Canceled, Corrective), due date, totals and remaining amount. Payment status comes from the invoice itself.
remainingAmount and status show what is unpaidDimensions (department, region, project and so on) tag documents for reporting. One environment can hold several companies, each with its own data.
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.
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.
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.
HubSpot owns contacts, marketing and pipeline. Business Central owns customer numbers, prices, credit, orders, invoices and payments. Neither overwrites the other's fields.
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.
HubSpot shows invoice status and balances so sellers can act. Posting, credit memos and cash application stay in Business Central.
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.
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.
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.
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.
Build the webhook receiver, subscription renewal, record matcher, document builder and batch writer, with idempotent writes and an error replay queue.
Load customers, contacts, items and an agreed window of orders and posted invoices, company by company, using paged API reads.
Build overdue-invoice tasks, credit-hold alerts, reorder plays and revenue reports by dimension.
Run live for two weeks with outbound document creation in review mode, then switch on and add remaining companies.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers & contacts | ||||
| customer.number | bc_customer_number | Company | ↔ Both | Primary key. Written to HubSpot on create in Business Central. |
| customer.id | bc_customer_id | Company | BC → HS | System ID used for API reads and webhooks. |
| customer.displayName | name | Company | ↔ Both | HubSpot creates; Business Central keeps its own on later edits. |
| customer.addressLine1, city, state, country, postalCode | address, city, state, country, zip | Company | ↔ Both | Fill blanks only after create. |
| customer.salespersonCode | hubspot_owner_id | Company | BC → HS | Mapped through a salesperson-to-owner table. |
| customer.balanceDue | bc_balance_due | Company | BC → HS | Read-only in HubSpot. |
| customer.creditLimit | bc_credit_limit | Company | BC → HS | Read-only in HubSpot. |
| customer.blocked | bc_blocked | Company | BC → HS | Drives a credit-hold flag for sellers. |
| contactsInformation (contact people) | email, firstname, lastname | Contact | ↔ Both | Associated to the company. Match on email. |
| Items & prices | ||||
| item.number | hs_sku | Product | BC → HS | Shared key for products and line items. |
| item.displayName | name | Product | BC → HS | |
| item.unitPrice | price | Product | BC → HS | Business Central owns price. |
| item.itemCategoryCode | bc_item_category | Product | BC → HS | |
| item.baseUnitOfMeasureCode | bc_unit_of_measure | Product | BC → HS | Confirm field name in discovery. |
| Quotes & orders | ||||
| Deal (closed won) + line items | salesQuote or salesOrder | Deal | HS → BC | Client chooses quote or order. Lines use item number. |
| salesQuote.number, status | bc_quote_number, bc_quote_status | Deal | BC → HS | Draft, Sent, Accepted, Expired. |
| salesOrder.number | bc_order_number | Order | BC → HS | Order record associated to the deal and company. |
| salesOrder.status, fullyShipped | bc_order_status, bc_fully_shipped | Order | BC → HS | Shipping status visible to the account team. |
| salesOrder.totalAmountIncludingTax | hs_total_price | Order | BC → HS | |
| salesOrderLines | Line items | Order | BC → HS | Item number, quantity, unit price. |
| Invoices & payments | ||||
| salesInvoice.number | bc_invoice_number | Invoice | BC → HS | Posted invoices only. |
| salesInvoice.invoiceDate, dueDate | bc_invoice_date, bc_due_date | Invoice | BC → HS | |
| salesInvoice.totalAmountIncludingTax | bc_invoice_total | Invoice | BC → HS | In invoice currency. |
| salesInvoice.remainingAmount | bc_remaining_amount | Invoice | BC → HS | Zero when fully paid. |
| salesInvoice.status | bc_invoice_status | Invoice | BC → HS | Open, Paid, Canceled, Corrective. |
| salesInvoice.currencyCode | Invoice currency | Invoice | BC → HS | Multi-currency must be on in HubSpot. |
| salesInvoice.shortcutDimension1Code, 2Code | bc_dimension_1, bc_dimension_2 | Invoice | BC → HS | Global dimensions for reporting. |
Business Central uses Microsoft Entra ID for service-to-service access. Limits below are Microsoft's published operational limits for Business Central online.
| Topic | Business Central | HubSpot |
|---|---|---|
| Interfaces | API 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. |
| Authentication | OAuth 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 notifications | Webhook 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 limits | 6,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 scope | Every call names one company: companies({id})/customers. Several companies means one loop per company. | One portal. Business Central company stored as a property. |
| Notification delivery | Notifications 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 requirements | Business 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. |
Severity reflects impact on the SOW, not technical difficulty alone.
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.
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.
Subscriptions last 3 days. The integration renews them on a schedule and runs a nightly reconciliation read in case a notification is missed.
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.
Each Business Central company has its own customers and numbers. The matcher keys on company plus customer number so two companies never merge.
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.
Sellers see balance due, credit limit and blocked status before they quote, so no one promises an order finance will hold.
Closing a deal creates the Business Central quote or order with the right customer and items, with no re-keying by sales operations.
An invoice past its due date with a remaining amount creates a task for the account owner, with the invoice attached.
Posted invoices and order lines let HubSpot report actual billed revenue by product, owner and dimension next to pipeline.
Order history by item drives lists for customers due to reorder or ready for the next product.
Service tickets show the customer's recent orders, shipping status and open invoices on the same record.
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.
All custom properties use the bc_ prefix in a Business Central property group. Finance fields are read-only for HubSpot users.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| bc_customer_number | BC Customer No. | Company | Single-line text | customer.number; unique per BC company |
| bc_customer_id | BC Customer ID | Company | Single-line text | customer.id (system ID) |
| bc_company | BC Company | Company | Dropdown | Business Central company name |
| bc_balance_due | Balance Due | Company | Number (currency) | customer.balanceDue |
| bc_credit_limit | Credit Limit | Company | Number (currency) | customer.creditLimit |
| bc_blocked | Blocked Status | Company | Dropdown | customer.blocked |
| bc_quote_number | BC Quote No. | Deal | Single-line text | salesQuote.number |
| bc_order_number | BC Order No. | Order | Single-line text | salesOrder.number |
| bc_fully_shipped | Fully Shipped | Order | Single checkbox | salesOrder.fullyShipped |
| bc_invoice_number | BC Invoice No. | Invoice | Single-line text | salesInvoice.number |
| bc_remaining_amount | Remaining Amount | Invoice | Number (currency) | salesInvoice.remainingAmount |
| bc_invoice_status | BC Invoice Status | Invoice | Dropdown | salesInvoice.status |
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.
Based on public documentation. Tenant-specific fields, extensions and permission sets are confirmed in discovery.
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.
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.
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.
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.
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.