NetSuite SuiteScript 2.1 requirement: What the 2028.2 deadline means for your custom scripts

NetSuite is moving all new and existing custom scripts to SuiteScript 2.1. SuiteScript is NetSuite’s scripting framework used to customize and automate the platform. If your organization uses older SuiteScript versions, you may already have received a notification from NetSuite warning that your account contains scripts that could be affected. SuiteScript 2.1 became the standard scripting model with NetSuite 2026.2, beginning a phased transition away from SuiteScript 1.0, SuiteScript 2.0, and scripts using older 2.x version annotations.

The final deadline is NetSuite 2028.2, when affected custom scripts must use SuiteScript 2.1 to continue running. However, important changes begin before then, making it important to understand your environment early. In this article, we explain what NetSuite announced, which scripts are affected, the transition timeline, what the change could mean for your business, and how to prepare. Organizations with significant NetSuite customizations should begin reviewing their scripts now so they have time to assess, update, and test them before the final deadline.

What did NetSuite announce about SuiteScript 2.1?

NetSuite announced that SuiteScript 2.1 is now the standard scripting version for new and existing customizations. Through a phased transition ending with NetSuite 2028.2, NetSuite is retiring SuiteScript 1.0, SuiteScript 2.0, and older 2.x version annotations. By the 2028.2 release, legacy SuiteScript versions will no longer be available to run.

The requirement applies to existing customizations as well as new development. NetSuite recommends reviewing scripts that use SuiteScript 1.0, SuiteScript 2.0, @NApiVersion 2.0, or @NApiVersion 2.x and preparing them for SuiteScript 2.1 before the final deadline.

If you received a notification from NetSuite, it does not mean your customizations are failing today. It means your account may contain older scripts that will be affected as support and runtime behavior change over the next several releases. The phased timeline gives organizations time to identify, test, update, or retire affected scripts before they can disrupt business processes.

Why is NetSuite making this change?

SuiteScript 2.1 uses a newer JavaScript runtime and supports more modern development capabilities than earlier SuiteScript versions. NetSuite says the transition is intended to improve script performance, strengthen security, modernize the development model, and prepare customizations for future platform changes.

SuiteScript 2.1 is also becoming the foundation for future SuiteScript development. Moving customizations to the current scripting model gives developers access to newer language features, APIs, and ongoing enhancements while reducing reliance on scripting versions NetSuite is retiring.

Which NetSuite scripts are affected?

The SuiteScript 2.1 requirement applies to older custom scripts already running in NetSuite, not just new development. NetSuite specifically identifies the following scripts and version annotations as part of the transition:

• SuiteScript 1.0 scripts
• SuiteScript 2.0 scripts
• Scripts using @NApiVersion 2.0
• Scripts using @NApiVersion 2.x
• Existing customizations built on any of these versions

Not every affected script will require the same amount of work. SuiteScript 2.0 and SuiteScript 2.1 use largely the same SuiteScript API, but they run on different JavaScript engines. As a result, some SuiteScript 2.0 or 2.x scripts may work correctly with the SuiteScript 2.1 runtime after testing, while others may need changes.

SuiteScript 1.0 generally requires a more involved conversion because SuiteScript 2.1 uses a different, module-based architecture. Older functions, APIs, and dependencies may need to be replaced or reworked before the script can run correctly in SuiteScript 2.1.

For organizations with years of NetSuite customizations, the first step is understanding what is actually in the account. NetSuite administrators can identify older scripts by reviewing script records and filtering by API version. Saved searches and SuiteAnalytics Workbook can also help create a more complete inventory of scripts that still need to be reviewed.

NetSuite SuiteScript 2.1 transition timeline

NetSuite is phasing in the SuiteScript 2.1 requirement across several releases rather than making the change all at once. The timeline gives organizations time to identify affected scripts, test compatibility, complete required updates, and retire customizations that are no longer needed.

The 2028.2 release is the final deadline, but 2028.1 is an important checkpoint for organizations using SuiteScript 2.0 or 2.x. Because those scripts are scheduled to run with the SuiteScript 2.1 runtime by default, compatibility issues could surface before the final requirement takes effect.

