SuiteScript 2.1 migration: is your NetSuite account ready for 2028.2?
Category NetSuite
Blog_field_Datum October 12, 2026
If your NetSuite account still uses SuiteScript 1.0, 2.0 or scripts tagged with @NApiVersion 2.x, it's time to review your customisations.
Oracle has made SuiteScript 2.1 the standard scripting model. Its published transition plan requires all new and existing scripts to use 2.1 by NetSuite 2028.2, when legacy versions are scheduled to stop running. Some changes will affect your account before then.
What changes, and when?
Oracle's SuiteScript transition timeline sets out these milestones:
| NetSuite release | Approximate timing* | What changes |
| 2026.2 | Second half of 2026 | SuiteScript 2.1 becomes the standard for new and existing scripts. |
| 2027.1 | First half of 2027 | SuiteScript 1.0 support is limited to critical issues. Other issues require conversion to 2.1 first. |
| 2028.1 | First half of 2028 | SuiteScript 1.0 scripts can no longer be deployed in new accounts, but remain deployable in existing accounts. Scripts annotated as 2.0 or 2.x run using the 2.1 runtime by default. |
| 2028.2 | Second half of 2028 | All new and existing scripts must use SuiteScript 2.1. Legacy script versions will no longer run. |
* Calendar periods are planning estimates based on NetSuite's twice-yearly release cycle, not confirmed deadlines for individual accounts. Releases roll out in phases, so upgrade dates differ per account. The milestones themselves are confirmed in Oracle's NetSuite 2026.2 release notes.
For the exact date: check the New Release portlet on your NetSuite production account's Home page once the relevant upgrade is scheduled. See NetSuite Version Upgrade Maintenance.
The 2028.1 runtime change deserves attention: existing 2.0 and 2.x scripts need compatibility testing before NetSuite changes how they execute.
What does migration involve?
The work depends on which versions your account uses.
SuiteScript 1.0 scripts require code conversion, including replacing legacy API functions with the appropriate 2.1 modules and methods.
For 2.0 and 2.x scripts, updating the version annotation is part of the process. You also need to check behaviour in the 2.1 runtime because some capabilities work differently. Oracle explains these differences in its 2.0 to 2.1 migration guidance.
Give particular attention to scripts that support integrations, financial processes, order management or workflows. Testing should cover the business process each script supports, including its dependencies and error handling.
Unsure which scripts need attention? TEKNURO can help you review your existing customisations and identify where to start.
Discuss your SuiteScript migration with TEKNURO
How TEKNURO can help
We can help you work through the migration, from the initial script inventory to testing before production deployment:
- Identify SuiteScript 1.0, 2.0 and 2.x scripts that need attention.
- Assess their business impact, dependencies and migration complexity.
- Prioritise scripts supporting critical business processes.
- Convert customisations to SuiteScript 2.1.
- Test functionality and compatibility before deployment.
- Identify obsolete or duplicated scripts that can be retired.
- Review existing customisations for improvements during the migration.
This is also a useful time to remove unused code and make the customisations you keep easier to maintain.
Start with a script inventory
A NetSuite account can contain years of custom scripts and dependencies. Understanding what you have gives you a basis for estimating the work and scheduling it around day-to-day operations.
Oracle recommends testing in a sandbox before deployment. A phased migration gives your team time to validate changes before moving on to the next group of scripts.
If you need help assessing your account or planning the work, tell us which NetSuite processes depend on custom scripts. We can help you identify priorities and build a practical migration plan.
