Salesforce CRM integration capabilities NetSuite ERP integration capabilities

Salesforce ↔ NetSuite Integration: Custom Object Sync Methods

Last updated: November 11, 2026

Oracle's own NetSuite Connector for Salesforce syncs the order-to-cash flow: accounts, items, closed-won opportunities to sales orders, then fulfillments, invoices and payments back. Its documentation doesn't say whether custom fields or records are supported. If your sync depends on Salesforce custom objects or NetSuite custom records, pick a tool that documents them: Breadwinner, Celigo, Make's custom record modules, or n8n's community node.

Five ways to sync Salesforce and NetSuite

Checked November 11, 2026, against each vendor's documentation.

Method What syncs Custom records Requirements Source
NetSuite Connector for Salesforce (Oracle) Subsidiaries, items ↔ products, customers ↔ accounts, contacts, closed-won opportunities → sales orders, then orders, fulfillments, invoices, payments, cash sales → Salesforce Not documented NetSuite OneWorld with at least one subsidiary; Salesforce API-only user and External Client App Oracle
Celigo integration app Accounts, contacts, items, opportunities → sales orders, order status, financials, fulfillments, exchange rates Yes (custom record flows) Celigo subscription; 30-day trial Celigo
Breadwinner Standard objects in both directions Yes, per vendor (Apex Generator) AppExchange managed package Breadwinner
Make Any record via NetSuite modules, SuiteQL, REST and SOAP calls Yes (create, update, get, search, delete a custom record) Make Enterprise plan; NetSuite token-based auth Make
n8n 150+ record types and SuiteQL through a verified community node, or the HTTP Request node Yes (community node) No built-in NetSuite node; OAuth 2.0 n8n community

Oracle, Celigo and Breadwinner don't publish prices. Make Enterprise is priced on request.

Oracle's connector syncs the order-to-cash flow

The NetSuite Connector for Salesforce is a NetSuite SuiteApp that runs on Oracle Integration Cloud, installed from the NetSuite side. When an opportunity is closed-won, it creates the NetSuite sales order, then sends the order, fulfillments, invoices, payments and cash sales back to Salesforce. Customers and accounts, and items and products, sync in both directions.

It needs a NetSuite OneWorld account with at least one subsidiary. On the Salesforce side, setup uses an API-only integration user, an External Client App, permission sets, lookups and an initial load of historical items. Plan for a project with your NetSuite administrator.

→ Salesforce + NetSuite integration details

Breadwinner and Celigo document custom records

Breadwinner is a managed package installed in Salesforce; the vendor says its Apex Generator handles NetSuite custom records and fields. Celigo's Salesforce–NetSuite integration app covers the standard order-to-cash flows and has documented custom record flows. Both are purpose-built for this pair, so choose one of them over a general automation platform if the sync is business-critical and you'd rather buy than build.

Make's NetSuite app needs the Enterprise plan

Make ↗ 's NetSuite app is only available on Make's Enterprise plan. On that plan, a custom object sync looks like this:

  1. Salesforce: Watch Records on your custom object, such as Contract_Line_Item__c.
  2. NetSuite: Search Custom Records to find a matching record, such as customrecord_contract_line.
  3. NetSuite: Update a Custom Record if found, otherwise Create a Custom Record.
  4. Turn on Store incomplete executions in scenario settings, and add a Retry error handler to the NetSuite modules.

With incomplete executions stored, Make retries rate-limit, connection and timeout errors automatically with increasing delays. The Retry error handler covers other errors; by default it tries 3 times, 15 minutes apart.

Set up the sync in Make →

n8n reaches NetSuite through a community node

n8n ↗ has a built-in Salesforce node but no built-in NetSuite node. Use the verified community node (n8n-nodes-netsuite-rest), which covers more than 150 record types, custom fields and records, and SuiteQL with OAuth 2.0, or call NetSuite's REST API with the HTTP Request node. n8n's credential store refreshes OAuth 2.0 tokens automatically, and an error workflow can alert your team in Slack or email when a run fails.

n8n suits two cases: data that has to stay on your own servers (the self-hosted Community Edition is free), and SaaS products that want to offer this sync to their own customers, which needs a separately licensed n8n Embed agreement.

Start syncing with n8n →

Affiliate disclosure

Plan for two auth changes

  • Salesforce: since the Spring '26 release, creating new Connected Apps is off by default, and Salesforce points to External Client Apps instead. Existing Connected Apps keep working.
  • NetSuite: from NetSuite 2027.1, new integrations can't use token-based authentication (TBA) and must use OAuth 2.0 with PKCE; existing TBA integrations are supported for longer. Make's NetSuite app uses TBA today, so check its status before building anything long-lived.

Sources: Salesforce, Oracle.

Three causes of a stalled sync

Custom object fields arrive empty

The field is mapped by label instead of API name, or the integration user can't see the field. Map by API name (ending in __c in Salesforce, custrecord_ in NetSuite) and check field-level security for the integration user.

Sync stops after a few days

The Salesforce token was revoked or expired. Re-authenticate the connection, and check the External Client App's refresh token policy.

Some runs fail and are lost

In Make, incomplete executions aren't being stored, so failures aren't retried. Turn on Store incomplete executions and add a Retry error handler.

Related guides and integration pages