Table of Contents
Introduction
Oracle’s decision to phase out SOAP web services marks one of the most significant integration shifts for NetSuite users in years. As enterprises prepare for releases from 2025.2 through 2028.2, this transition is more than a technical update; it moves toward faster, more secure, and scalable REST-based integrations.
This blog explores Oracle’s SOAP web service deprecation for NetSuite users, the official timeline, migration best practices, and how your organization can prepare to maintain seamless connectivity across systems.
What Does “Deprecation” Mean For NetSuite SOAP Web Services?
Deprecation in NetSuite means SOAP web services remain available but are no longer the preferred integration method. Support will gradually decline as REST web services prioritize scalability and performance.
Over 70% of public APIs now use REST as their architecture, underscoring why NetSuite’s shift isn’t isolated; it’s part of a global trend toward modern, lightweight, and scalable integrations.
This change does not remove SOAP immediately. It indicates limited investment, fewer feature updates, and reduced long-term innovation. Enterprises that stay dependent on SOAP may face:
- Compatibility issues with the new NetSuite features
- Higher maintenance costs from custom workarounds
- Eventual migration pressure as SOAP phases out
Deprecation signals the start of transition planning. Moving toward REST-based integrations keeps systems aligned with NetSuite’s direction and avoids future disruption.
What is the Official NetSuite SOAP Deprecation Timeline?
SOAP web services are being retired in phases. The last SOAP release is scheduled for 2025.2, and complete removal will occur in 2028.2. Organizations must transition to REST before this cutoff to avoid disrupting integrations and business processes.
Here is the phased schedule Oracle has announced:
2025.2 Release – Final SOAP endpoint released:
The last official SOAP endpoint will be introduced in 2025.2, and no new SOAP functionality will be developed after this. This is the last opportunity for organizations to validate SOAP integrations before the platform begins winding down support.
2026.1 Release – No new SOAP endpoints:
Starting in 2026.1, NetSuite will stop releasing new SOAP endpoints. Any new features or capabilities introduced in NetSuite will only be available through REST. SOAP users will be limited to existing functionality, creating a risk of falling behind.
2027.1 Release – REST becomes mandatory for new integrations:
By 2027.1, all new integrations must be built using REST. SOAP will still function for existing integrations, but Oracle will not allow SOAP to be used for fresh deployments. This transition forces organizations to adopt REST as the default approach.
2027.2 Release – Only the 2025.2 SOAP endpoint is supported:
From 2027.2 onward, NetSuite will restrict SOAP usage to a single endpoint—the final one released in 2025.2. Older endpoints will no longer be supported. This creates stability for legacy users but increases migration urgency.
2028.2 Release – Complete SOAP retirement:
By 2028.2, SOAP web services will be fully removed from NetSuite. Any remaining SOAP integrations will fail. Businesses that have not transitioned to REST by this point risk disruption of critical operations, including ERP, CRM, and financial workflows.
The key takeaway is that the three-year countdown starts now. SOAP endpoints have a fixed retirement horizon, and businesses must plan migration accordingly.
The table below outlines support for SOAP endpoints across releases:
Key:
- S = Supported endpointU = Available but unsupported endpoint
- – = Disabled and unavailable
| Endpoint Version | 2025.2 | 2026.1 | 2026.2 | 2027.1 | 2027.2 | 2028.1 | 2028.2 |
|---|---|---|---|---|---|---|---|
|
2025.2 |
S |
S |
S |
S |
S |
S |
– |
|
2025.1 |
S |
S |
S |
S |
U |
U |
– |
|
2024.2 |
S |
S |
S |
S |
U |
U |
– |
|
2024.1 |
S |
S |
S |
U |
U |
U |
– |
|
2023.2 |
S |
S |
U |
U |
U |
U |
– |
|
2023.1 |
S |
U |
U |
U |
U |
U |
– |
|
2022.2 |
U |
U |
U |
U |
U |
U |
– |
|
2022.1 |
U |
U |
U |
U |
U |
U |
– |
|
2021.2 |
U |
U |
U |
U |
U |
U |
– |
|
2021.1 |
U |
U |
U |
U |
U |
– |
– |
|
2020.2 |
U |
U |
U |
U |
– |
– |
– |
|
2020.1 |
U |
U |
U |
– |
– |
– |
– |
|
2019.2 |
U |
U |
– |
– |
– |
– |
– |
|
2019.1 |
U |
– |
– |
– |
– |
– |
– |
|
2019.1 |
– |
– |
– |
– |
– |
– |
– |
Modernize Legacy Integrations for Future NetSuite Updates
Outdated SOAP scripts can block future upgrades. We re-engineer your integrations using SuiteTalk REST and SuiteScript for secure, scalable, and update-ready performance.
Request a DemoBonus Reading: What’s New in SuiteCommerce Advanced (SCA) Updates
What Should Users Do to Prepare for SOAP Deprecation?
With SOAP web services approaching their end of life in NetSuite, preparation is not optional. Enterprises relying on SOAP for integrations must take proactive steps now to avoid disruption. Below are the key actions every organization should prioritize.
1. Start Planning Your Migration Immediately:
Organizations should begin by conducting a full inventory of current SOAP-based integrations, scripts, and partner solutions. For each, determine whether a REST equivalent exists in SuiteTalk. This planning stage creates the foundation for a structured migration roadmap and helps identify potential risks early.
2. Adopt SuiteTalk REST Web Services as the Standard:
SuiteTalk REST is SOAP’s official successor and fully aligns with NetSuite’s roadmap. Oracle actively enhances REST with new features, ensuring long-term compatibility. Most SOAP capabilities already exist in REST, and the remaining gaps are scheduled for closure in future releases. Transitioning now reduces technical debt and ensures smoother adoption.
3. Use OAuth 2.0 for Authentication:
While token-based authentication remains supported, it is considered legacy and will eventually be phased out. NetSuite recommends OAuth 2.0 for all new integrations. Migrating authentication methods early avoids last-minute changes, strengthens security, and ensures compliance with Oracle’s best practices.
4. Leverage SuiteScript RESTlets When REST is Missing Functionality:
In cases where SOAP provides functionality that is not yet supported in SuiteTalk REST, SuiteScript RESTlets can bridge the gap. RESTlets allow developers to expose custom endpoints tailored to specific business needs. Depending on the integration requirement, they can serve as either temporary stopgaps or permanent solutions.
5. Engage Your Partners and Vendors:
Many third-party applications still rely on SOAP. Enterprises should contact vendors to confirm their transition plans and timelines for REST-based versions. Oracle will replace its own SOAP-based integrations, but external vendors may not act unless customers demand clarity. Early vendor engagement helps avoid broken integrations later.
6. Review Oracle’s Upgrade and FAQ Documentation:
Oracle has published resources to support the transition:
- SOAP to REST Web Services Upgrade Guide (1021295) – provides step-by-step instructions for migrating integrations.
- SOAP Removal Plans FAQ (1021281) – details timelines, support phases, and policy updates.
Keeping these resources close ensures that IT teams remain aligned with Oracle’s official guidance and can confidently plan migrations.
7. Test Early and Often:
Testing should not wait until SOAP is retired. Organizations should create sandbox environments to validate REST-based integrations, ensuring data mappings, authentication, and workflows function as expected. Early testing reduces migration risks, minimizes downtime, and provides a smooth cutover once SOAP is removed.
What are the Alternatives to SOAP Web Services in NetSuite?
As SOAP web services reach their end of life, NetSuite customers must adopt modern integration approaches. The primary replacement is SuiteTalk REST web services, but several other options can complement or substitute SOAP depending on the use case.
1. RESTful Web Services:
SuiteTalk REST is the direct successor to SOAP and should be the first choice for most migrations. It supports standard CRUD (Create, Read, Update, Delete) operations, provides JSON-based responses instead of XML, and aligns seamlessly with NetSuite’s long-term integration strategy. REST is continuously updated with new functionality and offers better compatibility with SuiteAnalytics and SuiteScript 2.x.
2. File Based Data Import (FBDI):
FBDI can be more efficient than API-based calls for bulk data processing or high-volume transactions. It allows organizations to upload structured CSV/XML files for large imports, making it ideal for data migration, batch updates, or synchronization tasks where real-time integration is not required.
3. Oracle Integration Cloud (OIC) and Middleware Tools:
Middleware solutions such as Oracle Integration Cloud, MuleSoft, Dell Boomi, or Informatica can simplify the transition when enterprises manage complex multi-application ecosystems. These platforms support REST, event-driven architecture, and asynchronous processing, making them valuable for organizations looking to centralize and streamline integrations.
4. SuiteScript RESTlets:
For scenarios where REST does not yet cover SOAP functionality, RESTlets offer flexibility. Developers can expose specific business logic as REST endpoints through SuiteScript. This approach ensures no functionality gap disrupts business processes during or after migration.
5. Hybrid Models:
Some enterprises may temporarily run SOAP and REST in parallel, especially if not all integrations can be converted simultaneously. A hybrid model reduces disruption, allowing teams to phase migrations strategically while keeping critical operations online.
Example of What Changes Look Like
To understand the impact of SOAP deprecation, consider a common use case: a custom integration that retrieves customer records and updates their credit limits. Under SOAP, this process relied on XML-based requests and token authentication. After migration, the workflow changes significantly under REST.
- Use the SuiteTalk REST web services customer endpoint to retrieve customer records in JSON format instead of SOAP XML.
- Update your integration logic to send PATCH requests through REST when modifying fields such as credit limits.
- Switch authentication from token-based login to OAuth 2.0. Update your scripts to handle token generation and refresh.
- Adjust error handling since REST returns standard HTTP status codes and JSON error messages, which differ from SOAP faults.
- For any functionality not yet available in SuiteTalk REST, implement a SuiteScript RESTlet that exposes the needed business logic as a REST endpoint.
Bonus Reading: NetSuite Field Service Management (FSM) – NetSuite FSM
Key Risks to Anticipate in the SOAP-to-REST Transition
Migrating from SOAP to REST in NetSuite is not a simple “lift-and-shift.” While REST is the strategic path forward, organizations must anticipate and plan for pitfalls in advance. Below are the major risks to monitor.
- Missing features in REST equivalents – Sometimes, the REST API does not yet support every function SOAP had (for example, certain holds, status transitions, or attributes).
- Performance differences – Bulk operations may be slower or require retries.
- XML to JSON translation issues – Some data type mismatches or schema mismatches will occur.
- Authentication/security changes – Older SOAP login mechanisms may be deprecated, and you may need to support tokens or modern credentials.
- Code breaking silently – If a SOAP service is deprecated but still supported until removal, your script may continue working but it will stop getting fixes. That means once removal happens, there may be urgent failures.
How to Build a Strategic SOAP-to-REST Migration Roadmap?
A successful transition from SOAP to REST requires more than just code changes; it demands a structured roadmap that aligns technology, resources, and timelines. The following components should be part of your official migration plan.
Create
- a complete inventory of SOAP integrations
- Assess for each one: is there an existing REST equivalent? If yes, when is REST stable / supported? If not, is Oracle planning one?
- Schedule migration per integration: assign priorities (high risk, high volume, business critical).
- Budget resources for testing, refactoring, and validation.
- Plan for rollback or fallback if the REST version has gaps or unexpected behavior.
Optimize Your Current NetSuite Setup with AlphaBOLD
Eliminate performance bottlenecks and streamline integrations with expert-led audits and optimization services.
Request a DemoConclusion
Oracle’s gradual phaseout of SOAP web services marks a major shift for NetSuite users. While the change is inevitable, it doesn’t have to be disruptive. Early preparation, structured migration planning, and adoption of REST web services will position your business for greater scalability, security, and integration flexibility.
The companies that act now, mapping integrations, updating authentication, and testing REST workflows, will transition smoothly. Those who delay risk service interruptions, technical debt, and compliance challenges as SOAP endpoints are retired.
At this stage, migration is no longer optional; it’s a business continuity requirement.
FAQs: Moving from SOAP to REST in NetSuite
Is SOAP being completely removed from NetSuite?
No, SOAP web services are still supported but are gradually being deprecated. REST web services are the preferred option for future integrations due to their modern architecture and scalability.
How does REST improve NetSuite integration performance?
REST provides faster response times, supports modern authentication, and uses lightweight JSON payloads, making integrations more efficient and easier to maintain.
What’s the best approach to migrate existing SOAP integrations?
Start with a detailed audit of your existing SOAP integrations, then design equivalent REST endpoints using NetSuite’s REST API. Tools like Postman or SuiteTalk REST can simplify the process.
Can AlphaBOLD help with custom NetSuite integrations?
Yes. AlphaBOLD provides end-to-end NetSuite consulting, which includes custom API development, integration with third-party tools, workflow optimization, and long-term managed support.
How long does a SOAP to REST migration usually take?
It depends on integration complexity and data volume. Simple endpoint migrations can take a few days, while full-scale ERP integration modernization may take several weeks.
