NetSuite SuiteTalk SOAP to REST Migration Checklist

0%

0 of 34 items complete

11 critical items still open - these are the highest-risk gaps.

Download checklist:

1. Inventory

List every integration that calls SuiteTalk SOAP, including scripts, middleware and vendor connectorsCRITICALRecord the SOAP operations each one uses (get, search, add, update, upsert, delete)CRITICALRecord the record types and custom fields touched per operationNote call volume, schedule and peak times for each integrationIdentify which integrations are vendor-owned and need the vendor to migrateCheck Oracle release notes for the current SOAP support timelineCRITICAL

2. Capability mapping

Confirm each record type is available in the REST API BrowserCRITICALMap SOAP search calls to REST filters or SuiteQL queriesMap saved search usage to SuiteQL or a RESTlet where REST cannot reproduce itMap upsert calls to external ID addressing (eid:) or PUTCheck that custom record and custom field names resolve in the REST metadata catalogList sublist handling needs and decide on expandSubResources or sublist callsIdentify operations with no REST equivalent and plan a RESTletCRITICAL

3. Authentication and roles

Choose OAuth 2.0 or token-based authentication for RESTCRITICALEnable the REST Web Services feature and confirm role permissionCRITICALCreate or adjust an integration role with the least privilege neededCreate separate integration records for sandbox and productionStore secrets in a vault, not in code or config files

4. Build and behavior

Use the account-specific host with the correct sandbox suffixImplement limit and offset paging with a stable sortUse the fields parameter to cut payload sizeHandle HTTP errors, 429 concurrency responses and retry with backoffCRITICALAdd idempotency using external IDs so retries do not duplicate recordsCRITICALParse the REST error body and log the full response for failed callsCheck date, currency and list value formats against SOAP behaviorRespect the account concurrency limit shared with other integrations

5. Testing and cutover

Run old and new integrations in parallel in sandbox and compare resultsCRITICALTest with production-sized data and peak loadTest failure cases: invalid data, missing permission, locked recordAgree a cutover window and freeze changes during itKeep the SOAP path available for rollback until the new path is verifiedCRITICALMonitor errors and throughput for the first weeks after cutoverRetire SOAP integration users and tokens after rollback is no longer neededUpdate runbooks and documentation

Treat every critical item as a gate. Do not cut over while a critical item is open. Verify details against current Oracle documentation, since REST coverage and support timelines change between releases.

Integration migration review

Optional review of your SOAP inventory and REST migration plan.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Work through the five groups in order and mark items as you finish them. Critical items are the ones that cause outages or data problems if skipped, such as missing a vendor-owned integration or cutting over without a rollback path. Export the completed list as evidence for change management, and attach it to the release ticket.

What changes between SOAP and REST

SOAP uses typed XML requests against one endpoint, while REST uses JSON, resource URLs and HTTP verbs. Searches become filters or SuiteQL queries, paging is done with limit and offset, and upserts rely on external ID addressing. Not every record type or operation is exposed in REST, so coverage must be checked per integration against the REST API Browser and metadata catalog before any rewrite begins.

XML to JSON payloads
Search calls to REST filters or SuiteQL
Typed operations to HTTP verbs
Gaps filled with RESTlets where needed

Risk areas

The biggest risks are searches that depend on saved search features, sublist-heavy transactions whose payloads change shape, concurrency throttling when many calls run in parallel and implicit behavior, such as default values or sourcing, that differs between APIs. Compare outputs record by record in sandbox and sample production data before cutover rather than trusting a few happy-path calls.

Common mistakes

Teams underestimate vendor connectors, skip the inventory and discover forgotten scripts later, migrate without idempotency and create duplicates on retry, and cut over without a way back. Allow time for parallel running, and assign an owner for each integration so nothing is orphaned.

Frequently Asked Questions

Is SuiteTalk SOAP being retired?

Oracle has published a deprecation and support timeline for SOAP web services in its release notes. Check the current notes for your account, since dates and details can change, and plan the migration before the final support date.

Does REST cover everything SOAP does?

Not entirely. Some record types and operations are not available in REST, and saved search behavior differs. Check each integration against the REST API Browser and use SuiteQL or a RESTlet to fill gaps.

How should I handle retries safely?

Address records by external ID so a repeated call updates rather than creates, and back off on 429 or transient errors. Log request and response bodies for failed calls so you can reconcile.

Should I migrate everything at once?

Usually no. Migrate integration by integration, starting with low-risk ones, run old and new in parallel and keep the SOAP path for rollback until each is verified.

Netray builds custom NetSuite integrations and can review your migration plan, with read-only checks and human approval on any write-back.

Talk to an Expert Explore More Free Tools

Related Tools

NetSuite

More NetSuite tools

See all