Week 6 of 8

Integrations and the authentication deadlines

Integrations are where NetSuite upgrades hurt most, and Release Preview makes them easy to skip: tokens and SAML are not copied, so someone has to reconnect each one before it can be tested.

Oracle has also put dates on the old methods. From 2027.1, integrations that use NLAuth stop working and no new TBA integrations can be created. Full TBA end of support is tentatively 2028.1, and SOAP web services are removed in 2028.2. New integrations should use REST web services with OAuth 2.0.

This week: list every integration and how it signs in

Record each integration’s technology (SOAP, REST, RESTlet, SuiteAnalytics Connect, file, iPaaS) and authentication method (OAuth 2.0, TBA, NLAuth).
Flag every NLAuth integration as a 2027.1 blocker and every SOAP integration as a 2028.2 migration. Ask partners and SuiteApp vendors for their dates in writing.
In Release Preview, reconnect and run each integration: a positive test, a negative test and a volume sample.
Treat every migration from SOAP to REST as a change of its own, with the same regression as any other release.

Number of the week

2028.2

is the release in which SOAP web services are removed and existing SOAP integrations stop working.

Source: Oracle NetSuite Help Center, SOAP Web Services Overview

Use this week

NetSuite Customization Regression Inventory →
An Integrations & auth sheet that flags each deadline automatically.
SIT Cycle Plan & Entry/Exit Criteria →
End-to-end scenarios that cross integrations, with a burn-down.

Next week: data migration. Whether you are leaving QuickBooks or adding a subsidiary, the data is under test too.

Get the playbook in your inbox, one week at a time

Subscribe free and every template in the library is yours.