In short
  • HubSpot's NetSuite integration is built by HubSpot and available on all HubSpot plans.
  • It can sync contacts, companies, deals, orders, invoices, products, tickets and activities, each one way or both ways.
  • Deals map to NetSuite opportunities. HubSpot orders map to NetSuite sales orders. A closed deal doesn't become a sales order on its own unless you set up that step.
  • Custom field mappings need a Data Hub subscription.
  • The gaps are approvals, bundles, subsidiaries, renewals and anything your finance team checks by eye.

The hand-off that eats an afternoon

A rep marks a deal closed won in HubSpot. Finance needs a sales order in NetSuite. Somewhere between the two, a person opens both screens and retypes the line items, the billing contact and the terms.

Then the invoice goes out, and the rep can't see whether it was paid without asking.

HubSpot's own integration closes much of that gap. Knowing exactly what it maps saves weeks of guessing.

What HubSpot's integration handles

HubSpot publishes the NetSuite integration itself. Its knowledge base says it is available on all HubSpot products and plans. Installing it takes a HubSpot super admin and a NetSuite administrator, and it can connect to a NetSuite sandbox as well as production.

According to HubSpot, these records can sync:

  • Contacts and companies, to NetSuite contacts, individuals and companies.
  • Deals, to NetSuite opportunities.
  • Orders, to NetSuite sales orders, with tax codes on line items mapped automatically.
  • Invoices, to NetSuite invoices.
  • Products, to several NetSuite item types, including inventory, kit, assembly and service items.
  • Tickets to support cases, and activities to calls, events and tasks.

Each one can be set to sync one way or both ways, or turned off. The integration also adds a NetSuite Subsidiary property to the records it creates, so you can see which subsidiary each one belongs to.

For a team with one subsidiary, a clean product list and simple terms, that may be enough.

Where it stops

The integration moves records. It doesn't know your rules. These are the places teams usually find that out:

  • Deal to sales order. A deal maps to an opportunity, not a sales order. Decide how a closed deal becomes an order, and who checks it first.
  • Your own fields. HubSpot says custom field mappings need a Data Hub subscription. Even syncing NetSuite's status field means creating a matching property in HubSpot first.
  • Approvals. If finance reviews discounts, credit or terms before an order is released, check where that step lives once records sync on their own.
  • Bundles and pricing. Kits, tiered pricing and one-off discounts can look different on each side. Check how a real quote comes through, line by line.
  • Several subsidiaries. The subsidiary property helps you compare. Check whether it also routes a new customer to the right subsidiary, currency and tax setup.
  • Renewals and changes. An amended order, a mid-term upgrade or a credit memo is where two systems most often drift apart.
  • Duplicates. A company entered twice in HubSpot can become two customers in NetSuite. Decide which system creates customers.

Your three options

Use HubSpot's integration as it comes. It is free to install, maintained by HubSpot and covers the common records. Start here and run it in a sandbox against real deals before deciding anything else.

Use a third-party connector or integration platform. Several companies sell HubSpot and NetSuite connectors, and general integration platforms let an admin build flows visually. These suit teams that need more control over mapping or timing and have someone to maintain the flows.

Build a custom connection for the rules that are yours. This suits companies whose quote-to-cash process has real judgment in it: approval paths, complex pricing, multi-subsidiary routing. Our page on slow quotes shows where those delays usually start.

Most teams end up with the built-in sync for everyday records and something narrower on top for the parts that need a decision.

What a custom connection usually adds

  • A closed deal that creates a draft sales order, held for finance review, with the reason for any discount attached.
  • Invoice and payment status shown on the deal, so reps stop asking finance.
  • New customers routed to the right subsidiary and currency from rules you set once.
  • Renewals and amendments handled as changes to an existing order, not new records.
  • A short daily list of records that didn't match, written for the person who fixes them.

Each one should replace a step someone does by hand today. If nobody is doing it by hand, it probably doesn't need building.

Questions to settle before you switch it on

An hour with sales ops and finance in the same room saves a month of cleanup. Bring these:

  1. Which system creates a new customer, and what happens when the other one finds a near match?
  2. When does a deal become an order: on close, on signature, or after finance approves it?
  3. Who can change an order once it exists, and in which system?
  4. Which products and prices does HubSpot need, and which belong only in NetSuite?
  5. Which subsidiary, currency and tax setup does each new customer get, and who decides?
  6. What should a rep see about invoices and payments, and what should stay with finance?
  7. Who reads the list of records that failed to sync, and how often?

Write the answers down. They become the rules any option has to follow, whether that is HubSpot's integration, a connector or a custom build. They also make a fair test: run ten real deals through the sandbox and check each answer held.

Who owns the access

Your HubSpot super admin installs the app. Your NetSuite administrator installs HubSpot's bundle and creates the role it uses. Anything custom should run under access your company creates and can switch off, not under a developer's own account.

HubSpot changed how private connections to your own account are created in late 2026. Our guide to when an integration needs the vendor's approval covers what that means.

What most guides miss

Pick one place where customers are created. If both systems can create them, you will have duplicates within a month.

Test with your messiest deals. The deal with three discounts and a split invoice tells you more than ten tidy ones.

Ask finance what they check by eye. Those checks are the real requirements. They rarely appear on a mapping sheet.

How we do it

We start with a free intro call and a look at how a deal becomes an invoice today. Then we work alongside your HubSpot and NetSuite admins, keep the built-in sync where it fits, and build only the piece it leaves behind. More on our HubSpot and NetSuite pages.

Sources

  1. HubSpot Knowledge Base: Use HubSpot's integration with NetSuite
  2. HubSpot Knowledge Base: Sync the Status field between HubSpot and NetSuite
  3. HubSpot App Marketplace: NetSuite