HubSpot Microsoft Business Central Integration: The Complete 2026 Guide

What is a HubSpot Microsoft Business Central integration?

A HubSpot Microsoft Business Central integration connects HubSpot (your CRM, marketing and sales platform) with Microsoft Dynamics 365 Business Central (your ERP). Customer, product, order and invoice data then flows automatically between the two systems. Sales sees what customers actually bought and paid, and finance gets clean orders without retyping deals.

Quick answer: there are four ways to connect HubSpot and Business Central.

1. HubSpot's native Business Central app: free and quick to set up, but focused on syncing customer records.
2. No-code automation tools (Zapier, n8n, Make): good for one-way triggers such as "deal won → create customer", but weak at two-way sync and error handling.
3. A Business Central extension or packaged connector: installed inside BC, with deeper object coverage, but you configure and maintain it yourself.
4. A managed iPaaS integration (like SyncMatters): two-way sync of standard and custom objects, designed, built and monitored by an integration team, from $300/month.

The right choice depends on how many objects you need to sync, whether the sync must run in both directions, and who will fix it when a record fails. The rest of this guide covers what data to sync, how the four options compare, and the Business Central quirks that break most integrations.

"When you build in-house, it often becomes a question of not if, but when you'll encounter scalability and maintenance issues." Darren Trumeter, SyncMatters

In this guide:

1. HubSpot vs. Business Central: who owns what
2. Why connect HubSpot and Business Central?
3. Use cases by team and industry
4. What data should sync (with field-level mapping)
5. 4 ways to integrate, compared and explained
6. 7 Business Central quirks that break integrations
7. Implementation roadmap
8. Data cleanup before the first sync
9. API limits, sync frequency and performance
10. Security, permissions and compliance
11. Testing and go-live checklist
12. Reports and dashboards to build
13. Cost and total cost of ownership
14. 10 common mistakes to avoid
15. How SyncMatters delivers the integration
16. Moving to HubSpot from another CRM while keeping BC
17. How to choose the right integration
18. Glossary and FAQ

HubSpot vs. Business Central: who owns what

HubSpot and Business Central don't compete; they cover opposite ends of the customer lifecycle. HubSpot runs everything before and around the sale. Business Central runs everything after the order: fulfillment, invoicing, payments and the books. The integration is the handoff between them.

Why not just use Dynamics 365 Sales?

Microsoft offers its own CRM, Dynamics 365 Sales, and Business Central can integrate with it by first connecting to Dataverse and then completing setup inside Business Central. Many mid-market companies still choose HubSpot as their CRM because marketing, sales and service share one platform, adoption by sales teams tends to be easier, and HubSpot's marketing automation is a core strength. The trade-off is that HubSpot and BC don't share a data platform, so you need a dedicated integration.

Why connect HubSpot and Business Central?

Without an integration, the same customer lives in two systems, and someone keeps them in sync by hand. Orders get retyped, prices drift, and sales calls customers without knowing they have an overdue invoice. Connecting the two systems gives each team the data it is missing.

Use cases: how companies use a HubSpot–Business Central integration

The most common use case is quote-to-cash: a deal moves through HubSpot, becomes an order in Business Central, and the invoice and payment status flow back to the CRM. Everything else builds on that loop.

Items and prices sync to HubSpot first, so every won deal becomes a BC order with real products; invoices and payments then flow back to the CRM.

Use cases by team

• Deal to order without retyping. When a deal reaches Closed Won, the integration creates or updates the BC customer and creates a sales order with the deal's line items.
• Accurate quotes. BC items, prices and units of measure sync to the HubSpot product library, so reps quote real SKUs at current prices.
• Revenue visibility for sales. Posted invoices, open balances and payment status appear on the HubSpot company record, so reps know who is overdue before they call.
• Purchase-based marketing. Order history lets marketing build lists such as "bought product A but not B" or "no order in 180 days" for cross-sell and win-back campaigns.
• Service with context. Support agents see what a customer bought and when it shipped next to each ticket.
• Credit control. Sales sees credit limits or blocked status before promising a new order.

Use cases by industry

What data should sync between HubSpot and Business Central?

Most integrations sync six to eight object pairs. The rule of thumb: HubSpot owns relationships and pipeline, and Business Central owns products, prices and money. Decide for each pair which system is the source of truth before anyone maps a field.

Start with companies, contacts and products, prove they stay clean for two weeks, then add deals and invoices. Syncing everything on day one makes the first duplicate impossible to trace.

Field-level mapping example

