What we do
Tools
Industries
Department
How we workLet's talk →
Home/HubSpot/HubSpot NetSuite Integration
HubSpot + NetSuite

The HubSpot NetSuite Integration: What HubSpot's Own Sync Covers, and What It Leaves to You

Older articles say HubSpot has no NetSuite connector. It has one now, on every HubSpot plan, installed from the App Marketplace. It pairs contacts, companies, deals, products, orders, invoices and tickets with their NetSuite records. What it doesn't do is decide your business rules for you, like which subsidiary owns a deal or when a deal becomes a sales order.

What the native sync pairs up

Each pair can run one way or both ways. Choosing the direction per pair is the most important setup decision you'll make.

HubSpot record NetSuite record Decide before you switch it on
Contacts Contacts and individuals Which system creates people. If both can, duplicates follow.
Companies Companies The matching key. Names drift between systems; an ID stored on both sides doesn't.
Deals Opportunities This is an opportunity in NetSuite, not a sales order. Decide if finance wants one, and at which stage.
Orders Sales orders Where orders are born. Most companies create them in NetSuite and let HubSpot show them.
Products Inventory, assembly, kit, non-inventory and service items Keep NetSuite as the item master and sync one way, or prices get edited in two places.
Invoices Invoices Usually NetSuite to HubSpot only, so reps can see what's been billed and paid.
Tickets and activities Support cases, and calls, events and tasks Only worth syncing if someone in NetSuite actually works cases there.

Setting it up: the NetSuite side

A NetSuite administrator does these steps, and someone with Super Admin or App Marketplace permissions does the HubSpot side. HubSpot's own setup article has the full detail.

  1. 1

    Turn on the features the sync needs

    Setup Company Enable Features

    Enable SuiteAnalytics Workbook, SOAP and REST web services, token-based authentication and server SuiteScript.

  2. 2

    Install the HubSpot Sync Bundle

    Customization SuiteBundler Search & Install Bundles

    Search for the HubSpot bundle and install it. It can take a few minutes to finish.

  3. 3

    Give the connecting user the HubSpot Sync role

    Assign the role to whichever NetSuite user HubSpot will connect as. A dedicated integration user makes it obvious in audit trails which changes came from the sync.

  4. 4

    Create an access token

    Setup Users/Roles Access Tokens New

    Copy the account ID, token ID and token secret into HubSpot when it asks for them.

  5. 5

    Set up each sync in HubSpot

    Connected Apps NetSuite CRM syncs

    Pick the record pairs, the direction for each, and the field mappings. Default mappings work on every plan.

    Watch for: custom field mappings. They need a HubSpot Data Hub subscription, so check that before you promise finance a custom field.

Where HubSpot's NetSuite sync needs help

None of these are bugs. They're decisions specific to your business that a general sync can't make.

The subsidiary is a label, not a route

How you'll know: HubSpot records carry a NetSuite Subsidiary property, but deals for your newer subsidiary still end up under the wrong one, or get keyed in by hand.

Fix: Decide what sets the subsidiary (the company, the rep's region, the product line) and have the order created under it, with that subsidiary's tax setup and price book.

A closed deal never becomes a sales order

How you'll know: The deal shows up in NetSuite as an opportunity, and finance still creates the order from the deal notes.

Fix: Create the NetSuite sales order when the deal reaches the stage you choose, with its line items, and link it back to the deal so reps can see fulfillment and invoices.

Negotiated prices get lost

How you'll know: The order goes in at list price and someone fixes each line afterwards.

Fix: Carry the deal's line-item prices and discounts onto the order, and send anything outside your discount rules to approval first.

One customer, two companies

How you'll know: A customer that existed in NetSuite before the sync now appears twice, once from each side.

Fix: Match existing companies and customers once, store each side's ID on the other, then turn the sync on.

A distributor whose acquisition broke the handoff

Distributor · HubSpot for sales, NetSuite OneWorld for fulfillment

Before

The connector the company ran handled deals for its original subsidiary well.

After an acquisition added a second subsidiary, every deal for those customers was keyed into NetSuite by hand, because nothing decided which subsidiary owned the customer.

After

n-frames built a trigger on the HubSpot deal stage that reads the deal's subsidiary field and creates the NetSuite sales order under the right subsidiary, with its tax nexus and price book, as soon as the deal closes.

The existing connector kept handling everything else. Only the missing route was built.

Let's talk

Deals closing in HubSpot and still retyped in NetSuite?

n-frames builds the pieces HubSpot's NetSuite sync doesn't decide for you: subsidiary routing, sales orders created at the right deal stage with negotiated prices, and approvals before an order exists. The native sync keeps doing the rest.

Turn closed deals into NetSuite orders →

Questions people ask

Is there an official HubSpot integration for NetSuite?

Yes. HubSpot's own NetSuite integration is installed from the HubSpot App Marketplace and available on every HubSpot plan. It syncs contacts, companies, deals, products, orders, invoices, tickets and activities with their NetSuite records. Third-party connectors, such as Celigo's HubSpot-NetSuite template, still exist for teams that want more control.

Can a HubSpot deal automatically create a NetSuite sales order?

Not by default. The native sync pairs deals with NetSuite opportunities, and HubSpot orders with sales orders. Creating a sales order the moment a deal closes, with the right items and prices, is a step you add, through a connector's template or a custom build on both APIs.

Does a NetSuite connector handle multiple subsidiaries?

HubSpot's integration stores the NetSuite subsidiary on each synced record. Choosing which subsidiary a new deal belongs to, and applying that subsidiary's tax and price book, depends on your own OneWorld setup and usually needs custom logic on top.

Do we need Data Hub for the HubSpot NetSuite integration?

Not for the integration itself, which works on every plan with default mappings. You need Data Hub to map custom fields, which most NetSuite accounts have plenty of.

Is Zapier enough to connect HubSpot and NetSuite?

For a narrow job, like posting to Slack when a big deal closes, a tool like Zapier can work. For creating sales orders with line items, subsidiaries and tax, it's the wrong tool. Use the native sync, a connector, or code against NetSuite's API.

Who builds the custom part when the native sync falls short?

We do, at n-frames: subsidiary routing, deal-to-order creation, approval steps and the matching of records that existed before the sync. We build on HubSpot's API and NetSuite's, alongside the native sync, not instead of it.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.