Integration Products | Campaign Creators

SAP Business One HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 17, 2026, 2:41:22 PM
Integration Assessment
Integration Assessment · ERP

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.

Service Layer (OData REST)DI APIBusiness partnersMarketing documentsUser-defined fieldsOrder write-back
Platform ownerSAP
Integration typeCustom, built on the Service Layer
Primary directionBoth ways
FeasibilityBuildable, well suited
API accessOpen API
01 — Summary

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.

API access
Open APIOpen with conditionsGated API

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.

Scorecard
Data richnessHigh
API coverageStrong
Connectivity setupVaries
Build complexityModerate

Ratings are CC judgments from SAP's public documentation. The client's version, database, hosting and custom fields are confirmed during discovery.

Strength

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.

Plan for

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.

Gate

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.

02 — API modules

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.

Core

BusinessPartners

Service Layer · BusinessPartners

Customers, 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
Core

Items & price lists

Service Layer · Items

The 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
Core

Orders

Service Layer · Orders

Sales 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 DocEntry and DocumentStatus
Core

Invoices & IncomingPayments

Service Layer · Invoices · IncomingPayments

A/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
Enrichment

Quotations

Service Layer · Quotations

Sales 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
Enrichment

User-defined fields & tables

U_ fields · UDTs · UDOs

Client-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
Scope decision

Lead and customer creation

Master data rules

Business 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
03 — Framework

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.

SAP Business One
BusinessPartnerscustomers, leads, contacts
Itemsitem master and price lists
Orders & Quotationssales documents and lines
Invoices & IncomingPaymentsbilling and cash
CC integration layer
Secure connectionallowlisted path to the Service Layer
Session managerone signed-in session per company database
Change readerscheduled reads by update date
Order builderdeal → B1 order, price list rules
HubSpot writerbatch upserts, error replay
HubSpot
Companies & contactsB1 customers and contact employees
Productsitems with B1 codes and prices
Deals & line itemspipeline and order lines
Orders & invoicesB1 orders, invoices, payment status
Lists, workflows & reportsreorder, collections, account health
Business One → HubSpot (master data, documents, payments)HubSpot → Business One (won deals as sales orders; new customers or leads)
Principle

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.

Principle

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.

Principle

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.

04 — Process

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.

1

Ownership & rules

Confirm which system owns each record, whether leads live in Business One, and which company databases, branches and currencies are in scope.

Gate to next phaseSigned ownership matrix and scope
2

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.

Gate to next phaseTest sign-in and reads succeed against a test company database
3

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.

Gate to next phaseSigned mapping and match rules
4

HubSpot data model

Create the properties, product library settings, order and invoice pipelines, association labels and property groups in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

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.

Gate to next phaseTest orders created in B1 test company and visible in HubSpot
6

Backfill

Load customers, items and an agreed history of orders and invoices, then compute rollups once.

Gate to next phaseHubSpot totals reconcile to Business One reports within an agreed tolerance
7

Parallel run & launch

Run order write-back alongside the current process for two weeks, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

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 fieldHubSpot propertyObjectDirectionNotes
BusinessPartners · customers and leads
CardCodeb1_card_codeCompany↔ BothPrimary match key. Written to HubSpot when B1 creates it.
CardNamenameCompany↔ BothB1 name wins once the customer exists in B1.
CardTypeb1_card_typeCompanyB1 → HSCustomer or lead. Suppliers are not synced.
Bill-to and ship-to addressesaddress, city, zip, countryCompanyB1 → HSDefault bill-to address. Confirm address fields in discovery.
Contact employees (name, email, phone)firstname, lastname, email, phoneContact↔ BothMatch on email. HubSpot keeps contacts it creates.
Price listb1_price_listCompanyB1 → HSCustomer's price list. Confirm field in discovery.
Payment termsb1_payment_termsCompanyB1 → HSConfirm field in discovery.
Sales employeehubspot_owner_idCompanyB1 → HSMapped through a sales employee to HubSpot user table.
HubSpot record IDU_ field (user-defined)Business partnerHS → B1Optional UDF that stores the HubSpot company ID.
Items & prices
ItemCodehs_skuProductB1 → HSPrimary match key. Unique.
Item namenameProductB1 → HSItem description.
Item groupb1_item_groupProductB1 → HSFor reporting and segments.
Price (default price list)priceProductB1 → HSFrom the item's price list entries.
Stock on handb1_in_stockProductB1 → HSOptional. Confirm warehouse rules in discovery.
Deals → sales orders
CardCodeb1_card_code (company)DealHS → B1Taken from the associated company.
DocDueDateb1_delivery_dateDealHS → B1Requested delivery date captured in HubSpot.
Customer referenceb1_customer_poDealHS → B1Customer PO number. Confirm field in discovery.
DocumentLines: ItemCode, Quantity, UnitPricehs_sku, quantity, priceLine itemHS → B1One B1 line per HubSpot line item.
DocNumb1_order_numberDealB1 → HSWritten back after B1 accepts the order.
Document total and currencyamount, deal_currency_codeDealB1 → HSB1 total replaces the estimate.
Orders, invoices & payments
Orders (header)Order recordOrderB1 → HSAll B1 orders for synced customers, including those entered in B1.
DocumentStatusb1_document_statusOrderB1 → HSOpen or closed.
Invoices (header and total)Invoice recordInvoiceB1 → HSRead-only copy of B1 A/R invoices.
Invoice totalsb1_invoiced_ytdCompanyB1 → HSRolled up in the integration layer.
IncomingPayments appliedb1_open_balanceCompanyB1 → HSInvoiced less paid. Confirm calculation in discovery.
Last order dateb1_last_order_dateCompanyB1 → HSDrives reorder and lapse workflows.
06 — Auth & API

