NetSuite–HubSpot integration

The brief

CNC Cabinetry had already identified the natural integration path between NetSuite and HubSpot, but the marketplace application did not surface all of the data the team relied on.

I built a custom integration so the business could define the data contract around its actual process rather than the limitations of a generic connector.

Why the marketplace app was not enough

Packaged integrations are valuable when their assumptions match the organization. They become limiting when important records, fields, relationships, or update rules fall outside the supported model.

Adding more automation around an incomplete sync would not solve that problem. The project required a clearer understanding of what HubSpot needed, where NetSuite remained authoritative, and how those values should move over time.

The approach

The custom middleware established an explicit boundary between the platforms:

• inventory the business data missing from the existing connector;
• define mappings and identifiers for the required records;
• normalize NetSuite values before writing to HubSpot;
• distinguish creation from update behavior;
• make repeated processing safe and predictable; and
• preserve useful error context when a record could not synchronize.

The integration focused on the full data set the operating team depended on instead of reproducing the smallest common denominator between the APIs.

Why custom was the maintainable choice

Custom does not automatically mean better. In this case, it was justified because the gap affected essential business context and could not be configured away.

By keeping the integration narrowly focused on the missing contract, the solution avoided turning into a replacement ERP or CRM. NetSuite and HubSpot retained their roles, while the middleware coordinated the information needed between them.

The takeaway

This project demonstrates how I evaluate build-versus-buy decisions for integrations. I prefer the simplest connector that satisfies the workflow, but I am comfortable building the missing layer when the packaged option cannot represent the business accurately.