NetSuite is phasing out SOAP Web Services: timeline and migration plan

What’s Changing and Why It Affects You

Most NetSuite users don’t think about the protocol their integrations run on every day. And they don’t need to, as long as everything works. But behind the scenes, something fundamental is changing. Oracle has decided to completely phase out SOAP Web Services, which have long been the backbone of many NetSuite integrations. And the first milestones are closer than many organizations realize.

For companies that automatically route orders to their ERP, synchronize inventory levels with an online store, or exchange invoicing data between systems, now is the time to assess how their integrations are technically structured. In this article, we explain what’s changing, why Oracle is making this decision, where REST specifically performs better, and how to approach the migration in a structured way without disrupting your day-to-day operations.

The Timeline: Three Years to Migrate

Oracle is following a phased schedule that gives organizations ample time, provided they start early enough. The starting point is NetSuite version 2025.2: that is the last planned SOAP endpoint. After that release, Oracle will stop including new SOAP versions by default with every update.

Specifically, this means the following:

By the2026.1 release, Oracle expects all new integrations to be built using REST, preferably with OAuth 2.0 authentication. Existing SOAP integrations will continue to function as usual at that time, but you will no longer be allowed to build new ones using SOAP.
With the2027.1 release, this cutoff becomes final: it will then no longer be technically possible to create new SOAP integrations.
As of the2027.2 release, only the 2025.2 endpoint will still receive bug fixes; all older versions will no longer be supported.
With the2028.2 release, SOAP will be permanently removed from the platform. Integrations still running on SOAP at that time will cease to function.

So this is not a matter of a sudden shutdown, but a carefully planned path with clear deadlines. The key message: those who start assessing their systems now will have the luxury of migrating in a controlled manner rather than under time pressure.

Why is Oracle discontinuing SOAP?

The reason behind the phase-out is not arbitrary. SOAP Web Services no longer meet the standards Oracle applies for modern integrations. There are three specific issues:

Limited support for new functionality

New NetSuite records and features have not been made available via SOAP for years. Those who use SOAP therefore miss out on the platform’s latest capabilities.

Outdated technical architecture

SOAP does not support modern standards such as NetSuite’s current metadata architecture, SuiteAnalytics Workbooks, and SuiteScript 2.x Analytics APIs. Furthermore, the XML-based structure with WSDL schemas is complex to develop and maintain.

Outdated authentication

SOAP uses Token-Based Authentication (OAuth 1.0), which no longer aligns with the security standards Oracle applies to its cloud products. REST supports OAuth 2.0, the current industry standard.

What makes REST better?

Simpler data format

REST uses JSON instead of XML. JSON is lighter, more readable, and easier to process. This translates to faster development and a lower risk of errors during data transformations.

SuiteQL for advanced queries

One of REST’s most powerful features is its integration with SuiteQL. This is an SQL-like query language that allows you to directly execute complex data queries on NetSuite data. In many cases, SuiteQL eliminates the need for Saved Searches, offering greater flexibility and better performance.

OAuth 2.0 authentication

More secure, more flexible, and aligned with the standards used by other cloud platforms. For integrations that run unattended (machine-to-machine), OAuth 2.0 M2M offers a good solution, with tokens remaining valid for up to two years.

RESTlets as a fallback

For situations where the standard REST endpoint does not yet support a specific record type or operation, RESTlets offer an alternative. These are SuiteScript-based endpoints that you can configure yourself. This allows you to make the transition to REST even if full parity with SOAP has not yet been achieved.

Active Further Development

Oracle is continuously investing in expanding REST capabilities. New record types, Suite Tax support, and improved analytics are being added to REST, while SOAP is in maintenance mode.

Where REST Is Not Yet Fully Equivalent to SOAP

It’s fair to note that REST is not yet fully equivalent to SOAP in some respects. Three areas deserve specific attention:

Batch processing

SOAP allows multiple operations to be bundled into a single request. REST currently processes requests individually, which can result in more API calls when dealing with large volumes. Oracle has indicated that it plans to improve this.

Legacy Tax Engine

Organizations still using the old tax calculation in NetSuite (instead of SuiteTax) may encounter limitations, as it is not fully supported via REST. Oracle recommends considering a switch to SuiteTax as well.

Saved Searches via API

SOAP offers direct support for running Saved Searches. This is not natively available in REST, but SuiteQL offers a powerful and more flexible alternative in most cases.

What does this mean for your organization?

The impact depends on how your current integrations are set up. Three questions can help you assess the urgency:

Which integrations run on SOAP?

Identify which integrations use SOAP Web Services. Examples include ERP integrations with online stores, CRM synchronizations, logistics integrations, and financial integrations. Don’t forget the integrations that were built by a third party and have received little attention since then.

Which SOAP endpoint do they use?

Check which WSDL version your current integrations use. If it’s an older version than 2025.2, you run the risk of support being discontinued sooner.

Are any third parties involved?

If your integrations run through a partner or middleware platform (such as Celigo, Boomi, or a custom solution), check whether that party already has a REST migration plan in place.

How an iPaaS platform simplifies this transition

Jaco de NooijTechnisch Directeur

j.denooij@fortiqo.nl 0548-201010

Organizations that manage their integrations via an iPaaS platform have a significant advantage during this transition. In an iPaaS environment, integrations are centralized and clearly documented. This makes it easier to identify SOAP dependencies than in a landscape filled with separate, custom-built integrations.

With ConnectR, Opticode’s integration platform, all active integrations are visible in a single dashboard. For each integration, you can see which technology is used, how many messages are processed, and whether any errors occur. This allows you to quickly determine which integrations require attention and the best order in which to approach the migration.

Furthermore, the building-block approach of an iPaaS ensures that when switching to REST, you don’t have to completely rebuild every integration from scratch. The data transformations and business logic generally remain intact; it is the underlying communication layer that changes.

Start Early

The timeline Oracle has set provides organizations with ample time to make the transition in a controlled manner. But that’s only possible if you start early. Waiting until SOAP is actually discontinued means you’ll have to migrate under time pressure, with all the risks that entails.

Our advice: start by taking stock. Once you know which integrations run on SOAP and how complex the migration is for each one, you can create a realistic schedule.

Time to future-proof your integrations

We’ll map out your integrations and guide you through the transition to REST.

Schedule a consultation

Kennishub

Blogs FAQ

Pages

Services Data Integration Web Apps Assessment & Advice ERP Specialization About Us Contact

Contact

Terms and Conditions Privacy and Cookie Policy

NetSuite Is Phasing Out SOAP: Here’s How to Make the Switch to REST