Is SuiteScript 1.0 deprecated?

Two statements from the NetSuite Help Center, quoted rather than paraphrased.

SuiteScript 1.0 scripts continue to be supported, however, SuiteScript 1.0 functionality is no longer being updated, and no new feature development or enhancement work is being done for SuiteScript 1.0.

And on the documentation itself:

While our support and service teams remain able to troubleshoot solutions previously written in SuiteScript 1.0, this version is no longer updated.

The 1.0 API reference is no longer published as individual help topics — it survives as a login-gated PDF. That is a signal about Oracle's intentions. It is not a deadline, and it should not be sold to you as one.

There is no cliff, but there is erosion — twice a year, at each release, as the platform moves under code that is not moving with it. Practitioners report a recognizable set of symptoms:

• nlapiGetCurrentRecord() returning null, as the UI became progressively more asynchronous and page regions began rendering independently. pageInit can now fire before the fields it reads are populated.
• Searches returning empty result sets with no error thrown, particularly where filters use compound logic.
• Type coercion drifting, so a value that used to arrive as an empty string arrives as undefined — which silently changes which branch a script takes rather than failing loudly.
• Scheduled scripts exhausting governance mid-run and stalling without a clear error.

There is a live thread in Oracle's own community titled "2025.1 version update seems to have broken my SuiteScript 1.0 Suitelet." That is the shape of this risk: not a date, but a slow accumulation, discovered by whoever happens to be on support that week.

This is the part that does have dates, and it is why I would sequence the work sooner rather than later.

Token-Based Authentication stops accepting new integrations at 2027.1, and support for existing ones ends at 2028.1. SOAP endpoints are disabled entirely at 2028.2. A great many SuiteScript 1.0 RESTlets authenticate with TBA, and a great many 1.0 integrations call SOAP. Those scripts sit inside a blast radius that is already scheduled.

An account remediating its authentication is going to be inside those scripts anyway. Converting them to 2.1 in the same pass is cheaper than opening them twice — which is an argument about sequencing rather than a manufactured emergency, and it is the honest version of the urgency you will see elsewhere.

The dates, with sources: the full timeline.

Ask most NetSuite accounts how many custom scripts they run, which are third-party, which record types they are deployed against, and which nobody has touched in five years. You will not get an answer. Not because the team is careless — because the information has never been assembled anywhere.

That matters beyond migration. Any company heading toward an audit, an acquisition, or an IPO needs a documented catalogue of its customizations, and "we're not sure" is an expensive answer in all three situations.

This particular need has no deadline attached, and it never goes away.

Probably. Not in a panic, and not all at once.

The case for moving is that 1.0 receives no new capability, decays quietly, and sits inside two deadlines that are real. The case against rushing is that a conversion done badly is worse than no conversion, and there is no date forcing your hand.

What I would suggest: find out what you actually have, score it for risk rather than for age, and move the pieces that carry real exposure first.

That is an ordinary engineering judgment, and it is available to you whether or not you ever hire anybody.

25 August 2026, against Oracle's NetSuite Help Center. Re-checked each release; the date changes whether or not anything did.

Widely repeated but unconfirmed: that NetSuite 2026.2 adds a warning banner for SuiteScript 1.0. I could not verify it against Oracle's release notes, and will not repeat it until I can.