In 2028, to ensure your company’s NetSuite stays up and running.
NetSuite's "3. Phase-out of Major Technologies" Overcoming Challenges Full Migration and System Refresh Support Services

According to NetSuite’s official announcement, legacy SuiteScript (1.0/2.0/2.x), SOAP communication, and TBA authentication will be completely discontinued in the fall of 2028. As a result, all non-compliant core systems and data integrations will cease to function. The deadline for compliance is not 2028. To avoid a global shortage of engineers caused by a last-minute rush and soaring costs due to rush fees, it is essential to begin work in “early 2027 (Q1).”

100% Coverage

From code modification to operation guarantee

Zero Downtime

Safe switchover via parallel testing

Early Access

Special support for early 2027 adoption

● ● ●   netsuite-risk-audit.json 

Impact Level: Urgent

SuiteScript Engine                                         1.0 / 2.0 / 2.x

2028.2 Execution Engine Full Shutdown

※ Note: @NApiVersion 2.x is treated as legacy 2.0 and will be stopped.

SuiteTalk Web Services                                 SOAP WSDL

2027.1 New Creation Blocked / 2028.2 Calls Blocked

※ External integrations such as orders and inventory will halt..

Authentication Protocol                     TBA (OAuth 1.0a)

2027.1 Issuance Stopped / 2028.2 Auth Errors

※ Transition to OAuth 2.0 M2M authentication is mandatory.

Assess your account risk:                  

Understanding the "3 Major Technical Deprecations"

For NetSuite 2028.2, the three core areas that form the foundation of the system
「script execution framework」「external API communication」「authentication methods」will be completely overhauled.
This will require a comprehensive system-wide response, rather than just isolated fixes.

2028.2 Legacy Engine Shutdown

Complete Migration to SuiteScript 2.1

Legacy JavaScript execution engines (1.0 / 2.0 / 2.x) will be shut down completely. Syntax checks are stricter in 2.1, meaning existing legacy code carries a high risk of unexpected runtime errors.

2.x Pitfall: Scripts with @NApiVersion are treated as legacy 2.0 and will be stopped.
Array Indexing Changes: Array line numbers switch from 1-based to 0-based indexing.
Legacy Functions Removed: 1Old 1.0 nlapi functions are deprecated; redesign into Map/Reduce is required

Affected Areas:
Internal Workflows, Custom Screens, Automated Batch Processing

2027.01 New Creations Blocked

Deprecation of SOAP Web Services

XML-based SOAP communications used for years will be retired, blocking external connections. Rebuilding integration architecture using REST APIs or high-performance SuiteQL is urgently needed.

REST API Migration: Transition to lightweight, modern JSON-based communication protocols.
SuiteQL Utilization: Optimize batch data extraction via SQL queries.
API Governance: Implement proper request control to prevent concurrency limits (429 errors).

Affected Areas:
E-Commerce Platforms, WMS, External ERP/System Integrations

2027.1 New Token Issuance Ends

End of Token-Based Authentication (TBA)

Traditional fixed-key authentication (OAuth 1.0a) is being retired. Migrating to the secure OAuth 2.0 Machine-to-Machine (M2M) standard is mandatory. New integrations cannot be configured using TBA starting Spring 2027.。

Enhanced Security: Uses JWT (digitally signed tokens) to eliminate credential leak risks.
Key Management: Requires setup of public/private key pairs and routine key rotation workflows.
iPaaS Reconfiguration: Connectors on tools like Boomi, Celigo, and custom scripts must be reconfigured.

Affected Areas:
External API Communications, Automated DataSynchronization

Official System Changes Roadmap

System restrictions from Oracle NetSuite are taking effect in phases leading up to the final 2028.2 deadline.
Because new integration development is blocked starting January 2027, last-minute actions will be too late.

01

2025.2

End of SOAP API Updates

New feature updates for SOAP (WSDL) are frozen. The protocol officially entered its deprecation phase.

02

2026.2

Admin Warnings Begin

Deprecation warning banners display on all account dashboards urging migration to SuiteScript 2.1.

03

2027.2

New API & Token Freeze

