SuiteScript 1.0 has a deadline now: 2028.2

There's a cliff now, at 2028.2, and a silent floor-shift a release before it, at 2028.1. But there was already erosion before either date existed, and it doesn't wait for a release cycle either. 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's a risk that runs alongside the two dates above, not one they replace: a slow accumulation, discovered by whoever happens to be on support that week.

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 catalog 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.

Yes — and now there's a date forcing it.

The distinction that mattered in August doesn't anymore: this used to be a case for moving without a deadline. Now there's one, in two parts. 2028.1 is the one that will actually surprise people, because it changes what your code does without anyone touching it. 2028.2 is the one with no argument left: unconverted scripts stop working.

That's still not a reason to panic before 2027. It's a reason to know what you're carrying, this year, while there's still runway to sequence the work instead of rushing it.