SuiteScript 2.1 Migration

Every custom script moves to 2.1by the 2028.2 release.

SuiteScript 2.1 is now NetSuite's standard, and older versions drop away over the next few releases. We list what you have, drop the unused scripts, and test the rest before your live account sees them.

Book an Assessment →

What changes, and when

  1. 2027.1SuiteScript 1.0 support narrows to critical issues. Other fixes mean converting the script first.
  2. 2028.12.0 and 2.x scripts run as 2.1 by default, and 1.0 can no longer be deployed in new accounts.
  3. 2028.2All new and existing custom scripts must be on 2.1.

Sound familiar?

  • You've heard about the deadline and don't know how many of your scripts it touches.
  • Your account still runs SuiteScript 1.0 code from consultants who have moved on.
  • Other systems call your RESTlets, and what they expect back isn't written down.
  • Some scripts came with bundles or SuiteApps, so you can't change them yourself.

What we do

  • List every script and deployment by version, and what depends on it.
  • Retire scripts nobody uses, so you don't pay to convert them.
  • Rewrite SuiteScript 1.0 code against the 2.1 modules.
  • Move 2.0 and 2.x scripts across, checking the changes that raise no error, like RESTlet responses, numbers and dates.
  • Ask your bundle and SuiteApp vendors when their scripts will be ready.

How it runs

  1. ListCount every script and rank them by what breaks if they fail.
  2. ConvertMove scripts in batches and test each batch in a sandbox or the release preview.
  3. Hand overDeploy, watch the first live runs, then hand your admin the documentation.

Questions buyers ask first

When do we have to finish?

By the 2028.2 release. Your 2.0 and 2.x scripts start running as 2.1 by default a release earlier, in 2028.1, so test them before then.

Do our 2.0 scripts need work, or only the 1.0 ones?

Both, in different amounts. SuiteScript 1.0 needs a rewrite, because 2.1 replaces its functions with modules and some have no direct equivalent. 2.0 scripts keep the same API but run on a different engine, so some behave differently and need testing.

Can we just change the version tag?

That's the last step for a 2.0 script, after it has passed testing. It doesn't work for 1.0, and on its own it won't tell you whether a RESTlet now returns something different to the system calling it.

What about scripts from bundles and SuiteApps?

Those belong to the vendor. We list them, ask the vendor for dates and plan around the answer.

How is it priced?

Defined conversion work gets a fixed quote after the assessment.

Let’s Talk

Still working around NetSuite? That’s what we fix.

Free 30-minute call. We’ll look at your setup and tell you what we’d fix first. If we’re not the right team for it, we’ll say so.

Book an Assessment →Meet the Team