NetSuite SOAP Retirement: Plan Your iPaaS Migration

By Marco Meisert, Founder and Managing Director, Synergy Flow Consult

Published: 20 July 2026

Oracle has published a clear runway for removing SOAP web services from NetSuite. If your business runs NetSuite integrations, and most growing organisations across Australia, New Zealand and Southeast Asia do, this is a known, dated change you need to plan for. The organisations that treat it as a checkpoint rather than a chore will get more out of it. Here is how I would think about this.

What is actually changing

NetSuite's SuiteTalk SOAP web services are being phased out in favour of REST web services with OAuth 2.0 authentication. Oracle's own published plan sets the runway:

• 2025.2: The last planned SOAP endpoint, already released.

• 2026.1: New integrations should be built on REST with OAuth 2.0.

• 2027.1: It will no longer be possible to build new SOAP integrations.

• 2028.2: SOAP is removed and integrations still relying on it stop working.

There is still time but there is also a real end date. The window between now and 2028 is your runway: comfortable if you start planning now but tight if you push this out.

Why it is more than flipping a setting

The phrase I would gently push back on is "we will just swap the connector to REST." Sometimes it is close to that but often it is not. It is worth understanding why before you scope the work.

There are three things that tend to require genuine effort regardless of which platform you run.

1. Saved Searches. A lot of NetSuite integrations lean on Saved Searches executed directly through SOAP. REST does not offer that in the same way. The equivalent is typically rebuilt using SuiteQL queries or RESTlets. That is design work, not a configuration change.

2. Authentication. SOAP integrations commonly use token-based authentication. New REST integrations move to OAuth 2.0. That is a security improvement, but it is still a change to plan and test carefully.

3. The data model. SOAP works in strongly typed XML, whereas REST primarily uses JSON. Even where operations map across cleanly, transformations and field mappings usually need revisiting. Oracle has been clear that REST will not reach full parity with SOAP. Some legacy capabilities are intentionally not carried over, and RESTlets fill those gaps.

The key takeaway is that most migrations involve some real rebuild of integration logic, not just a connector toggle.

Where your platform fits in the NetSuite SOAP retirement

This is the part that matters most for organisations planning ahead. The platforms are handling it differently, and the differences matter.

Boomi

The Boomi team has been active on this since the start of the year. The existing NetSuite connector has been certified on SOAP version 2025.2, which is the last planned SOAP release, meaning Boomi customers are fully covered and protected through to the 2028.2 deadline. On the REST side, Boomi has also been building. A NetSuite REST connector is now available under a Tech Preview designation. Tech Preview means the connector is not yet cleared for production use, but customers can access it today, evaluate it and begin planning their migration path.

Workato

Workato has both a SOAP connector and a dedicated REST connector for NetSuite. The REST connector has been in active development and Workato has been investing heavily to reach parity with SOAP ahead of the deadline. As of mid-2026, Workato has shipped a substantial expansion of the REST connector, including new triggers, additional record types and improved OAuth handling. Migration from SOAP to REST on Workato requires a manual rebuild. Because the two connectors surface actions and objects differently at the recipe level, each recipe needs to be assessed and rebuilt using REST equivalents.

Celigo

Celigo's approach is architecturally different from the others. Celigo's NetSuite connector has, by default, operated via custom RESTlets installed as a SuiteApp bundle in NetSuite, rather than through SOAP Web Services directly. For most Celigo customers this means the SOAP deprecation does not require a significant migration at all, provided they are running the current SuiteApp and have not explicitly configured SOAP Web Services in their flows. If you are a Celigo customer, the first thing to check is whether your flows are using the default RESTlet path or whether you have specifically selected SOAP Web Services. In most cases, the migration impact is low.

MuleSoft

MuleSoft's NetSuite connector is SOAP-based and has been maintained through regular WSDL upgrades, now certified on 2025.2. For organisations running MuleSoft, the path to REST involves moving to OAuth 2.0 connectivity, which requires revisiting authentication and payload handling. MuleSoft's documentation and community resources cover this transition in detail, and organisations with in-house technical capability will find the guidance comprehensive.

A note from a recent client conversation

In a recent client conversation, a customer asked one of their iPaaS vendors directly what the SOAP retirement meant for their integrations. The vendor confirmed that a new NetSuite REST connector is in development and will be released as a separate connector. Once available, customers will need to configure it independently, including activities, schemas and transformation mappings. The existing SOAP connector will continue to coexist alongside the new one, and Saved Search support is retained in the existing connector.

If you are running NetSuite integrations on other platforms not covered here, the same principle applies. Reach out to your vendor directly, ask for their specific SOAP-to-REST roadmap and confirm the timing. Every platform has a path through this. The important thing is to understand what that path looks like for your specific environment before 2027 arrives.

The part most teams skip

Here is the strategic point that I would want a board or an IT leader to sit with.

Because a migration usually means revisiting and partly rebuilding integration logic anyway, it is a natural moment to ask a bigger question: does the build we scoped three or four years ago still fit where the business is heading?

Requirements change. Integrations that were designed for nightly batch jobs now sit in businesses that expect near real-time data flows. Event-driven patterns have become the norm. The systems around NetSuite have changed. Finance teams that were comfortable with an overnight sync now want near real-time visibility.

None of this means anything is wrong with your current setup. Very often the right answer is to stay where you are and modernise, but sometimes requirements have changed enough that it is worth looking wider. The value is not in the destination. It is in making that an evidence-based decision rather than a default you back into because the connector changed.

That is the moment a genuinely independent view earns its place. An assessment with no financial tie to any platform can tell you the unglamorous truth: is your current platform still the right one, or is it not?

A sensible way to use the runway for your NetSuite SOAP migration

If I were planning this, I would do four things in order.

1. Map your exposure. Find every NetSuite integration touching SOAP and understand what each one actually does, especially any Saved Search logic. Use NetSuite's Web Services Usage Log and your platform documentation to capture endpoints, authentication methods and data volumes.

2. Prioritise by risk and value. Not everything needs to move at once. Sequence against the 2027 and 2028 dates and your own risk profile. Some integrations will migrate cleanly but others will need to be redesigned. Knowing which is which before you commit to a scope is the difference between a migration that runs to plan and one that blows out.

3. Make the platform decision deliberately. Confirm whether your current integration platform still fits where your business is heading, or assess alternatives on your own requirements rather than on anyone's sales pitch. Understand your platform's specific SOAP-to-REST path, timing and support model before committing.

4. Execute and modernise. Rebuild what needs rebuilding and take the chance to improve it while you are in there. Cleaner error handling, better observability, documented integration logic that the next person on your team can actually follow.

You have time. The organisations that use it well will not just keep their integrations running past 2028.2. They will come out the other side with a cleaner, more capable foundation than they had going in.

If you are starting to think through your NetSuite SOAP-to-REST migration path and want an independent view on your options, that is exactly the kind of work we do at Synergy Flow Consult. Book a free consultation at info@synergyflowconsult.com and we will help you understand where your environment stands and what a sensible path forward looks like.

My name is Marco Meisert. I am the Founder and Managing Director of Synergy Flow Consult, a vendor-agnostic integration consultancy operating across Australia, New Zealand and Southeast Asia. Synergy Flow Consult does not resell integration platform licences.