NetSuite is preparing to phase out SuiteScript 1.0, 2.0 and 2.x, which means organisations will need to migrate custom scripts to SuiteScript 2.1. As organisations upgrade to NetSuite version 2026.2, users will begin seeing notifications that older script versions will eventually stop working in a future release.

If your organisation relies on NetSuite customisations, understanding the potential impact now can help you plan ahead, reduce risk and avoid unnecessary disruption. While NetSuite has not yet announced an official deprecation date, when features and functions will no longer be recommended for use and may be removed, organisations that rely on legacy SuiteScript versions should consider reviewing their customisations and planning for future upgrades.

For businesses that have invested heavily in NetSuite customisations, this change is more than a routine platform update. It provides an opportunity to review existing customisations, address technical debt and improve the long-term maintainability of their NetSuite environment.

SuiteScript evolution at a glance

Since its introduction in 2006, SuiteScript has been the foundation for custom development within NetSuite. Over time, Oracle NetSuite has introduced newer versions to align with evolving JavaScript standards and provide a more modern development framework.

The planned deprecation of older SuiteScript versions reflects NetSuite's continued focus on supported and up-to-date technologies. For organisations relying on legacy customisations, it highlights the importance of reviewing existing scripts and preparing for future upgrades.

Why organisations should act now

For many NetSuite customers, custom scripts support business-critical processes – from financial operations and reporting to inventory management and workflow automation. Once legacy SuiteScript versions are no longer supported, affected scripts may no longer function as intended.

Although the deprecation deadline has not been announced, delaying preparation can create unnecessary challenges:

• Large NetSuite environments often contain dozens or even hundreds of custom scripts.
• Script conversion requires thorough testing to ensure existing business processes continue operating effectively.
• Demand for experienced NetSuite developers may increase as the deprecation deadline approaches.

Organisations that begin planning early are likely to have greater flexibility when prioritising resources and managing the transition.

How to prepare for the transition

A successful migration starts with understanding your current NetSuite environment.

Organisations should consider:

1. Creating an inventory of existing SuiteScript customisations
2. Identifying business-critical scripts and integrations
3. Assessing the complexity of required upgrades
4. Developing a phased migration plan
5. Establishing a testing strategy before deployment.

Taking these steps early can help reduce risk and minimise pressure on internal teams responsible for supporting core business operations.

Can AI support script conversion?

Recent advancements in AI are helping organisations modernise their NetSuite environments more efficiently.

RSM’s NetSuite technical team has been evaluating the software’s AI-assisted development capabilities and AI agent skills to support the conversion of SuiteScript 1.0, 2.0, and 2.x code to SuiteScript 2.1. These tools can help accelerate the migration process by generating updated code more quickly than traditional manual approaches.

However, experienced developers remain critical to making sure upgraded scripts continue to support underlying business requirements. AI can help streamline the conversion process, but human oversight remains essential to maintain quality, reliability and business continuity.

Many organisations find that script modernisation gives them an opportunity to review their wider application architecture, integrations and automation strategies. For companies already engaged in a wider modernisation, script conversion can be a catalyst for broader enterprise application and upgrades that improve scalability, reduce technical debt and support long-term business objectives.

Support with your SuiteScript transition

Whether your organisation has a small number of custom scripts or a highly customised NetSuite environment developed over many years, a structured approach can reduce risk and support a smoother transition.

We can help organisations:

• Assess their current SuiteScript landscape
• Identify scripts that need to be fixed
• Establish a migration roadmap
• Accelerate conversions using AI-enabled tools
• Support testing and deployment
• Reduce operational disruption during the transition process.

Planning your next steps

In summary, organisations should:

• Begin planning now to enable greater flexibility when prioritising upgrades, allocating resources and testing business-critical processes before legacy versions are retired.
• While the transition to SuiteScript 2.1 may begin as a technical requirement, it can also provide opportunity to improve the health, maintainability and long-term scalability of their NetSuite environment.
• For some organisations, this may also be an appropriate time to review their broader NetSuite strategy, including integrations, automation opportunities and future platform requirements.

Need support preparing for the transition to SuiteScript 2.1?

Whether you're assessing the impact of the changes, reviewing customisations or planning a migration roadmap, our NetSuite specialists can help you take a practical, risk-based approach to the transition and ensure investment is directed towards the areas that will deliver the greatest business value. Speak to Darren Birt or your usual RSM contact.

Latest related insights