Oracle NetSuite × HubSpot
How NetSuite customers, items, prices, sales orders, invoices and payments connect to HubSpot companies, deals, products and quotes, so sales sees the full quote-to-cash picture and finance keeps NetSuite as the book of record.
Does NetSuite integrate with HubSpot?
NetSuite is the ERP behind many growing companies: it holds customers, items, pricing, orders, invoices and payments. HubSpot holds the people, the pipeline and the conversations. Connecting the two closes the gap between a closed deal and cash collected.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. SuiteTalk REST is documented publicly. A NetSuite administrator creates the integration record, OAuth 2.0 credentials and role.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
NetSuite exposes its full record model through documented APIs, so HubSpot can carry every step from quote to cash without finance leaving NetSuite.
Campaign Creators assessment
NetSuite offers SuiteTalk REST web services (record service and SuiteQL queries), SOAP web services and RESTlets. HubSpot's own NetSuite app already syncs the standard records: contacts, companies, opportunities, items, sales orders, invoices, support cases and activities. The custom build starts there and adds what the app does not cover in a given account: custom records, subsidiary and currency rules, price levels, quote-to-order handoff and finance rollups on the HubSpot record.
Ratings are CC judgments from Oracle's and HubSpot's public documentation. Account-specific features (OneWorld, multi-currency, custom records, concurrency) are confirmed in discovery.
A documented API for every record
The REST record service reads and writes standard records, custom records and custom lists. SuiteQL returns joined, filtered result sets in one call, which keeps backfills and rollups efficient.
Subsidiaries, currencies and custom fields
In a OneWorld account each customer belongs to a subsidiary and transacts in set currencies. Every account also carries its own custom fields. Mapping rules are written per account, not copied from a template.
Access and concurrency come first
A NetSuite administrator creates the integration record, OAuth 2.0 credentials and a dedicated role, and allocates part of the account's concurrent request limit to the integration before the build starts.
Which NetSuite APIs does the integration use?
Seven surfaces matter for a HubSpot build. Four carry the integration, two support it, and one is a scope decision made with the client.
REST record service
/services/rest/record/v1Create, read, update and upsert NetSuite records over REST, including customers, contacts, items, estimates, sales orders, invoices and payments.
- Account-specific URL:
<accountID>.suitetalk.api.netsuite.com - Upsert by external ID keeps writes idempotent
metadata-catalogdescribes each record and its custom fields
SuiteQL query service
/services/rest/query/v1/suiteqlSQL-style queries across records in one request. Used for change detection, backfills and finance rollups.
POSTwithPrefer: transient- Paging with
limitandoffset - Up to 100,000 rows per query result
Custom records and fields
customrecord_ · custentity_ · custbody_Account-specific record types and fields. REST supports full CRUD on custom record instances, custom lists and some custom transactions.
- Referenced by script ID
- Record types are created in NetSuite, not through REST
- Map to HubSpot custom objects or properties
HubSpot's NetSuite app
HubSpot App MarketplaceHubSpot-built sync for standard records, configured one-way or two-way. The custom build extends it rather than replacing it.
- Contacts, companies, deals ↔ opportunities, items, orders, invoices, cases, activities
- Custom field mappings need Data Hub
- Adds a NetSuite Subsidiary property on synced records
RESTlets
Server SuiteScript endpointsCustom endpoints written in SuiteScript and deployed inside NetSuite. Used when one call must run NetSuite business logic, such as converting an estimate to a sales order.
- Runs logic close to the data
- Same OAuth 2.0 credentials as REST
- Shares the account concurrency limit
SOAP web services
SuiteTalk SOAPThe older SuiteTalk interface. New integrations use REST because Oracle directs new integrations to OAuth 2.0, which SOAP does not support.
- Kept only where an account already depends on it
- REST and SuiteQL cover the same records
- No new SOAP credentials created
Quote ownership
HubSpot quotes or NetSuite estimatesDecide where a quote is built. Most clients quote in HubSpot from NetSuite prices and send the accepted quote to NetSuite as a sales order. Some must keep estimates in NetSuite.
- One system builds quotes, the other receives them
- Price levels and discounts come from NetSuite
- Written into the SOW before mapping starts
How does the NetSuite HubSpot integration work?
HubSpot's NetSuite app handles the standard records. A CC-built integration layer sits beside it for everything the account needs beyond that, and both write to one HubSpot data model with clear ownership per record.
Each record has one owner
HubSpot owns contacts, deals and quotes. NetSuite owns customers' financial terms, items, prices, orders, invoices and payments. The other system reads them.
Extend the app, don't duplicate it
Standard records stay on HubSpot's NetSuite app. The custom layer handles only what the app does not, so two syncs never write the same field.
Finance data arrives as rollups
HubSpot gets open balance, last invoice and lifetime revenue on the company. Ledger detail and revenue schedules stay in NetSuite.
What does NetSuite HubSpot integration setup involve?
Each phase ends on a gate the client signs off before the next begins. Finance and sales operations both sign the ownership rules, because both teams depend on them.
Discovery & record inventory
List the NetSuite features in use (OneWorld, multi-currency, price levels, custom records), the HubSpot hubs and tiers, and the decision each team should make from HubSpot.
Access & governance
The NetSuite administrator creates the integration record, OAuth 2.0 credentials and a dedicated role in sandbox and production, and allocates concurrency to the integration.
Ownership & mapping rules
Agree which system owns each record and field, the match keys (NetSuite internal ID and external ID), and how subsidiaries and currencies route.
HubSpot data model
Configure HubSpot's NetSuite app for standard records, then create custom properties, custom objects for NetSuite custom records, and the deal pipeline stages that trigger orders.
Build the custom layer
Build change detection, ownership rules, upserts by external ID and the error replay queue. Test the won-deal-to-sales-order handoff end to end.
Backfill
Load customers, items, open orders and an agreed invoice history window, then compute finance rollups once.
Parallel run & launch
Run two weeks with order creation in review mode, compare daily, then switch on automatic sales order creation.
What does the NetSuite HubSpot integration sync?
NetSuite field names follow the REST record service and SuiteQL. Custom field IDs differ in every account and are read from the metadata catalog during discovery. Rows marked for the app are handled by HubSpot's NetSuite app; the rest by the custom layer.
| NetSuite field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers & contacts | ||||
| customer.companyName | name | Company | ↔ Both | HubSpot's app handles the base sync. NetSuite owns the name once a customer exists. |
| customer.id (internal ID) | ns_customer_id | Company | NS → HS | Primary match key. Unique. |
| customer.entityId | ns_customer_number | Company | NS → HS | Customer number shown to finance. |
| customer.subsidiary | ns_subsidiary | Company | NS → HS | Routes the record in OneWorld accounts. |
| customer.currency | ns_primary_currency | Company | NS → HS | Primary transaction currency. |
| customer.terms | ns_payment_terms | Company | NS → HS | Read-only in HubSpot. |
| customer.creditLimit | ns_credit_limit | Company | NS → HS | Read-only in HubSpot. |
| customer.salesRep | hubspot_owner_id | Company | ↔ Both | Matched on employee email. Confirm which system owns assignment. |
| contact.email, firstName, lastName | email, firstname, lastname | Contact | ↔ Both | HubSpot owns contact details. Associated to the company. |
| Items & pricing | ||||
| item.itemId | hs_sku | Product | NS → HS | Match key for products. |
| item.displayName, description | name, description | Product | NS → HS | NetSuite owns the catalog. |
| item pricing by price level | price, ns_price_level | Product | NS → HS | Base price on the product; price levels applied at quote time. Confirm sublist fields in discovery. |
| item type | ns_item_type | Product | NS → HS | Inventory, service, kit, assembly or non-inventory. |
| item.isInactive | ns_inactive | Product | NS → HS | Inactive items are hidden from quotes. |
| Deals, quotes & orders | ||||
| opportunity.title, projectedTotal | dealname, amount | Deal | ↔ Both | HubSpot owns the pipeline. Handled by HubSpot's app where opportunities are used. |
| opportunity.expectedCloseDate | closedate | Deal | ↔ Both | HubSpot owns the date. |
| estimate (from HubSpot quote) | Quote | Quote | HS → NS | Only if quotes must also exist in NetSuite. Scope decision. |
| salesOrder (from won deal) | Deal + line items | Order | HS → NS | Created on closed-won with NetSuite item IDs and price level. |
| salesOrder.tranId | ns_order_number | Order | NS → HS | Written back after creation. |
| salesOrder.status | ns_order_status | Order | NS → HS | Pending approval, pending fulfillment, billed, closed. |
| salesOrder line: item, quantity, rate, amount | Line items | Line item | ↔ Both | Created from the deal; NetSuite values returned after save. |
| department, class, location | ns_department, ns_class, ns_location | Order | ↔ Both | Set from deal properties when finance requires them. |
| Invoices & payments | ||||
| invoice.tranId | ns_invoice_number | Invoice | NS → HS | One HubSpot invoice per NetSuite invoice. |
| invoice.total, amountRemaining | ns_invoice_total, ns_amount_remaining | Invoice | NS → HS | In transaction currency. |
| invoice.dueDate, status | ns_due_date, ns_invoice_status | Invoice | NS → HS | Open, paid in full. |
| customerPayment applied to invoice | ns_last_payment_date | Company | NS → HS | Rolled up per customer in the integration layer. |
| sum of open invoices | ns_open_balance | Company | NS → HS | Computed with SuiteQL. |
| sum of invoices, trailing 12 months | ns_revenue_12m | Company | NS → HS | Computed with SuiteQL, in base currency. |
| Custom records | ||||
| customrecord_<scriptid> | Custom object | Custom object | NS → HS | One HubSpot custom object per NetSuite custom record type in scope. |
| custentity_ / custbody_ fields | ns_ properties | Company, Deal, Order | ↔ Both | Field list read from the metadata catalog in discovery. |
How are authentication and API limits handled?
NetSuite and HubSpot both publish their authentication and API rules. Values that depend on the client's NetSuite licence are confirmed in discovery.
| Topic | NetSuite | HubSpot |
|---|---|---|
| Interfaces | SuiteTalk REST web services (record service, SuiteQL), RESTlets, and SOAP web services. New work uses REST. | REST APIs: CRM objects, associations, products, line items, quotes, orders, invoices, custom objects. |
| Authentication | OAuth 2.0 through an integration record. Oracle directs all new integrations to OAuth 2.0; token-based authentication remains for existing ones. OAuth 2.0 does not apply to SOAP. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Integration identity | A dedicated NetSuite role with only the record permissions in scope. Credentials are created separately in sandbox and production. | A dedicated HubSpot integration with only the scopes in use. |
| Rate and concurrency limits | Concurrent request limit per account, shared by web services and RESTlets. Part of it can be allocated to one integration. Exact limit depends on the account's licence. Confirm with Oracle. | Per-10-second burst and daily limits by subscription tier. Batch endpoints for volume. |
| Query limits | SuiteQL returns up to 100,000 rows per query, paged with limit and offset. | Search API returns up to 10,000 results per query; the integration uses IDs and batch reads. |
| Change detection | SuiteQL on last-modified date, plus SuiteScript event scripts where near-real-time updates are needed. | Webhooks on deal stage and company changes trigger outbound writes. |
| Environments | Sandbox and production accounts. Tokens and credentials are not copied by a sandbox refresh. | HubSpot sandbox portal for build and testing (Enterprise). |
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
Custom fields and records are specific to each NetSuite account. Budget discovery time to read the metadata catalog and agree the field list before mapping.
If HubSpot's NetSuite app and the custom layer both map a field, they overwrite each other. The ownership table assigns every field to exactly one sync.
In OneWorld accounts, a customer and its transactions sit under a subsidiary with allowed currencies. Orders created from HubSpot must carry the right subsidiary and currency or NetSuite rejects them.
Every integration in the account draws on the same concurrent request limit. Agree an allocation with the NetSuite administrator and write in batches.
Accounts on older token-based credentials should plan the move. New credentials for this build use OAuth 2.0 from the start.
Revenue schedules and ledger postings remain in NetSuite. HubSpot shows billed and collected totals, not recognized revenue, unless finance asks for a specific rollup.
Opportunities in HubSpot
A closed-won deal creates the NetSuite sales order with the right items, prices, subsidiary and currency. No re-keying, and no orders lost between teams.
Reps quote in HubSpot from the NetSuite catalog and price levels, so every quote matches what finance will invoice.
Open balance, overdue invoices, credit limit and payment terms sit on the HubSpot company, so sales and service see account health before they call.
Overdue invoices and expiring terms trigger HubSpot tasks and sequences for the account owner.
NetSuite revenue rolled up to the company joins HubSpot attribution, so leaders see which campaigns produce billed revenue.
Account-specific NetSuite records, such as contracts or installed equipment, become HubSpot custom objects that sales and service can act on.
One flow, two systems, clear owners.
HubSpot runs the selling motion and NetSuite runs fulfilment and finance. The integration hands each record across at the moment ownership changes.
- HubSpot: deal and quote built from NetSuite items and price levels.
- Closed-won: the integration creates the NetSuite customer (if new) and the sales order.
- NetSuite: fulfilment, invoicing and payment, with status written back to the HubSpot order and invoice.
- HubSpot: open balance and revenue rollups on the company drive renewals and collections.
Which HubSpot properties does the integration create?
All custom properties use the ns_ prefix in a NetSuite property group. Standard records synced by HubSpot's NetSuite app keep that app's own properties; these extend them. Rollups are calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| ns_customer_id | NetSuite Customer ID | Company | Single-line text | Internal ID; unique |
| ns_customer_number | NetSuite Customer Number | Company | Single-line text | customer.entityId |
| ns_subsidiary | NetSuite Subsidiary (routing) | Company | Dropdown | customer.subsidiary |
| ns_primary_currency | Primary Currency | Company | Dropdown | customer.currency |
| ns_payment_terms | Payment Terms | Company | Dropdown | customer.terms |
| ns_credit_limit | Credit Limit | Company | Number (currency) | customer.creditLimit |
| ns_open_balance | Open Balance | Company | Number (currency) | Sum of open invoices (SuiteQL) |
| ns_revenue_12m | Revenue, Trailing 12 Months | Company | Number (currency) | Sum of invoices, base currency |
| ns_price_level | Price Level | Product | Dropdown | NetSuite price level used for quoting |
| ns_order_number | NetSuite Order Number | Order | Single-line text | salesOrder.tranId |
| ns_order_status | NetSuite Order Status | Order | Dropdown | salesOrder.status |
| ns_amount_remaining | Amount Remaining | Invoice | Number (currency) | invoice.amountRemaining |
Interactive scope builder
Choose the records 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 from Oracle and HubSpot. Account-specific features, custom fields and concurrency allocation are confirmed with the client's NetSuite administrator during discovery.
- HubSpot: Use HubSpot's integration with NetSuite
- Oracle NetSuite: REST web services URL schema and account-specific URLs
- Oracle NetSuite: Executing SuiteQL queries through REST web services
- Oracle NetSuite: CRUD operations on custom records, custom lists and custom transactions
- Oracle NetSuite: Token-based authentication and OAuth 2.0 guidance
- Oracle NetSuite: OAuth 2.0 client credentials flow
- Oracle NetSuite: Concurrency limits
NetSuite HubSpot integration FAQ
Does NetSuite integrate with HubSpot?
Yes. HubSpot’s NetSuite app syncs standard records: contacts, companies, deals and opportunities, items, sales orders, invoices, support cases and activities. Campaign Creators extends it with a custom integration layer for what the app does not cover, such as NetSuite custom records, OneWorld subsidiaries, multi-currency rules, price levels and finance rollups on the HubSpot company.
What data syncs between NetSuite and HubSpot?
Customers and contacts sync to HubSpot companies and contacts; items and price levels sync to HubSpot products; closed-won HubSpot deals create NetSuite sales orders; and NetSuite order status, invoices, payments, open balance and trailing 12-month revenue are written back to HubSpot.
Which system owns which data?
Each record has one owner. HubSpot owns contacts, deals and quotes. NetSuite owns customer financial terms, items, prices, sales orders, invoices and payments. The other system reads those records, so the two never overwrite each other.
What does setting up the NetSuite HubSpot integration involve?
Seven phases, each closed by a client sign-off: discovery and record inventory, access and governance (OAuth 2.0 credentials and a dedicated NetSuite role), ownership and field mapping, HubSpot data model, building the custom layer, historical backfill, and a two-week parallel run before automatic sales order creation is switched on.
How long does the integration take and what does it cost?
Timeline and cost depend on the records, custom fields and NetSuite features in scope (for example OneWorld, multi-currency and custom records). 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)