NetSuite Modernization
Reduce the cost and risk of every change you make from now on.
Why it exists
Most long-running NetSuite accounts carry a decade of decisions, half of them no longer relevant. SuiteScript 1.0 still in production. Three different solutions to the same problem. Code paths nobody dares delete because nobody is sure what calls them. Modernization is the slow, deliberate work of removing that liability.
The SuiteScript 2.1 deadline
Oracle is retiring SuiteScript 1.0, 2.0 and 2.x. By the 2028.2 release, every script in every account has to run on SuiteScript 2.1 — not just the ones that matter.
- 2026.2
- SuiteScript 2.1 becomes the standard for new and existing scripts.
- 2027.1
- SuiteScript 1.0 support narrows to critical issues. Anything else, Oracle asks you to convert to 2.1 first.
- 2028.1
- SuiteScript 2.0 and 2.x scripts run as 2.1 by default — whether or not anyone has tested them.
- 2028.2
- All new and existing scripts must use SuiteScript 2.1.
Changing the version annotation is the easy part. Underneath it is a different runtime engine: RESTlet responses that serialize differently, dates that format differently, error details that can drop out of your logs, and 24 SuiteScript 1.0 APIs with no direct 2.1 equivalent. Oracle's own AI conversion tools say to review the converted code, test it in a sandbox, and never deploy it straight to production. That review is the work.
Sources — Oracle NetSuite Help Center
What's included
- Migration of SuiteScript 1.0, 2.0 and 2.x → 2.1 — every script converted or retired before the 2028.2 cutoff
- Consolidation of duplicated customizations
- Dead-code removal, with proof of non-use
- Refactoring toward governance-aware patterns: Map/Reduce where appropriate, deferred execution, idempotent integration jobs
- Test scaffolding where it makes economic sense
Deliverable
Working code in your account, with a written summary of what changed and why. Each change reviewable as its own atomic unit.
Ideal fit
- Your account still runs SuiteScript 1.0 or 2.0 scripts, and 2028 is closer than the backlog
- You spend more time managing the customization layer than building on it
- Every new feature collides with old code in unexpected ways
- You've already audited (here or elsewhere) and now want execution