NetSuite to HubSpot: Building a Reliable ERP–CRM Integration

Every business running NetSuite as its ERP and HubSpot as its CRM eventually asks the same question: why doesn't a closed deal automatically update inventory, and why doesn't a restock automatically notify the sales team? The honest answer is that nothing connects them out of the box — you have to build the bridge.

Where to put the logic

NetSuite's SuiteScript 2.x RESTlets are the right place for NetSuite-side logic — they run inside NetSuite's governance limits and can react to record changes with a saved search or a scheduled script. HubSpot's side is a custom app with webhook subscriptions on deal and contact changes. The mistake I see most often is putting business logic in the wrong system, then fighting each platform's constraints — API rate limits, governance units, batch size caps — trying to make it work.

The sync engine in between

Rather than a direct NetSuite → HubSpot call, I run a small Java sync service in between:

NetSuite RESTlets → Sync Daemon → Buffer (Postgres/Kafka) → HubSpot Webhook API

That buffer layer matters more than it looks. NetSuite governance limits mean you can't always process a webhook immediately, and HubSpot's API has its own rate limits on the other side. A buffer decouples the two systems' rate limits from each other, and gives you a retry point when either API has a bad five minutes — which, at scale, happens weekly.

Data mapping is the real work

The technical plumbing is maybe 30% of the effort. The rest is mapping: NetSuite's item categories don't map cleanly to HubSpot's deal pipelines, customer records split differently across the two systems, and someone has to decide what "source of truth" means for every overlapping field. I build a small mapping dashboard for this on every integration project — not because it's exciting, but because six months later someone always asks "why does this field say X in one system and Y in the other," and you need an answer that isn't "check the code."

What good looks like

A working NetSuite–HubSpot bridge should be boring: inventory changes show up in HubSpot within minutes, closed-won deals trigger the right NetSuite workflow, and when something does fail, there's a clear error log instead of silently dropped data. That reliability is the actual deliverable — the code is just how you get there.