The SuiteScript 2.1 banner and what it’s actually asking you to do

If you’ve logged into NetSuite recently and seen a banner about updating scripts to SuiteScript 2.1, you’re not imagining it and it’s not going away on its own. NetSuite is retiring SuiteScript 1.0, 2.0 and 2.x. Anything still running on those versions stops working in the 2028.2 release.

2028.2 sounds far off. It isn’t, once you look at what’s actually involved.

First, find out what’s flagged

The banner tells you something needs attention, not what. Two ways to see the actual list.

In the UI, go to Customization > Scripting > Scripts, then add or filter on the API Version column.

If you’d rather query it directly, this pulls the same thing:

SELECT s.id, s.name, s.scripttype, s.apiversion, s.scriptfile
FROM script s
WHERE s.apiversion != '2.1'
ORDER BY s.apiversion, s.scripttype

On a long-lived account this list is usually bigger than people expect. We pulled one recently that came back at 977 scripts.

Most of what’s on that list probably isn’t yours

That number looks alarming until you sort it by name. On the account we ran this against, the overwhelming majority weren’t custom scripts at all. They were part of installed bundles: NetSuite WMS, Electronic Payments, Bank Feeds, SuiteCommerce, SuitePeople modules, and a handful of third-party ISV bundles layered in over the years.

That distinction changes what you actually have to do. A script that ships inside a bundle gets updated when the bundle publisher pushes a 2.1-compatible version. Nothing for you to write or test yourself, just something to track. A script your team or a consultant wrote is a different story: somebody has to open it, convert it, and test it against your actual workflows before 2028.2 arrives.

So the real first step isn’t converting anything. It’s sorting the list into three piles: native NetSuite bundles, third-party bundles, and custom work. The first pile you watch. The second pile you check with each vendor, since ISV support varies a lot and some of these bundles haven’t been touched in years. The third pile is the actual project.

Do it yourself with a prompt

If you’re already running Claude with a NetSuite MCP connector, this prompt does the pull, the sorting and the spreadsheet in one pass. Paste it as-is.

Query my NetSuite account for every script not yet on SuiteScript 2.1:

SELECT s.id, s.name, s.scripttype, s.apiversion, s.scriptfile
FROM script s
WHERE s.apiversion != '2.1'
ORDER BY s.apiversion, s.scripttype

Pull all rows (page with OFFSET/FETCH if the result is capped). Then:

1. Add a "Family" column. Group scripts by the vendor/bundle their name
   points to (a shared prefix or clearly common naming pattern, e.g. WMS,
   Bank Feeds, SuiteCommerce, Electronic Payments, SuitePeople modules,
   or a named ISV bundle). Anything that doesn't match a bundle pattern,
   mark "Custom / Unclassified."

2. Add a "Likely Source" column: "NetSuite native bundle," "Third-party
   bundle," or "Custom." Base this on the Family column, not a guess
   about who wrote it.

3. Build a spreadsheet with two tabs:
   - Summary: one row per Family, with total scripts, count on 1.0,
     count on 2.0, and Likely Source.
   - Full list: every script, sorted by Family, with columns for Status
     (Not Started / In Progress / Blocked / Done), Owner, and Notes,
     left blank for me to fill in.

4. Give me the custom/unclassified scripts as a separate short list at
   the top of the full list tab. Those are the ones that need an actual
   conversion project before 2028.2. Everything else just needs tracking
   against the vendor's release notes.

If your MCP setup doesn’t expose runCustomSuiteQL directly, ask it to list available tools first. Some accounts have it under a slightly different name.

What that third pile usually looks like

Once you strip out the bundled scripts, what’s left tends to be smaller and more specific: a few user event scripts on transactions, a client script or two on a custom form, maybe a scheduled script that runs a nightly process. That’s manageable. It’s also exactly the kind of thing that gets missed if the only signal you’re working from is “977 scripts flagged” instead of the dozen that are actually yours.

We’ve been doing this since 2003

Fourth Wave has been through enough NetSuite release cycles to know the difference between a banner that needs a project plan and one that needs a spreadsheet. If you want a second pass on your account, we’ll pull the script list, sort it the way this post describes, and tell you honestly which pile is worth your time before 2028.2. Get in touch.