1. SuiteCloud Platform
  2. SuiteScript
  3. Transitioning To SuiteScript 2.1
  4. Transitioning To SuiteScript 2.1

Transitioning To SuiteScript 2.1

SuiteScript 2.1 is now the standard scripting model for new and existing NetSuite customizations. This guide provides the information you need to transition your scripts to SuiteScript 2.1. It outlines the transition timeline, migration and conversion options, testing and rollout recommendations, solutions to common issues, and answers to frequently asked questions.

What is Changing?

Support for legacy SuiteScript versions and annotation values including SuiteScript 1.0, SuiteScript 2.0, and scripts annotated with @NApiVersion 2.0 or @NApiVersion 2.x, is expected to be removed in NetSuite 2028.2. This change improves performance, strengthens security, and aligns SuiteScript with modern JavaScript capabilities.

Transition Timeline

The removal of legacy SuiteScript versions and annotation values will occur through a phased rollout. Review the following timeline to understand upcoming changes to help you plan and complete your transition to SuiteScript 2.1.

NetSuite Release

Change

2026.2

SuiteScript 2.1 becomes the standard scripting model for new and existing scripts.

2027.1

SuiteScript 1.0 enters end-of-life support, covering critical issues only. Other problems will require you to convert scripts to SuiteScript 2.1 first.

2028.1

SuiteScript 1.0 scripts can no longer be deployed in new accounts but remain deployable in existing accounts. SuiteScript 2.0/2.x scripts run as SuiteScript 2.1 by default.

2028.2

All new and existing scripts must use SuiteScript 2.1.

Why is This Change Happening?

SuiteScript 2.1 uses a newer JavaScript standard and provides a more modern development model.

SuiteScript 2.1 supports:

  • Modern language features - Use features such as let, const, arrow functions, spread operators, and async/await to write clearer code.

  • Improved performance - Use a more current scripting model that supports efficient execution and resource usage.

  • Enhanced security - Align scripts with updated standards for data access, integrations, and platform behavior.

  • Ongoing support - Prepare for future enhancements, fixes, and platform capabilities focused on SuiteScript 2.1.

What This Means For Your Scripts

You should use SuiteScript 2.1 for new scripts whenever possible. If a feature or product area still requires an older SuiteScript version, follow the version requirements documented for that feature until related help content is updated.

You should also review existing scripts that use SuiteScript 1.0, SuiteScript 2.0, or the @NApiVersion 2.0 or @NApiVersion 2.x annotation values. Update those scripts to SuiteScript 2.1 as part of regular maintenance, enhancement work, or migration planning.

When reviewing a legacy script, decide whether to:

  • Update the script to SuiteScript 2.1.

  • Test its compatibility with the SuiteScript 2.1 runtime before updating it.

  • Retire the script if it is inactive, obsolete, or duplicated.

For more information about updating existing scripts, see Choosing a SuiteScript 2.1 Migration Path.

Recommended Actions

The following list provides information about how to start updating your existing scripts to SuiteScript 2.1.

  1. Identify existing scripts - Create an inventory of scripts that are not already using SuiteScript 2.1. In NetSuite, you can review script records and filter scripts by version to help identify scripts that use SuiteScript 1.0, 2.0, or the @NApiVersion 2.0 or @NApiVersion 2.x annotation values.

  2. Prioritize critical customizations - Start with scripts that support critical business processes. Give higher priority to high-usage scripts, integrations, and scripts with complex dependencies. Lower-priority scripts can be reviewed later, and inactive or obsolete scripts should be evaluated for retirement instead of migration.

  3. Choose an update approach - Review the available update options to determine the best path for each legacy script or customization. For more information, see Choosing a SuiteScript 2.1 Migration Path.

  4. Test before deployment - Validate script behavior in a suitable test environment before deployment. Compare the SuiteScript 2.1 version with the original script behavior and complete testing for the affected process.

  5. Plan a phased rollout and monitor results - Move scripts to SuiteScript 2.1 in manageable groups rather than changing everything at once. After deployment, monitor script execution and performance before proceeding with the next group.

SuiteScript 2.1 is the standard for new and updated scripts. Begin moving legacy scripts to SuiteScript 2.1 now to reduce risk, improve maintainability, and prepare for future NetSuite platform changes.

Related Topics

General Notices