NetSuite is sunsetting SOAP. Here’s what every integration team needs to know — and how to get ahead of it.
Oracle’s deprecation of SOAP Web Services by 2028.2 is one of the most consequential shifts in the NetSuite ecosystem in years. This is what the transition means, what Workato is doing about it, and the practical playbook for teams running on Workato today.
If you’re running integrations with NetSuite, you’ve probably heard the news: Oracle has formally announced that SOAP Web Services will be fully deprecated by 2028.2. Starting with the 2026.1 release, no new SOAP endpoints will be published as part of the regular release cycle. The era of SuiteTalk SOAP, which has been the backbone of NetSuite integrations for well over a decade, is drawing to a close.
But here’s the thing — the hard deadline is years away, and the right moves to make depend heavily on where you are in your integration journey. Let me break it down.
Why is NetSuite doing this?
Oracle’s reasons aren’t arbitrary. SOAP has been showing its age for a while. New record types and fields introduced in recent releases haven’t been exposed via SOAP — meaning any integrations that need the latest business data have already hit a ceiling. SOAP also doesn’t support modern metadata architecture, SuiteAnalytics Workbooks, or SuiteScript 2.x. And its reliance on token-based authentication is out of step with the rest of Oracle’s product portfolio.
The replacement — SuiteTalk REST Web Services — already supports most core CRUD operations, metadata queries, and SuiteQL search. Oracle has committed to closing the remaining parity gaps, and from a performance and authentication standpoint (with OAuth 2.0 as the recommended standard), REST is the better platform to build on going forward.
The key dates you need to know
2025.2 = SOAP continues to work fully. The 2025.2 WSDL is expected to be the last routinely released SOAP endpoint. Safe to continue using existing SOAP integrations, but new builds should start on REST.
2026.1 onward = No new SOAP endpoints released by default. New fields, record types, and features added after 2025.2 will only be available via REST. SOAP is effectively feature-frozen.
2027.1 = As of 2027.1, no new integrations using TBA can be created for SOAP web services, REST web services, and RESTlets. Existing integrations will continue working. Use OAuth 2.0 for new RESTlets and REST web services integrations.
2028.2 = SOAP Web Services fully removed. All existing SOAP-based integrations stop working. Full migration to REST is required by this date.
The practical migration playbook
Workato has been investing heavily in the NetSuite REST connector to get it to parity with SOAP ahead of the deprecation.
Migration from SOAP to REST on Workato will be a manual effort. Because the two connectors surface actions and objects differently at the recipe level, there is no automated conversion tooling — each recipe needs to be assessed and rebuilt using REST equivalents. This is important to factor into your planning and resourcing timelines.
Short term (2025–2026) – Continue using SOAP safely. All new integrations should start on REST. Begin auditing which recipes use SOAP and assess their complexity for migration.
Mid-term (2026–2028) – Prioritize migrating recipes to REST. Monitor SOAP endpoint support windows. Avoid using endpoints older than 3 years for custom actions.
Long term (post 2028) – All integrations must be on REST. Customers still on SOAP by 2028.2 will face broken recipes. Plan resourcing well in advance — especially for large estates.
Where REST doesn’t yet cover your use case, SuiteScript RESTlets remain a valid bridge. Workato already supports RESTlet execution seamlessly within recipes — so you’re not stuck waiting on REST parity for every edge case.
“Migration will be a manual effort — but the connectors are fundamentally different in how actions and objects are surfaced. The good news is the major blockers — async actions, upsert action, transform record action — are now shipped and triggers are on the way”
What Workato is building next
The REST connector roadmap continues to move fast. Beyond the items already shipped or in testing, the team is working on support for all missing records exposed with the 2025.2 release.
A migration best-practices guide and customer communications are also in the pipeline, intended to land once the connector reaches a level of parity where migration is not a downgrade.
Workato’s commitment is clear: the SOAP connector will be maintained with version upgrades (the WSDL will be bumped to 2025.2) through to 2028.2, so existing recipes keep functioning without interruption — but the long-term investment is firmly on REST.
We have also released a new connector, NetSuite2, in our Data Pipelines for NetSuite, connecting to SuiteAnalytics Connect. It uses JDBC to extract large datasets from NetSuite, overcoming Concurrency Limits, Rate Limiting and time-outs (valid for REST and SOAP APIs) that limit efficient extraction of larger volumes and pushing them to a Database or data warehouse.
The bottom line
The SOAP deprecation is not a crisis — it’s a long runway with a hard stop. The teams that will fare best are those who treat it as an opportunity: to audit their integration estate, retire technical debt, and build new integrations on a modern, OAuth 2.0-authenticated foundation that will carry them well beyond 2028.
If you’re running NetSuite integrations in Workato and want to start mapping your migration path, the conversation is worth having now—not in 2027. Refer to our product documentation to review our current coverage (it will be updated with the new features, actions, and triggers planned for this year).
Are you navigating this transition? I’d love to hear how teams are approaching planning—drop a comment below or reach out directly.
View original post on LinkedIn.