Get your NetSuite scripts ready for SuiteScript 2.1
Oracle is phasing out SuiteScript 1.0, 2.0 and 2.x. From release 2028.2, every script in your NetSuite account must use SuiteScript 2.1. We help you find out what that means for your account, set up a safe test in your sandbox and convert the scripts that need it.
Why should you start before 2028?
Oracle has published the dates in the NetSuite help centre:
- 2026.2: SuiteScript 2.1 becomes the standard for new and existing scripts.
- 2027.1: SuiteScript 1.0 gets support for critical issues only.
- 2028.1: Scripts marked 2.0 and 2.x run as 2.1 by default, even if no one changes the code.
- 2028.2: Every new and existing script must use SuiteScript 2.1.
Most teams plan for 2028.2. We recommend you look closely at 2028.1 too.
A SuiteScript 1.0 script that stops working tells you straight away. A 2.0 script that moves to the 2.1 engine can keep running and simply return a different answer. The code looks the same, nobody deployed anything, and the cause is hard to find.
Scripts marked 2.x are not on 2.1 today. They run on the 2.0 runtime. So even if your account has no SuiteScript 1.0 left, your scripts are still in scope.
Sources (Oracle NetSuite help centre):
- Transitioning To SuiteScript 2.1: the release timeline
- Enabling SuiteScript 2.1 at the Account Level: the setting we use in the dry run
- Differences Between SuiteScript 2.0 and SuiteScript 2.1: what can behave differently
How can we help you?
Choose one service or combine them. They all start from the same list of scripts, so nothing you do is wasted.
1. SuiteScript 2.1 readiness assessment
Know your effort, script by script.
We list every script in your account by version, type and deployment status. Then we rate each one for how much work it takes to convert. SuiteScript 1.0 rewrites and 2.0 updates are different jobs with different costs, so we keep them apart.
You get:
- A register of all your scripts, with a complexity rating
- An effort estimate for each script
- A recommended order for converting them
2. The 2028.1 dry run
See what 2028.1 does to your account, before it happens.
NetSuite already has the setting that 2028.1 will switch on for you. We turn it on in your sandbox, so your team can test your own processes against it before 2028.1 arrives. You can switch it back at any time, and we never do this in production.
You get:
- Your sandbox switched to the 2.1 runtime
- An updated effort estimate based on what your testing finds
3. Rewrite and regression
New scripts, proven against the original.
We convert your scripts in batches, starting with what the assessment and your dry-run testing flagged and what your business cannot afford to have behave differently. We test each batch against how the original behaved, then deploy it through your own release process.
You get:
- Converted scripts on SuiteScript 2.1
- Test evidence for every batch
- Updated deployment objects
4. Script quality audit
Find out what state your NetSuite code is in.
Scripts get written to solve a real problem. They work, and then the person who wrote them moves on. Our audit is an independent, read-only review of every script in your account, in four areas:
- Security: checked against the OWASP Top 10 (a widely used list of the most common web security risks) and our checklist of 48 NetSuite-specific pitfalls
- Performance at volume: will the script still work when your transaction volume doubles?
- Maintainability: can anyone other than the author work on it?
- Deployment and permissions: does each script have only the access it needs?
We rate every finding as critical, high, medium or low, and give you the effort to fix it. We would rather hand you six critical items you act on than ninety you file. If your code is in good shape, we say so.
You get:
- A register of all your scripts
- A findings register with severity and effort to fix
- A prioritised plan for fixing them
- A two-page summary for non-technical readers
- A walkthrough with your team
Converting to 2.1 anyway? Running the audit at the same time costs less than running it separately, because both start from the same list of scripts. It is also the cheapest moment to find out what state your code is in.
How does it work?
We work in three steps rather than one large project:
Assess. We list and rate every script before we give you an estimate. A script count alone tells you very little about effort.
Test. We set up the 2028.1 dry run in your sandbox before we rewrite anything. Your team’s testing is the cheapest way to see which scripts need real work and which only need a small update and a test.
Convert. We rewrite in batches, in the order that matters most to your business, and test each batch before it goes live.
What do we need from you?
A sandbox refreshed from production.
A role with access to scripts and account settings.
A named owner for each process you test.
Access to your release and deployment process.
That is all. We only read in your production account. We never change, deploy, switch on or delete anything there.
What does it cost?
The readiness assessment and the script quality audit both have a fixed scope and a fixed price. We tell you the price before we start.
We quote the conversion after the assessment, not before. Until we have the list of scripts, any estimate is a guess. Your assessment gives you the effort for each script, so you decide how much to do, in what order and over how many releases. Any figure we give you before that is an estimate, and we label it as one.
The audit never comes with an obligation to buy more. Your own team, or another partner, can act on the findings without us.
Why choose Addovation?
- We are a Nordic-based NetSuite partner, and we deliver globally.
- We work in complex NetSuite accounts with many subsidiaries, as well as single-country setups.
- Our platform and business process experts work in the same team. We test each converted script against the process it supports, not only against itself.
Frequently asked questions
We have no SuiteScript 1.0 left. Does this affect us?
Very likely. Scripts marked 2.0 or 2.x run on the 2.0 runtime today. They must move to 2.1 by release 2028.2.
Can we check our own scripts first?
Yes. Run this query in your account to list every script that is not on 2.1:
SELECT scriptid, name, scripttype, apiversion, isinactive FROM script WHERE apiversion IS NULL OR apiversion <> '2.1'
Group the result by script type. Server scripts are where the 2028.1 change lands.
Is the dry run safe?
Yes. We only do it in your sandbox, and the setting can be switched back at any time.
What about scripts from SuiteApps and bundles?
We include them in the assessment and flag the ones you cannot edit yourself, so you can raise them with the vendor in good time.
Do we need both the conversion and the audit?
No. Each one stands on its own. Running them together saves time and cost, because both start from the same list of scripts.