Coming Soon: NetSuite Custom Object Sync to HubSpot

Improving the connector is welcome. Read the example list closely, though: two of the four are things HubSpot already has native objects for, subscriptions and tickets. This is where these projects go awry. People know their own system, so the request becomes "we have repair tickets over there, they work completely differently, and we need it called exactly that every time," when renaming or extending HubSpot's tickets might have done the job. These systems are complex enough that, in most cases, there is no such thing as a standard integration. The usual story: someone sets up the sync quickly because HubSpot made it look easy, then asks whether they can add one more thing, and the answer is no, you cannot use this integration anymore and it has to be rebuilt.

Zach Hussion has seen the same thing from the other side. Most people working in HubSpot do not have the experience to build this the right way, and a smart person who knows how to move data back and forth is not the same as someone who can make two systems work for both the systems and the people. He has a client right now whose homegrown integration has been causing problems across the organization for months. And the real issue is not the data move, it is governance: the moment someone changes picklist options in NetSuite, the sync breaks. Changes on one side need an approval step that tells the HubSpot owner before it happens.

The bigger picture is that updates like this are stepping stones for Breeze. You can already ask Breeze to go get things from NetSuite with the NetSuite connector for Breeze Assistant, no integration setup required, because getting people who know NetSuite, HubSpot and your business into one room is hard.

Who should act: teams running NetSuite and HubSpot together. Before mapping custom records, check whether a native HubSpot object already fits, and decide who governs changes on both sides.