Two dated deadlines, one that doesn't exist, and a lot of confident writing about the difference.
Token-Based Authentication and SOAP web services are being retired on Oracle's published schedule. SuiteScript 1.0 is not — despite what a good deal of the internet says. This page quotes Oracle's own documentation for each, states the date I last checked it, and doesn't inflate any of it.
Two have published dates. One does not.
Oracle's dates: 2027.1, then 2028.1. From 2027.1 you cannot create new integrations that use TBA — SOAP, REST and RESTlets alike. At 2028.1 support ends for the ones you already have, and they stop authenticating. SuiteAnalytics Connect (ODBC/JDBC) is excepted.
Oracle's dates: 2027.1, 2027.2, then 2028.2. No new SOAP integrations from 2027.1. From 2027.2 only the 2025.2 endpoint remains supported. At 2028.2 all endpoints are disabled and every remaining SOAP integration stops working. This is a removal, not a deprecation.
No dates announced. Oracle's help center states that 1.0 continues to be supported but is no longer being updated, with no new feature development. It is frozen. It is not scheduled for removal.
Anyone telling you SuiteScript 1.0 has a cutoff is either mistaken or selling something — and the distinction matters, because the two that are dated deserve your attention first.
Four phrases get used interchangeably in this conversation, and they mean very different things. Sorting them out is most of the value of this page.
A vendor who slides from the first of those to the fourth inside a single sentence is worth reading carefully.
The honest answer is that nobody can tell you without looking — and most accounts have never looked.
For integrations, what you need is the login audit trail rather than the configuration screens: what actually authenticated, by which method, and when. Configuration tells you what exists; the audit trail tells you what's alive. An account with forty integration records where six have authenticated in ninety days has a completely different problem from one where all forty are live.
Remediating TBA and SOAP isn't something I offer yet — it's on my list to build, and if it's what you actually need, say so. What people ask for is how I decide what gets built next. Meanwhile the queries aren't secret, and if this helps you scope your own work, that's a better outcome than you not knowing.
Your SuiteScript estate is the part I do work on. Same blindness, different question: which scripts are yours versus a vendor's, which are actually deployed, which use APIs with no 2.1 equivalent, and which would genuinely be hard to move. That's what the catalogue answers, and it's where every engagement starts.
One page each, with the source documents linked.
25 August 2026, against Oracle's NetSuite Help Center — the transition guidance for SuiteScript 1.0, the Token-Based Authentication end-of-support notice, and the SOAP removal FAQ.
I re-check this at every NetSuite release and change the date above whether or not anything moved. If you find something here that is out of date or wrong, tell me and I will fix it.
One claim I have deliberately left out: several sites report that NetSuite 2026.2 introduces a warning banner for SuiteScript 1.0. I could not confirm that against Oracle's own release notes, so it is not stated here as fact.
Every custom script cataloged and scored for complexity and risk, with the vendor-owned and unconvertible ones named and excluded. Engagements start at $2,000.
See what it costs