SAP Business One × HubSpot
How SAP Business One customers, items, prices, quotations, sales orders, invoices and payments can reach HubSpot, and how won HubSpot deals can become Business One sales orders, using the Service Layer OData API.
Does SAP Business One integrate with HubSpot?
Business One runs inventory, orders and accounting for growing companies. HubSpot runs marketing, sales and service. The integration gives reps ERP facts and turns won deals into Business One orders without re-keying.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. The Service Layer is documented publicly. The integration signs in as a licensed Business One user set up by the client or its SAP partner.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
The Service Layer makes Business One a strong fit for a two-way HubSpot integration, with HubSpot owning the pipeline and Business One owning orders and accounting.
Campaign Creators assessment
SAP Business One exposes its business objects through the Service Layer, an OData REST API that supports create, read, update and delete on business partners, items and sales documents, plus batch requests. The DI API remains available for server-side add-ons. HubSpot does not publish its own Business One app, so this is a custom build on the Service Layer. Two things set the pace: the client's server must be reachable over a secure path (most Business One systems run on-premise or with a hosting partner), and the integration needs a Business One user license and agreed rules for which system creates customers.
Ratings are CC judgments from SAP's public documentation. The client's version, database, hosting and custom fields are confirmed during discovery.
One API for every sales document
Quotations, orders, invoices and payments share one document model in the Service Layer (header, DocumentLines, CardCode), so read and write logic is built once and reused.
Leads, customers and custom fields
Business One stores leads and customers in the same BusinessPartners object, told apart by CardType. Many clients also add user-defined fields (U_ prefix). Both need clear rules before mapping.
Network path and license
The integration signs in as a Business One user, and the Service Layer must be reachable from the integration layer. The client's IT or hosting partner sets up both before the build.
Which SAP Business One APIs does the integration use?
Seven Business One surfaces matter to HubSpot. Four carry the integration, two enrich it, and one is a scope decision the client makes early.
BusinessPartners
Service Layer · BusinessPartnersCustomers, leads and vendors in one object, with addresses and contact employees.
- Key:
CardCode; name:CardName CardType: customer, supplier or lead (cLid)- Contact employees match HubSpot contacts
Items & price lists
Service Layer · ItemsThe item master with prices per price list. Feeds the HubSpot product library.
- Key:
ItemCode - Price per price list, matched to the customer's list
- Stock levels can be shown on request
Orders
Service Layer · OrdersSales orders. The main path for won HubSpot deals, and a read source for orders entered in Business One.
- Header:
CardCode,DocDueDate DocumentLines:ItemCode,Quantity,UnitPrice- Returns
DocEntryandDocumentStatus
Invoices & IncomingPayments
Service Layer · Invoices · IncomingPaymentsA/R invoices and the customer payments applied to them. Read into HubSpot for account and collections views.
- Invoice lines can reference the source order
- Payments show what is paid and what is open
- Read-only into HubSpot
Quotations
Service Layer · QuotationsSales quotations, for clients whose official quote is issued from Business One rather than from HubSpot.
- Same document model as orders
- Quote number and value on the deal
- Off by default; choose one quoting system
User-defined fields & tables
U_ fields · UDTs · UDOsClient-specific fields on standard objects, and custom tables and objects, all reachable through the Service Layer.
- Fields use the
U_prefix - Discovered from the service
$metadata - A UDF can hold the HubSpot record ID
Lead and customer creation
Master data rulesBusiness One can hold leads as business partners. The client chooses whether HubSpot pushes prospects as B1 leads, or only creates the B1 customer when a deal is won.
- Leads in B1 help when quotes are issued there
- Creating at close keeps B1 to paying customers
- Decide before mapping; it sets the match rules
How does the SAP Business One HubSpot integration work?
HubSpot never calls Business One directly. A CC-built integration layer keeps one Service Layer session, reads changes on a schedule, matches them to HubSpot records, and writes won deals back as sales orders after validation.
Each record has one owner
HubSpot owns prospects, contacts, deals and pre-sale quotes. Business One owns customer accounting data, items, prices, orders, invoices and payments.
Business One prices the order
Line items use B1 item codes and the customer's price list. After the order is created, the B1 document total is written back to the deal.
Write once, then confirm
Each HubSpot deal creates at most one B1 order. The DocNum is stored on the deal, and failures go to a queue a person can replay.
What does SAP Business One HubSpot integration setup involve?
Each phase ends on a gate the client signs off before the next begins. Master data goes live first, then order write-back, then invoices and payments.
Ownership & rules
Confirm which system owns each record, whether leads live in Business One, and which company databases, branches and currencies are in scope.
Access & network
The client's IT or hosting partner opens a secure path to the Service Layer and creates a licensed integration user with the right authorizations.
Mapping & match rules
Agree how business partners match HubSpot companies, how contact employees match contacts, and which user-defined fields come across. Read $metadata to confirm field names.
HubSpot data model
Create the properties, product library settings, order and invoice pipelines, association labels and property groups in a HubSpot sandbox.
Build & test
Build master data sync, then order write-back with validation, then invoice and payment reads. Test against a copy of the company database, never the live one.
Backfill
Load customers, items and an agreed history of orders and invoices, then compute rollups once.
Parallel run & launch
Run order write-back alongside the current process for two weeks, then switch on.
What does the SAP Business One HubSpot integration sync?
Field names come from SAP's Service Layer and SDK documentation. User-defined fields and exact field names in the client's version are confirmed from $metadata during discovery.
| Business One field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| BusinessPartners · customers and leads | ||||
| CardCode | b1_card_code | Company | ↔ Both | Primary match key. Written to HubSpot when B1 creates it. |
| CardName | name | Company | ↔ Both | B1 name wins once the customer exists in B1. |
| CardType | b1_card_type | Company | B1 → HS | Customer or lead. Suppliers are not synced. |
| Bill-to and ship-to addresses | address, city, zip, country | Company | B1 → HS | Default bill-to address. Confirm address fields in discovery. |
| Contact employees (name, email, phone) | firstname, lastname, email, phone | Contact | ↔ Both | Match on email. HubSpot keeps contacts it creates. |
| Price list | b1_price_list | Company | B1 → HS | Customer's price list. Confirm field in discovery. |
| Payment terms | b1_payment_terms | Company | B1 → HS | Confirm field in discovery. |
| Sales employee | hubspot_owner_id | Company | B1 → HS | Mapped through a sales employee to HubSpot user table. |
| HubSpot record ID | U_ field (user-defined) | Business partner | HS → B1 | Optional UDF that stores the HubSpot company ID. |
| Items & prices | ||||
| ItemCode | hs_sku | Product | B1 → HS | Primary match key. Unique. |
| Item name | name | Product | B1 → HS | Item description. |
| Item group | b1_item_group | Product | B1 → HS | For reporting and segments. |
| Price (default price list) | price | Product | B1 → HS | From the item's price list entries. |
| Stock on hand | b1_in_stock | Product | B1 → HS | Optional. Confirm warehouse rules in discovery. |
| Deals → sales orders | ||||
| CardCode | b1_card_code (company) | Deal | HS → B1 | Taken from the associated company. |
| DocDueDate | b1_delivery_date | Deal | HS → B1 | Requested delivery date captured in HubSpot. |
| Customer reference | b1_customer_po | Deal | HS → B1 | Customer PO number. Confirm field in discovery. |
| DocumentLines: ItemCode, Quantity, UnitPrice | hs_sku, quantity, price | Line item | HS → B1 | One B1 line per HubSpot line item. |
| DocNum | b1_order_number | Deal | B1 → HS | Written back after B1 accepts the order. |
| Document total and currency | amount, deal_currency_code | Deal | B1 → HS | B1 total replaces the estimate. |
| Orders, invoices & payments | ||||
| Orders (header) | Order record | Order | B1 → HS | All B1 orders for synced customers, including those entered in B1. |
| DocumentStatus | b1_document_status | Order | B1 → HS | Open or closed. |
| Invoices (header and total) | Invoice record | Invoice | B1 → HS | Read-only copy of B1 A/R invoices. |
| Invoice totals | b1_invoiced_ytd | Company | B1 → HS | Rolled up in the integration layer. |
| IncomingPayments applied | b1_open_balance | Company | B1 → HS | Invoiced less paid. Confirm calculation in discovery. |
| Last order date | b1_last_order_date | Company | B1 → HS | Drives reorder and lapse workflows. |
How are authentication and API limits handled?
Values SAP does not publish are marked for confirmation. The client's hosting decides the network setup.
| Topic | Business One | HubSpot |
|---|---|---|
| Access model | The integration signs in as a dedicated Business One user with the authorizations it needs. That user needs a suitable license; confirm with the client. | Self-serve in the client portal. Custom objects need an Enterprise hub; orders and invoices are standard objects. |
| Interfaces | Service Layer: OData REST over HTTPS, with batch requests and access to user-defined fields and objects. DI API for server-side add-ons. | REST APIs: CRM objects, associations, products, line items, orders, invoices, webhooks. |
| Authentication | Login with company database, user name and password returns a session cookie. OpenID Connect through an identity provider in recent releases. Confirm in discovery. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Network | Usually on-premise or with a hosting partner. Needs an allowlisted HTTPS path or VPN, and a trusted certificate on the Service Layer. | Public HTTPS endpoints. |
| Change detection | No outbound webhooks. The integration reads changes on a schedule by update date and time. Confirm field names in discovery. | Webhooks on deal stage change trigger order write-back. |
| Rate limits | Not published. Throughput depends on the client's server. Confirm with the client's IT or hosting partner. | Per-10-second burst and daily limits by subscription tier. |
| Company databases | A session works in one company database. Each company in scope needs its own session. | One HubSpot portal can hold all companies, tagged by source. |
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
Most Business One servers sit behind a firewall. Make the secure path and a test company database client-owned dependencies in the SOW, with IT or the hosting partner named.
Business One can hold leads, customers and vendors in one object. Agree whether HubSpot creates B1 leads, B1 customers at close, or neither, before mapping starts.
The integration signs in as a Business One user. Confirm the license type with the client and their SAP partner and include it in the client's costs.
Price lists, special prices and discounts are calculated in Business One. HubSpot shows the customer's list price, and the B1 document total is written back after the order is created.
Clients often add fields with the U_ prefix, and some are mandatory on orders. Read $metadata early and include required UDFs in the order mapping.
Each company database needs its own session, and documents can carry a branch and a foreign currency. Scope which companies and currencies are in, and tag records by source.
Opportunities in HubSpot
Reps stop re-keying orders. The deal carries the B1 order number and total, and errors land in a queue someone owns.
Invoiced revenue, payments and open balance sit on the company record, so sales and service see the whole relationship.
Customers who stop ordering enter HubSpot lists and tasks for the account owner, based on last order date from Business One.
Overdue balances trigger HubSpot tasks or sequences for the right owner, with the invoice details attached.
HubSpot products match B1 item codes and prices, so quotes and line items use the same data the ERP does.
Item groups and order history feed HubSpot segments for cross-sell and replenishment campaigns.
Who owns each step from quote to cash.
HubSpot runs the pipeline up to the signed deal. Business One runs fulfillment and accounting from the sales order on. The integration hands over at close and reports back at every step after.
- Quote in HubSpot with B1 items and price-list prices, or in Business One when the client issues official quotes there.
- Deal won: the integration creates the B1 customer if needed, then the sales order, and writes the order number back.
- Business One delivers, invoices and records payments. Order status, invoices and payments flow to HubSpot.
- Invoiced revenue, open balance and last order date roll up to the company for renewals and reorders.
Which HubSpot properties does the integration create?
All custom properties use the b1_ prefix in an SAP Business One property group. Rollups are calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| b1_card_code | B1 Card Code | Company | Single-line text | CardCode; unique |
| b1_card_type | B1 Partner Type | Company | Dropdown | CardType: customer or lead |
| b1_price_list | B1 Price List | Company | Dropdown | Customer's price list |
| b1_payment_terms | B1 Payment Terms | Company | Dropdown | Customer's payment terms |
| b1_invoiced_ytd | Invoiced YTD | Company | Number (currency) | Sum of A/R invoice totals |
| b1_open_balance | Open Balance | Company | Number (currency) | Invoiced less payments applied |
| b1_last_order_date | Last B1 Order Date | Company | Date picker | Latest sales order date |
| b1_item_group | B1 Item Group | Product | Dropdown | Item group |
| b1_in_stock | B1 In Stock | Product | Number | Stock on hand; optional |
| b1_customer_po | Customer PO | Deal | Single-line text | Customer reference on the order |
| b1_order_number | B1 Sales Order | Deal | Single-line text | DocNum returned on create |
| b1_document_status | B1 Order Status | Order | Dropdown | DocumentStatus: open or closed |
Interactive scope builder
Choose the modules 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
Sources & verification
Based on public documentation. Each item marked for confirmation is verified against the client's Business One system during discovery.
- SAP: Working with SAP Business One Service Layer
- SAP Learning: Performing basic operations using the Service Layer API
- SAP Learning: Logging in with OAuth authentication on the Service Layer
- SAP Business One SDK: BoCardTypes (customer, supplier, lead)
- SAP Business One SDK: Documents.CardCode
- HubSpot: Create and manage orders
- HubSpot developers: Invoices API
SAP Business One HubSpot integration FAQ
Does SAP Business One integrate with HubSpot?
Yes, through a custom integration. HubSpot does not publish its own Business One app, so Campaign Creators builds on the Service Layer, the OData REST API SAP documents for Business One. It reads and writes business partners, items and sales documents, and supports batch requests.
What data syncs between SAP Business One and HubSpot?
Business One customers, leads and contact employees sync to HubSpot companies and contacts, and items with price-list prices sync to HubSpot products. Won HubSpot deals create Business One sales orders. Order status, invoices, payments, open balances and last order dates are written back to HubSpot.
Does it work with an on-premise or partner-hosted Business One?
Yes. Most Business One systems run on-premise or with a hosting partner, so the client's IT or hosting partner opens a secure path to the Service Layer and creates a licensed Business One user for the integration before the build starts.
What does setting up the SAP Business One HubSpot integration involve?
Seven phases, each closed by a client sign-off: ownership and rules, access and network, mapping and match rules, the HubSpot data model, build and test against a test company database, backfill, and a two-week parallel run before order write-back is switched on.
How long does the integration take and what does it cost?
Timeline and cost depend on the Business One version and hosting, the company databases and branches in scope, user-defined fields 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.
.png?width=1920&height=553&name=cc-logo-color%20(2024).png)