If you’re a NetSuite admin, you’ve probably logged in recently and seen a yellow banner at the top of your home page: “Update Needed: Update Scripts to SuiteScript 2.1.” It says scripts in your account will stop working in NetSuite 2028.2, and that you should convert them “as soon as possible.”
If you don’t write code, that’s an unsettling message to get with no context. Here’s the short version: nothing in your account is breaking today, and you have time. It’s still worth understanding what’s in your account so you can plan.
What the Message Is Telling You
SuiteScript is the code behind many NetSuite customizations. If your account has automations that run when a record is saved, custom buttons, scheduled jobs that run overnight, or integrations with other systems, some of that is probably SuiteScript.
Over the years, NetSuite has released several versions of SuiteScript: 1.0, 2.0, and 2.1. Version 2.1 is the current one, and Oracle is retiring the older versions. The banner appears in any account with at least one script on an older version. That includes nearly every account that’s been live for a few years, and many accounts where the older scripts came from a SuiteApp rather than your own team.
So if you’re seeing it, you’re not behind, and nothing went wrong. It’s a general notice, not a sign that something in your account is broken.
The SuiteScript 2.1 Timeline, in Plain Terms
The banner mentions 2028.2, but Oracle’s transition plan (SuiteAnswers login required) has four steps. NetSuite releases two versions a year, so here’s how it breaks down:
2026.2 (now): SuiteScript 2.1 becomes the standard. This is when the banner started showing up. Your scripts keep running as they do today.
2027.1: SuiteScript 1.0 moves to limited support. If a 1.0 script has an ordinary problem after this point, NetSuite Support will generally ask you to convert it to 2.1 before they help. The script still works, but fixing it gets harder.
2028.1: Scripts on version 2.0 or 2.x start running as 2.1 automatically. Most will work fine. Some may behave differently, and this is when you’d find out.
2028.2: All scripts must be on 2.1.
A practical way to read this: use the rest of 2026 to find out what you have, use 2027 to fix what matters, and be done before 2028.1. That’s a comfortable pace, not a scramble.
If you want help mapping your own scripts against these dates, we can put that plan together with you.
How to See What’s in Your Account (No Coding Required)
You can see which of your scripts use older versions in a few minutes:
- Go to Customization > Scripting > Scripts.
- Find the API Version filter.
- Select 1.0, review the list, then repeat for 2.0.
If you want a list you can save and return to, create a saved search on script records with the criteria API Version is not 2.1. Add columns for Name, Script Type, Owner, and Description so you have some context for each one.
Treat this as a quick first look, not a complete picture. The filter shows what’s recorded on each script record, but it won’t catch every possible issue. It also doesn’t tell you how hard each script is to convert, whether it’s still being used, or who owns it. Those are the questions that decide how much work this actually is.
When we do an evaluation, we don’t stop at this filter. We pull the actual script files and review the code, which is how you find the issues a version filter can’t show you.
The Part You Can’t Change: Locked Scripts and Bundles
Some of the scripts on your list may not be yours to update. Many accounts have scripts that were installed as part of a SuiteApp or third-party bundle. If the vendor locked those scripts, nobody outside that vendor can view or edit the code. That includes you, your internal team, and any NetSuite partner, including us.
For those, the fix has to come from the vendor. Check that the bundle is on its latest version, and if you’re unsure, ask the vendor directly whether they plan to update to SuiteScript 2.1. It’s common for a good share of the list to fall into this category, so sorting these out early gives you a much clearer picture of what’s actually on your plate.
We can sort out which of your scripts are locked and which ones we can update, so you know exactly which vendors you need to contact.
What Trips People Up
Not every script should be converted. Some were built for a process you no longer run, or duplicate something another script already does. Retiring those is less work than converting them, and it cleans up your account in the process.
Converting isn’t just changing a version number. Moving a 1.0 script to 2.1 is effectively a rewrite, because the two versions are structured differently. Moving from 2.0 to 2.1 is usually a smaller change, but it still needs testing. If anyone suggests updating the version in production without testing in a sandbox first, push back.
Nobody may remember what a script does. If a script was written by a former employee or a previous consultant, documentation may not exist. Figuring out what it does, and whether it’s still needed, is often the most time-consuming part of the whole process.
This is where an evaluation saves the most time: figuring out what each script does, deciding whether to convert or retire it, and testing changes in a sandbox before anything goes live.
The Takeaway
Treat this banner as a reminder to take inventory, not as a fire drill. The accounts that handle this smoothly will be the ones that know what they have by early 2027, when the first real change arrives.
Want someone to sort through it with you? If you’d rather not work through your script list yourself, we can do an evaluation for you. We’ll go through the scripts in your account, sort them into what needs converting, what can be retired, and what’s owned by a bundle vendor, and give you a plan with a realistic sequence. We can also handle the conversions for any scripts that aren’t locked. Talk to us about a SuiteScript 2.1 evaluation.
Related reading: What Breaks (and What Doesn’t) When You Turn On NetSuite Next