SuiteScript 2.1 migration

NetSuite expects to remove SuiteScript 1.0 and 2.0 support in release 2028.2

That includes 1.0 scripts and scripts annotated for 2.0 or 2.x. Here is Oracle's timeline, what tends to break, and how we move an account across without surprises.

Oracle's timeline

  1. 2.1 becomes the standardSuiteScript 2.1 becomes the standard scripting model for new and existing scripts.
  2. 1.0 enters end-of-life supportCovers critical issues only. Other problems require converting scripts to 2.1 first.
  3. 1.0 cannot be deployed in new accounts1.0 scripts remain deployable in existing accounts. Scripts marked 2.0 or 2.x run as 2.1 by default.
  4. All new and existing scripts must use 2.1Support for 1.0, 2.0 and 2.x annotations is expected to be removed.

Source: Oracle NetSuite Help Center, Transitioning to SuiteScript 2.1. Rows above follow that page. Check the Help Center for changes before you plan around a date.

Why a line-by-line rewrite is not enough

Most 1.0 code was written around limits that 2.1 handles differently: 1,000-row search pages, yield and reschedule tricks, helpers copied into every file. Translating those habits keeps the old problems and adds new bugs. We fix the habit while we rewrite the script. The casebook shows the ones we meet most.

Scripts already on 2.0 are not safe either. When they start running as 2.1, differences in the language level and in some module behaviour can change results quietly. Those scripts need a test pass, even when the code looks modern.

How we run a migration

  1. Inventory. Every script and deployment, what triggers it, what records it touches, and whether it still runs.
  2. Risk ranking. Scripts that touch money, inventory or integrations go first and get the most testing. Unused scripts are retired, not rewritten.
  3. Rewrite and test. Each script is rewritten in 2.1 and tested in your sandbox against real records, with the old and new results compared.
  4. Release in small batches. The old version stays available until the new one has run clean in production.

What a script review gives you

  • A list of every 1.0 and 2.0 script in the account, grouped by risk
  • The habits in your code that need more than a translation
  • A suggested order and batch size for the rewrite

Find out how much of your account needs to move before 2028.2.

Book a script review