Your Legacy SuiteScripts Will Stop Working in NetSuite 2028.2

Oracle NetSuite has confirmed that SuiteScript 1.0 scripts will stop working in the 2028.2 release. NetSuite is displaying an account-level warning on affected accounts now. Customers should start the audit and conversion process well before the 2028.2 upgrade window to avoid business process failures.

SuiteScript 2.0 scripts will stop working in the NetSuite 2028.2 release alongside SuiteScript 1.0 and 2.x scripts. Many accounts contain a mix of 1.0, 2.0, and 2.x scripts. The audit should identify all three versions so the full migration scope is clear before conversion begins.

Yes. Scripts configured with the 2.x version declaration will stop working in the 2028.2 release. Scripts must be explicitly updated to 2.1 and tested for strict mode compatibility. The 2.x declaration was intended as a forward-compatibility marker; it does not provide automatic compatibility with 2.1.

NetSuite 2028.2 is the release in which Oracle plans to retire SuiteScript 1.0, 2.0, and 2.x. Scripts running on those versions will stop executing after the upgrade. Customers need to complete a script inventory, convert affected scripts to SuiteScript 2.1, test in sandbox, and deploy to production before the 2028.2 upgrade window.

Legacy scripts can be identified through the Script list at Customization > Scripting > Scripts. The API Version column shows which version each script uses. However, this list does not show library files, inactive scripts, or scripts installed through bundles and SuiteApps. A thorough audit requires checking script files, library files, and deployment records to build a complete picture.

No. SuiteScript 1.0 uses a completely different API structure (global nlapiXxx functions) that has no direct equivalent in 2.1. Every 1.0 script requires a full rewrite using the N/ module system. Automated tools cannot reliably translate business logic between the two APIs. The conversion must be performed by a developer who understands both what the original script does and how to replicate that behavior in 2.1.

No. Changing the version declaration to 2.1 tells NetSuite to run the script under the 2.1 runtime, but it does not fix incompatible code. SuiteScript 2.1 enforces strict mode, which means undeclared variables, deprecated patterns, and certain object literal forms that worked under 2.0 will throw errors under 2.1. Every script must be reviewed and tested after the version declaration is updated.

SuiteScript 2.0 and 2.1 use the same N/ module system and the same API calls. The primary difference is that 2.1 enforces JavaScript strict mode, supports ES6+ syntax (arrow functions, template literals, destructuring, let and const), and disables features forbidden in strict mode. Well-written 2.0 scripts with clean code migrate quickly. Scripts with accumulated technical debt may require additional remediation.

A single 2.0 script with no strict mode issues can be updated in hours. A full account migration covering a mixed inventory of 1.0, 2.0, and 2.x scripts across all script types typically takes weeks to months depending on script count, complexity, and the presence of undocumented 1.0 logic. The audit phase produces an accurate timeline before conversion begins.

Migration is available as part of a monthly retainer starting at $799 per month with a three-month minimum followed by month-to-month terms. The audit phase clarifies the conversion scope and produces an estimate before work begins. Larger or more complex inventories require more hours; the monthly plan determines how quickly the work is completed.

Yes. We work with scripts created by any developer, former employee, implementation partner, or independent contractor. Undocumented scripts require additional review to understand the business logic before the rewrite begins. We document the original logic as part of the migration process so the converted script can be maintained going forward.

We can identify bundle and SuiteApp scripts during the audit and flag their version status. However, scripts distributed through managed SuiteApp bundles must be updated by the SuiteApp provider. We identify which scripts fall into this category and provide guidance on what to request from the provider.

The objective of the migration is to preserve existing business processes while making scripts compatible with SuiteScript 2.1. We do not redesign functionality unless there is a specific technical reason or the customer requests an improvement. Material changes are documented. If we find unsafe or outdated logic that could cause problems, we report it separately and let you decide whether to address it during or after the migration.

Yes. Every converted script is tested in a NetSuite sandbox environment before production deployment. Sandbox testing covers all entry points, record types, approval workflows, scheduled processes, and business-critical scenarios. We also work with business users on user acceptance testing for the processes they own before the production deployment.

Yes. The risk classification phase assigns each script a business-impact tier. We can prioritize Critical and High scripts and complete those before addressing lower-priority scripts. This approach reduces immediate risk while spreading the migration across retainer months at a manageable pace.

Scripts that have not been converted to SuiteScript 2.1 will stop executing after the 2028.2 upgrade. Depending on what each script controls, the impact could include failed order saves, blocked approvals, stopped batch processes, failed integrations, missing field values, broken Suitelets, or failed scheduled jobs. Discovering these failures after the upgrade is significantly more disruptive than completing the migration beforehand.