Object mapping tells you what syncs; field mapping decides whether it syncs cleanly. Below is a typical starting point. Your BC setup, custom fields and required posting data will change it.

HubSpot Company ↔ BC Customer

HubSpot Contact ↔ BC Contact (person)

HubSpot Deal → BC Sales Order

4 ways to integrate HubSpot with Business Central, compared

The native app is the default starting point, and it is worth checking the HubSpot Marketplace listing and its reviews before you rely on it; at the time of writing it shows a 1.5 rating from 10 reviews. No-code tools work for alerts and one-way pushes, but two-way sync between a CRM and an ERP needs conflict rules they don't have. Extensions go deep but leave mapping, upgrades and failures with your team. A managed iPaaS makes sense when the integration is business-critical and nobody in-house owns it full-time.

Option 1 in depth: HubSpot's native Business Central app

HubSpot's own app, built on its Data Sync engine, is the fastest way to get customer records flowing. It works with all HubSpot plans and requires a Business Central Essentials, Premium or Team Members subscription.

What it does: two-way sync of customer data, default field mappings out of the box, and a historical sync that brings existing records across on day one, then syncs updates as they happen (AppSource listing).

How setup works, at a high level:

1. In Business Central, upload HubSpot's extension (.app file).
2. In BC Web Services, publish the page the app needs (object type: Page) so HubSpot can read and write it.
3. In HubSpot, install the Microsoft Business Central app from the App Marketplace and authorize your BC environment.
4. Review the default field mappings, add custom mappings, and choose sync direction per field.
5. Turn on the sync and watch the first historical run for errors.

Follow HubSpot's knowledge base for the exact screens; the steps above show the shape of the work.

Where it falls short:

• It is built around customers and contacts. Items, sales orders, invoices and payments are outside its core scope.
• There is no deal → sales order automation, so finance still re-enters won deals.
• Logic is limited to field mapping: no conditional rules such as "create the BC customer only at Closed Won".
• Some fields aren't imported from Business Central, so check the mapping list against your requirements.
• User reviews on the marketplace are low (1.5 from 10 reviews at the time of writing), so test with a sandbox first.

Choose it when you only need a shared customer list and your team can handle occasional sync errors itself.

Option 2 in depth: Zapier, n8n and Make

No-code automation tools connect HubSpot and Business Central through triggers and actions. They shine for small, one-way automations and struggle once you need a true sync.

Recipes that work well:

• Deal moves to Closed Won → create a BC customer
• New BC customer → create or update a HubSpot company
• BC sales order updated → post a note or task on the HubSpot deal
• New HubSpot form submission from an existing customer → notify the account owner

Where they break:

• Two-way sync needs two separate flows, and each can trigger the other, creating update loops unless you add guard logic.
• No shared matching key. Each flow has to look up records itself, which is where duplicates come from.
• Line items are hard. Deals with many products require loops or code steps.
• Business Central setup isn't always no-code. With n8n, for example, BC is reached through a generic HTTP Request node that you authenticate yourself (n8n).
• Failures are per task. A failed run is logged in the tool, but nobody owns the fix unless you set up alerts.
• Costs scale with volume, because pricing is usually per task or per operation.

Choose it when you need a few event-driven automations and someone on your team is comfortable maintaining them.

Option 3 in depth: Business Central extensions and packaged connectors

Packaged connectors are products built specifically for HubSpot and Business Central. Some install as an AL extension inside your BC tenant, and others run as a HubSpot app with a setup wizard. They typically cover customers, contacts, items, quotes, orders, invoices and credit memos, and some write posted invoices and payments back to the HubSpot timeline.

They go much deeper than the native app, but you still own the configuration, the BC upgrade testing and the error queue. If your BC partner installed it, their support hours become part of the cost.

Questions to ask any connector vendor:

1. Which objects sync, and in which direction, out of the box?
2. Can I map custom fields and custom objects on both sides?
3. How are duplicates matched, and what is the matching key?
4. Is sync real-time, scheduled, or both? How are BC API limits handled?
5. Does it support multiple BC companies and BC on-premises?
6. What happens when a record fails: who is notified, and who fixes it?
7. How quickly is the connector updated after each BC major release?
8. What does onboarding include, and what is billed as extra services?

Choose it when your needs match the connector's standard model and you have a BC admin or partner to run it.

Option 4 in depth: managed iPaaS

An iPaaS (integration platform as a service) is middleware that sits between HubSpot and Business Central. It reads changes from both systems through their APIs, applies your mapping and business rules, and writes to the other side. In a managed model, the provider's engineers also design, build and monitor the integration.

