This will be the first of our four-part guideline on SuiteScript 2.1, what it entails, what you should do, and why. Part 2 will discuss the benefits of SuiteScript 2.1

Part 1: The Clock is Ticking: Why Your NetSuite Account Needs a Code Audit Today

If your company runs NetSuite, custom code likely handles your key processes: automated order creation, approval routing, inventory syncs, or custom billing rules. For nearly two decades, NetSuite allowed these scripts to run across different generations of its underlying language. That window is closing.

Oracle has published a clear timeline ending with release 2028.2. By that point, every script in every account must run on SuiteScript 2.1.

If your account relies on legacy SuiteScript 1.0 or early 2.0 scripts, you have work to do. Ignoring it will eventually stall daily operations when older scripts break or lose support.

The official transition timeline

Oracle is moving the platform toward SuiteScript 2.1 across four distinct phases:

• 2026.2: SuiteScript 2.1 becomes the default scripting model across all accounts. Accounts on this release show an in-account banner warning administrators that scripts need updating.
  
• 2027.1: SuiteScript 1.0 reaches end-of-life support. Oracle will only fix critical platform issues for 1.0 scripts.
  
• 2028.1: You can no longer add SuiteScript 1.0 files to new accounts. Existing 2.0-era scripts tagged as 2.x will automatically start executing under the 2.1 runtime.
  
• 2028.2: The final hard deadline. All new and existing scripts must run on SuiteScript 2.1. Legacy runtimes will be retired completely.
  

Where accounts break during updates

The migration is rarely a quick switch. Older accounts often run a mix of 1.0, 2.0, and 2.1 scripts side-by-side, sometimes attached to the very same invoice or customer record.

When Oracle shifts the execution default, subtle differences between versions surface:

• Sublist line numbers: SuiteScript 1.0 uses 1-based indexing for line items on sales orders or invoices. SuiteScript 2.1 uses 0-based indexing. Converting a script without catching this shifts every item line off by one, causing incorrect calculations or saving data to the wrong row.
  
• Tax calculations: The SuiteTax Engine does not support SuiteScript 2.1. If you run custom tax scripts alongside SuiteTax, they must stay on legacy syntax.
  
• Global form scripts: Client-side scripts set to run across “All Records” must remain on ES5.1 syntax.
  
• Third-party vendor bundles: Code installed by external SuiteApp vendors belongs to those vendors. You cannot edit their files directly, but you must confirm they are updating their packages before the deadline.
  

The immediate step: audit your account

Before writing or converting any code, you need a complete inventory of every script in your system. Filter your script records by version to separate inactive scripts from mission-critical ones.

PS Global Consulting runs fixed-scope code assessments to map your account. We identify active scripts, flag high-risk dependencies, separate your custom code from vendor bundles, and deliver a prioritized plan before you spend time or budget on development.