Connect HubSpot to NetSuite

Sales closes in HubSpot, finance fulfills and bills in NetSuite, and the handoff is a rep pasting deal details into a NetSuite form, or a nightly job that cannot handle a deal with a new company. Deals stack up at month-end and revenue recognition slips.

• A closed-won deal becomes a NetSuite sales order the same day, with the company and contacts read straight from the deal's associations
• Customers are matched, not duplicated, on an external ID stored on both sides, and a new company is created from the HubSpot company record
• Deals above a threshold pause for controller approval before the order posts, so a large or unusual order is checked
• Order number, invoice, and payment status flow back to the deal, so reps stop asking finance. Every order is an ordered run log

The deal-to-order flow most teams turn on first.

Closed-won HubSpot deal to a NetSuite customer and sales order, with a value gate

Triggered on the deal stage change, using the deal's associations to resolve the customer.

1. 1Trigger: HubSpot Deal stage changed to closedwon, passing the deal ID and amount.
2. 2Read associations: Get associations on the deal returns the primary company and every associated contact with its label.
3. 3Gate: if amount is 25,000 or more, send an approval to the controller with the company name and line items. On reject, log a note on the deal and stop.
4. 4Customer: NetSuite Upsert record on Customer, keyed on externalId = hs_company_id, from the mapping below, with the primary contact's details.
5. 5Order: NetSuite Create record on SalesOrder, keyed on externalId = hs_deal_id, with a line per HubSpot line item matched to a NetSuite item by SKU.
6. 6Write back: write the order number to Deal.erp_order_number and post the order link to the deal owner.
7. 7Ongoing: a second flow listens for NetSuite Invoice and CustomerPayment changes and updates a billing-status property on the deal.

The starting map for the deal and company to NetSuite Customer and Sales Order.

• Deals and companies. Closed-won deals become sales orders. Associated companies become customers. Deal amendments update the open order. (HubSpot to NetSuite)
• Billing status. Invoice created, payment received, and item shipped events update a billing-status property and the amount on the deal. (NetSuite to HubSpot)
• Account financials. Credit hold, payment terms, and balance sync onto the HubSpot company so reps see risk before they quote a renewal. (NetSuite to HubSpot)
• Products and pricing. New items and price changes keep the HubSpot product library and the NetSuite item list aligned, with one source of truth. (Either direction)

The same controls apply to this sync as to every other Neblex workload.

• Ordered run log. Every order is an event log with the deal, the association read, the customer and item resolution, and the sales order. Replay without re-posting.
• Approval and holds. Large deals pause for controller approval. Orders with an unmapped SKU hold in a review queue.
• Scoped access. HubSpot uses a private app token with deal, company, and product scopes. NetSuite uses a role limited to sales orders, customers, and items.
• Environments. Build against a HubSpot test account and a NetSuite sandbox, then promote the same flow to production.