Neither HubSpot nor Business Central needs custom code: the middle layer holds the rules, the record IDs and the error queue.

What makes it different:

• Business rules live in one place: which system wins per field, when a BC customer is created, and how deals map to quotes or orders.
• A matching layer stores the HubSpot and BC IDs for every pair of records, which prevents duplicates and loops.
• Error handling is someone's job. Failed records are queued, retried and fixed by the integration team.
• No code inside BC is required in most cases, because the integration uses BC's standard APIs. This keeps BC upgrades simpler.
• It scales across systems. The same platform can connect HubSpot to other tools in your stack later.

Choose it when the integration touches orders, billing or commissions, you need custom logic, and nobody in-house owns integrations full-time.

7 Business Central quirks that break HubSpot integrations

Most failed integrations don't fail on the API connection. They fail because CRM and ERP data models disagree. Plan for these before go-live.

1. Customers vs. contacts. HubSpot treats contacts and companies as peers. BC centers on the customer, and people attach to it through a company contact. Map this wrong and you get orphan contacts or duplicate customers.
2. Duplicates on day one. Both systems usually already hold the same customers under slightly different names. Deduplicate and set a matching key (e.g. domain, VAT ID or BC customer number stored in HubSpot) before the first sync.
3. Posted documents are read-only. Posted invoices and credit memos can't be edited in BC. Invoice data should flow only from BC to HubSpot.
4. Multiple companies in one BC environment. Each BC company is a separate data set. Decide which HubSpot business unit or pipeline maps to which BC company.
5. Dimensions, currencies and posting groups. BC requires fields HubSpot doesn't have, such as customer posting groups, payment terms and dimensions. The integration must fill them with defaults or rules, or orders will fail to post.
6. Items and pricing. Price lists, discounts and units of measure live in BC. Let BC push items to HubSpot and block reps from inventing products in quotes.
7. API limits and upgrades. BC online throttles API calls and changes with each major update. Batch high-volume syncs and retest after BC upgrades.

If your team doesn't want to own these rules, that's the strongest argument for a managed integration.

Implementation roadmap: from kickoff to go-live

A full HubSpot–Business Central integration usually runs in six phases. Durations below are typical for a mid-size scope (customers, contacts, items, deals to orders, invoices back); simple customer-only syncs move much faster.

The two phases teams most often underestimate are data cleanup and UAT. Both depend on people outside the project team, so book their time at kickoff.

Data cleanup before the first sync

An integration copies whatever is in both systems, including the mess. Cleaning first is the cheapest step in the whole project.

• Deduplicate HubSpot companies and contacts. Merge by domain and email first.
• Deduplicate BC customers and contacts. Check for the same customer created under several numbers.
• Match existing records across systems. Decide which HubSpot company equals which BC customer, and store the BC customer number in HubSpot before the first sync.
• Standardize reference data. Country codes, currencies, payment terms and salesperson codes must use the values BC expects.
• Align products. Every HubSpot product used in deals needs a matching BC item number, or should be archived.
• Decide what to leave behind. Old leads with no orders usually don't need a BC customer record.
• Clarify ownership. Map each HubSpot owner to a BC salesperson code.
• Back up both systems before the historical sync.

For large or messy databases, run a duplicate audit before integration design, not after the first sync has spread the duplicates to both systems.

API limits, sync frequency and performance

Business Central online limits web service traffic per user. Any integration has to work within these limits, especially during the first historical sync.

Source: Microsoft Learn, Business Central service scalability and operational limits. Microsoft raised these from an older per-environment limit of 600 requests per minute (release notes).

What this means in practice:

• Use a dedicated integration user so sync traffic doesn't compete with people working in BC.
• Prefer change-based sync over polling. BC APIs support webhooks, so the integration can react to changes instead of re-reading everything every few minutes.
• Batch the historical load. Moving tens of thousands of records at once needs batching, retries and back-off when a 429 comes back.
• Pick sync frequency per object. Deals → orders and customer changes benefit from near real-time sync. Invoices and payments can usually sync every 15 to 60 minutes. Item and price updates can often run a few times a day.
• Plan for BC upgrades. Business Central ships two major releases a year, so retest the integration after each one.

Security, permissions and compliance

The integration will read and write customer and financial data, so treat it like any other privileged user.

