NetSuite + HubSpot integration: getting order data into marketing
Most companies connect HubSpot to NetSuite for one of two reasons: sales wants won deals to become NetSuite orders without retyping, or marketing wants purchase history in HubSpot to segment and email customers. The two goals need different data flowing in different directions.
- Updated
- October 5, 2026
- Written by
- Nitya Hoyos
- Covers
- Approach, cost, mapping
- Questions
- 3 answered below
(01)The situation
HubSpot is built around contacts, the people; NetSuite is built around customers, which are usually companies. A NetSuite customer can be a company with several contacts, or an individual. Before syncing anything, decide whether a NetSuite customer matches a HubSpot company or a HubSpot contact, and how a HubSpot contact with no company is handled. Getting this wrong is the most common reason HubSpot fills up with duplicate companies or NetSuite fills up with one customer per email address.
For marketing, the valuable data is what customers bought: last order date, lifetime revenue, product categories, open invoices. This flows one way, from NetSuite to HubSpot company or contact properties, and is easy to keep correct because HubSpot never writes it back. It can run nightly. Most of the value of the integration often sits here, and it is the cheapest part to build.
For sales, deals become sales orders. That needs HubSpot products and line items to match NetSuite items, which in practice means NetSuite owns the item list and pushes it to the HubSpot product library. A deal moved to closed-won then creates the NetSuite sales order with the deal ID as external ID. As with Salesforce, the order belongs to NetSuite after that; HubSpot gets status updates, not edits.
(02)What it costs
Cost and timeline by approach
Connector
$3,000–$9,000
33–73 hours · 2–3 weeks
Middleware
$6,500–$18,500
71–149 hours · 3–5 weeks
Custom code
$15,000–$41,000
157–327 hours · 6–11 weeks
For a two-way NetSuite–CRM (Salesforce, HubSpot) integration moving customers, sales orders, invoices & payments, at medium volume with hourly sync and some existing NetSuite customization. Hours are priced at $95–$125 an hour and include discovery and 15% for testing and cutover. Connector and middleware figures leave out license fees, which are paid to the vendor. These are estimates from the published method, not a quote.
(03)The options
Which approach fits
| Approach | Best for | Trade-off |
|---|---|---|
| Marketplace app or integration app | Standard company, contact and deal syncs with properties HubSpot already has. | Subscription cost; limited control over matching rules. |
| Middleware | HubSpot is one of several systems connected to NetSuite. | Rules live in the middleware’s mapping screens. |
| Custom (HubSpot API + NetSuite SuiteQL/RESTlets) | Custom purchase-history properties, unusual matching rules, or a nightly rollup of order data. | You own monitoring and HubSpot API rate limits. |
(04)Field mapping
Mapping decisions that matter
| Source | NetSuite | Note |
|---|---|---|
| Company (or contact) record ID | Customer: external ID | Decide company vs contact once; store the ID on both sides. |
| Deal (closed won) | Sales order | Deal ID as external ID makes a retried sync safe. |
| Deal line item → product | Item | NetSuite owns items; HubSpot’s product library is a copy. |
| Custom property: last order date | Max(trandate) of sales orders | One-way, nightly, from a SuiteQL query. |
| Custom property: lifetime revenue | Sum of invoice amounts | One currency, stated in the property label. |
(05)Where it goes wrong
The mistakes that cost the most
- 01HubSpot merges duplicate contacts and companies; the merged-away record ID disappears, so the integration must look up the surviving record instead of failing.
- 02Syncing every HubSpot contact into NetSuite turns newsletter sign-ups into customers. Only create NetSuite customers from won deals or real orders.
- 03Pushing order data to contact properties when NetSuite customers are companies gives every contact at a company the same revenue, which inflates reports that sum contacts.
- 04HubSpot API rate limits differ by subscription tier, so a large first backfill should be batched and resumable.
(06)Before you build
When not to do this
If marketing only needs a list of customers and their last order date, a scheduled export from a NetSuite saved search imported into HubSpot may be enough for months. Build the integration when the import becomes a weekly chore or when deals must become orders automatically.
(07)Questions
Can HubSpot connect to NetSuite?
Yes, through apps in HubSpot’s marketplace, through middleware such as Celigo, or with a custom integration on the HubSpot API and NetSuite’s RESTlets, REST web services and SuiteQL.
Should a NetSuite customer map to a HubSpot company or contact?
For B2B businesses, usually a company, with NetSuite contacts mapped to HubSpot contacts. For businesses that sell to individuals, a contact. Pick one rule and apply it everywhere, including to records created in the past.
How do I get NetSuite purchase history into HubSpot?
Run a SuiteQL query or saved search in NetSuite that rolls up order and invoice data per customer, and write the results to custom properties on the matching HubSpot records on a schedule. It is one-way, so it cannot corrupt NetSuite data.
Free checklist