Upgrade Path Planner

NetSuite upgrade planner: release preview, API and integration changes to 2028.2

Oracle upgrades every NetSuite account twice a year, so the work is release readiness: testing in Release Preview and clearing the platform deadlines Oracle has announced. Pick the release your scripts and integrations were last validated on and the release you are preparing for. The planner lists the documented steps (Release Preview, SuiteScript 2.1, SOAP endpoint and OAuth 2.0 changes, SuiteCommerce Advanced migration), the changes in each release you cross, and sizes risk, effort and a regression test plan from your scripts, integrations and saved searches.

Free, runs in your browser, no sign-in needed. Release data checked 2026-10 against 40 cited sources.

1Releases
SupportedVersion names give the year.
CurrentRelease notes revision dated October 19, 2026. One of two scheduled version upgrades a year.
Vendor cloud
2Landscape
What to count in NetSuite
customizations:
Script deployments (user event, client, scheduled, map/reduce, Suitelet, RESTlet), SuiteFlow workflows, custom records, custom fields, custom transactions and SDF objects. Count what you expect to touch.
integrations:
Integration records: SOAP and REST web services clients, RESTlet callers, iPaaS or connector flows, NetSuite Connector, SuiteAnalytics Connect consumers, CRM, ecommerce, 3PL and payroll.
interfaces:
CSV import jobs, bank and payment files, EDI maps, SFTP drops and scheduled file exports.
reports:
Saved searches, saved reports, SuiteAnalytics workbooks and datasets, and Advanced PDF/HTML templates.
sites:
Production NetSuite accounts upgraded separately. Subsidiaries in one OneWorld account count once.
Modules in use
Integration types
NetSuite 2025.1NetSuite 2026.2 (current)

No upgrade to run: Oracle upgrades the account on its scheduled date. The work is a Release Preview test cycle plus clearing the SuiteScript, SOAP endpoint and authentication deadlines that fall on or before the target release.

