Book a Free Consultation

NetSuite 2028.2 confirmed deadline: Oracle NetSuite has confirmed that SuiteScript 1.0, 2.0, and 2.x scripts will stop working in the 2028.2 release.

SuiteScript Migration Readiness

NetSuite 2028.2 SuiteScript Readiness Checklist

Use this checklist to verify how prepared your NetSuite account is for the 2028.2 SuiteScript deadline. Ten questions covering script inventory, process dependencies, testing environment readiness, and migration scope. Each question includes context explaining why it matters and what to check.

Ready to plan

8 or more yes answers and all critical questions answered yes.

Action needed

5-7 yes answers, or one critical question answered no.

Start now

Fewer than 5 yes answers, or two or more critical gaps.

Free SuiteScript 2.1 Readiness Check

Want Help Reviewing Your Readiness?

Not sure which scripts are affected? Request a free initial SuiteScript check. We will understand your current situation and help you determine the right next step.

No obligation. We will discuss your situation before requesting any account access.

The 10-question SuiteScript 2028.2 readiness checklist

Review each question and select your answer. A "no" answer is not a crisis; it is a gap to close before the migration begins. Critical items represent questions where a "no" answer creates the most operational risk after the 2028.2 upgrade. Your result updates automatically as you answer.

1

Have you identified whether the account contains SuiteScript 1.0, 2.0, or 2.x scripts?

Critical

Go to Customization > Scripting > Scripts and check the API Version column. Look for scripts showing 1.0, 2.0, or 2.x. This list may not show library files or scripts installed through bundles.

2

Have you identified which of those scripts are actively deployed to Production?

Critical

A script that is not deployed to Production carries lower immediate risk. Use the Deployments column to filter for active Production deployments on legacy-version scripts.

3

Do you know who owns or originally built each legacy script?

High

Scripts built by former employees, previous implementation partners, or third-party developers may contain undocumented business logic. Owner identification is required before conversion work can begin.

4

Have you reviewed whether any legacy scripts share library files?

High

A single shared library file referenced by multiple scripts can affect every dependent script if it contains compatibility issues. Library files must be identified and reviewed as part of the migration scope.

5

Have you mapped which critical business processes depend on legacy scripts?

Critical

Sales order saves, invoice generation, fulfillment, approval routing, batch jobs, and integrations are the highest-risk areas. Scripts controlling these processes must be migrated first.

6

Have you identified scripts installed through bundles or third-party SuiteApps?

High

Scripts distributed through managed bundles may be locked or controlled by the SuiteApp provider. If the files cannot be modified, the provider must release a SuiteScript 2.1-compatible update. Unlocked or unmanaged bundle components should be reviewed separately.

7

Does the account have a Sandbox or suitable non-production environment available for testing?

Critical

Testing in a Sandbox or suitable non-production environment is strongly recommended before converted scripts are deployed to Production. Without a suitable testing environment, validation may need to happen in Production, creating significant operational risk.

8

Do test cases exist for the business processes that legacy scripts support?

Medium

Test cases document what must be verified after conversion. Without them, testing relies on memory and may miss edge cases. Critical processes should have documented test scenarios before conversion begins.

9

Are business process owners available to review and confirm converted scripts before Production deployment?

Medium

User acceptance testing by the people who run the processes is the most effective way to confirm a converted script behaves correctly. If business users are unavailable, the migration team cannot confirm business-level accuracy.

10

Has a migration timeline been discussed or approved that completes before the 2028.2 upgrade window?

High

The 2028.2 upgrade typically releases in late 2028. Accounts with large or complex script inventories need to start in 2026 or 2027 to avoid time pressure. A defined timeline ensures the work is planned rather than reactive.

What to do with your checklist results

If you are ready to plan (8 or more yes, no critical gaps)

Your account has good foundational readiness. The next step is completing the formal script inventory and risk classification to confirm the migration scope and timeline before conversion begins.

If action is needed (5-7 yes, or one critical gap)

There are meaningful gaps to close before the migration can start safely. Focus first on identifying all legacy scripts, mapping critical business processes, and confirming a testing environment. These gaps represent the highest risk if left unresolved.

If you should start now (fewer than 5 yes, or two or more critical gaps)

The migration audit should begin now. Without a script inventory you do not know the scope. Without process mapping you cannot prioritize. Without a testing environment you cannot validate safely. Starting the audit creates the visibility needed to plan the rest of the work.

If you have third-party or bundle scripts

Scripts installed through managed bundles may be locked or controlled by the SuiteApp provider. If the files cannot be modified, the provider must release a SuiteScript 2.1-compatible update before the 2028.2 deadline. Unlocked or unmanaged bundle components should be reviewed as part of the standard audit.

Ready to start the SuiteScript compatibility audit?

SuitePacific identifies every legacy script in your account, classifies each by business risk, and produces a migration scope and estimate before any conversion work begins.

Request a Free SuiteScript Check

SuiteCloud Developer II certified · Sandbox-first delivery · Month-to-month from $799

Last updated September 2026

Related reading