Get Ready for NEXT
at SuiteWorld 2026
Meet the Folio3 team at the largest NetSuite community gathering.
Schedule a Meeting
Audit, modernize, test, and migrate your NetSuite customizations ahead of the SuiteScript 2.1 transition.
NetSuite's transition is phased through 2028.2, when scripts must use SuiteScript 2.1.
Folio3 helps you assess your current customization environment and identify the changes required for SuiteScript 2.1.
SuiteScript 2.1 migration is the process of reviewing and updating existing NetSuite scripts so they can run correctly under the SuiteScript 2.1 runtime. The work can involve code conversion, refactoring, dependency review, testing, and deployment updates.
Not necessarily. Some SuiteScript 2.0 or 2.x scripts may require relatively small changes.
Changing the version annotation alone should therefore not be treated as the complete migration process.
Folio3 reviews the script, its dependencies, deployment configuration, and the business process it supports before deciding what work is actually required.
SuiteScript 2.1 is now the standard scripting model, and NetSuite is phasing out older versions through 2028.2. The transition affects SuiteScript 1.0, 2.0, and scripts using the @NApiVersion 2.x annotation.
SuiteScript 2.1 becomes the standard scripting model
SuiteScript 1.0 enters end-of-life support
SuiteScript 2.0 / 2.x scripts run as 2.1 by default
All new and existing scripts must use SuiteScript 2.1
The 2028.2 requirement gives NetSuite teams a deadline, but the assessment and testing work can start much earlier.
Folio3 helps you assess your existing SuiteScript environment, determine which customizations need to change, and migrate them to SuiteScript 2.1. We also review dependencies and business impact to support testing and a controlled deployment.
Review your existing scripts, versions, deployments, dependencies, integrations, and business processes to determine what needs attention.
Migrate required scripts to SuiteScript 2.1 and address API changes, entry points, JavaScript compatibility, and technical debt (if any).
Determine which customizations should be retired, replaced, refactored, or migrated instead of converting every script.
Test migrated scripts in sandbox and validate the transactions, integrations, searches, workflows, and business processes they affect.
Folio3 starts by assessing your scripts, dependencies, and business impact, then determines what needs to change. The process continues through migration, business validation, testing, and controlled deployment.
Identify scripts, versions, deployments, dependencies, and owners.
Review compatibility, technical debt, (if any) integrations, and business impact.
Determine what should be retired, replaced, refactored, or migrated.
Refactor required customizations where appropriate.
Convert selected scripts to SuiteScript 2.1.
Validate migrated functionality against affected business processes with business-user input.
Run technical and business-process testing in sandbox.
Move validated changes into production with a controlled plan.
We assess your scripts and dependencies alongside integrations and business processes to identify potential migration issues. This helps determine what needs to change before testing and deployment.
| Area | What We Review |
|---|---|
| Script version | 1.0, 2.0, 2.x, 2.1 |
| Script type | User Event, Client, Map/Reduce, Suitelet, RESTlet, etc. |
| APIs | Migration-sensitive and deprecated APIs |
| JavaScript | 2.1 compatibility and modernization opportunities |
| Deployments | Status, execution context, parameters |
| Dependencies | Scripts, workflows, searches, records |
| Integrations | External systems and middleware |
| Business process | Processes affected by the customization |
| Testing | Functional, integration, regression, and business-process validation with client input |
Yes. AI-assisted SuiteCloud development tools can help analyze scripts, convert code, suggest refactoring, generate initial tests, and assist with SDF-related work.
Folio3 uses AI-assisted tooling as part of the development workflow where appropriate, but generated changes still require developer review and sandbox validation. The goal is to reduce manual development effort without treating automated code conversion as a substitute for migration assessment and testing.
Use our interactive assessment to identify potential migration risks across your customization environment.
The assessment looks at:
The assessment provides directional guidance and does not replace a technical review of your NetSuite account.
SuiteScript 2.1 Migration Readiness Calculator
QUESTION 1 OF 10
How many custom scripts does your NetSuite account have?
Experience across NetSuite implementations, customizations, integrations, and ongoing development.
A broad delivery track record across different NetSuite environments, industries, customizations, and business processes.
Experience across NetSuite modules gives our team context on the business processes and functionality connected to custom scripts.
Experience with integrations helps identify dependencies between SuiteScript, external systems, and other parts of the NetSuite environment.
After migration, your scripts should be monitored through normal NetSuite operations and future release cycles. Documentation should also be updated so your team knows what was migrated, why changes were made, and which customizations support critical business processes. Folio3 can continue supporting your NetSuite environment through
The migration timeline depends on the SuiteScript version and the applicable NetSuite release requirements. Oracle’s current transition path makes SuiteScript 2.1 the standard scripting version in 2026.2, with further changes to older versions scheduled for later releases.
Yes. SuiteScript 1.0 migrations generally involve more substantial development work than a 2.0/2.x to 2.1 transition because the scripting architecture and APIs are different.
No. The annotation is only one part of the migration. The script should also be reviewed for runtime behavior, dependencies, deployment settings, and business-process impact.
Yes. Migrated scripts should be tested in a sandbox before production deployment, including the business processes and integrations they affect.
Yes. The migration process can begin with an assessment of the existing customization environment, even when the original scripts were developed by another partner or internal team.
