SuiteScript Migration

How to use it

The top navigation has four tabs: Dashboard, Import, Assessment and Migrate.

1. Set up an account

  1. On first sign-in, fill in the form to add a NetSuite account (a name and the NetSuite account ID). An MCP URL and token are optional fields.
  2. To add more accounts later, use the account switcher in the header.
  3. To deliver conversions as pull requests, set the account's delivery repository in owner/name format.

2. Import your scripts

  1. Open the Import tab. This tab works even when the account is empty.
  2. Read the note on the screen about bundle-installed scripts before you upload. A default SDF object import only includes customizations with no application ID, so scripts installed from bundles will not be in the project. Recording what NetSuite reports for the account's bundles lets the app show how large that gap is. An unchecked count is not the same as "none found".
  3. Choose your project zip (up to 60 MB) and upload it.
  4. When the upload finishes, the app reports how many scripts were imported, how many of them have source code, how many deployments were found, and anything skipped. If the "with source" number is far below the script count, the file cabinet was probably not downloaded, so re-pull the project.
  5. A project that contains no script objects is rejected rather than recorded as an empty success.

3. Review the catalog on the Dashboard

  1. Start with the summary counts to see how much of the account is still on 1.0.
  2. Use the filters, search and column sorting to find what matters. The register sorts by risk, highest first, by default.
  3. Open a script to see its detail, including deployments and any past conversions.
  4. In the detail view you can set business criticality (1–5). This re-scores the script's risk, because a trivial script wired into something critical is riskier to change than a complex script nobody depends on.
  5. Tick the scripts you want to migrate to mark them as selected.

4. Produce assessment documents

  1. Open the Assessment tab to see the portfolio summary: totals, overall risk, vendor-owned code, map/reduce candidates, the highest-risk scripts and a recommended migration order.
  2. Generate an Executive deck (PPTX) or a Technical document (DOCX).
  3. Download generated documents from the list. Each is stamped with who generated it and how many scripts it covered.

5. Convert a script

  1. Open a script and choose to migrate it. The conversion runs in the background and the screen updates when it finishes.
  2. Review the result:
    • the 2.1 source and a line-by-line diff against the original;
    • a narrative explaining the substantive changes;
    • a list of warnings, meaning things to check or test;
    • a PASS/FAIL validation that flags leftover 1.0 calls, 1-based loops, missing modules in define() and similar problems. Any Critical or High finding fails the conversion.
  3. If you are satisfied, accept the conversion and add an optional note. Acceptance is recorded under your name. You can withdraw it later, and the history keeps a record that it was accepted and then withdrawn.
  4. Open the script's conversion record to see every attempt, including superseded ones. You can export it as JSON, for example for a due-diligence pack.

6. Derive regression tests

On a successful conversion, choose to derive tests. They are generated from the original 1.0 source, not the converted code, so they check what the script was supposed to do. The result includes a list of uncovered behaviors that could not be tested, such as external calls or account-specific data. Regenerating tests keeps the existing ones if the new attempt fails.

7. Work on many scripts at once

Select scripts in the register and run one phase across them: analyze, migrate, validate or tests (up to 500 at a time). Scripts that cannot take that phase are skipped, and the reason is listed for each one. You will see reasons such as no source in the catalog, vendor-owned, or already converted from this same source.

8. Get the converted scripts out of the app

  1. For your selected scripts, preview what will be packaged. You will see which are included and which are skipped, with a warning for conversions that have no regression tests.
  2. Download the SuiteCloud project zip. It contains the 2.1 sources, regenerated script records, manifest and deploy files, and the original 1.0 scripts for easy reversion. Deployment audience and execute-as-role are preserved as discovered. Where a deployment is restricted to specific roles, the project leaves the value as a comment for you to set.
  3. Or deliver as a pull request to the account's delivery repository. If the repository isn't yet connected in Product Manager, you will be told to connect it. Conversions already delivered are excluded by default, and you can tick "include already delivered" to send them again.
  4. Deploy into a sandbox first. The project has not been validated against any NetSuite account.