• Use OAuth, not shared passwords. Business Central online connects through a Microsoft Entra ID app registration, and HubSpot through an app or private app token.
• Grant least privilege. Give the integration user only the BC permission sets and HubSpot scopes it needs, for example no access to payroll or general ledger setup.
• Keep financial data read-only in HubSpot. Balances, credit limits and invoices should flow from BC only, and HubSpot users shouldn't be able to edit them.
• Limit who sees financial fields. Use HubSpot field-level permissions or teams so not every user sees credit data.
• Respect consent and data subject requests. A deletion request handled in HubSpot may also need action in BC, so document the process across both systems.
• Log changes. Make sure every write by the integration can be traced to the integration user.
• Check your vendor. Ask for security certifications, data residency, and whether data is stored in transit. SyncMatters is ISO 27001 certified.

Testing and go-live checklist

Test in a Business Central sandbox and a HubSpot test or sandbox account before touching production.

Test scenarios:

• New company in HubSpot reaches the trigger stage → one BC customer is created, with all required fields filled
• Existing BC customer is matched, not duplicated
• Contact added to a synced company → linked correctly to the BC customer
• Closed Won deal with several line items → sales order with correct items, quantities, prices and discounts
• Deal in a foreign currency → correct currency code in BC
• Field edited in both systems at once → the agreed system wins
• Posted invoice and payment in BC → visible on the HubSpot record
• Blocked or credit-limit customer → flagged in HubSpot
• Product with no BC item → order fails with a clear error, not silently
• Deleted or merged records → handled as designed

Go-live:

• Freeze large imports and bulk edits in both systems during the historical sync
• Run the historical sync and reconcile record counts
• Switch on live sync and spot-check the first 20–50 deals
• Confirm who receives error alerts and how fast they respond
• Brief sales and finance on what now happens automatically, and what they must stop doing manually

Reports and dashboards to build once data is connected

The payoff of the integration is reporting that neither system can produce alone.

Cost and total cost of ownership

The license or subscription is rarely the biggest cost. The bigger costs are setup time, cleanup after sync errors, and the hours someone spends maintaining the integration every month.

A quick way to estimate your cost of not integrating: count the won deals finance re-enters each month, multiply by the minutes per order, and add the time spent fixing mismatched customer records. For most teams processing more than a few dozen orders a month, that figure exceeds the subscription cost of a managed integration.

10 common mistakes to avoid

1. Syncing every lead to BC. Create BC customers at a defined deal stage, not for every form fill.
2. No single source of truth per field. Two-way sync on every field guarantees overwrites.
3. Skipping cleanup. The integration spreads duplicates to both systems within hours.
4. No matching key. Without a stored BC customer number, records get matched by name and duplicated.
5. Letting reps create products in HubSpot. Quotes with SKUs that don't exist in BC fail to become orders.
6. Ignoring BC-required fields. Posting groups, payment terms and dimensions need defaults, or orders won't post.
7. Using your admin's personal BC login. Use a dedicated integration user with least-privilege permissions.
8. Launching without error ownership. Silent failures are worse than no integration.
9. Going live everywhere at once. Start with customers and products, then add orders and invoices.
10. Forgetting change management. If finance keeps re-entering orders "just in case", you get duplicate orders.

How SyncMatters delivers HubSpot–Business Central integrations

SyncMatters runs HubSpot–Business Central integrations on its own iPaaS (integration platform as a service), and its engineers design, build and maintain each one. You don't buy a connector and configure it; you get a working, monitored integration built around your process. SyncMatters is a Leading-tier HubSpot Technology Partner, is ISO 27001 certified, and its platform connects 45+ CRMs, ERPs and sales and marketing tools.

What you get:

• Two-way sync of companies, contacts, products, deals and orders, plus invoice data back into HubSpot
• Custom field mappings, sync rules and source-of-truth logic for each object
• Custom CRM cards that show BC data, such as open invoices or order status, inside HubSpot
• Ongoing monitoring, error resolution and updates after launch

The process takes five steps:

1. Kickoff and design. Align teams and design the integration around your requirements.
2. Weekly meetings. Review status, answer questions and set goals for the next week.
3. Phased execution. Move through discovery, design, setup and configuration.
4. Testing and validation. Run extensive testing, including user acceptance testing, before go-live.
5. Launch and support. Monitor the sync, resolve errors and keep it current.

Pricing. Integration plans are monthly subscriptions based on processing volume:

Scope and support can be adjusted to your project. See integration pricing or request a free estimate.

Moving to HubSpot from another CRM while keeping Business Central

Many HubSpot–Business Central projects start with a CRM switch, for example from Dynamics 365 Sales, Salesforce, Pipedrive or Zoho. In that case, migration and integration should be planned together.

