+1 480 485 7373
Microsoft Teams
Why HubSpot and Business Central disagree about customers
HubSpot centers on people. Someone fills in a form and becomes a lead. HubSpot then links them to a company, which it may have created from their email domain. Business Central centers on customers: legal entities with a billing address, payment terms, tax status and a ledger. Those are different ideas, and the integration has to bridge them.
Our practical rule is that a HubSpot company becomes a Business Central customer only when it buys. Until then, it is marketing data. When a rep wins a deal, the integration creates or matches the customer. From that point, Business Central owns the commercial fields. HubSpot keeps the relationship: emails, meetings, marketing history and the people involved.
Going the other way, sales and customer success teams gain a lot from seeing lifetime revenue, last order date and overdue balance on the HubSpot company record. Those properties also sharpen segmentation, for example a campaign aimed at customers who have not ordered in six months.
HubSpot property and object mapping
HubSpot quirks that affect the sync
- ✓Companies auto-created from email domains, which splits one customer across records or lumps unrelated firms sharing a domain
- ✓Deals with only a typed amount and no line items, which cannot become a valid sales order
- ✓Several deal pipelines with different stage names, each needing its own trigger rule
- ✓API rate limits that differ by subscription tier, so a large backfill needs batching
- ✓Merged records, where one ID survives and the other goes away, breaking any link stored on the loser
- ✓Quotes and payments taken inside HubSpot, which must not spawn a second invoice in Business Central
Connection routes that fit a HubSpot stack
Prebuilt connector
Connector apps listed on AppSource and in HubSpot's App Marketplace from several vendors handle companies, deals and products out of the box. A good fit when your use of HubSpot is fairly standard.
- ✓Configure rather than build
- ✓Check custom object support
- ✓Vendor absorbs API version changes
Power Automate or another iPaaS
Power Automate has a Business Central connector and can call HubSpot's API, and other iPaaS tools ship prebuilt HubSpot endpoints. Suitable for a narrow flow, such as creating a customer and order when a deal closes.
- ✓Quick for one or two flows
- ✓Error handling needs deliberate design
- ✓Grows fragile if stretched too far
Custom API integration
A custom service built on HubSpot's CRM APIs and the Business Central APIs suits companies with custom objects, several pipelines or subscription billing logic.
- ✓Handles custom objects
- ✓Precise control over what triggers an order
- ✓Upkeep sits with you or with us
Testing first, then a weekly health check
Not every HubSpot subscription includes a full sandbox. So teams often test in a developer test account, or a standard sandbox where your tier has one. Either way, connect it to a Business Central sandbox. Write a short script of cases: a brand new company, a returning customer, a discounted deal, a deal dragged back out of Closed Won, and a merged contact.
After go-live, a weekly review of the Business Central HubSpot integration covers the business side. It looks for won deals with no ERP order, BC customers with no HubSpot company, and records that failed to sync. The technical side needs a same-day alert on failures. A deal that silently failed to create an order is a customer waiting for a delivery nobody scheduled.
HubSpot integration questions from buyers
Which HubSpot deal stage should create the order in Business Central?
Use the stage that means the customer has committed, which is Closed Won in most pipelines. Some companies create a sales quote earlier, at a proposal stage, so pricing and availability come from the ERP. That works when reps keep stages up to date. Whatever you choose, moving a deal backwards should alert someone rather than delete an order automatically.
Which HubSpot subscription do we need?
You need a tier that gives you deals, line items, products and API access at the volume you plan to sync. Rate limits and some features differ between tiers, so compare HubSpot's current tier list against your planned flows. If you only use HubSpot for marketing, the integration may be as simple as sending customer revenue data to HubSpot for segmentation.
Can HubSpot show invoices from Business Central?
Yes, as summary properties, or as a custom object if your subscription supports custom objects. Most teams are well served by open balance, overdue amount, last invoice date and lifetime revenue on the company record. Invoice PDFs are better opened in Business Central or emailed from it. Keep HubSpot data to what someone will use in a conversation or a list.
More Business Central HubSpot integration questions
Is HubSpot or Dynamics 365 Sales the better CRM alongside Business Central?
Either can work well, and the answer depends on how your teams sell and market. Dynamics 365 Sales connects to Business Central through a built-in Dataverse integration, which reduces integration effort. Teams that value its marketing tools and ease of use often prefer HubSpot. If HubSpot already works for you, integrating it is usually a better use of budget than switching.
What happens if someone merges two companies in HubSpot?
The integration must fall back on the stored Business Central customer number, because only one HubSpot record ID survives a merge. If both companies were already customers in Business Central, finance decides whether to merge them there as well. That call stays manual, since it affects balances and history. The integration should flag the merge rather than act on it.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.