Steps
15
1 to confirm
Releases crossed
3
NetSuite 2026
Risk
45 / 100
Moderate
Effort
45-177 d
about 2-9 person-months
  1. 1
    PreparationDocumented

    Inventory scripts, workflows, integrations and SuiteApps

    List every script deployment (Customization > Scripting > Script Deployments) as the checklist Oracle's Release Preview Guide recommends. On Customization > Scripting > Scripts, use the API Version filter, or a saved search with API Version is not 2.1, to find SuiteScript 1.0, 2.0 and 2.x scripts. Add each integration record with its authentication method (TBA, OAuth 2.0 or NLAuth), its channel (SOAP, REST, RESTlet, SuiteAnalytics Connect) and, for SOAP, the WSDL version it binds to. Add installed SuiteApps, bundles and SDF projects.

    Script Deployments listScripts list (API Version filter)Saved search on script recordsSource 25Source 30Source 29
  2. 2
    PreparationDocumented

    Find the upgrade date and request a Release Preview account

    Your upgrade date is in the What's new in the Suite portlet on the production home dashboard; the current version number is at the bottom of the Home page. An Administrator opts in at Setup > Company > Release Preview > Request Release Preview, from production or from the sandbox you want to test with. Creation takes about 5 to 7 calendar days; track it in the Account Status and Account Notifications fields. The account is purged after 14 consecutive days without a login, and access ends on the day the source account is upgraded, so book testers before you request it.

    What's new in the Suite portletSetup > Company > Release PreviewSource 16Source 17Source 5
  3. 3
    PreparationDocumented

    Read the release notes for every area you use

    Read the scheduled release notes for each version you cross (SuiteScript, SuiteTalk, authentication, SuiteAnalytics, SuiteBuilder, SuiteCloud SDK and your business modules), plus the Monthly Release Notes: Oracle can ship selected enhancements in monthly releases between scheduled upgrades. Release notes change weekly; the Help Center Weekly Updates page lists the edits. SuiteApps follow their own release schedule.

    Release NotesMonthly Release NotesHelp Center Weekly UpdatesSource 1Source 2Source 3Source 4
  4. 4
    PreparationDocumented

    Move SDF deployments off SuiteCloud CLI for Java

    SuiteCloud CLI for Java reached end of support: 2025.2 is its final version and it stays downloadable only until 2027.1. Move build and deployment pipelines to SuiteCloud CLI for Node.js (4.1.0 in 2026.2), the SuiteCloud Extension for Visual Studio Code or the SuiteCloud IDE Plug-in for WebStorm.

    SuiteCloud CLI for Node.jsSuiteCloud Extension for Visual Studio CodeSource 14
  5. 5
    PreparationDocumented

    Plan two-factor authentication for all roles

    From September 21, 2026 administrators can require 2FA for all users with Employee, Vendor and Partner roles (not Customer Center roles). With 2027.1 the Require 2FA for All Roles feature is enabled automatically; an administrator can disable it. Since 2026.2 a FIDO2 passkey can act as the second factor. Brief users with shared or service logins before the change.

    Require 2FA for All RolesSource 8
  6. 6
    PreparationDocumented

    Prepare the Release Preview account for testing

    Release Preview is a separate account with a copy of configuration, data, passwords and customizations as of the Snapshot Date. Not copied: TBA tokens (create new ones for every integration you test), SAML configuration (set up SAML again), web store domains (create a unique domain), Customer Center roles, system notes, workflow history and instances, and campaign response history. Saved searches are set to inactive and email goes to the logged-in user by default; change it to Send Email To for testing. Payment processing profiles are in test mode. Scheduled scripts and scheduled workflows are copied but do not run automatically; run them manually. For SuiteAnalytics Connect, switch the Service Host to the Release Preview host (it contains rp) and switch it back afterwards.

    Release Preview email preferencesPayment Processing ProfilesSuiteAnalytics Connect Driver Download pageSource 19Source 18Source 24Source 16
  7. 7
    ConversionDocumented

    Move scripts to SuiteScript 2.1

    SuiteScript 2.1 is the standard version from 2026.2. SuiteScript 1.0 gets critical fixes only from 2027.1; from 2028.1 1.0 scripts cannot be deployed in new accounts and 2.0 or 2.x scripts run as 2.1 by default; from 2028.2 legacy versions no longer run. Test 2.0 and 2.x server scripts in the 2.1 runtime first with Setup > Company > Preferences > General Preferences (Execute SuiteScript 2.x Server Scripts as 2.1, and the 2.0 equivalent), check execution logs, then change the annotation to @NApiVersion 2.1. The preference affects server scripts only and can be set back to 2.0. SuiteScript 1.0 scripts must be rewritten. Retire inactive or duplicate scripts instead of converting them.

    Execute SuiteScript 2.x Server Scripts as 2.1@NApiVersion 2.1Script execution logSource 6Source 31Source 32Source 30
  8. 8
    ConversionDocumented

    Repoint SOAP integrations to the 2025.2 endpoint

    In the 2026.2 Help Center the supported WSDL versions are 2025.2, 2025.1, 2024.2 and 2024.1; 2020.1 to 2023.2 are still accessible but unsupported, and every release disables the oldest unsupported endpoint. 2025.2 is the last planned SOAP endpoint. Oracle states that only 2025.2 will be supported with 2027.1 (the SOAP Removal Plans FAQ gives 2027.2). Regenerate client stubs from the 2025.2 WSDL, retest, and treat this as a bridge: SOAP is removed in 2028.2.

    2025.2 WSDLSOAP web services usage logSource 27Source 29Source 28
  9. 9
    ConversionDocumented

    Move NLAuth and TBA integrations to OAuth 2.0

    With 2027.1 integrations that use NLAuth stop working, new integrations can no longer use TBA (IssueToken endpoint and the three-step TBA flow), and PKCE is required for new OAuth 2.0 authorization code integrations. Existing TBA integrations keep working until TBA end of support, tentatively 2028.2. Because SOAP requires TBA, no new SOAP integrations can be built from 2027.1. From 2026.2, enabling SuiteAnalytics Connect also enables OAuth 2.0.

    OAuth 2.0PKCEIntegration recordsSource 8Source 29Source 9
  10. 10
    ConversionDocumented

    SuiteCommerce Advanced only: migrate the site to the new SCA release

    SuiteCommerce and SuiteCommerce MyAccount are a managed bundle and update automatically. SuiteCommerce Advanced is an unmanaged bundle: install the new release from Customization > SuiteBundler > Search & Install Bundles (bundle IDs are in the SC/SCA release notes), download the source from Live Hosting Files > SSP Applications > NetSuite Inc. - SCA [version] > Source, diff distro.json (never copy the old one over), compare module versions, link the development domain to the SuiteCommerce Advanced Dev SSP application, reactivate themes and extensions in Extension Manager, and deploy core customizations with the SCA developer tools. Kilimanjaro and earlier must recreate customizations as themes and extensions. The 2026.2 SC and SCA release is due in a later release.

    Search & Install BundlesSSP ApplicationsExtension ManagerSCA developer toolsSource 35Source 36Source 37Source 38Source 39Source 3
  11. 11
    ValidationDocumented

    Test business workflows, reports and forms in Release Preview

    Oracle calls business workflow testing the most important part of Release Preview: document each critical task path with role, email, navigation steps and expected results (the Release Preview Test Plan Template has a matrix and worksheets). You are not expected to test new features. List saved reports, saved searches, workbooks and datasets (they cannot be exported), run each with a date range comparable to production, and compare formula columns. List custom transaction and entry forms, skipping NetSuite defaults, and test forms linked to scripts.

    Release Preview Test Plan TemplateReports > Saved Searches > All Saved SearchesCustomization > Forms > Transaction FormsSource 20Source 21Source 16
  12. 12
    ValidationDocumented

    Test script deployments, integrations and SuiteApps

    Run every operational script; put a failing server script deployment in testing mode and use the debugger. Point each SOAP, REST and RESTlet integration at the Release Preview account (see URLs for Account-Specific Domains) with newly issued tokens. Test SuiteApps installed as bundles and as SDF files. Managed bundle upgrades are not pushed to Release Preview, so install them manually; Copy to Account is not supported there. Tell third-party SuiteApp providers your Release Preview dates.

    Script debuggerURLs for Account-Specific DomainsSource 25Source 23Source 22
  13. 13
    ValidationDocumented

    Web store only: test Site Builder, SuiteCommerce or SCA on a Release Preview domain

    Domains are not copied and duplicates raise an error, so someone with DNS experience creates a unique domain (for example test.checkout.releasepreview.example.com for checkout.example.com) and sets it up per Set Up Domains for Web Stores before you test.

    Source 26Source 19
  14. 14
    UpgradeDocumented

    Oracle upgrades the production account on the scheduled date

    There is no customer-run installer. On the upgrade date Release Preview access ends; confirm the new version number at the bottom of the Home page. SuiteCommerce and MyAccount update with the managed bundle; SCA stays on its installed release until you migrate it.

    Source 16Source 5Source 35
  15. 15
    CutoverVerify with vendor

    Freeze deployments around the upgrade and smoke test production

    Hold SDF and bundle deployments in the days around the upgrade, run the priority 1 tests in production on the first business day, check script execution logs and integration error queues, and keep the Release Preview findings list open for the sandbox once it is on the new version.

