Connect HubSpot and NetSuite so your reps can see what customers actually buy
HubSpot's own NetSuite connector copies customers, orders, invoices and items between the two systems. We help you decide what should sync, test it on a NetSuite test account first, and fill the gaps the connector leaves.
Free, 30 minutes, and you'll leave with at least one clear next step.
- Hub
- Any HubSpot hub
- Plan needed
- All plans
- Status
- Generally available
Custom field mappings need Data Hub
What does the HubSpot NetSuite integration do?
Companies on NetSuite tend to hit the same wall. Accounting can see every order and invoice, and sales can't. A rep about to call a customer has to email someone to ask what that account bought last quarter, or whether the last invoice got paid.
HubSpot makes its own NetSuite connector, and it comes with every HubSpot product and plan. Once it's on, records copy between the two systems by themselves. A sales order in NetSuite shows up as an order in HubSpot, tied to the right customer, on the screen your reps already use.
For each type of record, you choose whether data moves one way or both ways. That choice matters more than anything else in the setup.
Which records can sync between HubSpot and NetSuite?
- HubSpot contacts and NetSuite contacts or individuals
- HubSpot companies and NetSuite companies
- HubSpot deals and NetSuite opportunities
- HubSpot invoices and NetSuite invoices
- HubSpot orders and NetSuite sales orders, with tax codes on line items mapped for you
- HubSpot products and NetSuite assembly, inventory, kit, non-inventory and service items
- HubSpot tickets and NetSuite support cases
- HubSpot activities and NetSuite calls, events and tasks
Is HubSpot's own connector enough for you?
The built-in connector is often enough when
- You want reps to see order and invoice history on the company record
- Your item list maps cleanly to HubSpot products
- You mostly use NetSuite's standard fields, or you have Data Hub for your custom ones
- One person on your team can own NetSuite settings and permissions
Plan for extra work when
- You rely on custom NetSuite records the connector doesn't map
- Prices come from a matrix by customer, region or volume
- Reps need stock by location, not one total
- You want order history turned into totals, such as 12-month revenue per account
What has to be ready on the NetSuite side?
This part needs your NetSuite admin, and it's where most projects stall. Your admin turns on a handful of NetSuite features: SuiteAnalytics Workbook, SOAP and REST web services, token-based authentication and server SuiteScript. Then they install the HubSpot Sync Bundle, give a user the HubSpot Sync role and create an access token. On the HubSpot side, the person connecting it needs Super Admin or App Marketplace permissions.
The connector works with live NetSuite accounts and with sandboxes, which are test copies of NetSuite. We always connect the sandbox first, so you can see what the sync does to test records that look like yours before it touches your books.
We agree on every sync with your NetSuite admin before we switch it on
A NetSuite connection touches your books, so the person who runs NetSuite has a say in every step.
Stage 1: Look at both systems as they are
We look at your NetSuite records and your HubSpot account side by side, and follow a few recent orders through both.
We pull a sample of customers, items and sales orders from NetSuite and find the same customers in HubSpot. We check how many match, how many are duplicates and which fields your team actually fills in.
You get A short list of matching problems and duplicate records to fix before anything syncs.
Stage 2: Pick the owner and direction for each record
For each record type, we agree which system owns it and whether it moves one way or both ways.
Your NetSuite admin and your sales lead go through customers, contacts, items, orders, invoices and support cases together. For each one, they agree which system wins when the two disagree. Most companies keep NetSuite in charge of anything that affects what gets delivered or what gets billed.
You get A written ownership list, like the one below this section.
Stage 3: Get NetSuite ready and clean up matches
Your admin turns on the required NetSuite features and creates the access token. We fix the duplicates that would break matching.
We give your admin a checklist for the NetSuite features, the HubSpot Sync Bundle, the sync role and the token. Meanwhile we merge duplicate companies in HubSpot, so one NetSuite customer doesn't land as three HubSpot companies.
You get A NetSuite account ready to connect, and a cleaner HubSpot to connect it to.
Stage 4: Connect the sandbox and test with copies of your records
We connect a NetSuite sandbox and run copies of your customers, orders and items through the sync.
We turn on one object at a time and check the results with your team. Does a new NetSuite customer land on the right HubSpot company? Do order lines carry the right products and tax codes? We adjust the mapping until accounting signs off.
You get A tested field mapping your NetSuite admin has approved.
Stage 5: Switch on production and train each team
We connect production, watch the first syncs closely and show each team what changed in their day.
We connect production using the mapping you approved and watch the first runs for errors. Reps learn where order history now shows up, and accounting learns what HubSpot can and can't change. We also name who owns the connection from here.
You get A live connection, a trained team and a named owner.
Which records NetSuite owns and which HubSpot owns
A typical split for a company on NetSuite. NetSuite keeps anything that changes what gets delivered, what it costs or what gets billed. HubSpot keeps the work that comes before the order. A few records move between them, each in one direction.
HubSpot owns
- New leads and prospect contacts
- Companies before their first order
- Deals and quotes in progress
- Marketing emails, forms and website visits
- Sales tasks, calls and meetings
- Customer service tickets
Shared, synced one way
- Won deal sent to NetSuite as an opportunity CRM to ERP
- New contact details from HubSpot CRM to ERP
- Customer record and ID, once created ERP to CRM
- Sales orders and invoices ERP to CRM
- Items for HubSpot products ERP to CRM
NetSuite owns
- Customer records once they're set up to order
- Items, assemblies and kits
- Price levels and customer pricing
- Sales orders and fulfillment or delivery
- Invoices and payments
- Credit limits and terms
What changes for a rep before a customer meeting?
Without the connection, a rep preparing for a meeting with a big account has to ask accounting for last year's orders. With it, the customer's HubSpot record shows every NetSuite sales order and invoice. The rep walks in knowing what the customer stopped buying and whether anything is overdue.
Marketing can use the same data. Build a list of customers who bought a product or service before but haven't ordered in a while, send them a reminder email and give reps a task to call the biggest accounts. For many companies, the biggest win is the handoff. A won deal shows up in NetSuite without anyone typing it twice.
What the connector won't do on its own
The connector copies records as they are. Totals like "last order date" or "12-month revenue" take extra work, often workflows and Data Hub custom code. Custom NetSuite records, pricing matrices and stock by location often need a third-party connector or a custom sync.
Reading purchase order PDFs into deal line items or predicting when an account is due to buy again is custom AI workflow work. We build it on top of the NetSuite connection, and the results land in HubSpot fields your team already uses.
Push Analytics completed the task in half the time compared to our previous vendor …
Companies we've connected HubSpot to other systems for
NetSuite integration questions
Does the HubSpot NetSuite integration cost extra?
HubSpot lists its NetSuite integration as available on all products and plans. The one exception is custom field mappings, which need a Data Hub subscription. Your NetSuite account also needs certain features turned on, which your NetSuite admin can check.
What does our NetSuite admin need to do?
Turn on a few NetSuite features, install HubSpot's Sync Bundle, give a user the HubSpot Sync role and create an access token. We give your admin a checklist and stay on hand while they work through it.
Can the sync go both ways?
Yes. You set one-way or two-way sync for each object. We usually recommend one-way for anything financial, such as invoices and pricing, so a change in HubSpot can't overwrite your books.
Can we test the integration before it touches our live NetSuite account?
Yes. The connector works with NetSuite sandboxes, which are test copies of your account. We connect the sandbox first, test with sample records, and only connect your live account after your NetSuite admin signs off.
Will NetSuite item data show up as HubSpot products?
Yes. NetSuite assembly, inventory, kit, non-inventory and service items can sync to HubSpot products, so reps can add them to deals and quotes. Complex pricing, such as customer price levels, usually stays in NetSuite.
What if we already have duplicate customers in HubSpot or NetSuite?
Fix them first. A sync copies whatever it finds, so one messy customer list quickly becomes two. We match and merge duplicates before connecting, and agree how new records will be matched from then on.
Related
Find out what should sync with NetSuite
Bring your NetSuite admin to a 30-minute call. We'll go through what you want reps to see and point out the records most likely to cause trouble.