1. Home
  2. NetSuite integration
  3. NetSuite and Salesforce

NetSuite Salesforce connector: Oracle's own sync turns Closed Won deals into sales orders, if your accounts fit its rules

Oracle now has its own Salesforce Connector for NetSuite: when an opportunity moves to Closed Won, it creates the NetSuite sales order. It needs a OneWorld account and a Salesforce edition with API access. Check both before you weigh it against MuleSoft or a custom build.

Checked 18 November 2026

Oracle’s Salesforce Connector runs inside NetSuite Connector Platform

Oracle’s answer to this pairing is the Salesforce Connector. It runs in the NetSuite Connector Platform SuiteApp, and Oracle says those connectors are built on Oracle Integration Cloud. The point, in Oracle’s words: sales people “can continue to work in Salesforce” while their data syncs with NetSuite’s financial and inventory data.

Scroll the table sideways to see every column.

Data Direction What arrives
Items and products Both ways NetSuite items become Salesforce products, and the reverse
Closed Won opportunity Salesforce to NetSuite A NetSuite sales order
Sales order NetSuite to Salesforce A Salesforce order
Item fulfillment NetSuite to Salesforce A custom fulfillment object
Invoices and payments NetSuite to Salesforce A financial record, for reference only
Customers and accounts Both ways Customer and account updates, plus contacts

How a Closed Won deal becomes a NetSuite sales order

The trigger is the opportunity stage. When it changes to Closed Won, the connector creates the sales order in NetSuite.

  1. The account on the opportunity syncs to NetSuite as a customer record of the type Company.
  2. The sales order is created from the opportunity’s details.
  3. Later changes to that opportunity sync to the same sales order.
  4. The sales order syncs back to Salesforce as an order.
  5. When NetSuite fulfills it, the item fulfillment syncs back as a custom fulfillment object.
  6. The invoice and payments arrive in Salesforce as financial records.

One rule applies on Multi-Subsidiary accounts. If the NetSuite Subsidiary field on the deal is blank, the deal does not post. You get an error instead.

Six rules decide whether the connector fits your accounts

  • OneWorld only. Every NetSuite account on the connector must be a OneWorld account with at least one subsidiary. Legacy Tax and SuiteTax are both supported.
  • API access in Salesforce. The Salesforce edition must support API access.
  • A locked integration user. Salesforce needs an API-only user. That user cannot log in to the Salesforce screens.
  • An External Client App. Oracle’s setup creates one in Salesforce. That matches Salesforce’s own change: creating connected apps is restricted as of Spring ’26, and Salesforce recommends external client apps.
  • NetSuite owns the money. NetSuite is the source of truth for invoices. The invoice copy in Salesforce is only for reference.
  • Only Salesforce-born orders flow back. Invoices for NetSuite sales orders that did not start as a Closed Won opportunity do not sync to Salesforce. A new customer made in NetSuite does not become a Salesforce account either.

The connector treats Subsidiary plus Customer Name as what makes a customer unique. Clean up duplicate names in each subsidiary before the first sync. Price levels should map 1:1, with NetSuite as the authoritative source.

The connector’s setup still asks for SOAP and token-based sign-in

Oracle’s feature checklist for the Salesforce Connector asks for SOAP Web Services and REST Web Services to be on. It also asks for Token-based Authentication. Both are on Oracle’s retirement list: no new TBA integrations from 2027.1, and no SOAP at all from 2028.2. The full list of dates is on our NetSuite integration page.

The setup pages we read on 18 November 2026 do not say which connector calls use SOAP. If the connector does call SOAP, Oracle’s SOAP FAQ says that for SOAP apps NetSuite built itself, a REST version will come “in time”. Ask Oracle for that timeline in writing if your contract runs past 2027.1.

Custom data syncs arrived with release 2026.2

Oracle’s 2026.2 release note on NetSuite Connector, updated October 19, 2026, adds custom data syncs. They cover records the ready-made flows miss.

  • Each custom data sync runs in one direction, NetSuite to Salesforce or Salesforce to NetSuite.
  • A Suggest Field Mappings with AI button proposes field mappings.
  • A Salesforce custom object needs one field set as both External ID and Unique.

That button is the only AI we found in Oracle’s pages for this pairing. It suggests mappings. It does not run a sales process.

Loading old records takes a careful first pass

After setup, the connector does not see records that already exist. Oracle’s method is to turn the sync off, post one record by hand, check it, then run the bulk sync. Bulk loads go in as CSV imports, with Run Server SuiteScript and Trigger Workflows checked.

Errors land in the connector’s Error Report portlet, which shows the 20 most recent failures. One error Oracle lists is Missing fields. It gives two causes: the custom field does not exist in NetSuite, or it exists but is not on the preferred form the connector posts to.

MuleSoft’s NetSuite connector is SOAP, and its default setting ends early

