Which NetSuite Scripts Are Affected?
Every custom script written in SuiteScript 1.0 or SuiteScript 2.0 is affected, along with any script annotated @NApiVersion 2.0 or @NApiVersion 2.x. Filter your script records by API version to find them, following NetSuite’s “Identifying Scripts That Are Not Using SuiteScript 2.1” help topic. Each affected script falls into one of three groups based on its version or source, and each group requires a different level of migration work.
SuiteScript 1.0
SuiteScript 1.0 uses a global API model built on functions such as nlapiLoadRecord and nlapiSubmitRecord. SuiteScript 2.1 organizes those capabilities into modules that each script loads, so a 1.0 script must be rewritten with new entry points and module calls. NetSuite requires every SuiteScript 1.0 script to be converted to 2.1.
SuiteScript 2.0 and 2.x
SuiteScript 2.0 introduced the module-based API that SuiteScript 2.1 still uses, and NetSuite states that the SuiteScript API functionality is the same for 2.0 and 2.1. SuiteScript 2.1 runs on a newer JavaScript engine, so some capabilities behave differently. NetSuite currently executes scripts annotated @NApiVersion 2.x as SuiteScript 2.0, which places them under the requirement even when the code is recent.
SuiteApp and Bundle Scripts
Scripts installed through SuiteApps and bundles belong to their developers. Those scripts fall under the same SuiteScript 2.1 requirement, and developers need to update their solutions and roll the updates out to customers before 2028.2. Managed SuiteApps receive updates from the developer, while unmanaged apps require your team to install the updated version. Ask each vendor for its 2.1 timeline and track it in your migration plan.
Claim Your Free NetSuite Assessment
.png?width=500&height=500&name=NetSuite%20%20500x500%20(9).png)
Where SuiteScripts Run in Manufacturing and Distribution Accounts
Manufacturers and distributors often rely on SuiteScripts for processes that standard NetSuite configuration does not handle on its own. Scripts in these accounts frequently support:
- Pricing logic: Customer-specific pricing, contract pricing, and quantity breaks calculated on quotes and sales orders.
- Order approvals and validation: Credit holds, margin checks, and required-field rules applied before orders release.
- Fulfillment and inventory: Allocation rules, lot and bin assignments, and shipping updates.
- EDI processing: Inbound purchase orders and outbound acknowledgments, advance ship notices, and invoices.
- Integrations: RESTlets that exchange orders, inventory, and customer data with ecommerce platforms, warehouse systems, and third-party logistics providers.
- Financial automation: Custom GL entries, commission calculations, and scheduled reconciliation jobs.
Many of these scripts run in the background, so users may not know that a script controls part of their workflow until the process breaks. Integration scripts carry added risk because a change in output can affect connected systems outside NetSuite. Our NetSuite Data Integration Services page covers how Snapshot designs and maintains these connections.
Choosing the Right Migration Path for Each Script
NetSuite's "Choosing a Migration Path" guidance outlines the following preparation steps: inventory scripts and customizations, identify each script's version and type, choose an update option, convert or test in a sandbox, review generated or converted code, and validate behavior and deployment metadata. Each script follows one of four paths:
Test and Update 2.0 and 2.x Scripts
NetSuite provides two account-level preferences under Setup > Company > Preferences > General Preferences: Execute SuiteScript 2.x Server Scripts as 2.1, and Execute SuiteScript 2.0 Server Scripts as 2.1. These preferences run matching server scripts in the account on the 2.1 runtime without code changes, although scripts that NetSuite does not support or recognize as compatible with 2.1 continue to run as 2.0. Enable them in a sandbox or Release Preview account, confirm the Execute As Version on each script record, test your processes, and switch back to 2.0 while fixing any script that fails. Scripts that pass still need their annotation changed to @NApiVersion 2.1, and client scripts fall outside these preferences and need separate testing.
Convert SuiteScript 1.0 Scripts
Converting a SuiteScript 1.0 script involves rebuilding its logic with 2.1 modules, entry points, and API calls, using NetSuite's ”Converting a SuiteScript 1.0 Script to a SuiteScript 2.x Script” documentation as a reference. NetSuite also offers a SuiteScript Upgrade agent skill, part of its SuiteCloud Agent Skills, to assist with conversion. The output still requires developer review and full testing before deployment.
Retire or Replace Unused Scripts
NetSuite lists retirement as one of three recommended options for inactive, obsolete, or duplicated scripts, and each retired script comes out of the migration scope entirely. Some active scripts can also be replaced with native NetSuite features, workflows, or configuration that now covers the same requirement.
Coordinate with SuiteApp Vendors
SuiteApp and bundle scripts update on each developer's schedule, so your role is to confirm each vendor's 2.1 timeline and install updated versions of unmanaged apps as they release. Add each vendor commitment to your migration plan so you can test their updates alongside your own scripts.
Claim Your Free NetSuite Assessment
.png?width=500&height=500&name=NetSuite%20Native%20AI%20(6).png)
Testing and Validating Migrated Scripts
A script can load without errors and still produce a different result under the 2.1 runtime. NetSuite documents known behavior changes in its "Differences Between SuiteScript 2.0 and SuiteScript 2.1" topic, and your developers should review each affected script against it before deployment. Validation should cover:
- Business-process regression testing: Run the full transaction flow, such as quote to order to fulfillment to invoice, and compare results with production.
- Integration testing: Confirm connected systems receive the same data, formats, and responses they received before the change.
- Entry-point testing: Exercise each event the script handles, including record loads, saves, scheduled runs, and RESTlet calls.
- Phased deployment: Release migrated scripts in batches grouped by business process so issues are easy to isolate.
- Post-deployment monitoring: Review execution logs and downstream results after each release.
How Snapshot Supports Your SuiteScript 2.1 Migration
Snapshot’s free 60-minute NetSuite assessment includes a high-level discussion of your SuiteScript exposure, and the written summary you receive afterward outlines a recommended path forward. It gives you a starting point for scoping migration work before you commit to it.
Script Inventory and Prioritization
Snapshot inventories every affected script, maps its dependencies and ownership, and ranks the work by business impact. Each script receives a recommended path: test and update, convert, retire, or vendor follow-up.
Testing, Conversion, and Deployment
Our NetSuite development team converts and updates scripts, tests them in your sandbox against your business processes, and deploys approved changes in phased releases. Every change ships with documentation of what changed and why.
Ongoing Support and Managed Services
After migration, Snapshot can keep your customizations current through NetSuite’s twice-yearly releases as part of our NetSuite Support and Managed Services. New scripts we build for you use SuiteScript 2.1 wherever NetSuite supports it.
Why Work with Snapshot for Your SuiteScript 2.1 Migration
NetSuite Alliance Partner with long-term experience
Snapshot has been in business for more than 25 years and a NetSuite Alliance Partner for over 12 years, bringing deep platform knowledge and real-world consulting experience across more than 500 accounts served.
Development and integration expertise
Our team builds and maintains SuiteScript customizations and the integrations that depend on them, so we test migrated scripts against the full processes they support.
Practical and execution focused
We prioritize usability, adoption, and measurable operational outcomes over theoretical ERP design.
Long-term partnership mindset
Our engagements are designed to support continuous improvement as NetSuite introduces platform changes and your business needs evolve.
Claim Your Free NetSuite Assessment
.png?width=500&height=500&name=ERP%20Optimization%20500x500%20(90).png)