HubSpot SAP Business One integration: what to sync, and which route fits

Does HubSpot have an SAP Business One integration?

No. HubSpot builds its own data sync apps for NetSuite and Business Central, but not for SAP Business One. HubSpot’s SAP page points to partner apps in its marketplace and to integration platforms.

Search the marketplace for “SAP Business One” and you find two kinds of result: apps that connect to Business One, and HubSpot partners who build connections. Their vendors make and support these apps.

Every route below reaches Business One through the Service Layer, Business One’s REST interface, or directly through its database. For the general questions behind any ERP connection, such as which system owns which field, read the ERP guide. This guide covers what is particular to Business One.

SAP Business One CRM: is it enough, or do you need HubSpot?

SAP Business One comes with its own CRM module: business partners, contact persons, activities, sales opportunities with stages and a forecast, and campaigns. For some teams that is enough.

What to sync between SAP Business One and HubSpot

Start from the business partner. In Business One, one business partner record holds the company, its contact persons, addresses, payment terms, credit limit and account balance. In HubSpot, the same information lives on a company and its contacts.

Sync totals before documents. Open orders, account balance and the date of the last invoice on the company answer most sales questions. Single invoices as HubSpot records only pay off when someone has a question that needs them.

Where SAP Business One and HubSpot don’t fit: eight points to settle first

These eight points come up in almost every Business One connection. Settle each one with your partner before anything syncs.

• The business partner is a company and its people at once. HubSpot splits them into a company and contacts. A connection must create both, and associate them, or contacts end up without a company.
• Contact persons have no unique key. Their ID in Business One is the name, unique only within one business partner, and the email address is optional. Contacts without an email can’t be matched in HubSpot.
• Leads live in both systems. Business One has business partners of type Lead, HubSpot has leads and the lifecycle stage. Decide where a prospect is created and when it becomes a customer in Business One, usually with the first order.
• One item, many prices. An item has a price on every price list, and business partners can have special prices. A HubSpot product has one price per currency. Price books close part of that gap, not all of it.
• A quotation becomes an order becomes an invoice. Business One keeps each document as its own record, linked in a chain. In HubSpot that chain belongs on one deal.
• Stock changes often. Before Feature Package 2602 there was no event for a stock change, so connections polled Business One on a schedule. With thousands of items, batch updates of 100 records at a time get slow.
• Several company databases. Groups often run one Business One company per country. Few connectors bring several into one HubSpot account, so check this first.
• Business One on your own servers. The Service Layer must be reachable from the connector, through the partner’s cloud, a VPN or an agent on site.

What changed in 2026: webhooks in Business One, price books in HubSpot

Two changes in 2026 make Business One connections simpler than most vendor pages still describe.

Business One reports changes itself

Since SAP Business One 10.0 Feature Package 2602, the Service Layer supports webhooks. Business One sends a notification to an HTTPS address when a business partner, item or document is created, updated or deleted. The change can come from the desktop client, the Web Client or any interface. Feature Package 2608 adds your own fields to the notification.

• Webhooks are off by default for each company database. Your partner installs the Webhook Messenger service and switches them on.
• The receiving address must use HTTPS.
• A company database allows 16 subscriptions by default. Your partner can raise the limit.
• Business One logs each notification and retries failed ones.

With webhooks, changes reach HubSpot within seconds instead of on the next scheduled run, and nobody has to poll thousands of items to find the few that changed. You need Business One 10.0 FP 2602 or later.

HubSpot has price books

Since June 2026, HubSpot has price books: named lists of products with their own prices, one currency each. Price books map well to Business One’s price lists. A deal is assigned a price book, and quotes on that deal use its prices.

• Price books need Revenue Hub Enterprise.
• Each price book holds one currency. Business One price lists in EUR and CHF become two price books.
• A price book is assigned when a deal is created, by rules on deal properties, or by hand. Changing the company later doesn’t reassign it.
• Workflows can’t use price books. The workflow action “Add line item to deal” uses the product library price, not the price book.
• Through the API, products can only be added to a price book or repriced while the price book is inactive. A nightly price update from Business One has to switch the price book off and on again.

Special prices for single business partners don’t fit price books. Show them to sales on the company, or let Business One price the order.

