Boomi NetSuite Integration: How the Connector Works and What to Plan For

By Louis Balla, Chief Revenue Officer, Nuage. Updated October 2026.

The Boomi NetSuite connector lets Boomi processes create, update, query and delete NetSuite records. Boomi’s documentation says it uses NetSuite’s SuiteTalk SOAP web services and recommends token-based authentication, and Boomi also lists a separate NetSuite REST connector. Oracle removes SOAP with its 2028.2 release, so new work should be planned on REST with OAuth 2.0.

This guide explains how the connector works, how to connect it, which of the two connectors to choose and what our team checks after go-live.

What is Boomi NetSuite integration?

Boomi, formerly Dell Boomi, is an integration platform as a service. You build integration processes in Boomi, run them on a Boomi runtime and use connectors to reach each application. The NetSuite connector is the piece that talks to NetSuite. According to Boomi’s connector documentation, it can insert, retrieve, look up, update and delete data in a NetSuite account over HTTPS.

Typical flows move orders from a CRM or an ecommerce platform into NetSuite, send fulfillment and inventory status back out, and keep customer records matched in both directions. The same platform can run flows that touch a bank, a shipping carrier or a payroll provider. Companies with many connected systems often choose an integration platform over a separate script for each.

Is Boomi the same as NetSuite CRM?

Boomi and NetSuite CRM do different jobs. NetSuite CRM holds customer, sales and support records inside NetSuite. Boomi moves data between applications. A company might use Boomi to connect NetSuite to Salesforce, to an ecommerce store or to a warehouse system, and NetSuite CRM is one of the places that data can land.

If your question is how to connect a particular CRM, our Salesforce and NetSuite integration guide compares Oracle’s connector, integration platforms such as Boomi and custom code for that pair.

Is there an official Boomi NetSuite connector?

Boomi publishes and documents its own NetSuite connectors. Its connector catalog lists two:

	NetSuite connector	NetSuite REST connector
NetSuite API	SuiteTalk SOAP web services	NetSuite REST web services
Authentication in Boomi’s documentation	User credentials, or token-based authentication (recommended)	OAuth 2.0 or token-based authentication
Where it stands against Oracle’s timeline	SOAP is removed with the 2028.2 release	REST with OAuth 2.0 is Oracle’s direction for new integrations
Ask Boomi	Which NetSuite endpoints it supports	Its current status: Boomi’s changelog lists the first release, in May 2026, as a Tech Preview, so confirm the status with Boomi

Boomi’s NetSuite REST connector page and its changelog are the places to confirm the current status before you rebuild anything on it.

How do you connect Boomi to NetSuite?

The connection takes five steps. Do them in a sandbox first.

1. Enable the features. In NetSuite, turn on the web services features and token-based authentication on the SuiteCloud subtab of Enable Features.
2. Create an integration record. Check the token-based authentication option. NetSuite shows the consumer key and consumer secret once, so store them securely.
3. Create a dedicated integration role and user. Use a dedicated integration user instead of an existing admin, so the connection keeps working when a person’s access changes and the same pattern can serve other integrations with separate roles. Give the role only the permissions your processes need, then create an access token for that user. NetSuite shows the token ID and token secret once.
4. Create the connection in Boomi. Boomi’s page lists the values for token-based authentication as the NetSuite account number, the consumer key and secret, and the token ID and secret.
5. Test the connection, then build. Run the connection test before you design any process.

For the REST connector the same idea applies with OAuth 2.0 in place of the token values. Oracle’s OAuth 2.0 guidance says to use it for all new integrations.

What should you plan for as NetSuite retires SOAP?

Oracle’s SOAP removal FAQ gives the dates:

• 2025.2 is the last planned SOAP endpoint.
• From 2026.1, newly built integrations should use REST web services with OAuth 2.0.
• From 2027.1, no new integrations can use token-based authentication, which SOAP requires.
• From 2027.2, only the last endpoint is supported.
• With the 2028.2 release, SOAP integrations stop working.

Oracle tells customers who use a partner’s SOAP application to contact the partner and agree a timeline for a REST alternative. For a Boomi account, that translates into a short list:

• Inventory every process that uses the SOAP connector, with its owner and its schedule.
• Ask Boomi about the status of the REST connector and which NetSuite operations your processes depend on.
• Rebuild one low-risk process on REST and OAuth 2.0 in a sandbox, and compare its output with the existing process.
• Schedule the remaining moves well before 2028.2, because each rebuilt process needs its own test cycle.

