SuiteScript is how you extend NetSuite beyond point-and-click setup, and the ground has shifted. SuiteScript 2.1 is now the standard, Oracle has set a firm end date for older versions, and a new module lets your scripts call generative AI directly. If you run custom scripts, this update matters for two reasons: a deadline you need to plan for, and new capabilities worth using. Here is what changed and what to do about it.
What's new since this guide first published
- SuiteScript 2.1 is now the standard for new and existing customizations, not just an option.
- Older versions are being retired. Support for SuiteScript 1.0, 2.0, and generic 2.x annotations is expected to end in the 2028.2 release.
- The clock is visible. From the 2026.2 release, NetSuite shows in-app notifications about the change.
- AI is now inside SuiteScript. The N/llm module (2.1 only) lets scripts call large language models directly.
- 2.1 enforces strict mode and supports modern JavaScript, so cleaner code is the default.
What is SuiteScript 2.x?
SuiteScript 2.x is NetSuite's JavaScript-based framework for customizing and automating the platform beyond its standard configuration. It uses a modular architecture, supports object-oriented programming and asynchronous operations, and manages dependencies automatically. SuiteScript 2.1 is the current standard version, and it adds strict mode enforcement and a generative AI module.
Almost any customization you cannot do through NetSuite's setup screens is done with SuiteScript: validating a record on save, syncing data with another system, processing large batches overnight, or building a custom interface. It comes in ten script types, each with a specific trigger and purpose, such as client scripts that run in the browser, user event scripts that fire when a record is saved, scheduled and Map/Reduce scripts that run in the background, and RESTlets that expose custom endpoints for integrations.
The deadlineThe SuiteScript deprecation timeline you need to plan for
Oracle has confirmed that support for legacy SuiteScript versions, including SuiteScript 1.0, SuiteScript 2.0, and scripts annotated with the generic 2.0 or 2.x version tags, is expected to be removed in the NetSuite 2028.2 release. Starting with the 2026.2 release, NetSuite shows notifications about scripts that will stop working. The fix is to migrate those scripts to SuiteScript 2.1.
This is the single most important change for any business with custom NetSuite scripts. It is not an emergency, but it is a real deadline, and legacy scripts often run business-critical processes such as billing, inventory syncs, and reporting. The risk of waiting is discovering a broken process after support ends, rather than on your own schedule.
What this means in practice: if a script is annotated @NApiVersion 2.0 or @NApiVersion 2.x, it is on the list, even if it feels modern. Migrating to @NApiVersion 2.1 is usually a manageable change, but it needs inventorying, testing, and a plan. Two years sounds like a lot until you count how many scripts a mature account has accumulated.
A sensible migration path looks like this: inventory every script and its version tag, flag the business-critical ones, assess how much each needs to change, migrate and test in a sandbox, then roll out in phases. It pairs naturally with your normal release testing, and the 2026.2 notifications are a good trigger to start. See our NetSuite 2026.2 release guide for the wider release context.
Running scripts on SuiteScript 1.0, 2.0, or 2.x?
EPIQ can inventory your scripts, flag what must move before 2028.2, and migrate them to SuiteScript 2.1 with testing, so nothing breaks on Oracle's timeline.
Get a SuiteScript migration reviewWhy SuiteScript 2.x is better for modern businesses
Beyond the deadline, there are good reasons the 2.x line, and 2.1 specifically, is the right foundation. The benefits are practical, not academic.
Modular design for cleaner code
Instead of long, repetitive scripts, developers break logic into reusable modules. Updates are faster and safer, because a change in one module does not ripple through the others. A billing routine, for example, can be written once and reused across workflows.
Object-oriented and modern JavaScript
SuiteScript 2.1 supports modern JavaScript, including arrow functions, let and const, and classes, and it enforces strict mode. Developers used to standard JavaScript are productive quickly, and strict mode catches a category of bugs before they reach production.
Asynchronous operations
Promises and async/await let scripts handle large datasets and slow operations without blocking. A job processing thousands of records runs in the background instead of freezing the interface.
Automatic dependency management
You declare what a script needs and NetSuite loads it in the right order. That removes an entire class of manual errors that plagued SuiteScript 1.0.
Cleaner integrations
SuiteScript works with REST and SOAP, RESTlets, and external services, so NetSuite can connect to platforms like Shopify or a payment provider without brittle workarounds. When those connections break, the causes are usually predictable, which we cover in why NetSuite integrations fail and how to fix them.
The new capabilityAI inside SuiteScript: the N/llm module
The N/llm module lets SuiteScript 2.1 scripts send requests to large language models supported by NetSuite and use the responses in your code. It is available in server scripts on SuiteScript 2.1 only, and its calls consume NetSuite AI Units. This is how custom scripts can now summarize records, draft text, classify data, or extract information without an external AI integration.
This is the most forward-looking reason to be on 2.1. Instead of building and securing a separate connection to an AI provider, a developer can call generative AI natively from within a script. Practical uses include generating a plain-language summary of a customer record, drafting an item description, classifying incoming cases, or extracting fields from unstructured text. A companion N/machineTranslation module, also 2.1 only, handles AI-assisted translation.
Two things to keep in mind. First, generative AI is creative by design, so outputs should be validated where accuracy matters, especially in finance workflows. Second, these calls use AI Units, so usage has a cost worth planning for. This native AI capability is also part of the foundation for NetSuite's agentic features. For the bigger picture, see how AI is transforming SuiteScript development and where it fits in NetSuite Next.
Useful toolsPowerful SuiteScript 2.x features that save time
Several built-in modules and script types do heavy lifting that would otherwise take custom infrastructure.
- Map/Reduce scripts break large data jobs, such as nightly invoice processing, into parallel stages that run within governance limits.
- N/sftp module moves files securely between NetSuite and external servers, such as bank files or inventory feeds.
- N/cache module stores frequently used data in memory, so scripts do not reload the same values repeatedly.
- Search pagination retrieves results in chunks to avoid timeouts on large searches.
- File streaming reads and writes very large CSV files without exhausting memory.
- N/crypto module encrypts sensitive data using standard methods.
Every script type runs under governance limits that cap how much work it can do in one execution. Designing within those limits, rather than fighting them, is what separates a script that scales from one that fails at month-end volume.
Version comparisonSuiteScript 1.0 vs 2.0 vs 2.1
A quick reference for anyone comparing versions or planning a migration.
| Feature | SuiteScript 1.0 | SuiteScript 2.0 | SuiteScript 2.1 |
|---|---|---|---|
| Architecture | Functional | Modular | Modular |
| Dependency handling | Manual | Automatic | Automatic |
| Async support | Limited | Promises | Promises and async/await |
| JavaScript | Older (ES5) | Older (ES5) | Modern, with strict mode |
| Generative AI (N/llm) | No | No | Yes |
| Status | End of life | Being retired | Current standard |
| Support expected until | Removed in 2028.2 | Removed in 2028.2 | Supported |
Security, authentication, and compliance
SuiteScript runs inside NetSuite's security model. Scripts execute under a role's permissions, sensitive data can be encrypted with the N/crypto module, and role-based access controls who can do what. For audit and compliance, actions are captured in NetSuite's audit trail.
One authentication change deserves attention if you use RESTlets. Oracle has confirmed that older login methods for integrations are being retired, with NLAuth retired for integrations from the 2027.1 release and OAuth 2.0 as the standard going forward. RESTlets that still authenticate with older methods should move to OAuth 2.0. Our TBA to OAuth 2.0 migration guide explains the timeline and steps.
Two deadlines, one plan
The 2027.1 authentication change and the 2028.2 SuiteScript change both touch your customizations. EPIQ can plan them together so your team handles them once, not twice.
Talk to EPIQ's NetSuite teamHow EPIQ helps businesses modernize SuiteScript
EPIQ Infotech works with NetSuite customizations every day. For SuiteScript specifically, that means inventorying your existing scripts, migrating SuiteScript 1.0, 2.0, and generic 2.x code to 2.1 with proper testing, tuning scripts that hit governance limits, and building new automation, including AI-assisted scripts with the N/llm module. It is the work behind our NetSuite customization services, backed by ongoing support and optimization. If you want a picture of your current environment first, a NetSuite health check is a good starting point.
FAQFrequently asked questions
What is SuiteScript 2.x?
SuiteScript 2.x is NetSuite's JavaScript-based framework for customizing and automating the platform. It uses a modular architecture, supports object-oriented programming and asynchronous operations, and manages dependencies automatically. SuiteScript 2.1 is the current standard version.
Is SuiteScript 1.0 being deprecated?
Yes. Oracle has confirmed that support for SuiteScript 1.0, 2.0, and scripts using the generic 2.0 or 2.x version tags is expected to be removed in the NetSuite 2028.2 release. In-app notifications about affected scripts begin with the 2026.2 release.
What is the difference between SuiteScript 2.0 and 2.1?
Both are modular, but 2.1 supports modern JavaScript, enforces strict mode, and adds capabilities that 2.0 does not, including the N/llm generative AI module. 2.1 is the current standard, while 2.0 is being retired.
What is the N/llm module in SuiteScript?
The N/llm module lets SuiteScript 2.1 server scripts send requests to large language models supported by NetSuite and use the responses in your code, for tasks like summarizing, drafting, or classifying. Its calls consume NetSuite AI Units.
How long does a SuiteScript migration take?
It depends on how many scripts you have and how complex they are. A handful of simple scripts is quick, while a mature account with many customizations needs an inventory, a phased plan, and sandbox testing. Starting when the 2026.2 notifications appear gives you comfortable lead time before 2028.2.
Does SuiteScript 2.x support integrations?
Yes. It works with REST and SOAP, RESTlets for custom endpoints, and external services such as eCommerce and payment platforms. RESTlets should move to OAuth 2.0 authentication ahead of the 2027.1 change.
Is SuiteScript 2.x secure?
Scripts run under a role's permissions within NetSuite's security model, sensitive data can be encrypted with the N/crypto module, and actions are recorded in the audit trail. Good role design and current authentication methods are what keep it secure in practice.
Ready to get your scripts onto SuiteScript 2.1?
Whether you need to beat the 2028.2 deadline, tune scripts that hit limits, or build AI-assisted automation, EPIQ Infotech can help. Tell us what your scripts do and we will map the next step.
Get in touch with EPIQNote: SuiteScript version support timelines, the 2028.2 legacy-removal target, the 2027.1 authentication changes, and N/llm behavior are set by Oracle and can change. Confirm current specifics in your official NetSuite release notes and SuiteScript documentation. This guide is practical interpretation from EPIQ Infotech based on hands-on NetSuite customization and support experience.
Santosh Krishnamoorthy is a Principal ERP Consultant at EPIQ Infotech, with extensive experience in NetSuite and enterprise systems. He works with finance and operations teams to improve reporting accuracy, streamline workflows, and build ERP environments that support sustainable growth. His writing focuses on practical insights drawn from real implementation and support experience.
Free Consultation
Talk to a NetSuite Expert
Response within 1 hour
