Release readiness begins with the scripts, integrations, and reporting connections you actually use. Keep each program’s owner, evidence, and migration plan separate.
Declared version is not executed version
Check both the API Version and the Execute As Version fields. Oracle documents that the account preference can change the runtime used for a script while list views continue to show the original API version. Test account-level runtime changes in a sandbox before applying them to production.
Source: Oracle: version information in the script record.
The deprecation calendar
Use release milestones to assign work. They are release identifiers, not exact calendar dates for your account.
| Program | Milestone | What to plan |
|---|---|---|
| SuiteScript | Verify current account guidance | Catalog 1.0, 2.0, 2.x, and 2.1 scripts. Confirm actual execution and test compatibility. This guide does not assign an unverified retirement date. |
| Token-based authentication | 2027.1 2028.1 tentative | New TBA integrations close in 2027.1. Oracle tentatively plans to end support for existing integrations in 2028.1, excluding SuiteAnalytics Connect. Identify affected integrations and plan OAuth 2.0 migration. |
| SOAP web services | 2027.1 2028.2 | Only the 2025.2 endpoint remains supported from 2027.1. SOAP is scheduled to be unavailable in 2028.2. Coordinate REST migration with your integration owners and vendors. |
| SuiteAnalytics Connect | 2026.1 | The legacy NetSuite.com data source is removed when the account upgrades to 2026.1. Move affected Connect queries and connections to NetSuite2.com. |
Oracle sources: TBA end of support, SOAP removal plans, and Connect data-source removal. Checked September 14, 2026. Confirm changes against your account’s release preview.
Check compatibility before migrating
Oracle’s current SuiteScript 2.1 documentation still excludes 2.1 client scripts from Scriptable Cart. Test the script types, modules, and business processes you use instead of treating a version change as a blanket compatibility guarantee.
Source: Oracle: SuiteScript 2.1 support notes.
Document, Diagnose, Deliver
- Document: Record each script’s owner, declared and executed versions, deployments, dependencies, and vendor status.
- Diagnose: Identify compatibility gaps, business-critical paths, and external dependencies. Assign an owner to each unresolved question.
- Deliver: Test the change, review the results, and schedule a controlled release. Keep a rollback plan and the evidence behind the decision.
Give every gap an owner
A migration plan needs more than dates. It needs the affected customization, business process, responsible owner, test evidence, and next decision. Get vendor commitments in writing and keep unresolved items visible.