Creating new SOAP integrations and issuing new TBA tokens is completely blocked. Only existing setups remain active.

★ Early 2027 Start Deadline

04

2028.2

Complete Shutdown

Legacy scripts (1.0/2.0/2.x) fail to execute. SOAP communications and TBA authentication are fully disconnected.

Final Hard Deadline

STRATEGIC TIMELINE COMPARISON

Timeline Comparison: Why "Early 2027" is Ideal ?

Optimal Start Dev Limits Begin High Resource Risk
Present – End 2026
★ Early 2027 (Q1-Q2)
Late 2027
2028 (Shutdown Year)
Audit & Prep
★ Optimal Project Window
Dev Limits & Congestion
Severe Resource Shortage

【Early 2027 Start】
Safest & Most Cost-Effective Scenario

【Recommended】Best Practices

【Late 2027 ~ 2028 Start】
Dangerous Scenario with Downtime Risks

Critical Turning Point for Project Success

Why You Must Start in "Early 2027":

3 Decisive Reasons

As the 2028 deadline approaches, rushed migration requests will flood vendors worldwide. Initiating your project early before being caught in engineer shortages and cost surges is the only reliable path to a smooth transition.

Zero Business Disruption.
Our Proven "4-Phase Migration Process"

We go beyond simple code conversion to guarantee complete business logic integrity.
Drawing on Shearwater Taiwan extensive NetSuite implementation track record,
our phased approach minimizes operational risk.

PHASE 01

Current Architecture & Code Discovery

We scan all active scripts (1.0 / 2.0 / 2.x), SOAP endpoints, and TBA usage across your account. Identifying dormant legacy scripts allows us to exclude unnecessary code and optimize overall project costs.

PHASE 02

Business Impact Evaluation & Prioritization

We assess impacts on core processes (orders, billing) and external integrations. By clearly distinguishing custom scripts from 3rd-party SuiteApps, we build a risk-free roadmap to keep daily operations uninterrupted.

PHASE 03

Code Refactoring & Auth Infrastructure Modernization

We rewrite legacy code to full SuiteScript 2.1 compliance (modularity, array indexing, Map/Reduce). We also replace deprecated SOAP endpoints with REST API / SuiteQL and implement secure OAuth 2.0 M2M protocols.

PHASE 04

Validation, Phased Cutover & Production Go-Live

We perform differential testing and external connectivity checks in sandbox environments using real operational data. With complete rollback procedures in place, we execute a safe, phased production release.

Frequently Asked Questions

Here are answers to common questions regarding SuiteScript 2.1 migration and external data communication changes (SOAP / TBA).

Q. If my script already specifies @NApiVersion 2.x, won't it automatically run on the latest version ?

No, code modification and validation are required.
In NetSuite, declaring “2.x” does not automatically switch your execution to the 2.1 engine. In most cases, scripts fall back to account defaults and execute on the legacy 2.0 engine, which will shut down in 2028.2. You must explicitly update scripts to “2.1” and conduct strict runtime testing under the new JavaScript execution engine (ES6+).

Third-party bundle scripts are locked and cannot be directly edited by users. Shearwater Taiwan identifies all installed bundles during our initial audit and assists in inquiring with vendors regarding their SuiteScript 2.1 update roadmaps. We support you all the way through applying vendor updates safely in your production environment (UAT).

No, daily operations will continue without disruption.
We perform strict differential testing in a Sandbox environment first. Once verified, refactored code is deployed to production in phases using parallel execution approaches. Immediate rollback procedures are also established in advance for absolute safety.

As the 2028 deadline nears, a flood of last-minute migration requests worldwide will cause severe NetSuite engineer shortages.
Furthermore, step-by-step restrictions begin early—such as blocking new SOAP/TBA connections starting in Spring 2027. Initiating your project in early 2027 avoids unexpected price hikes and guarantees project execution by top senior engineers.

Apply for a Free Risk Assessment & Migration Consultation

For companies uncertain about how much their NetSuite environment will be impacted, we offer a complimentary initial assessment.
We will analyze your current usage and present an optimal migration roadmap.