What should you monitor after go-live?

Two examples from our client work, and one check we recommend, show what to watch.

Schedules and the clock change

An automotive software company syncs Salesforce and NetSuite through scheduled Boomi processes, and its finance team expects them to run at set Eastern times. Boomi schedules here were set in UTC, so after a clock change the runs shift by an hour unless someone moves them. When one process ran two hours off its normal time in March 2026, our team adjusted every scheduled process back one hour in UTC, checked the run logs for the error the client reported, and confirmed the new times with her. We now treat the daylight saving change as a standing check on any account with scheduled middleware.

Data volume against the license

A nonprofit housing organization learned its Boomi account was running over the data allowance in its license and asked us to review its syncs. Our developers found that three processes, all moving donation and invoice records into NetSuite, carried most of the volume, and that each of them cached a list of about 47,000 constituent records returned from NetSuite on every run, which became the first thing to change.

Credentials and users

A dedicated integration user keeps a connection running when staff change roles. Put the integration’s access token on the list of items someone reviews on a regular schedule, so an expired or revoked credential is found before a process fails.

What are the other ways to integrate NetSuite?

Boomi is one route among several. The others, in short:

• Oracle’s own connectors and SuiteApps: packaged integrations such as NetSuite Connector for Salesforce, installed from the SuiteApps Marketplace.
• Other integration platforms: Celigo, MuleSoft, Jitterbit, Workato and Oracle Integration all publish NetSuite connectors or adapters.
• Custom code: RESTlets and REST web services, written for flows that a packaged connector does not cover.

Our guide to choosing a NetSuite integration provider lists these platforms with the connection methods in their own documentation and the questions to put to any provider. Our NetSuite integration overview covers the methods at a higher level.

How Nuage approaches Boomi and NetSuite integrations

In recent projects with Boomi accounts, our team has taken these steps. The order changes with each client.

1. List every scheduled process and the time zone it runs in. After a clock change, a process scheduled in UTC runs an hour off unless someone moves it.
2. Check the connection method. Our developers note whether each process uses the SOAP connector, the REST connector or a third-party application, and which authentication it uses.
3. Review volume against the license. We look at which processes move the most records and what they repeat on every run, such as a cached list that never changes.
4. Run the connection under a dedicated integration user. The role carries only the permissions the processes need, and someone owns the review of its token.
5. Test connection changes in sandbox before production. This applies to a new authentication method, a changed endpoint and a moved schedule alike.

Nuage’s NetSuite experts do this work as part of ongoing NetSuite optimization and managed services.

Boomi NetSuite integration FAQ

Does Boomi have an official NetSuite connector?

Yes. Boomi documents a NetSuite connector that uses SuiteTalk SOAP web services, and a NetSuite REST connector beside it. Both are in Boomi’s own connector catalog. Boomi’s changelog lists the REST connector’s first release, in May 2026, as a Tech Preview, so confirm its current status with Boomi before you plan a rebuild on it.

What do I need to connect Boomi to NetSuite?

For token-based authentication with the SOAP connector, you need the NetSuite account number, the consumer key and secret from an integration record, and the token ID and secret for a user and role. The role should carry only the permissions the processes need. Use a dedicated integration user so the connection survives staff changes.

Which authentication should a new Boomi connection use?

Oracle says to use OAuth 2.0 for all new integrations, and that from 2027.1 no new integrations can be created with token-based authentication. Existing token-based integrations keep working. A new Boomi connection to NetSuite should therefore use the REST connector with OAuth 2.0 where Boomi supports your operations.

How is Dell Boomi different from NetSuite CRM?

Boomi moves data between applications, and NetSuite CRM manages customer and sales records inside NetSuite. Companies use Boomi to connect NetSuite, including its CRM records, with other systems. Because they serve different purposes, the useful comparison is between integration approaches: Boomi, another platform or custom code.

Does Nuage work on Boomi accounts?

Yes. Our team has adjusted scheduled Boomi processes after a clock change, reviewed which processes use the most data against a license allowance, and tested a changed Boomi connection in sandbox before the production change. Those jobs are part of how Nuage’s NetSuite experts support integrations alongside the NetSuite account itself.

About the author

Louis Balla is Chief Revenue Officer at Nuage, a NetSuite optimization partner that has served 250+ clients since 2011 and holds a 4.9 out of 5 rating on Clutch. The client integration work in this article is our team’s.