A SuiteScript 2.1 migration plan documents every custom script in a NetSuite account, decides whether each one is migrated, retired, or replaced, and schedules the work before the 2028.2 release, when NetSuite’s published timeline calls for all new and existing scripts to use SuiteScript 2.1. A well-built plan spreads the work across several releases, gives the scripts behind order processing, pricing, and period close the most testing time, and prepares 2.0 and 2.x scripts before 2.1 becomes their default runtime in 2028.1.
Snapshot has worked as a NetSuite Alliance Partner for more than 12 years helping manufacturers and distributors build, maintain, and modernize NetSuite customizations.
NetSuite describes three ways to find affected scripts in its “Identifying Scripts That Are Not Using SuiteScript 2.1” help topic:
Record the following for each script in your NetSuite script inventory, so every migration decision has appropriate business and technical context behind it:
Execution logs can show which scripts have run recently, but they only capture entries a script writes or errors it returns, and NetSuite keeps them for 30 days at most. A script that runs only at quarter-end, year-end, or during peak season, or a script that writes no log entries, won’t appear in the logs and can appear inactive. Confirm each script with its process owner before marking it for retirement.
NetSuite outlines three options for each legacy script:
Every SuiteScript 1.0 script that stays in use must be converted to SuiteScript 2.1.
Some scripts can also be replaced with a SuiteFlow workflow. NetSuite’s “Know When to Use SuiteFlow and SuiteScript” topic lists actions both tools can perform, including field validation, default values, required fields, email notifications, record creation, and approval routing. It also describes SuiteScript capabilities such as custom interfaces, programmatically run saved searches, custom dashboard portlets, and batch processes. RESTlet integrations also require SuiteScript.
NetSuite recommends SuiteFlow if you don’t have any JavaScript developers on staff, and SuiteFlow does not require programming knowledge, so moving a script’s logic into a workflow lets your team maintain it without writing code. Scripts that depend on SuiteScript capabilities stay in code and follow the migration path for their version.
Evaluating inactive, obsolete, and duplicated scripts for retirement, and workflow-eligible scripts for replacement, before setting migration priorities shrinks the conversion workload, since only the scripts that stay in code need to move to SuiteScript 2.1. Workflow replacements still need to be built and tested before the original scripts are retired, so include them in your batch schedule.
NetSuite's guidance points in two directions on where to start:
A phased plan follows both recommendations: a small pilot batch of low-complexity scripts first, then business-critical scripts with the most testing time before their target releases. Your SuiteScript 2.1 migration plan can follow five phases:
Group scripts into batches by business process, such as order-to-cash or procure-to-pay, so your team knows which process to check when a test fails. Schedule batches around peak seasons, period close, and NetSuite’s release dates, and test each batch in a sandbox before deployment. Our post on NetSuite sandbox strategy covers refresh timing and test environments.
Assign administrators to inventory and test coordination, developers to conversion and code changes, and process owners to user acceptance testing against real transactions.
Overall effort depends on how many scripts require conversion to SuiteScript 2.1. Some SuiteScript 1.0 functions have no direct SuiteScript 2.1 equivalent and might require a different implementation, and client scripts need separate testing time because the account-level 2.1 preferences apply only to server scripts. Plan extra testing and discovery time for integration scripts and undocumented scripts.
NetSuite’s SuiteScript Upgrade skill, part of NetSuite’s SuiteCloud Agent Skills, can accelerate migration. It analyzes, converts, explains, and validates SuiteScript 1.0, 2.0, and 2.x scripts for 2.1, and developers run it in an AI coding assistant against their script files. NetSuite requires reviewing all generated code before production use and still calls for functional testing in a sandbox before deployment, so plan testing time for converted scripts.
Starting a SuiteScript 2.1 migration plan now gives your team several releases before 2028.1 to inventory, decide, and test, and time to finish remaining changes ahead of 2028.2.
With more than 12 years as a NetSuite Alliance Partner, Snapshot helps manufacturers and distributors inventory, migrate, and test their NetSuite customizations. Our SuiteScript 2.1 migration services page covers how we support each phase. You can get started today with a free NetSuite assessment.