This phased timeline makes early testing important. Organizations that identify compatibility issues before 2028.2 will have more time to update affected scripts without waiting until the final deadline.

What does the SuiteScript 2.1 requirement mean for your business?

SuiteScript is NetSuite’s scripting framework for extending and customizing the platform. It allows organizations to automate tasks, apply business rules, connect systems, and tailor NetSuite to support processes that standard functionality may not fully address.

Many SuiteScripts work behind the scenes. Employees may rely on a customized process every day without realizing that a script is controlling part of the workflow, validating data, moving information between systems, or automating a recurring task.

Depending on how your NetSuite environment has been configured, SuiteScripts may support:

• Custom workflows and automation
• Transaction processing and business logic
• Custom forms and user interactions
• Data imports, exports, and processing
• Third-party integrations
• Financial and operational processes
• Approval workflows
• Scheduled and recurring processes
• Other account-specific customizations

These customizations can deliver significant value by reducing manual work, improving consistency, and helping NetSuite fit the way your organization operates. That also means some scripts can become closely tied to important business processes over time.

The SuiteScript 2.1 requirement creates risk when an older script supports a process your business depends on. If that script stops running or behaves differently under the SuiteScript 2.1 runtime, the related workflow, integration, transaction, or automated process may also be affected.

The potential impact will vary by organization. A company with a few simple customizations may have a relatively limited transition, while a business with years of custom development, multiple integrations, or industry-specific functionality may have a much larger dependency on legacy scripts.

For that reason, the number of affected scripts does not tell the full story. Organizations also need to understand what each script does, which processes rely on it, how critical those processes are, and whether the script interacts with other customizations or systems.

The key business priority is to identify where legacy SuiteScripts create operational dependencies before upcoming NetSuite releases change how those scripts are supported and executed. This gives organizations time to address the most important customizations before they can affect day-to-day operations.

Does every legacy SuiteScript need to be rewritten?

No. Every affected script should be reviewed, but not every legacy SuiteScript will need to be completely rewritten. The right approach depends on the script version, how it is used, and whether it works correctly with the SuiteScript 2.1 runtime.

NetSuite outlines three main paths for older customizations:

• Test the script for SuiteScript 2.1 compatibility
• Update or convert the script to SuiteScript 2.1
• Retire the script if it is inactive, obsolete, or duplicated

SuiteScript 2.0 and 2.x server scripts may require less work. NetSuite allows organizations to test these scripts with the SuiteScript 2.1 runtime before changing the version annotation. If a script performs correctly, it may only need a limited update before it can be moved to SuiteScript 2.1.

Client scripts follow a different process. Because they run in the user’s browser, they can’t be tested with the SuiteScript 2.1 runtime option. To test a client script with SuiteScript 2.1, organizations will need to update the version annotation and test the script directly.

SuiteScript 1.0 often requires a more involved conversion. SuiteScript 2.1 uses a module-based architecture, while SuiteScript 1.0 relies on older global functions. As a result, some functions, APIs, and dependencies may need to be replaced or redesigned.

The goal should not be to rewrite every legacy script automatically. Organizations should determine the right path for each customization based on its version, complexity, business importance, dependencies, and compatibility with SuiteScript 2.1.

What should NetSuite customers do before the 2028.2 deadline?

NetSuite customers should begin preparing for the SuiteScript 2.1 requirement by understanding their current customizations and creating a plan for the scripts that need attention. NetSuite recommends identifying legacy scripts, prioritizing business-critical customizations, selecting the right update path, testing changes, and rolling updates out in manageable phases.

A high-level SuiteScript 2.1 readiness plan should include:

1. Identify affected custom scripts: Determine where SuiteScript 1.0, SuiteScript 2.0, and 2.x annotations are still being used.
2. Determine which customizations still matter: Separate active and business-critical scripts from inactive, obsolete, or duplicated customizations.
3. Assess SuiteScript 2.1 compatibility: Determine which scripts can move to SuiteScript 2.1 with limited changes and which require more development work.
4. Prioritize critical business processes: Address scripts that support finance, integrations, order processing, automation, and other important workflows first.
5. Update or convert affected scripts: Move required customizations to SuiteScript 2.1 using the appropriate approach for each script.
6. Test before production deployment: Confirm that both the updated script and the business process it supports continue to work as expected.

