Planning snapshot: October 4, 2026
The milestones below come from current Oracle documentation and may change. They identify work to investigate; they do not establish a customer-specific upgrade date or guarantee future feature availability.
SuiteScript: connect each version to its dependencies
Oracle’s transition guide sets SuiteScript 2.1 as the current standard and describes staged changes through 2028.2. Its 2027.1 milestone limits SuiteScript 1.0 support to critical issues; the 2028.2 plan requires new and existing scripts to use 2.1. Feature-specific version requirements still need to be checked.
Use the inventory to decide what to maintain, replace or retire. A script that no longer serves a business purpose does not need to be migrated simply because it exists. For active scripts, connect each deployment to a process owner and a representative test.
SOAP: plan the migration around actual behavior
Oracle’s SOAP FAQ describes full removal in 2028.2 and directs new work toward REST with OAuth 2.0. Migration needs a functional comparison, not just a different endpoint. The documented alternatives can include RESTlets for cases that are not covered by REST web services.
Identify the operations, record types, error handling and reconciliation that make your current connection reliable. Ask suppliers about supported replacements and responsibilities. Do not assume complete one-to-one parity or wait for the final retirement date to discover a missing dependency.
Organize the work by readiness
- 01
Discovery now
Identify scripts and integrations, confirm active usage and record ownership. Resolve unknowns before assigning a migration estimate.
- 02
Design and proof
Choose the supported replacement approach and demonstrate the hard part first: a complex transaction, a high-volume flow or a difficult exception.
- 03
Planned delivery
Build test coverage, schedule business validation and agree a controlled rollout. Leave time for supplier updates and retesting.
- 04
Post-change evidence
Confirm the real process works after migration. Compare transaction counts and outcomes, and ensure operational support knows the new recovery steps.
When official sources differ
Oracle’s public SOAP guidance differs on an intermediate endpoint-support milestone. Verify support for your exact endpoint before fixing a migration deadline; the consistent 2028.2 removal milestone remains the basis for long-range planning.