Free, optional. Reopen it on any device.
Export plan:

This is a planning model. Before you commit a budget or a date, have an engineer check the path, the effort drivers and the test scope.

How to use the NetSuite upgrade planner

  1. 1

    Pick your releases

    Choose the NetSuite release your customizations and integrations were last tested on (for SOAP integrations, the WSDL version they use) and the release you are preparing for: the current 2026.2, a planned release, or 2028.2 when SOAP and legacy SuiteScript are removed.

  2. 2

    Describe your account

    Enter scripts, workflows and custom objects, integrations, file and EDI interfaces, saved searches and reports, users and production accounts. Tick the modules and integration channels you use.

  3. 3

    Read the path and the drivers

    Each step cites the NetSuite Help Center topic it comes from. The Changes tab lists technical and functional changes per release crossed, and the Risk tab explains every driver behind the score.

  4. 4

    Export the test plan

    Download the regression plan as Excel, Word, PDF or CSV and use it in Release Preview. Tests marked for automation repeat at every scheduled upgrade.

  5. 5

    Save or get it reviewed

    Save the plan to your Netray account to reopen next release, or send it to an engineer for a written review.

Questions

How often is NetSuite upgraded, and can I see my date?

Oracle delivers two scheduled version upgrades a year, named YYYY.1 and YYYY.2 (2026.2 is current), and can add selected enhancements in monthly releases in between. Your account's upgrade date is shown in the What's new in the Suite portlet on the home dashboard, and the version number is at the bottom of the Home page.

What is NetSuite Release Preview and what is not copied into it?

A separate account built from a copy of production or of a chosen sandbox, requested by an Administrator at Setup > Company > Release Preview. It takes about 5 to 7 days to create and lasts until your account is upgraded, or is purged after 14 days without a login. Not copied: TBA tokens, SAML configuration, web store domains, Customer Center roles, system notes, workflow history and instances, and campaign response history. Saved searches are inactive, payment profiles are in test mode, and scheduled scripts and workflows only run manually.

When does NetSuite SOAP web services stop working?

With the 2028.2 release all SOAP endpoints are disabled and SOAP integrations stop working. 2025.2 is the last planned endpoint. From 2027.1 no new SOAP integrations can be built, because new integrations cannot use TBA. Oracle's pages give 2027.1 (WSDL support page) and 2027.2 (SOAP Removal Plans FAQ) as the point from which only the 2025.2 endpoint is supported.

Which NetSuite API should new integrations use?

SuiteTalk REST web services with OAuth 2.0, including SuiteQL queries through REST. Where REST web services do not cover a record or operation, Oracle points to SuiteScript RESTlets. SuiteAnalytics Connect (ODBC, JDBC, ADO.NET) remains the read channel for BI tools. From 2027.1, new OAuth 2.0 authorization code integrations must use PKCE.

What happens to SuiteScript 1.0 and 2.0 scripts?