Testing is an important part of the transition. NetSuite recommends validating updated scripts in a sandbox or other suitable test environment before deployment and comparing their behavior with the existing customization. Testing should confirm that the script continues to support the records, data, integrations, and processes that depend on it.

Organizations do not need to manage the SuiteScript 2.1 review and conversion entirely in-house. An experienced NetSuite partner can help inventory legacy scripts, identify dependencies, prioritize important customizations, complete required development work, and test changes before they reach production.

Why you should not wait until 2028 to update SuiteScript

NetSuite 2028.2 is the final deadline, but waiting until then can create unnecessary risk. Earlier milestones begin changing SuiteScript support and runtime behavior before the final requirement takes effect, giving organizations a limited window to identify and address issues in advance.

Many NetSuite environments also contain more custom code than current teams realize. Scripts may have been created over several years by internal developers, previous NetSuite partners, third-party vendors, or software providers. Some may still support important processes, while others may be outdated or no longer needed.

Dependencies can make the transition more complex than simply changing a script version. A legacy SuiteScript may connect to another customization, integration, custom record, or business process, so updates need to be tested in the context of how the organization actually uses NetSuite.

Starting early gives teams time to prioritize critical scripts, resolve compatibility issues, retire unnecessary customizations, and test changes in manageable phases. This reduces the chance of rushed development work or business disruption as the 2028.2 deadline approaches.

Partner with Rand Group for your SuiteScript 2.1 transition

Preparing for SuiteScript 2.1 requires more than identifying which scripts use an older version. Organizations also need to understand what those customizations do, which business processes depend on them, and how updates can be made without disrupting day-to-day operations.

Rand Group is an award-winning Oracle NetSuite Alliance Partner with decades of business technology experience and a 90% client retention rate. Our NetSuite team combines technical development expertise with accounting, finance, and business process knowledge, helping organizations address the code itself while also understanding the processes that depend on it.

For the SuiteScript 2.1 transition, Rand Group can help with:

• SuiteScript inventory and readiness review: Identify legacy scripts and determine which customizations require attention.
• Customization and dependency assessment: Understand what each script supports and prioritize business-critical processes.
• SuiteScript 2.1 conversion and development: Update SuiteScript 1.0, 2.0, and 2.x customizations where development changes are required.
• Compatibility and regression testing: Confirm updated scripts and related business processes continue to work as expected.
• Ongoing NetSuite development and support: Maintain customizations, integrations, automation, and other NetSuite functionality as the platform and your business evolve.

A SuiteScript 2.1 review can also create an opportunity to simplify an older NetSuite environment. When Unified Women’s Healthcare came to Rand Group, its NetSuite environment included complex scripting, limited documentation, and inefficient accounting processes. Rand Group reviewed the existing setup, simplified scripts, improved documentation, restructured parts of the system, and expanded automation. The result was more streamlined accounting processes, improved data accuracy, and more than 1,500 hours saved annually through automation.

What our clients say about us

“The level of care, thoughtfulness, and in-depth knowledge provided by Rand Group exceeded our expectations. We now have a partner who not only understands NetSuite but also comprehends the intricacies of accounting and finance. Rand Group has become an extension of our internal technical team, providing invaluable support as we continue to grow.”
– Carolina Pereira, VP of Finance Shared Services, Unified Women’s Healthcare

“Rand Group felt like part of our team, not a group that was there just to get the project done and move on. We wanted to build the environment the right way the first time, and they helped us customize NetSuite for requirements that were important to us.”
– Laza Assany, Controller, Henry Resources LLC

NetSuite SuiteScript 2.1 FAQs

Prepare your NetSuite customizations for SuiteScript 2.1

The SuiteScript 2.1 transition is already underway, and waiting until NetSuite 2028.2 can leave less time to address compatibility issues. Reviewing your customizations now gives your organization time to identify affected scripts, prioritize critical processes, and complete updates and testing in a controlled way.

Rand Group can help you assess legacy SuiteScripts, understand dependencies, update or convert affected customizations, and test the processes that rely on them. Contact us today to prepare your NetSuite environment for the SuiteScript 2.1 transition and reduce the risk of disruption as upcoming release changes take effect.