If your NetSuite account depends on older integrations or custom scripts, it’s time to plan the work to replace them.
Oracle has put three things on a retirement schedule: token-based authentication (TBA), SOAP web services, and SuiteScript versions older than 2.1. Most of the changes land between 2027.1 and 2028.2. Some dates are still marked as planned, but 2027.1 already limits what you can build, and NLAuth stops working that release.
The timeline by release
2026.1
- REST + OAuth 2.0Recommended
REST web services with OAuth 2.0 are the recommended approach for new integrations.
2026.2
- SuiteScript 2.1New standard
SuiteScript 2.1 becomes the standard for new and existing scripts.
2027.1
Key release- TBANo new integrations
New integrations can no longer use TBA, for SOAP, REST web services or RESTlets. Existing TBA integrations keep working until support ends.
- NLAuthStops working
Integrations that use NLAuth stop working.
- SOAPNo new integrations
No new SOAP integrations.
- SuiteScript 1.0Critical fixes only
SuiteScript 1.0 moves to end-of-life support. Only critical issues get fixed; anything else means converting the script to 2.1 first.
2028.1
- SuiteScriptDefault changes
SuiteScript 1.0 can no longer be deployed in new accounts, though existing accounts can still deploy it. SuiteScript 2.0 and 2.x scripts run as 2.1 by default.
2028.2
Key release- TBASupport ends · tentative
Support for existing TBA integrations ends, tentatively in this release. SuiteAnalytics Connect (ODBC/JDBC) isn’t affected.
- SOAPStops working
SOAP endpoints are turned off and SOAP integrations stop working.
- SuiteScript 1.0 / 2.0 / 2.xRemoval expected
SuiteScript 1.0, 2.0 and 2.x are expected to be removed. Every script will need to run on 2.1.
No date yet
- SuiteBundlerNo longer updated
SuiteBundler isn’t being updated anymore. Oracle wants bundles moved to the SuiteCloud Development Framework (SDF), SuiteApp Control Center or Copy to Account.
What this means for you
Start with an inventory. Find everything that uses TBA, NLAuth, SOAP or older SuiteScript, then give each item an owner and a target release. Look at your SuiteBundler dependencies while you’re at it, even though there’s no retirement date yet.
For third-party connectors, ask the vendor which version supports OAuth 2.0 and when their SOAP replacement ships. Sometimes it’s a configuration change, sometimes an upgrade. Your own scripts and in-house integrations are on you.
Budget for real development and testing. REST doesn’t cover everything SOAP does, so some integrations will need RESTlets. Some SuiteScript 1.0 functions have no direct 2.1 equivalent. That’s more than changing a version number.
How we help
We use CraftQL, our SuiteApp, to build the inventory: every script, deployment, RESTlet, Suitelet, bundle and integration in the account, which SuiteScript version each script runs, and which integrations still sign in with TBA tokens. Then we order the work around Oracle’s release dates.
From there we move integrations to OAuth 2.0 and REST, convert scripts to 2.1 and move bundles to SDF, testing each change in your sandbox before it goes to production.
Start with what 2027.1 touches. Talk to us and we’ll tell you what’s affected in your account.
Oracle references
- Token-based Authentication end of support Oracle NetSuite Help Center
- Authentication release notes Oracle NetSuite Help Center
- SOAP Web Services Removal Plans FAQ Oracle NetSuite Help Center
- SOAP web services WSDL and endpoint versions Oracle NetSuite Help Center
- Transitioning to SuiteScript 2.1 Oracle NetSuite Help Center
- SuiteScript 2.x Oracle NetSuite Help Center
- SuiteBundler Oracle NetSuite Help Center
- Transitioning from SuiteScript 1.0 to SuiteScript 2.1 Oracle NetSuite Help Center