Salesforce Custom Data Syncs in NetSuite Connector

Custom data syncs let administrators connect supported NetSuite records and Salesforce objects when prebuilt Salesforce Connector flows do not meet their needs. Each sync runs in one direction. Configuration includes field mappings, optional AI mapping suggestions, automatic processing, and a Post Record action to synchronize and verify a record.

When Should You Use a Custom Data Sync?

Custom data syncs provide an alternative when a prebuilt Salesforce Connector flow does not meet your integration needs. Each sync runs either from NetSuite to Salesforce or from Salesforce to NetSuite; a single custom sync is not bidirectional. Decide which application supplies the data and which receives it before configuring mappings.

For broader context on Connector synchronization, see NetSuite Connector data syncs. Keep the configuration steps below scoped to Salesforce Connector.

What Must Be Ready Before Configuration?

You need:

• A licensed NetSuite Connector Platform account with a valid Salesforce connection.
• Access to the Salesforce objects and fields used by the sync.
• Permission to configure data flows and view metadata for the selected NetSuite records and Salesforce objects.

For Salesforce custom objects, configure an available field with both required properties:

Setting only one property does not satisfy the requirement. Check both before testing a sync involving a Salesforce custom object.

How Do You Configure and Verify a Custom Sync?

In Salesforce Connector, go to Settings > Data Flows > Custom Data Sync. On the Data Mappings page, open the Custom Record Types tab.

Configure field mappings there, or click Suggest Field Mappings with AI to add suggested mappings. As a validation practice, review suggestions against the intended source and destination fields rather than treating them as confirmed business rules.

Select Post Record to synchronize and verify a record. A configured sync can also be enabled for automatic processing. Consider verifying a representative record before enabling automatic processing; that ordering is a recommendation, not a documented prerequisite.

Who This Affects

• Administrators configuring flows: Confirm licensing, connection access, and configuration permissions.
• Teams responsible for Salesforce access: Confirm object and field access, plus both required properties for custom-object fields.
• Integration teams: Assess whether supported records and objects meet needs that prebuilt flows cannot address.

For related release context, consult the NetSuite 2026.2 release-note updates.

Key Takeaways

• Each custom sync operates in one direction only.
• Field mappings can be configured manually or added through AI suggestions.
• Salesforce custom objects require an available field configured as both External ID and Unique.
• Post Record synchronizes and verifies a record; configured syncs can be enabled for automatic processing.