The routes: partner app, integration platform or your own connection

Choose the route by what sales needs from Business One, how often it changes, and who will look after the connection once it runs.

Every route involves your Business One partner. The partner gives the connection a user, opens the network path and often charges for the time.

How to set up the HubSpot side

Prepare HubSpot before any route writes to it. These five steps are the same for every route.

1. Step 01

   Make the customer number the key

   Go to Settings > Properties, choose Company properties and create a single-line text property “SAP customer number” in its own group. Under Rules, turn on Require unique values. Decide this when you create the property; switching it on later fails as soon as two companies share a value.

   

2. Step 02

   Show the SAP data on the company

   Create the other properties from the table above, then open a company and click Customize. Add a property card “SAP Business One” to the left sidebar with these properties. Leave “Let users add more properties” off, so the card stays the same for everyone.

   

   

3. Step 03

   Put the document numbers on the deal

   Add deal properties for the quotation number, the sales order number and the order status, and a second card on the deal record. The deal stays one record for the whole sale; the connection fills in the numbers as Business One creates the documents.

   

4. Step 04

   Match products on the item code

   Import or sync items as HubSpot products with the item code as SKU. Then create one price book per Business One price list and currency if you have Revenue Hub Enterprise, and assignment rules that pick the right one for each deal.
5. Step 05

   Hand won deals over with a checkbox

   Create a deal property “Send to SAP Business One” and a deal workflow that starts when it is ticked. Its action hands the deal to the connection, for example with Send a webhook (Data Hub Professional or Enterprise). A checkbox lets sales decide when the order is ready; a stage change alone fires on every won deal, including test and mistaken ones.

   

What your SAP Business One partner has to do

Bring this list to your partner before you pick a route. Each point costs time on their side.

• Access. The Service Layer reachable for the connection: in the partner’s cloud, through a VPN, or with an agent on your servers.
• A user for the connection. Its own Business One user with only the rights it needs. Ask whether that user needs a licence of its own in your contract.
• The version. Which Business One version runs today, and whether an update to FP 2602 or later for webhooks is due anyway.
• Webhooks. The Webhook Messenger service installed and webhooks switched on for your company database.
• A field for the HubSpot ID. A user-defined field on the business partner and on documents that holds the HubSpot record ID, so both sides can find each other.
• A test company. A copy of your company database, so tests never touch the live one.

What about SAP S/4HANA?

For SAP S/4HANA and SAP ECC, HubSpot names custom APIs, OData and integration platforms. The Business One apps above don’t cover them. The questions stay the same: which system owns which field, what the key is, and how documents land on the deal. S/4HANA connections usually run through SAP Integration Suite or another integration platform, and need SAP’s own experts on the project.

SAP Business One in Germany, Austria and Switzerland

• Partner-run systems. Business One is sold and hosted by SAP partners. Many run on the partner’s servers, some still on site. Every connection starts with the partner, not with SAP.
• Localisation. The German, Austrian and Swiss versions differ in tax, document and accounting settings. Field names in Business One also appear in German, as in the screenshots above, so agree the field list in one language with your partner.
• Accounting stays separate. In Germany, bookkeeping often goes on to DATEV through the tax adviser. HubSpot takes open items and balances from Business One itself.
• Several currencies. Swiss companies often sell in CHF and EUR. HubSpot needs each currency set up in the account, and one price book per currency.
• Data protection. A connector or platform that moves customer data is a processor. Check where it processes data and sign a data processing agreement. Your data protection officer decides what is needed.

How we connect HubSpot and SAP Business One

We start with what sales should see from Business One, then pick the route together with your Business One partner.

1. Step 01

   Agree the list with sales

   Which Business One values sales needs on the company and the deal, and which decisions they change. Usually fewer than the first list.
2. Step 02

   Fix the key and the owners

   The business partner code as the key, one owner per field, and where leads and contact persons are created.
3. Step 03

   Pick the route with your partner

   Partner app, integration platform or own connection, depending on access, version, webhooks and who looks after it.
4. Step 04

   Test on copies

   A Business One test company and a HubSpot test account, with bulk changes and a renamed field, then the first sync with error alerts from day one.

Frequently asked questions