NetSuite For NetSuite customers · SuiteScript 2.1

Your NetSuite scripts need to move to SuiteScript 2.1. Get there with confidence

Seen the SuiteScript notice in your NetSuite account? NetSuite is retiring SuiteScript 1.0, 2.0 and 2.x. Start with visibility, not conversion: a fixed-price readiness assessment shows which of your scripts are affected, what they touch, and a phased path to 2.1.

Start with an assessment What's changing
Key dates
2026.2In-product notice begins: older script versions will stop working
2028.2Release in which legacy versions are scheduled to stop working
$2,500Fixed-price readiness assessment, fully credited toward conversion
Recognized NetSuite expertise

RSM is an Oracle NetSuite Solution Provider and the 2025 Worldwide Solution Provider Partner of the Year.

Oracle NetSuite Partner of the Year 2025 — Worldwide Solution Provider Partner of the Year Oracle NetSuite Solution Provider Oracle NetSuite Alliance Partner Spotlight Winner 2022 — Apparel, Footwear and Accessories
00 · What NetSuite is retiring

NetSuite is retiring legacy SuiteScript runtimes. SuiteScript 1.0, 2.0 and 2.x scripts will need to move to SuiteScript 2.1.

This is more than a routine platform update, it is an opportunity to assess technical debt and reduce the risk of business disruption.
  • The notice in your NetSuite environment
    Beginning with NetSuite 2026.2, users see an in-product notification that older script versions will stop working in the 2028.2 release.
  • Scripts may stop functioning
    Scripts left on legacy versions may stop functioning once support ends.
  • SuiteCommerce is an exception
    NetSuite documentation currently states SuiteScript 2.1 is not supported for Commerce website development (1.0, 2.0 and 2.x are). RSM is monitoring for guidance and scopes Commerce customizations as a separate track.
01Why now

Time remaining is an advantage only if it is used

Why this deserves attention now, not later — and what early planning protects.

Why it's harder than a routine upgrade
  • 01Large NetSuite environments often contain dozens or even hundreds of custom scripts.
  • 02Years of customizations, integrations, third-party solutions and undocumented scripts are all in scope.
  • 03Every converted script requires testing to confirm business processes continue to operate correctly.
  • 04Demand for experienced NetSuite developers is likely to increase as the deadline approaches.
What early planning protects
  • Remediation spread across future upgrade cycles instead of one concentrated effort.
  • Priorities set by business criticality and your own timeline, rather than under deadline pressure.
  • Critical processes validated thoroughly before legacy versions are retired.
  • A planned modernization effort rather than an urgent remediation project.
02The path

Five steps to a confident transition

A structured approach that starts with visibility, not conversion.

01
Inventory
Inventory existing SuiteScript customizations across your environment.
02
Identify impact
Identify business-critical scripts, integrations and third-party SuiteApps that may be impacted.
03
Evaluate effort
Evaluate complexity, dependencies and level of effort for each upgrade — including who owns locked or bundled scripts.
04
Plan in phases
Develop a phased migration plan aligned to business priorities and upcoming NetSuite initiatives.
05
Test before deploy
Establish a testing strategy to validate functionality before deployment.

SuiteCommerce customizations are flagged as a separate track — NetSuite does not currently support SuiteScript 2.1 for Commerce website development.

03How RSM helps

Support for the transition, end to end

A structured approach that reduces risk and limits the burden on your internal team.

AAssess and plan
  • A1Readiness assessmentInventory existing scripts, identify those running on legacy versions, and evaluate complexity, dependencies and business impact.
  • A2PrioritizationRemediation ordered by risk and criticality.
  • A3Conversion planningA phased migration roadmap identifying quick wins, high-risk customizations, estimated effort and recommended timelines.
BConvert, test and deploy
  • B1Conversion servicesConvert SuiteScript 1.0, 2.0 and 2.x customizations to 2.1, modernizing code where appropriate and applying NetSuite development best practices.
  • B2Testing and validationFunctional testing, user acceptance testing support, sandbox validation and production deployment planning.
  • B3Deployment supportIssue remediation and post-conversion validation to reduce operational disruption.
04AI-assisted conversion

AI accelerates the work; experienced developers validate it

RSM's NetSuite technical team has been evaluating NetSuite's AI-assisted development capabilities and AI agent skills to support conversion of SuiteScript 1.0, 2.0 and 2.x code to 2.1. These tools can generate updated code more quickly than traditional manual approaches — and many organizations use the effort as a catalyst for broader modernization, integration and automation improvements.

Automation speeds discovery
Automated analysis and documentation accelerate inventory and generate updated code for portions of the migration.
Experts protect continuity
Developers who understand your business processes validate that upgraded scripts perform as intended — protecting quality and reliability.
05Our recommendation

Start with a fixed-price readiness assessment

$2,500fixed price, fully credited toward the transition work

A full SuiteScript conversion readiness assessment of your NetSuite account — no open-ended scoping or hourly billing.

If we move forward together on the follow-up conversion work, the full $2,500 is applied toward the transition engagement.

Request your assessment
What you receive
  • A complete script inventoryA deliverable document outlining every applicable script in your NetSuite environment.
  • Plain-language summariesA quick summary of what each script does, so business owners can follow along.
  • Complexity and priority ratingsEach script is rated, so remediation can be ordered by risk and criticality.
  • Records and processes touchedThe records and processes each script touches, so impact is clear before any work begins.
  • Locked and bundled scriptsBundles or third-party providers that need to update scripts our team can't change, and who to contact.
  • A phased roadmapWhich scripts are affected, which support critical processes, and a phased plan for conversion.
Recommended next steps

From first conversation to phased conversion

  1. STEP 01Working sessionReview your NetSuite environment and customization landscape together.
  2. STEP 02Readiness assessmentA quick-turnaround document: which scripts are affected, which support critical processes, and a phased roadmap.
  3. STEP 03Agree a timelineA practical remediation timeline based on your business priorities and upcoming NetSuite initiatives.
  4. STEP 04Convert, test, deployBegin phased conversion, testing and deployment, with RSM support as needed.
Let's talk

Ready to get ahead of the 2.1 transition?

Tell us about your NetSuite environment and we'll schedule a working session to scope your $2,500 readiness assessment.

Work with Oracle NetSuite's 2025 Worldwide Solution Provider Partner of the Year.

Loading form

Just a moment while we get everything ready.