How are authentication and API limits handled?

Values SAP does not publish are marked for confirmation. The client's hosting decides the network setup.

TopicBusiness OneHubSpot
Access modelThe 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.
InterfacesService 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.
AuthenticationLogin 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.
NetworkUsually 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 detectionNo 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 limitsNot 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 databasesA session works in one company database. Each company in scope needs its own session.One HubSpot portal can hold all companies, tagged by source.
07 — Issues & opportunities

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

Network access to the serverHigh

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.

Who creates customers and leadsHigh

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.

Integration user licenseMedium

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.

Pricing lives in Business OneMedium

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.

User-defined fieldsMedium

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.

Multiple companies, branches and currenciesLow

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

Won deals become B1 ordersHigh value

Reps stop re-keying orders. The deal carries the B1 order number and total, and errors land in a queue someone owns.

Invoices and payments on the accountHigh value

Invoiced revenue, payments and open balance sit on the company record, so sales and service see the whole relationship.

Reorder and lapse alertsHigh value

Customers who stop ordering enter HubSpot lists and tasks for the account owner, based on last order date from Business One.

Collections follow-upMedium value

Overdue balances trigger HubSpot tasks or sequences for the right owner, with the invoice details attached.

Product library from Business OneMedium value

HubSpot products match B1 item codes and prices, so quotes and line items use the same data the ERP does.

Marketing on buying behaviorMedium value

Item groups and order history feed HubSpot segments for cross-sell and replenishment campaigns.

Quote-to-cash flow

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.

  1. Quote in HubSpot with B1 items and price-list prices, or in Business One when the client issues official quotes there.
  2. Deal won: the integration creates the B1 customer if needed, then the sales order, and writes the order number back.
  3. Business One delivers, invoices and records payments. Order status, invoices and payments flow to HubSpot.
  4. Invoiced revenue, open balance and last order date roll up to the company for renewals and reorders.
08 — Property schema

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 nameLabelObjectTypeSource / logic
b1_card_codeB1 Card CodeCompanySingle-line textCardCode; unique
b1_card_typeB1 Partner TypeCompanyDropdownCardType: customer or lead
b1_price_listB1 Price ListCompanyDropdownCustomer's price list
b1_payment_termsB1 Payment TermsCompanyDropdownCustomer's payment terms
b1_invoiced_ytdInvoiced YTDCompanyNumber (currency)Sum of A/R invoice totals
b1_open_balanceOpen BalanceCompanyNumber (currency)Invoiced less payments applied
b1_last_order_dateLast B1 Order DateCompanyDate pickerLatest sales order date
b1_item_groupB1 Item GroupProductDropdownItem group
b1_in_stockB1 In StockProductNumberStock on hand; optional
b1_customer_poCustomer PODealSingle-line textCustomer reference on the order
b1_order_numberB1 Sales OrderDealSingle-line textDocNum returned on create
b1_document_statusB1 Order StatusOrderDropdownDocumentStatus: open or closed
09 — Scope builder

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

0Fields
0Inbound
0Write-back
Business One × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

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.