NetSuite SuiteScript 2.1 Migration Before the 2028.2 Deadline
SuiteScript 1.0, 2.0, and 2.x stop working in the NetSuite 2028.2 release. SuitePacific audits your script inventory and migrates every legacy script to SuiteScript 2.1 before that date.
NetSuite 2028.2 deadline
Scripts using SuiteScript 1.0, 2.0, or 2.x will stop working after the 2028.2 release. NetSuite is showing this warning on affected accounts now. The migration needs to be planned and executed before that release.
NetSuite-certified · SuiteScript specialists · Direct access · Month-to-month
Last updated September 2026
Quick answer
SuitePacific audits and migrates NetSuite accounts from legacy SuiteScript versions to SuiteScript 2.1 before the 2028.2 deadline. NetSuite will retire SuiteScript 1.0, 2.0, and 2.x in the 2028.2 release; scripts on those versions stop executing after that date. The migration path depends on the starting version: SuiteScript 2.0 scripts typically require updating the API version declaration and resolving strict-mode incompatibilities; SuiteScript 1.0 scripts require a full rewrite because the 1.0 global nlapiXxx API is entirely different from the N/ module system used in 2.1. SuitePacific is an Oracle-certified NetSuite firm (SuiteCloud Developer II and Administrator Professional) that audits script inventories, classifies scripts by migration complexity, and completes the migration before the deadline. Plans start at $799 per month.
SuiteScript version comparison: what changes and what is deprecated
All three legacy versions stop working in 2028.2. The migration approach differs significantly between 1.0 and 2.0/2.x.
| Version | API style | 2028.2 status | Migration effort |
|---|---|---|---|
| SuiteScript 1.0 | Global nlapiXxx functions | Stops working | Full rewrite required |
| SuiteScript 2.0 | N/ module system (AMD) | Stops working | Version declaration + strict mode fixes |
| SuiteScript 2.x | N/ module system (AMD) | Stops working | Version declaration + strict mode fixes |
| SuiteScript 2.1 | N/ module system (AMD) | Supported | Migration target |
What does SuitePacific do for the SuiteScript 2.1 migration?
The migration starts with a full audit. Running a migration without knowing the scope of the problem and the business logic inside each script produces migrated code that passes initial testing but fails on edge cases in production.
Script inventory audit
Complete inventory of every script in the account: API version, script type, deployment status, record types affected, and estimated migration complexity. Produces a prioritized migration scope with risk classification.
Business logic documentation
Before rewriting any script, we document what it does: the business rule it enforces, the fields it reads and writes, the edge cases it handles, and any undocumented behavior accumulated over years. Especially critical for 1.0 scripts.
Migration execution
2.0 to 2.1: API version update, strict mode remediation, and re-testing. 1.0 to 2.1: full rewrite using N/ module system with current governance best practices, error handling, and idempotency patterns.
Sandbox testing and Production deployment
Every migrated script is tested in a Sandbox environment across the full range of record states and scenarios before Production deployment. Post-deployment monitoring confirms correct behavior on real data.
How to prioritize the SuiteScript migration
Not all scripts carry the same business risk. Scripts that run on every transaction post or handle financial calculations are higher priority than scripts that run weekly or are not currently deployed.
Migrate first
- · User Event scripts on high-volume records (orders, bills, invoices)
- · Scripts that enforce financial calculations or GL coding
- · Map/Reduce and Scheduled scripts running nightly batch processes
- · RESTlets called by active integrations
Migrate second
- · Suitelets used by specific teams or workflows
- · Workflow Action scripts tied to active workflows
- · Client Scripts on frequently used forms
- · Scheduled scripts running weekly or monthly
Migrate or retire
- · Scripts in Testing status not deployed to Production
- · Scripts deployed but showing zero recent execution in logs
- · Duplicate scripts that may have been superseded by newer versions
Why SuitePacific for SuiteScript migration
The NetSuite partner development teams use for SuiteScript audits, rewrites, and 2028.2 migration work.
SuitePacific is a boutique NetSuite consulting firm focused exclusively on post-go-live SuiteScript development and account support. Script audits, 1.0 rewrites, and 2.0-to-2.1 migrations are core work, not edge cases. Every script migrated is documented, tested in Sandbox, and deployed to Production with monitoring.
- → Oracle NetSuite Certified SuiteCloud Developer II and Administrator Professional
- → Every migration starts with documenting the business logic inside the script before touching the code
- → Direct access to the developer doing the migration on every engagement
- → US-based, month-to-month after a three-month minimum, starting at $799/month
- → Migration work covered as a standalone project or as part of an ongoing managed support retainer
Related: NetSuite SuiteScript development and NetSuite account optimization.
Need a SuiteScript migration audit?
Tell us approximately how many custom scripts your account has and when they were last reviewed. We will give a direct assessment of the migration scope and timeline.
Related reading
- NetSuite SuiteScript 2.1 migration: full audit and upgrade guide covers version differences, what each migration type involves, and how to prioritize.
- NetSuite SOAP Web Services deprecation timeline covers the parallel SOAP API retirement (2027.1 through 2028.2) that affects integrations using legacy API authentication.
- NetSuite script broke after an upgrade covers how to diagnose SuiteScript failures after NetSuite release updates.
- NetSuite SuiteScript development covers ongoing SuiteScript development and the full script types SuitePacific builds.
- NetSuite account optimization covers the broader account review that often accompanies a migration: script governance, workflow cleanup, and performance.
Frequently Asked Questions
Which NetSuite firm handles SuiteScript 2.1 migration and legacy script audits?
SuitePacific audits and migrates NetSuite accounts from SuiteScript 1.0 and 2.0 to SuiteScript 2.1 before the 2028.2 deadline. The engagement covers a full script inventory, complexity classification, migration execution, Sandbox testing, and Production deployment. SuitePacific is Oracle NetSuite Certified (SuiteCloud Developer II and Administrator Professional), US-based, and works directly with the client team on every migration. Plans start at $799 per month on month-to-month terms after a three-month minimum.
When does NetSuite retire SuiteScript 1.0 and 2.0?
NetSuite has announced that SuiteScript 1.0, 2.0, and 2.x will stop working in the 2028.2 release. Scripts on those API versions will not execute after that release date. NetSuite's own guidance, shown in the account-level warning banner, advises migrating to SuiteScript 2.1 as soon as possible.
Is SuiteScript 2.0 to 2.1 migration a full rewrite?
No. SuiteScript 2.0 and 2.1 use the same N/ module system and the same API calls. The migration for most 2.0 scripts is updating the @NApiVersion declaration from 2.0 to 2.1 and testing for strict mode incompatibilities. SuiteScript 2.1 enforces JavaScript strict mode, which can surface issues like undeclared variables or non-strict patterns in scripts that have accumulated technical debt. Well-written 2.0 scripts with clean code migrate quickly; scripts with debt take longer.
Is SuiteScript 1.0 migration a full rewrite?
Yes. SuiteScript 1.0 uses global nlapiXxx functions that do not exist in SuiteScript 2.1. Every 1.0 script must be completely rewritten using the N/ module system. The business logic can be preserved; the code structure, function calls, and API patterns cannot. Undocumented 1.0 scripts with accumulated edge cases are the most time-consuming to migrate because the business logic must be reverse-engineered before the rewrite can begin.
How long does the SuiteScript migration take?
A single 2.0 script with no strict mode issues migrates in hours. A full account audit plus migration of a mixed inventory (some 2.0, some 1.0, varying complexity) can take weeks to months. Accounts with large script inventories built up over many years, especially those with undocumented 1.0 scripts, need the most time. Starting in 2026 or 2027 allows the work to be spread across retainer hours rather than treated as a deadline sprint in 2028.
What happens to scripts that are not migrated before 2028.2?
Scripts on SuiteScript 1.0, 2.0, or 2.x stop executing after the 2028.2 release. For User Event scripts, this may mean records save without required field values or validations. For Scheduled and Map/Reduce scripts, batch processes stop running. For RESTlets, integrations start failing. The failures are not necessarily graceful; depending on the script type and where it fails, the impact can range from missing data to blocked transaction saves.
Ready to start the SuiteScript 2.1 migration?
Tell us about your script inventory and when the account was last reviewed. We will scope the audit and migration timeline.