NetSuite Integration: What to Plan Before You Connect

A NetSuite integration connects NetSuite to your CRM, ecommerce store, payroll system or warehouse so data moves without retyping. Before you connect anything, plan the authentication method, which system owns each field, your concurrency limit and how errors get fixed. The authentication step matters more than usual right now, because NetSuite has published dates for retiring SOAP and token-based authentication.

Short version: build new work on REST and OAuth 2.0, list what you already run, and agree on data ownership before anyone writes code.

What is changing with NetSuite integrations?

NetSuite has published a SOAP removal timeline. Release 2025.2 is the last planned SOAP endpoint. From 2026.1, new integrations are expected to use REST web services and OAuth 2.0. From 2027.1, no new integrations can be built with SOAP. In 2028.2, all SOAP endpoints are disabled and SOAP integrations stop working.

Token-based authentication (TBA) is on a similar path. NetSuite's TBA end of support page says new TBA integrations are blocked from 2027.1, and existing ones are tentatively supported until 2028.2. SuiteAnalytics Connect is excluded from that cutoff, but confirm its authentication needs separately.

This affects more than custom code. NetSuite lists third-party connectors among the things that may need a change or a version update. If you bought an integration years ago, you may be running SOAP or TBA without knowing it.

What should you check in your current setup first?

Start with an inventory. It is dull work, but it tells you the size of the job. NetSuite itself recommends listing SOAP and TBA usage across scripts, RESTlets, integrations and connectors. We would record these for each one:

• The two systems it connects and the business process it supports
• The method and authentication it uses
• Who built it and who maintains it today
• What breaks, and for whom, if it stops for a day
• Whether the vendor has confirmed OAuth 2.0 support, with a date

Then sort by business impact. Order flow and invoicing usually come before a nightly report.

Which NetSuite integration method fits your project?

NetSuite's integration options page compares its main methods. In plain terms:

• REST web services: fits standard record work from an outside system, such as creating a customer or reading an order. It uses JSON, offers a metadata catalog and needs no server-side script.
• RESTlets: fit custom logic or several steps that should run in one call. They need JavaScript and SuiteScript skills, and they do not provide metadata.
• SOAP web services: keep these only for existing integrations you plan to move.

NetSuite also says REST will not reach full parity with SOAP, and points to RESTlets for what REST does not expose. So check your exact records and operations against the upgrade guide early. A gap you find in week one is a design choice. A gap you find during testing is a delay.

Which system should own each field?

Most integration trouble is about data, not code. If sales edits a customer address in the CRM and finance edits it in NetSuite, the integration will copy one mistake over the other, and nobody will trust either system.

Write a simple table with one row per field: the owning system, the systems that receive it, and what happens when they disagree. We would settle these first:

• Customer and company names, addresses and tax details
• Items, prices and discount rules
• Order status, invoices and payments
• Which ID links a record across systems

Finance should sign off on anything that touches the books. This table also feeds your budget, since field mapping is often where the hours go. Our guide to API integration cost explains how those hours add up.

How do concurrency limits affect your design?

NetSuite limits how many requests can run at once for the whole account. The governance page says the limit covers web services and RESTlet requests combined, and a request running more than 15 minutes times out. So your new integration shares a budget with everything else already connected.

The limit depends on your service tier. For contracts since June 2020, the base limit is 5 for Standard, 15 for Premium and 20 for Enterprise and Ultimate. Each SuiteCloud Plus license adds 10. A Standard account with one license gets 15.

Before buying more capacity, measure your peak. NetSuite's license guidance points to peak concurrency needs, the number of connected applications and your overall integration model. Often you can spread batch jobs across the night, cap parallel requests per integration and send only changed records. If you still run out, then licenses make sense.

What happens when a sync fails?

It will fail at some point. A required field is empty, a token expires or a request hits the limit. Plan the failure path as carefully as the normal one.

1. Log each failed record with the reason, not just a count.
2. Retry temporary errors with increasing waits, and send bad data to a person instead.
3. Prevent duplicates by checking an external ID, so a retry does not create a second invoice.
4. Name an owner. Someone in the business should get the alert and know what to do with it.
5. Test in a sandbox with real edge cases: returns, partial shipments, credit memos.

Ask any vendor to show you this part of their design. If the answer is only "we send an email," keep asking.

What should you ask an integration partner?

Whether you hire us or someone else, these questions separate a real plan from a sales pitch:

• Will this use REST and OAuth 2.0? If not, why not, and what is the replacement date?
• How many concurrent requests will it use at peak?
• Who owns the code, the mappings and the documentation?
• Who gets the alert when a record fails, and who fixes it?
• What does support cost after launch, and what happens at each NetSuite release?

If you are still deciding on the ERP itself, our guide on whether SAP fits a midsize company covers questions that apply to most ERP choices.

Frequently asked questions

Sources

• NetSuite: SOAP Removal Plans FAQ
• NetSuite: Preparing for TBA End of Support
• NetSuite: REST Web Services and Other Integration Options
• NetSuite: Concurrency Governance Limits by Service Tier
• NetSuite: Concurrency Governance and Session Management
• NetSuite: Determining How Many SuiteCloud Plus Licenses You Need