SuiteScript 2.1 is the standard from 2026.2. SuiteScript 1.0 gets critical fixes only from 2027.1. From 2028.1, 2.0 and 2.x scripts run as 2.1 by default and 1.0 cannot be deployed in new accounts. From 2028.2 only 2.1 scripts run. Test 2.0 and 2.x server scripts with the account preference Execute SuiteScript 2.x Server Scripts as 2.1 before changing the annotation.

Do I have to migrate TBA integrations to OAuth 2.0?

New integrations must use OAuth 2.0 from 2027.1. Existing TBA integrations keep working until TBA end of support, tentatively planned for 2028.2, but Oracle recommends switching as soon as possible. NLAuth integrations stop working with 2027.1.

Does SuiteCommerce Advanced upgrade automatically with NetSuite?

No. SuiteCommerce and SuiteCommerce MyAccount are a managed bundle and update automatically. SuiteCommerce Advanced is an unmanaged bundle: you install the new release, merge your customizations into the new source, link the development domain to the new SSP application, test, then deploy. Kilimanjaro and earlier must recreate customizations as themes and extensions.

How should we test NetSuite integrations before an upgrade?

In Release Preview, issue new tokens (TBA tokens are not copied), point each SOAP, REST and RESTlet client at the account-specific domain, replay saved production payloads and compare results. Switch SuiteAnalytics Connect to the Release Preview host. Record each SOAP client's WSDL version, and add explicit sort orders to SuiteQL queries after the 2026.2 default sort change.

Sources

  1. NetSuite Help: Release Notes
  2. NetSuite Help: NetSuite 2026.2 Release Notes (revision October 19, 2026)
  3. NetSuite Help: NetSuite Version 2026.2 (two scheduled upgrades a year)
  4. NetSuite Help: Monthly Releases
  5. NetSuite Help: Sneak Peeks (upgrade date and version number)
  6. NetSuite Help: 2026.2 SuiteScript release notes (SuiteScript 2.1 standard, phase-out milestones)
  7. NetSuite Help: 2026.2 SuiteTalk web services release notes
  8. NetSuite Help: 2026.2 authentication release notes (TBA, NLAuth, OAuth 2.0, 2FA, passkeys)
  9. NetSuite Help: 2026.2 SuiteAnalytics release notes
  10. NetSuite Help: 2026.2 inventory management release notes
  11. NetSuite Help: 2026.2 manufacturing release notes
  12. NetSuite Help: 2026.2 order management release notes
  13. NetSuite Help: 2026.2 SuiteBuilder release notes
  14. NetSuite Help: 2026.2 SuiteCloud SDK release notes
  15. NetSuite Help: Release Preview Guide
  16. NetSuite Help: Overview of Release Preview
  17. NetSuite Help: Accessing Your Release Preview Account
  18. NetSuite Help: Features Available for Testing in Release Preview
  19. NetSuite Help: Data That Is Not Copied from Production to Release Preview
  20. NetSuite Help: Test Your Business Workflows
  21. NetSuite Help: Test Your Custom Reports, Queries, and Forms
  22. NetSuite Help: Test Your Installed SuiteApps (Bundles)
  23. NetSuite Help: Test Your SOAP Web Services Integrations
  24. NetSuite Help: Test Your SuiteAnalytics Connect Connection
  25. NetSuite Help: Test Your SuiteScript Deployments
  26. NetSuite Help: Test Your Web Store
  27. NetSuite Help: Support for Existing WSDL Versions
  28. NetSuite Help: NetSuite Versioning and WSDL Versioning Overview
  29. NetSuite Help: SOAP Removal Plans FAQ
  30. NetSuite Help: Identifying Scripts That Are Not Using SuiteScript 2.1
  31. NetSuite Help: Enabling SuiteScript 2.1 at the Account Level
  32. NetSuite Help: Transitioning To SuiteScript 2.1
  33. NetSuite Help: User Guides (SOAP to REST upgrade guide, WMS, manufacturing guides)
  34. NetSuite Help: SuiteCommerce, SuiteCommerce MyAccount, and SuiteCommerce Advanced Release Notes
  35. NetSuite Help: Commerce Patches and Upgrades
  36. NetSuite Help: Migrate SuiteCommerce Advanced
  37. NetSuite Help: Migrate from Aconcagua and Later
  38. NetSuite Help: Migrate from Kilimanjaro and Earlier
  39. NetSuite Help: 2026.1 Release of SuiteCommerce, SuiteCommerce MyAccount, and SuiteCommerce Advanced
  40. NetSuite Help: 2025.2 Release of SuiteCommerce, SuiteCommerce MyAccount, and SuiteCommerce Advanced

Steps marked Verify with vendor are planning inferences, not vendor statements. Effort coefficients are Netray planning assumptions and are shown in full in the Effort tab.