1. Migrate CRM history to HubSpot first. Bring contacts, companies, deals, activities and notes across, and carry over any existing BC customer numbers as a property.
2. Clean and match during migration, so HubSpot starts with one record per BC customer.
3. Switch on the integration once HubSpot is the system of record for sales, and retire the old CRM-to-BC connection.

SyncMatters handles both parts: MigrateMyCRM moves data between 50+ CRMs, and SyncMatters integrations connect HubSpot to Business Central afterward. One team owning both avoids the classic gap where migrated records don't match the integration's keys.

How to choose the right Business Central integration

Answer these five questions. If you answer "yes" to two or more, a basic connector or no-code tool will likely cost you more in cleanup than it saves.

• Do you need more than customers and contacts to sync, such as items, orders or invoices?
• Must data flow in both directions with clear rules about which system wins?
• Do you use custom fields, multiple BC companies, or non-default posting groups and dimensions?
• Would a silent sync failure affect orders, billing or commissions?
• Is there nobody in-house who owns integrations as part of their job?

For BC partners and resellers: a managed HubSpot integration lets you offer CRM connectivity to your BC clients without building and supporting it yourself. SyncMatters works with partners on these projects.

Glossary

FAQ

Does HubSpot integrate with Microsoft Dynamics 365 Business Central? Yes. HubSpot offers a native Business Central app in its marketplace that focuses on syncing customer data. For orders, items, invoices or custom objects, companies use a BC extension, a no-code tool, or a managed iPaaS such as SyncMatters.

Can HubSpot deals create sales orders in Business Central? Yes, with a connector or managed integration. A common setup creates a BC customer and sales order when a deal reaches Closed Won, using deal line items mapped to BC item numbers.

Can I see Business Central invoices in HubSpot? Yes. Posted invoices and payment status can sync from BC into HubSpot as a custom object, timeline events or a custom CRM card. This flow is one-way because posted documents are read-only in BC.

Is Zapier good enough for a HubSpot Business Central integration? For simple one-way triggers, yes. For two-way sync of customers, products and orders, Zapier lacks conflict rules and central error handling, so duplicates and silent failures are common.

How much does a HubSpot Business Central integration cost? The native app is included with HubSpot. No-code tools charge per task, and packaged connectors charge a license plus setup. SyncMatters managed integrations start at $300/month.

How long does it take to integrate HubSpot with Business Central? A basic customer sync can run in a day. A full two-way integration with orders, invoices and custom fields typically takes weeks, including discovery, mapping, testing and user acceptance.

Does the integration work with Business Central on-premises? It depends on the solution. Many connectors support BC online only, so confirm on-premises support with the vendor before you commit.

Which Business Central plan do I need for HubSpot's native app? HubSpot's app requires Business Central Essentials, Premium or Team Members, and it works with all HubSpot plans.

Does a HubSpot Business Central integration sync in real time? It depends on the method. Change-based sync using webhooks can run in near real time; many integrations sync orders in near real time and invoices or items on a schedule.

Can I sync custom fields and custom objects? Most connectors support custom field mapping. Custom objects on either side usually need a configurable connector or a managed integration.

Can I connect several Business Central companies to one HubSpot account? Yes, but each BC company is a separate data set, so you need rules that route each HubSpot record to the right company, for example by business unit or region.

Can HubSpot tickets connect to Business Central? Yes, with a custom integration. Common setups show purchase and service history on tickets, or create BC service documents from HubSpot tickets.

Do I need a developer to integrate HubSpot and Business Central? Not for the native app or a managed integration. Custom API builds and complex no-code flows usually need technical skills to build and maintain.

What are the Business Central API limits? Business Central online allows 6,000 web service requests per user in a 5-minute sliding window, with 5 processed concurrently and 95 queued. Exceeding them returns HTTP 429.

What happens to the integration when Business Central is updated? BC ships two major releases a year. Integrations built on standard APIs are usually unaffected, but every release should be tested in a sandbox first.

Connect HubSpot and Business Central without the maintenance

Tell us which objects you need to sync and how your sales-to-invoice process works. We'll get back to you with a tailored estimate.

Get a free integration estimate

Sources

• HubSpot Marketplace: Microsoft Business Central app
• Microsoft AppSource: HubSpot for Microsoft Business Central
• Microsoft Learn: Business Central integration overview
• Microsoft Learn: Business Central service scalability
• Microsoft Learn: Operational limits for Business Central online
• n8n: HubSpot and Business Central API integration
• SyncMatters integration pricing