Key takeaways
- HubSpot's native NetSuite integration is available on all HubSpot plans; custom field mappings need a Data Hub subscription, and deal-based workflows that create sales orders need Professional or Enterprise.
- It maps companies, contacts, deals to opportunities, products to items, orders to sales orders, invoices, tickets to support cases and activities, with one-way or two-way sync.
- Deal-to-sales-order is where most projects fail: SKUs must match active NetSuite items, currencies must match and legacy tax accounts need tax codes.
- Decide which system owns customers, prices and invoice status before mapping a single field.
- A custom HubSpot-NetSuite integration with the typical scope takes about 330 to 660 hours, roughly $11k to $52k at Eastern European rates.
A HubSpot NetSuite integration connects your CRM to your ERP through HubSpot’s own NetSuite app, a third-party sync app or iPaaS, or a custom build on both platforms’ APIs. Start with the native app if your records and deal-to-order process fit its mappings, and add custom work only where quotes, pricing, subsidiaries or invoice status need rules the app does not have.
We are integration engineers. We build syncs between CRMs, accounting systems and ERPs, so this guide focuses on what actually moves between HubSpot and NetSuite, what each option needs and where it breaks. Plan requirements and prices are as published by the vendors in November 2026; where a vendor publishes no price, we say “quote-based”. For NetSuite’s APIs, limits and authentication in general, see our NetSuite integration guide.
What syncs, and in which direction
Sales lives in HubSpot and fulfillment and billing live in NetSuite, so the integration has two jobs. It has to turn a won deal into a sales order without retyping, and it has to show sales what happened next: whether the order shipped, whether the invoice was paid, whether the customer is on credit hold.
HubSpot’s knowledge base lists the native mappings: contacts to NetSuite contacts and individuals, companies to companies, deals to opportunities, invoices to invoices, orders to sales orders, products to NetSuite items (assembly, inventory, kit, non-inventory and service types), tickets to support cases, and activities to calls, events and tasks. You choose one-way or two-way sync per object. Quotes and NetSuite estimates are not in that table.
Two-way is not always better. A sensible default for most B2B teams looks like this:
- Companies and contacts: two-way, but NetSuite owns billing address, terms, subsidiary and credit fields, and HubSpot owns marketing and ownership fields.
- Products: one-way from NetSuite. Items, prices and active status belong to the ERP.
- Deals and orders: one-way from HubSpot at the won stage, then status flows back as a HubSpot order.
- Invoices: one-way from NetSuite, read-only in HubSpot, so sales sees what finance sees without editing it.
- Tickets and activities: only if support or service teams actually work in NetSuite; otherwise leave them out.
Your options
HubSpot’s native NetSuite integration. Built and supported by HubSpot. Its knowledge base says it is available on all products and plans. Two limits matter. Custom field mappings require a Data Hub subscription, so if you need anything beyond the default fields, budget for it. And creating NetSuite sales orders from deal-based workflows requires a Professional or Enterprise subscription; on lower tiers, a user creates the order manually from the deal record. Setup on the NetSuite side needs an administrator: you enable REST and SOAP web services, token-based authentication and server SuiteScript, install the HubSpot Sync bundle, assign the HubSpot Sync role and create an access token. You can connect a NetSuite sandbox first, which you should.
One point to raise with HubSpot: the setup described in its knowledge base uses a NetSuite access token. Oracle’s documentation says no new integrations can use token-based authentication from NetSuite 2027.1, and support for existing ones ends in 2028.2, a date Oracle marks as tentative. Ask how the app will move to OAuth 2.0 and whether you will need to reconnect.
Third-party sync apps and iPaaS. HubSpot’s App Marketplace lists other NetSuite sync apps, and iPaaS products such as Celigo, Boomi and Workato have HubSpot and NetSuite connectors. Most are quote-based; Boomi publishes a Pay-As-You-Go plan at $99 per month plus usage. These fit when you already run an iPaaS for other flows or need mappings the native app does not offer, and someone on your side will own them.
Custom integration. A service between the HubSpot API and NetSuite REST web services or RESTlets. You get exactly the mapping you want, including quotes, custom objects and multi-subsidiary rules, and you own the maintenance.
| Option | Best for | What it covers | Pricing as published | Limits |
|---|---|---|---|---|
| HubSpot native NetSuite app | Standard sales-to-order flow | Contacts, companies, deals, products, orders, invoices, tickets, activities | Included in all HubSpot plans; Data Hub for custom field mappings | No quotes-to-estimates mapping; workflow orders need Pro or Enterprise |
| Third-party marketplace apps | Specific needs the native app lacks | Varies by vendor | Varies, often quote-based | Check support, auth method and roadmap |
| iPaaS (Celigo, Boomi, Workato) | Teams with several integrations | Configurable flows with connectors for both systems | Boomi Pay-As-You-Go $99/month plus usage; others quote-based | Annual contracts; you build and own the flows |
| Custom build | Quotes, custom objects, unusual rules | Exactly what you specify | Development hours (see below) | You own monitoring and upkeep |
How to choose between them
If your sales team sells standard items at list or deal-level prices, in one currency, through one subsidiary, the native app covers the core flow and costs nothing extra beyond any Data Hub subscription you need for custom fields. Install it against a NetSuite sandbox, push ten real won deals through, and see what comes out.
If you sell configured products, use NetSuite price levels or customer-specific pricing in quotes, or run several subsidiaries with different currencies, expect gaps. Those gaps are usually narrow: a quote flow, a pricing lookup, or a card that shows open invoices on the company record. A small custom service that fills only that gap, next to the native app, is often cheaper than replacing the whole sync.
If you already pay for an iPaaS and have someone who maintains its flows, building the HubSpot-NetSuite flows there keeps all integrations in one place with one error dashboard. That is a good reason in itself.
Where these integrations break
1. SKUs that do not match. HubSpot’s sales order creation needs each product to match an active NetSuite item, either through product sync or by entering the NetSuite item name or number in the product’s SKU field. Inactive items cannot be added to sales orders. Fix: sync products from NetSuite to HubSpot, make NetSuite the owner of items and prices, and stop reps from creating ad-hoc products.
2. Duplicate customers. HubSpot companies are created loosely, from forms, imports and email domains. NetSuite customers are created carefully, with terms, subsidiaries and tax settings. Two-way sync without matching rules floods NetSuite with duplicates. Fix: create NetSuite customers only at the won-deal stage, match on a stored NetSuite ID, and let NetSuite own billing fields.
3. Currency and subsidiaries. HubSpot requires the company currency to match the NetSuite base currency for sales order creation, and each order needs a subsidiary. Multi-entity businesses need rules for which subsidiary takes which deal. Fix: map subsidiary from a deal or company property and test every currency you sell in.
4. Tax codes. HubSpot’s documentation says legacy tax accounts need a tax code on every sales order line and that the order is not created if the form requires one and none is set; SuiteTax accounts should leave it empty. Fix: confirm which tax setup you run and set the code in the workflow or mapping.
5. Required fields on custom forms. If your NetSuite sales order form requires a field the integration does not send, the order fails. Fix: list every required field on the form you use and map each one, or use a dedicated integration form.
6. Invoice status sales cannot see. The value for sales is often not the order but what happens after: shipped, invoiced, paid, overdue. Fix: decide which invoice fields sync to HubSpot, how often, and whether reps need a balance or credit hold flag on the company.
7. Concurrency and silent failures. Your HubSpot sync shares NetSuite’s account concurrency limit with every other integration. Fix: watch the sync error log, assign an owner, and reconcile orders and invoices weekly.
These are the same ownership, ID mapping and reconciliation problems we describe in our guide to two-way QuickBooks sync design.
What a custom integration costs
Pick the flows you need; hours include design, QA and project management, and the typical scope is preselected.
The preselected scope, covering companies, contacts, products, won deals to sales orders and invoice status back to HubSpot with alerts and reconciliation, comes to about 330 to 660 hours. 2026 outsourcing rate surveys put Eastern Europe at about $35 to $80 per hour and North America at $80 to $180 or more. At Eastern European rates that is about $11,000 to $52,000; at US onshore rates of $80 to $160 it is about $26,000 to $105,000. Quotes, custom objects and multi-subsidiary rules add to it. If you only need one gap filled next to the native app, such as quotes or a payment status card, the scope is a fraction of that.
How to run the project
- Agree on owners. Sales and finance sign off on who owns customers, prices, orders and invoice status, field by field.
- Clean the data. Merge duplicate companies, fix SKUs and deactivate old items before the first sync, not after.
- Map deal to order. Line items, prices, tax codes, currency, subsidiary, required form fields.
- Pick the tool per flow. Native app for standard objects, custom or iPaaS for the gaps.
- Test in a NetSuite sandbox. Run real deals through, including discounts, multi-currency and credited invoices.
- Go live and reconcile. Compare orders and invoices between systems weekly until the numbers hold.
If NetSuite also sells online, the same customers and items will flow in from your store; see Shopify NetSuite integration and Stripe NetSuite integration for those flows.
From related work
We have not published a NetSuite case. The patterns below come from CRM and two-way accounting syncs we built on other systems.
For Fairway Divorce, we wrote Umbraco Forms workflows that send website leads to Salesforce and Mailchimp, with each form field mapped to the matching CRM field so leads arrive complete. Field mapping and required fields are the same discipline a HubSpot-NetSuite sync needs.
On the ERP side, our One Motion ERP work includes a two-way QuickBooks sync covering invoice sync, vendor mapping, tax logic, duplicates and automatic remapping of item IDs, run as background jobs. Our custom ERP system keeps each customer’s QuickBooks ID on the customer profile, the cross-reference pattern that prevents duplicate customers. And our SaaS ETL platform work covers scheduled transfers with each run logged and failed records counted separately.
Where OSKI fits
OSKI is a .NET and React engineering company with a team mostly in Ukraine. We build integrations, CRM systems and ERP systems, and we often build just the flow a native app does not cover. Send the estimator selection and your field map, and an engineer will reply with a written estimate and its assumptions.
- HubSpot ⇄ Companies and contacts to customers: matching, subsidiaries NetSuite
- NetSuite → Items and prices to products HubSpot
- HubSpot → Won deals to sales orders NetSuite
- HubSpot → Quotes to estimates: not in the native mapping table NetSuite
- NetSuite → Invoices, balances and payment status HubSpot
- HubSpot ⇄ Tickets to support cases, activities NetSuite
● Works natively● Partial or one-way● Needs custom work
Based on the object mappings in HubSpot's knowledge base, checked November 2026. Amber flows need ownership and field decisions; gray flows usually need custom work.
- Standard objects both ways
- Sales orders from deals
- Custom field mappings need Data Hub
- Workflow-created orders need Pro or Enterprise
- Prebuilt templates, configurable flows
- Pricing often quote-based
- Fits teams already on an iPaaS
- Someone must own the flows
- Quotes, custom objects, unusual rules
- Your own ID mapping and reconciliation
- No per-flow license
- You own upkeep
HubSpot plan requirements from HubSpot's knowledge base, November 2026.
- 01 Agree on owners
Customers, prices, orders, invoice status.
- 02 Clean the data
Duplicate companies, SKUs, inactive items.
- 03 Map deal to order
Line items, tax, currency, subsidiary.
- 04 Pick the tool
Native app, iPaaS or custom, per flow.
- 05 Test in sandbox
Connect NetSuite sandbox, run real deals.
- 06 Go live and reconcile
Compare orders and invoices weekly.
Estimate a custom HubSpot-NetSuite integration
Pick the flows you need. Hours include design, QA and project management. Change the rate band and team size to see cost and calendar time.
Sources
Based on the following official vendor and regulator materials:
- HubSpot Knowledge Base: Connect HubSpot and NetSuite
- HubSpot Knowledge Base: Create a NetSuite sales order in HubSpot
- Oracle NetSuite Help: Preparing for Token-based Authentication (TBA) End of Support
- Oracle NetSuite Help: Concurrency Governance Limits Based on Service Tiers and SuiteCloud Plus Licenses
- Boomi: Pricing and editions