MuleSoft’s Anypoint Platform is a second route. Its NetSuite Connector lists quote-to-cash from a CRM such as Salesforce as a common use case. But check the version.

  • MuleSoft’s NetSuite Connector is SOAP-based. From version 11.0, it supports no REST-based operations.
  • It connects with token-based authentication.
  • Version 13.0.0 is dated November 11, 2026, and lists SuiteTalk API versions 2020.2, 2021.1, 2023.1 and 2025.2.
  • If no WSDL version is chosen, it works with SuiteTalk 2020.2.

Oracle’s SOAP endpoint table shows 2020.2 available without support through 2027.1, and disabled from 2027.2. NetSuite ships two major releases a year.

So a MuleSoft flow left on the default stops about a year before SOAP ends.

MuleSoft also has a NetSuite REST Connector. It signs in with OAuth 2.0 client credentials and a JWT bearer assertion, with no interactive login. It takes at most 100 records in one batch request.

A custom build uses both systems’ APIs and change events

A custom build fits when your accounts or rules do not fit the connector. A NetSuite account that is not OneWorld is the plainest case. The connector needs OneWorld. These are the limits a build must design around:

  • Salesforce change events. Change Data Capture keeps events for three days. Opportunity changes have their own channel, /data/OpportunityChangeEvent.
  • Salesforce volume. Salesforce says a job of more than 2,000 records suits Bulk API 2.0. Enterprise Edition gets 100,000 API calls a day, plus more per licence. Up to 25 long-running requests (20 seconds or more) can run at once in production.
  • Salesforce sign-in. SOAP API login() retires in the Summer ’27 release, so an older tool that signs in that way must move.
  • NetSuite capacity. Concurrent requests start at 5 on Standard, 15 on Premium and 20 on Enterprise and Ultimate.
  • NetSuite records. The sales order record ID in REST web services is salesorder.

An AI agent can sit on top. Salesforce says Agentforce Builder connects agents to Flows, Apex, MuleSoft APIs and prompt templates. See Salesforce AI agents.

OneWorld accounts can start with Oracle’s connector; the rest need a build

Scroll the table sideways to see every column.

Your situation Route Watch for
OneWorld account, standard opportunity to order flow Oracle’s Salesforce Connector The TBA and SOAP features it asks for
You already run MuleSoft for other systems MuleSoft NetSuite REST Connector The SOAP connector’s 2027.2 default
An account that is not OneWorld, or custom objects everywhere Custom build on both REST APIs Salesforce daily API calls and NetSuite concurrency
Records the connector’s flows miss Connector plus custom data syncs One direction per custom sync

Our team has taken NetSuite live and set up Salesforce

Our team has taken NetSuite live. It has also set up Salesforce end to end, moved data in, trained teams, and built agents in Agentforce and through the API.

The first call is free. We sign your NDA before you share any data, if you ask.

Questions

Does Oracle have its own Salesforce connector for NetSuite?

Yes. It is called the Salesforce Connector. It runs in the NetSuite Connector Platform SuiteApp, which is built on Oracle Integration Cloud. It turns a Closed Won opportunity into a NetSuite sales order. It also syncs items, customers, contacts, fulfillments, invoices and payments. Oracle requires a OneWorld account with at least one subsidiary.

What are the different types of Salesforce integration?

For NetSuite there are four. Oracle's Salesforce Connector is the ready-made sync. MuleSoft is an integration platform with NetSuite connectors for SOAP and for REST. Other iPaaS tools, such as Boomi or Celigo, also connect to NetSuite; ask each one which NetSuite API its connector calls. A custom build uses Salesforce's REST and Bulk APIs and its change events, plus NetSuite's REST web services.

Is NetSuite similar to Salesforce?

They overlap in sales tools but do different main jobs. Oracle's docs say the NetSuite platform includes ERP, CRM, PSA and e-commerce. Salesforce is a CRM. Oracle says its connector lets sales staff stay in Salesforce. Their data syncs with NetSuite's financial and stock data.

What is Oracle NetSuite used for?

NetSuite is an ERP, the system a company runs its orders, stock, buying and accounts in. Oracle's help says its CRM and sales force automation cover sales, marketing, partners and support management too. Oracle's connector treats NetSuite as the source of truth for invoices.

Will a MuleSoft NetSuite flow keep working after SOAP ends?

Not on MuleSoft's SOAP connector. Its NetSuite Connector has no REST-based operations from version 11.0. Oracle turns off every SOAP endpoint at release 2028.2. A flow left on the default WSDL setting uses SuiteTalk 2020.2, which Oracle's table disables at 2027.2. MuleSoft's separate NetSuite REST Connector signs in with OAuth 2.0 instead.

Do we need an official Salesforce or NetSuite partner for this?

Not for this work. What decides an integration is a team that knows both systems from the inside and builds on their published APIs. Our team has taken NetSuite live, set up Salesforce end to end and built Salesforce agents in Agentforce and through the API. You license each system from its vendor or a reseller, and we take the setup, data move and integration build from there.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Choose your NetSuite and Salesforce route before 2027.1

The first call is free. Bring your NetSuite edition, your Salesforce edition and the flows you run today, and we can go through which route fits.

Book a NetSuite and Salesforce call