Migration Status Updates for SuiteScript 2.0
Check the latest migration status for SuiteScript 2.0, including updates on module migrations and ongoing enhancements.
TL;DR
This article details the current state of the migration to SuiteScript 2.0, providing users with updates and module statuses. Regularly checking this information is crucial to ensure your SuiteScript applications are up to date and functional.
Migration Status Overview
The migration to SuiteScript 2.0 focuses on enhancing the developer experience by transitioning modules to a unified framework. The migration process is ongoing, and developers should stay updated with these changes to maintain compatibility and leverage new features.
Migration Updates (By Release)
This section provides a summary of changes associated with specific releases and the modules that have been migrated:
| Release | Description of Changes | Modules Migrated to SS 2.0 | New Modules |
|---|---|---|---|
| 2020.1 | - Continued module migration to a unified developer experience. |
- Continued implementation of My Account backend components (Service Controllers).
- Updated some modules for SuiteScript 2.0 migration to TypeScript. | StoreItem, Transaction, TransactionHistory | None | | 2019.2 | - Partial migration to a unified developer experience.
- Initial implementation of My Account backend components (Service Controllers).
- Expanded SSP Application support for SuiteScript 2.0, impacting SuiteApp installation and setup. | Case, Subscriptions (Limited Release) | None | | 2019.1 | - Added SSP Application support for SuiteScript 2.0 for implementations using the SuiteTax feature. | None | None |
Note: Modules that have migrated to SuiteScript 2.0 are stored in the Backend directory of the SCA source code: <SC_xxx/Backend/SC/ (where xxx refers to the specific release). If your current SCA implementation includes customizations to these modules, it’s advisable to review the changes and adjust customizations to ensure continued functionality. Furthermore, developing extensions that attempt to import or include migrated modules could result in runtime errors.
Who This Affects
- Developers: Those involved in the maintenance and development of SuiteScript applications are impacted by these module migrations and enhancements.
- Administrators: Administrators will need to ensure that custom scripts are updated in accordance with the migrated modules.
- SuiteCommerce Users: Users leveraging SuiteCommerce for e-commerce functionality must pay attention to specific module updates relevant to online commerce.
Key Takeaways
- SuiteScript 2.0 migration is ongoing with defined updates per release.
- Key modules like StoreItem and Transaction have been migrated.
- Developers should regularly review changes to ensure compatibility and optimize functionality.
- Pay attention to migration-related issues that may affect customizations and extensions.
Frequently Asked Questions (4)
What modules were migrated to SuiteScript 2.0 in the 2020.1 release?
Are there any new modules introduced in the 2019.2 or 2020.1 releases?
Do migrations to SuiteScript 2.0 affect customizations in SuiteCommerce applications?
What should developers consider when using modules migrated to SuiteScript 2.0 in their customizations?
Was this article helpful?
More in SuiteScript
- SuiteScript 2.1 Enhancements in NetSuite February Updates
SuiteScript 2.1 now supports async features and PATCH method. Discover the latest API and SuiteProcurement improvements.
- Custom Tool Script Enhancements in NetSuite
Custom tool scripts in NetSuite gain execution log support and a new management page in February 16, 2026.
- Scheduling Map/Reduce Script Deployments in NetSuite
Learn to schedule map/reduce script submissions, including one-time and recurring options in NetSuite.
- API Governance Units Calculation in NetSuite 2026.1
NetSuite 2026.1 introduces examples illustrating API governance unit calculations for both user event and scheduled scripts.
