It’s worth highlighting the third row: In 2028.1, your 2.0 and 2.x scripts start running on the 2.1 engine whether you converted them or not. That is the release where untested scripts surprise people, and it arrives a full cycle before the hard stop.
Why get ahead of it
The first cliff arrives in 2027.1. That is months from now. After it, 1.0 support covers critical issues only, and “convert it first” becomes the standard answer from NetSuite support for anything else.
Every NetSuite account needs this at the same time. As 2028 gets closer, developer capacity across the partner ecosystem tightens and pricing moves in the wrong direction. Early movers get calm schedules and first pick of the people who do this well.
Conversion needs real test cycles. A converted script should run through at least one month-end close in a sandbox before it goes live, and ideally several. Starting now gives you multiple closes to catch the subtle differences. Starting in 2028 gives you one, under pressure.
Budgets are being set now. A conversion sized from a proper inventory is a predictable line item for 2027. The same work in the second half of 2028 is an unplanned expense with a deadline attached.
Batches beat big bangs. With two years of runway you can convert in small groups, starting with 1.0, and keep the business running normally. Compressing the same work into a quarter forces everything to move at once.
What 2.1 does for your system
Compliance is the reason to start, but it’s rarely the biggest benefit.
- Modern JavaScript. SuiteScript 2.1 supports ES2019 syntax: let and const, arrow functions, template literals, destructuring, spread, classes. Code gets shorter, more readable, and easier for the next developer to maintain.
- Native promises and async/await on the server. Independent lookups and outbound calls can run concurrently instead of one at a time. Scheduled and Map/Reduce jobs that spend most of their time waiting finish sooner.
- Strict mode. Undeclared variables, silent assignment errors, and other sloppy patterns fail loudly during testing instead of quietly in production.
- Access to new modules. N/llm for generative AI inside NetSuite, N/pgp for encryption, and N/crypto/random are available in 2.1 only, and new platform capabilities target 2.1 first. Staying on 2.0 means watching new features go by.
- Better debugging. 2.1 server scripts debug in browser developer tools, which shortens the trip from “something is wrong” to “here is the line.”
- A cleaner account. A proper conversion starts with an inventory. Dead scripts get retired, duplicates consolidated, survivors documented. Fewer scripts firing on a record save means faster saves and lower governance usage.
- A deeper talent pool. Developers entering the NetSuite ecosystem learn 2.1. Finding someone who wants to maintain 1.0 gets harder every year.
Where Accordion fits
We convert SuiteScript for NetSuite customers, and we work alongside partners who have more 1.0 in their client base than hands to fix it.
Our approach starts with an inventory of every script in the account, pulled through SDF and read by a senior US-based developer. Each script gets a disposition: convert, retire, consolidate, or hand back to the bundle vendor. Conversion is fixed price per script, known before work begins, regression tested in your sandbox against your data, and deployed through SDF with a warranty window. The tooling handles the mechanical translation. Our people own the result.
If you are a NetSuite user, a partner, or an implementation team with clients on older scripts, the first step is the same. Get the inventory done and know your number.
And if the inventory turns up other problems, a scheduled script that times out, an integration that fails every Monday, a workflow nobody can explain, Accordion’s best-in-class technical team can help with those too.