Choosing A Migration Path
Use this topic to plan updates for customizations that use SuiteScript 1.0, SuiteScript 2.0, or SuiteScript 2.x patterns.
Whenever possible, convert legacy scripts to SuiteScript 2.1. SuiteScript 2.1 uses a newer JavaScript runtime and helps prepare your customizations for future NetSuite platform changes.
Prepare For Your Migration
Before you upgrade legacy scripts, complete the following preparation steps:
-
Inventory scripts and customizations.
-
Identify SuiteScript version and script type.
-
Choose the update option in the following table.
-
Convert or test in a sandbox.
-
Review generated or converted code.
-
Validate behavior and deployment metadata.
-
After the scripts are approved, deploy them in your account.
Start with low-complexity scripts. This helps you become familiar with the migration process before updating more complex customizations.
Choose An Update Option
Use the following table to choose the option that matches the customization you want to update.
Automated tools and agent skills can accelerate migration, but you must review all generated code, object updates, and deployment changes before using them in production.
|
If you need to |
Use this resource |
|---|---|
|
Test current SuiteScript 2.0 server scripts in a SuiteScript 2.1 runtime before making code changes. |
|
|
Test current SuiteScript 2.x server scripts in a SuiteScript 2.1 runtime before making code changes. |
|
|
Automatically upgrade SuiteScript 1.0, 2.0, and 2.x scripts and custom objects to SuiteScript 2.1. |
|
|
Get AI-assisted help with code generation, refactoring, testing, or SDF project updates. |
|
|
Get guidance on manually transitioning from SuiteScript 1.0 to SuiteScript 2.1. |
|
|
Get guidance on manually transitioning from SuiteScript 2.0 to SuiteScript 2.1. |
Validate Script Changes
After you update a script, complete the following validation steps.
-
Run the converted script in a sandbox environment.
-
Test all entry points.
-
Verify sublist behavior, searches, record operations, data handling, and error handling.
-
Confirm that deployment records and SDF objects still reference the correct files.
-
Compare behavior against the original customization.