NetSuite is making SuiteScript 2.1 the standard for every customization. From release 2028.2, later in 2028, SuiteScript 1.0 and 2.0 scripts will no longer run. Our SuiteScript 2.1 Migration Assessment maps every script in your account, what depends on it and how to migrate it, phase by phase.
TWO STEPS, YOUR CALL
A full review of every script in your account, with risk scores, effort estimates and a migration plan split into phases.
We implement the plan with you: conversion, sandbox testing, deployment in planned windows and closing documentation. Or your team takes the plan and runs it.
SUITESCRIPT 1.0 RETIREMENT
EARLY 2027
SuiteScript 1.0 support covers critical issues only.
EARLY 2028
SuiteScript 1.0 can no longer be deployed in new accounts, and 2.0 scripts run on the 2.1 engine by default.
LATER IN 2028
Every script must use SuiteScript 2.1. Older versions stop running.
Plan your move to SuiteScript 2.1 in phases, without disrupting operations.
See what each script does, what it affects and the current state of your account before any code changes.
A SuiteScript 2.1 Migration Assessment is a full review of the scripts in your NetSuite account before any code changes. UnlockCommerce inventories every script and deployment, analyzes the code, maps dependencies and impact, and delivers a report with risk scores, effort estimates and a migration plan split into phases.
We review every script record and deployment in your account. We separate third-party bundles and SuiteApps from your custom code, then classify each custom script by version (1.0, 2.0 or 2.x), type, status and risk. Inactive and legacy scripts are flagged too.
For each custom script, we review the APIs it uses and map the SuiteScript 2.1 equivalent. Often this is a refactor, not a find-and-replace, so we note where the logic itself needs to be rebuilt.
We check which scripts, workflows and records depend on each script, and what else a change could affect across your account.
We estimate the work script by script and group it into waves, phases with a clear reason behind them, such as scripts that share dependencies or run on the same record event.
Our assessment is read-only and focuses on technical metadata, script definitions, and source code. We do not extract business transactions or operational customer data, and no changes are made to your NetSuite account.
3 to 4 business days for most accounts. Every finding and estimate is reviewed by a NetSuite developer before it reaches you.
Book your SuiteScript assessmentEvery script ends up on one of four paths:
Beyond migration readiness, our assessment helps uncover existing technical issues, potential security risks, dependencies, and opportunities to improve the health and maintainability of your NetSuite customizations.
Many of these findings are worth fixing even without a migration. In a recent assessment, the report included a high-severity security finding.
YOUR DELIVERABLE
Everything you need to plan, budget and approve your move to SuiteScript 2.1.
Script ID, name, type, version, status, risk level, required work and estimated hours for every custom script.
Based on the 7-factor scoring model in NetSuite’s SuiteScript upgrade skill, which weighs factors such as lines of code, SuiteScript 1.0 functions used and library dependencies.
How many scripts, workflows and records depend on each script, so risk reflects your whole account, not just the code.
Phases you can approve one batch at a time, each with its own effort estimate.
Third-party components documented separately, so you can confirm upgrade plans with each vendor.
Security, performance and best-practice findings worth fixing even without a migration, such as a Suitelet deployed as available without login.
What each release means for your account, and what to do before it lands.
Get this report for your account
Every script scored and mapped, with a phased plan you can approve one batch at a time.
In a recent assessment for a B2B wholesale brand on NetSuite, UnlockCommerce reviewed the full account ahead of release 2028.2. The report also flagged security and performance issues unrelated to the migration.
100+
Scripts reviewed
2,000+
Records reviewed
80+
Scripts that need to move to 2.1 before release 2028.2
Scripts on older versions:
10+ on SuiteScript 1.0 70+ on SuiteScript 2.0Every custom script, with risk, required work and estimated hours for each one.
Starting with scripts that share dependencies across the account.
Scripts tied to third-party bundles and SuiteApps, listed separately to review with each vendor.
Including a high-severity security finding, worth fixing even without a migration.
Get the same report for your NetSuite account.
See what's in your accountSTEP 2 · OPTIONAL
After the report, we can implement the plan for you in five steps. You approve one wave at a time.
Inventory, code analysis, dependency mapping and a migration plan in waves.
Our developers convert each script to 2.1, using NetSuite's SuiteScript upgrade skill and our own tooling to speed up the code work, then review every change by hand.
Each script is tested in your sandbox, in every context it runs in, along with the workflows and records it affects.
Where possible, we replace the file on the existing script record, so deployments and settings stay in place. Releases go out in planned windows.
A map of the customizations we changed, what each one does and why it changed. It stays with your team for anyone who works on your account later.
UnlockCommerce is a NetSuite Alliance Partner and SuiteCloud Developer Network member whose team built the technology that became SuiteCommerce. We write SuiteScript every day for B2B distributors, wholesalers, parts and medical supply companies, so we migrate scripts without breaking the order, pricing and integration flows that depend on them.
Many providers now offer automated SuiteScript upgrades. We start with an assessment of your whole account, use AI and NetSuite’s tools where they help, and have a NetSuite developer review every finding and estimate before it reaches you.
350+
eCommerce Projects Delivered
60+
Proprietary Extensions
95%
Customer Satisfaction (CSAT)
ONE TEAM, BEFORE AND AFTER GO-LIVE
Your migration is handled by the same team that supports your NetSuite account, your SuiteCommerce site and your integrations.
Book your SuiteScript assessmentScript migration is part of our NetSuite ERP Managed Services, so the same team can keep supporting your scripts after go-live.
If your site has custom backend scripts, we coordinate the work with our SuiteCommerce services.
Scripts that sync with Shopify, 3PLs or other systems are tested alongside our NetSuite Connector Services.
If your SuiteCommerce or SuiteCommerce Advanced site has custom backend scripts or extensions built by your team or a partner, the assessment covers them, and we can migrate that custom code to 2.1. For the core SuiteCommerce product, we follow NetSuite’s official guidance and will update our recommendations as NetSuite shares more. Learn more about our SuiteCommerce Managed Services.
No. The assessment reviews your scripts and configuration and delivers a report and a plan. Changes happen only in the implementation phase, one approved wave at a time.
Often, yes. Because we review every script in the account, the report also flags inactive scripts, security risks and performance or best-practice issues worth fixing even without a migration.
Cost depends on how many scripts need work, their version and how complex the processes behind them are. The assessment gives you a script-by-script estimate before you commit to the migration.
Yes, many teams can. The assessment still helps: your team gets the inventory, dependency map and phased plan, whether we do the work, your team does, or we split it.
Read the full timeline, the differences between SuiteScript 1.0, 2.0 and 2.1, and what to look at first in our SuiteScript 1.0 end of life guide. NetSuite’s own reference is the 2026.2 release notes.
Only technical metadata, script definitions, and source code. We don’t extract transactions, orders, or customer records.
Get a full inventory of your scripts, what depends on them and a phased plan to move to SuiteScript 2.1. Then decide how you want to tackle it.
