NetSuite SuiteTalk SOAP Web Services Removal: What It Means for Your Integrations

You are reviewing your NetSuite environment, and someone mentions that one of your integrations runs on SuiteTalk SOAP. Maybe it is your third-party logistics platform. Maybe it is the custom connector your previous partner built three years ago. Maybe you are not entirely sure what it is, only that it has been running quietly in the background and nobody has touched it since go-live.

That is the situation most mid-market NetSuite customers are in right now. Oracle has confirmed that SOAP web services are being phased out entirely by 2028.2. The timeline is specific, the milestones are set, and the integrations that have not been migrated by then will stop working.

This page explains what is happening, who is affected, what migration involves, and how Sky High ERP helps companies get ahead of it.

What SuiteTalk SOAP Is and Why So Many Integrations Use It

SuiteTalk is NetSuite's web services layer, the part of the platform that allows external applications to communicate with NetSuite programmatically. When a third-party tool needs to push data into NetSuite or pull data out of it, one of the most common ways it does so is through SuiteTalk.

SOAP, which stands for Simple Object Access Protocol, is the older of the two communication standards SuiteTalk has historically supported. It has been the backbone of NetSuite integrations for years, which is why so many companies are exposed to it.

To modernize its integration channels, Oracle is completely removing SOAP by 2028, for a few reasons:

• Exposed objects - SOAP does not support the latest business features and new records have not been made available to SOAP for a couple of years.

• Outdated Technology Stack - SOAP does not support modern architecture standards like the most up-to-date metadata architecture, SuiteAnalytics Workbooks, and SuiteScript 2.x Analytics APIs.

• Legacy Authentication - SOAP still uses token-based authentication, which is not consistent with other Oracle products and does not meet modern security standards.

Oracle is replacing SOAP with REST web services, specifically SuiteTalk REST with OAuth 2.0 authentication. REST is a modern integration standard that supports current architecture requirements, newer NetSuite records and features, and more secure authentication protocols. The migration is not optional. It is a matter of when, not whether.

The Full Deprecation Timeline

Full Deprecation Timeline visualized above and elaborated below.

Oracle has published a detailed timeline for the gradual removal of SOAP. Here is what each milestone of this timeline means operationally:

2026.1 — All new integrations must use REST. Starting with the 2026.1 NetSuite release, all newly built integrations should use REST web services with OAuth 2.0. Building new integrations on SOAP is no longer recommended. Existing integrations continue to run for the time being, but with each new NetSuite release, the oldest supported SOAP endpoint will be entirely disabled. Other older endpoints will continue to work but will gradually lose support.

2027.1 — New SOAP integrations blocked entirely. With the 2027.1 release, it will no longer be possible to build new integrations using SOAP web services. All new integrations must use REST with OAuth 2.0 authentication. Existing SOAP integrations that are on supported endpoints will continue to function, but can no longer be extended or rebuilt on the same foundation.

2027.2 — Only the last SOAP endpoint is supported. Starting with the 2027.2 release, only the 2025.2 SOAP endpoint will be supported and receive bug fixes. All older endpoints remain available but unsupported, meaning no patches or bug fixes. If your integration runs on an endpoint older than 2025.2, it is already running without a safety net from this point forward.

2028.2 — All SOAP endpoints disabled. With the 2028.2 release, every SOAP endpoint is permanently disabled. Any integration that has not been migrated to REST stops working entirely, with no exceptions and no extensions. This is the hard deadline.

It is also worth reiterating that Oracle disables the oldest unsupported endpoint with every new release between now and the 2028.2 NetSuite release, so not every integration has until 2028 to be updated.

How to Know If Your Integrations Are Affected

The first step is identifying which of your current integrations use SOAP. This is less obvious than it sounds. Many mid-market companies have integrations that were built by previous partners or come bundled with third-party software, and the underlying protocol is rarely documented in plain language.

One practical place to start is: In NetSuite, navigate to Setup, then Integration, then SOAP Web Services Usage Log. This page lists logs that document every action done by SOAP integrations. A long list of logs is a clear indication that one or more of your integrations is still SOAP-based, and needs to be migrated.

Common integrations that frequently run on SOAP include third-party logistics platforms connected to NetSuite for order and fulfillment data, payroll systems that sync employee and compensation records, custom connectors built by implementation partners for specific workflows, and e-commerce platforms with older NetSuite connectors that have not been updated in several years.

If you use a SOAP-based application developed by a NetSuite partner, Oracle's guidance is direct: contact your partner and discuss a timeline for an alternative REST-based application. If your partner is not proactively raising this conversation, that is worth noting.

What Migration to REST Actually Involves

The technical path from SOAP to REST is well-documented. Oracle has published a SOAP to REST Upgrade Guide that maps specific SOAP operations to their REST equivalents. For most standard use cases, a REST-based alternative already exists.

What companies typically underestimate is the scope of the work relative to the original integration. Migrating an integration is not simply swapping one protocol for another. It involves reviewing the existing integration architecture, mapping SOAP operations to REST equivalents, rebuilding authentication using OAuth 2.0, testing against live NetSuite data, and validating that the data flowing between systems is accurate and complete before cutting over.

One nuance worth understanding: Oracle has confirmed that REST will not achieve 100% parity with SOAP, because a few legacy SOAP functionalities will intentionally not have an equivalent in REST. For scenarios where REST web services cannot accommodate a specific use case, SuiteScript RESTlets are the recommended alternative. This means a small number of migrations will require more architectural thought than a direct port, and identifying those cases early is part of doing this well.

The companies that struggle with this migration are the ones that start late, underestimate scope, or treat it as a purely technical project without involving the business teams who depend on the integrations day to day.

How Sky High ERP Can Help

At Sky High ERP, integration architecture is central to every NetSuite engagement we lead. The same principles that make a NetSuite environment ready for AI, clean data, structured permissions, and well-documented workflows, are the principles that make a migration like this manageable rather than disruptive.

Our approach to the SOAP to REST migration starts with an audit. We identify every integration in your NetSuite environment, determine which are SOAP-based, assess the complexity of each migration, and give you a clear picture of what needs to happen and in what order. From there we scope and execute the migration, rebuild on REST and OAuth 2.0, and test against your real business scenarios before any cutover.

For companies that have never worked with Sky High ERP before, we are offering a free integration audit. We will review your current NetSuite integration architecture, identify your SOAP exposure, and give you an honest assessment of your timeline and risk. No obligation. Just clarity on where you stand before the deadline pressure starts.

The Real Cost of Waiting

Every mid-market company affected by this deprecation has the same choice. Start the audit now and migrate on a timeline that works for the business or wait until the urgency forces the decision.

The companies that move early will migrate cleanly. The ones that discover the problem in 2027 or 2028 will be rebuilding under pressure, with less time, fewer options, and a higher risk of business disruption.

If you are not sure where you stand, that is the right place to start.

Book a free integration audit with Sky High ERP. Available to companies that have not previously worked with us through the button below:

Get in Touch