EBENSTEAD
Menu
Ebenstead / NetSuite Intelligence

Connect additional Salesforce and NetSuite records with a custom data sync

NetSuite Connector now supports configurable data flows for supported records and Salesforce objects that the standard connector does not cover. Choose one direction, map the identifiers and fields, and test a record before enabling ongoing synchronization.

← All NetSuite Intelligence

IntegrationsOptional improvement
Why it matters

A supported custom flow may eliminate a manual data handoff, but inconsistent identity mapping or conflicting edits can create data problems.

First step

Identify one missing Salesforce–NetSuite data flow, then validate supported objects, identifiers and access before enabling it.

Suggested owner

Salesforce administrator and NetSuite integration owner

Who should check?

Organizations using a licensed NetSuite Connector Platform with a valid Salesforce connection, suitable NetSuite and Salesforce record access, and an identified gap in a prebuilt Salesforce Connector flow. Customers without this connector or eligible objects are not presumed affected.

Availability, not a migration deadline

  1. October 19, 2026 — Oracle release-note updateOracle documents a custom data-sync option for NetSuite Connector and Salesforce; this is the stated documentation date, not a customer-specific activation date.
  2. NetSuite Connector 2026.2 — capabilityAvailable to eligible licensed Connector Platform deployments, subject to records, access and configured direction.

Check your Oracle account notice before scheduling an update.

A practical response

  • Choose one missing business data flow and agree which system owns each synchronized field; confirm licensing, connection, permissions and unique identity mapping.
  • Prepare a signed functional requirements document covering source/destination objects, mappings, exclusions, exception monitoring and acceptance criteria; configure and test one representative record using Post Record in an authorized environment.
  • Activate the agreed one-way flow only after testing, verify the scheduled or real-time behavior, document any initial-load/backfill gap, then complete client UAT and final signoff.

What we’ll review

Licensed NetSuite Connector Platform and active Salesforce connection; direction and owner of the data; supported source/target records; integration-user permissions; unique Salesforce external ID and corresponding NetSuite ID field; required destination fields, related records, sample records and test criteria.

Sources and updates

Oracle documentation

NetSuite Connector Salesforce custom sync release notice ↗Oracle document date: 2026-10-19 · Last successful source check:
Salesforce custom sync prerequisites and limitations ↗Oracle publication/update date not stated on this page. · Last successful source check:
Salesforce custom sync setup, mappings, timing and test ↗Oracle publication/update date not stated on this page. · Last successful source check:

Update history

  • 2026-10-28 — First verified and published by Ebenstead October 28 from Oracle's October 19 Connector release update; optional capability, not a newly announced October 28 product release.

Follow this topic via RSS

Let’s discuss your NetSuite needs

Share your priorities and we’ll discuss the right approach for your team.

Sending a message won’t subscribe you or connect to your account.

Topic: Salesforce-to-NetSuite Custom Data Flow

Please leave out passwords and sensitive records. We’ll use your details to reply, not subscribe you to marketing. Privacy information.