Oracle is retiring SOAP. Here is what actually breaks first
Oracle has set a fixed retirement schedule for SuiteTalk SOAP Web Services, and it is already in motion. Here is the timeline, and the part of it most teams overlook.
The timeline that matters
- 2026.1, active now. No new SOAP endpoint is enabled by default. Any new integration work is expected to go through REST with OAuth 2.0 instead.
- 2027.1. No new SOAP integrations can be built at all, on any account.
- 2028.2. SOAP is removed entirely. Any remaining SOAP calls simply stop working.
The risk that is easy to miss
That is the difference between a planned migration and an incident. A planned migration gets budgeted, scheduled, and tested. An incident gets discovered by a customer, a vendor, or an auditor, and gets fixed under pressure.
What to actually do about it
- Inventory every active integration touching NetSuite, not just the ones your team built, the ones a partner or a former employee set up too.
- For each one, identify whether it is SOAP or REST, and if SOAP, which WSDL version it was built against.
- Check the age of that WSDL version against the three year clock, not against 2028.2.
- Prioritize anything customer facing or finance critical for migration first.
- Budget the REST and OAuth 2.0 migration into your 2026 planning cycle, not your 2028 one.
This is exactly the kind of problem the group exists for. If you are in the middle of a SOAP to REST migration, or have already finished one, bring it to the next chapter meeting. Someone in the room needs to hear it.