By Louis Balla, Chief Revenue Officer, Nuage. Updated October 2026.
NetSuite integration service providers fall into four groups: NetSuite partners, integration platform vendors and their partners, specialist developers and managed services teams. The right one depends on the systems you connect, whether the work is a one-time build or ongoing support, and whether the flows suit a packaged connector, a platform or custom code.
What does a NetSuite integration service provider do?
A provider connects NetSuite to other business systems and keeps those connections working. The job has three parts. It starts with deciding which records move, in which direction and which system owns each field. It continues with building or configuring the connection, using NetSuite’s APIs, an integration platform or a packaged connector, and testing it in a sandbox. It ends with monitoring, so someone notices when a connection stops. Ask early who will do that monitoring.
Who provides NetSuite integration services?
The same label covers four kinds of organization. A company can use more than one type.
| Provider type | What they do | When it fits |
|---|---|---|
| NetSuite solution partners and implementation firms | Scope, build and support integrations as part of wider NetSuite work | You want one firm that knows the ERP configuration and the connections |
| Integration platform vendors and their partners | Provide the platform and its connectors, with partners building the flows | You connect many systems and want one place to run them |
| Specialist integration developers | Write custom code against NetSuite and the other system’s APIs | A flow has no packaged equivalent, such as a custom object or an unusual approval rule |
| Managed services teams | Monitor and maintain integrations after go-live | Several integrations are live and need ongoing care |
Nuage is a NetSuite optimization partner. Our team works in the first and fourth rows: we build, maintain and optimize integrations in client accounts, and we support them as part of ongoing managed services.
Which platforms connect to NetSuite?
A provider usually builds on an integration platform. The table lists six, alphabetically, with the NetSuite connection methods each vendor documents. It is not a ranking, and it is not a complete market list. Vendors change their documentation, so check the current page before you decide.
| Platform | NetSuite connection in the vendor’s documentation |
|---|---|
| Boomi | A NetSuite connector that uses SuiteTalk SOAP web services, and a separate NetSuite REST connector |
| Celigo | The integrator.io SuiteApp installed in NetSuite, with integration apps for pairs such as Salesforce and NetSuite, Shopify and NetSuite, BigCommerce and NetSuite, and Magento 2 and NetSuite |
| Jitterbit | A NetSuite connector for Jitterbit Studio, with token-based authentication enabled and a supported NetSuite WSDL version as prerequisites |
| MuleSoft | A SOAP-based NetSuite connector, a NetSuite REST connector for record web services and SuiteQL, and a NetSuite RESTlet connector |
| Oracle Integration | An Oracle NetSuite Adapter that uses SOAP APIs, and an Oracle NetSuite REST Adapter that uses REST APIs and JSON |
| Workato | A NetSuite REST connector, described in Workato’s connector guide |
Oracle also publishes packaged connectors that an Administrator installs from the SuiteApps Marketplace. One is the NetSuite Connector for Salesforce, which our Salesforce and NetSuite integration guide describes. Another covers marketplace and cart syncs, and its prerequisites page says every marketplace item must exist in NetSuite with a SKU that matches one to one.
What should you ask a NetSuite integration provider?
These questions work for a platform vendor, a partner or a specialist developer. A specific answer names a method, a person or a document.
| Question | Why it matters | What a specific answer sounds like |
|---|---|---|
| Which NetSuite API and authentication will you use? | Oracle says from 2026.1 new integrations should use REST web services with OAuth 2.0, from 2027.1 no new integrations can use token-based authentication, and SOAP stops working with the 2028.2 release | REST web services or RESTlets with OAuth 2.0, plus a plan for any flow that still runs on SOAP |
| Where are credentials stored and who can see them? | Integration passwords and tokens turn up in ordinary text fields | A masked field type or the platform’s credential store, a dedicated integration user and a named owner |
| How will we know a connection has failed? | A failing connection can run for weeks unnoticed | Alerts with thresholds, a named person who receives them and a review of the script execution log |
| What does an error message tell the person who reads it? | People can only act on an error they can understand | A readable message that names the record involved, and a way for your team to add new error types |
| What do you test in a sandbox, and what do you hand over? | A change that works in one account can fail in another | Test records for create, update and delete, plus written field mapping and run instructions |
| Who maintains the integration after go-live? | An integration problem often involves a second system, so ownership has to be clear | A named team, a response process and a clear line between your admin’s work and theirs |
| Which authentication and API changes affect the connections you already run? | Existing integrations continue to work until their method is removed | An inventory of current connections with a migration order |
| What happens if we leave? | The mapping and credentials should belong to you | Documentation and credentials stored in accounts you control |
Two patterns from our own assessments show why the second and third questions matter, and what a provider should catch. We reviewed 15 client accounts between July and September 2026. At least 10 had a connection that was failing when we looked, among them bank feeds, payment and tax add-ons, file transfers and connectors. One client’s three card feeds had failed on 87 of the previous 89 days, and its team reconciled those cards by hand outside NetSuite. In another account, a script error log held more than 5,000 entries labelled as errors that were routine logging, and once those were filtered out, 163 genuine integration failures remained over four weeks.
The second pattern was credential storage. At least 5 of the same 15 accounts kept integration passwords, tokens or keys in ordinary custom text fields rather than NetSuite’s masked password field type. One account had 12 custom fields on live integration setup records holding credentials, and none of its 4,378 custom fields used the masked type. One of those 12 appeared in list views. We recommend converting each such field to the masked type and narrowing who can see the records.
How do you choose a provider for ecommerce or enterprise software?
For ecommerce, the flows are orders, inventory, fulfillment and refunds. Start with the integration apps and connectors that already exist for your storefront. Celigo documents apps for Shopify, BigCommerce and Magento 2, and Oracle documents a connector for marketplaces and carts. A packaged app removes build work, and a provider then adds value by setting it up against your item and tax configuration and by monitoring it.
For enterprise software, such as an ERP, a billing system or a data platform, the questions that matter are volume, the number of subsidiaries and how many systems share one NetSuite account. Oracle’s concurrency governance page says the limit on concurrent requests depends on the service tier and the SuiteCloud Plus licenses in the account and applies to web services and RESTlet requests together. Ask each provider how it queues requests when several integrations share that limit.
Should you build in-house, buy a platform or hire a provider?
The choice follows who will own the integration after launch. If your team has a NetSuite developer and a clear change process, it can build and run RESTlet integrations itself. When you connect several systems, an integration platform holds the connectors, the schedules and the run logs in one place. If nobody on your side will own the integration, look for a provider who also monitors it. Whichever you choose, put the owner’s name in the plan.
How Nuage approaches integration work
In recent assessments and projects, our team has taken these steps. The order changes with each account.
- List every integration and read its logs. We confirm which connections are live, what each one sends and whether anyone reads the script execution log.
- Find the failing connections. In our assessments these have included bank feeds, payment and tax add-ons, file transfers and connectors.
- Resolve the cause and set up monitoring. We re-enter or rotate credentials, raise errors with an add-on’s vendor when the code is the vendor’s, and set alert thresholds on the logs.
- Move credentials to the masked field type. Where credentials sit in plain text fields, we convert them and narrow who can see the records.
- Plan the authentication and API changes. We list the connections that depend on token-based authentication or SOAP and put them in an order against Oracle’s dates.
Nuage’s NetSuite experts do this work as part of ongoing NetSuite optimization and managed services. Our NetSuite integration overview and custom ERP integration services page cover the methods in more detail.
NetSuite integration providers FAQ
Who are the best NetSuite integration providers?
The best fit depends on the systems you connect, your volume, who will own the integration afterward and which approach suits the flows. Use the evaluation table above, and ask each candidate to describe a similar integration they maintain, including a failure and how they found it.
Which company does NetSuite integration best?
That depends on the pair of systems and on what you need after launch. A platform vendor suits many connected systems, a specialist developer suits a custom flow and a NetSuite partner suits integrations that depend on the ERP configuration. Compare candidates on authentication method, monitoring and handover.
What is the best NetSuite integration for ecommerce?
Start with a packaged app for your storefront. Celigo documents integration apps for Shopify, BigCommerce and Magento 2, and Oracle documents a connector for marketplaces and carts that needs matching SKUs in NetSuite and the cart. If your flows go beyond the packaged ones, add a platform or custom code for the differences.
Do NetSuite integrations need to change because of the SOAP retirement?
Integrations that use SOAP web services stop working with the 2028.2 release, and from 2027.1 no new integrations can use token-based authentication. Existing ones continue to run until then. Ask your provider or platform vendor for a dated plan to REST web services with OAuth 2.0 for each SOAP flow.
Should we build NetSuite integrations in-house or hire a provider?
Build in-house if you have a NetSuite developer, a sandbox process and someone who will read the logs each week. Hire a provider if the integration touches several systems or if nobody on your team owns it after launch. Either way, keep the credentials and the documentation in accounts your company controls.
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 findings in this article are our team’s.
