SuiteScript 2.1 Migration: Know What You Have Before NetSuite Forces the Issue

NetSuite has announced that every custom script must use SuiteScript 2.1 by release 2028.2. Scripts on SuiteScript 1.0, 2.0 or 2.x will need to be updated to keep working. Most companies don’t know how many of their scripts are affected, or which ones run critical processes.

We’ve been writing SuiteScript since before 2.0 existed. We’ll find every affected script, test it, and give you a clear, prioritized plan, well before the deadline.

What NetSuite is changing, and when

NetSuite is phasing this in over several releases (source: SuiteAnswers 1047412):

Release	What happens
2026.2	SuiteScript 2.1 becomes the standard for new and existing scripts.
2027.1	SuiteScript 1.0 enters end-of-life support: critical fixes only.
2028.1	1.0 scripts can no longer be deployed in new accounts. 2.0/2.x scripts run as 2.1 by default, which is when untested scripts start behaving differently.
2028.2	All new and existing scripts must use SuiteScript 2.1.

That might sound like plenty of time. But your conversion work competes with every other project, and every other NetSuite customer will be looking for help at the same time. Accounts that plan now get to choose when the work happens.

Isn’t this just a version number change?

Sometimes it is. For many 2.0 and 2.x scripts, the fix is to test them under 2.1 and update the @NApiVersion annotation. But 2.1 runs on a newer JavaScript engine, and NetSuite notes that some capabilities behave differently. A script that “seems fine” can quietly produce different results in a saved search, an integration or a month-end process.

SuiteScript 1.0 is a different story. Those scripts have to be rewritten against a completely different API. They’re also often the oldest, least documented and most business-critical code in the account.

The SuiteScript 2.1 Readiness Audit

A fixed-scope engagement that turns “we should probably look at that” into a prioritized plan.

You keep the report whether or not we do the conversion work.

Why Head in the Cloud

• Every SuiteScript version, first-hand. We’ve worked with NetSuite since 2009. We mastered SuiteScript 1.0 back when it was the only option, and we know where its scripts tend to hide surprises.
• AI-assisted, developer-verified. We’re specialists in AI and MCP integrations with NetSuite. AI handles the repetitive conversion work, so it’s faster and cheaper than a manual rewrite. A senior developer reviews and tests every line, so it’s safer than DIY.
• NetSuite-only, by choice. SuiteCloud Developer Network Partner, three-time winners of the NetSuite Hackathon 4 Good, and builders of our own SuiteApps.
• Estimates based on your real code. Our estimates come from reading your actual scripts, not guesswork. We’ll tell you early if anything turns out bigger than expected.

Frequently asked questions

When should we start?

Ideally before SuiteScript 1.0 enters end-of-life support in 2027.1. Starting with an audit now lets you spread the work across normal maintenance instead of cramming it in before 2028.2.

Can’t we just use AI to convert the scripts ourselves?

AI is a great accelerator, and we use it ourselves. But converting code isn’t the hard part. Knowing it still does exactly what your business relies on is. That takes someone who understands both SuiteScript and your processes, and who tests properly.

What about scripts from SuiteApps or bundles we installed?

Those are usually the vendor’s responsibility. The audit identifies them so you can confirm each vendor’s 2.1 plans, and so nothing slips through the cracks.

Do we need a sandbox account?

A sandbox is ideal, but it isn’t required. NetSuite’s Release Preview account can also be used to test how scripts behave under 2.1.

We’ve had several developers over the years and nothing is documented. Is that a problem?

That’s very common, and it’s exactly what the audit is for. You’ll come out of it with a plain-English description of what every script does.