NetSuite 2026.2 Salesforce Custom Data Sync: Setup and Verification

NetSuite Salesforce custom data sync lets administrators connect supported NetSuite records and Salesforce objects when prebuilt Salesforce Connector flows do not fit. In NetSuite 2026.2, each custom sync runs in one direction, with configurable field mappings, optional AI mapping suggestions, and automatic processing. Choose the source system first. As a recommended validation sequence, review the mappings and verify a record with Post Record before enabling automatic processing.

Key takeaways

• A single custom sync sends data from NetSuite to Salesforce or from Salesforce to NetSuite—not both ways.
• Setup requires a licensed NetSuite Connector Platform account, a valid Salesforce connection, object and field access, and configuration and metadata permissions.
• A Salesforce custom object needs an available field with both External ID and Unique enabled.
• Configure mappings on Data Mappings under Custom Record Types, or add suggestions with Suggest Field Mappings with AI.
• Post Record synchronizes and verifies a record. Using it before automatic processing is recommended, not a documented prerequisite.

When should you use a NetSuite Salesforce custom data sync?

Use a custom flow when a prebuilt Salesforce Connector flow does not meet the integration requirement. Start by describing the data you need to move and why the prebuilt flow does not meet that need. This gives administrators a concrete requirement against which to review the custom mappings.

Write down the intended source and destination before configuration. For example, sending NetSuite-maintained information to Salesforce calls for a NetSuite-to-Salesforce flow. Bringing Salesforce-maintained information into NetSuite calls for the opposite direction. One custom sync does not satisfy both requirements.

That distinction matters during acceptance testing. A successful transfer from NetSuite to Salesforce does not establish that a later Salesforce edit will return to NetSuite through that same sync. Test the configured direction rather than treating two matching records as evidence of bidirectional synchronization.

Related reading: Salesforce Connector management enhancements. Keep broader administration research separate from the configuration and record-level validation of this custom flow.

Prerequisites for a custom sync

Confirm readiness for the actual records, objects, and fields you intend to map. A valid connection is only one prerequisite: access to the selected Salesforce objects and fields, permission to configure data flows, and permission to view the selected metadata must also be checked.

Prerequisite	What to confirm before mapping
NetSuite Connector Platform account	The account is licensed and has a valid Salesforce connection.
Salesforce access	The required Salesforce objects and fields are accessible.
Configuration and metadata permissions	The responsible administrator can configure data flows and view metadata for the selected NetSuite records and Salesforce objects.
Salesforce custom-object field	An available field has both External ID and Unique enabled.

For a Salesforce custom object, both settings must be enabled on the same field. Enabling External ID on one field and Unique on another does not satisfy the requirement.

Ask the Salesforce administrator to confirm object access and custom-object field settings. Ask the NetSuite administrator or integration owner to confirm the selected records, metadata access, and flow-configuration readiness. Establish support for the selected NetSuite record before proceeding; custom-sync availability does not mean every record type is supported.

As a preparation step, capture the agreed direction and proposed field assignments in a short mapping worksheet. This is a recommended review artifact, not an additional Connector setup requirement. It gives both administrators a shared basis for checking the configuration.

Configure the one-way flow and field mappings

Review each assignment in the direction of the selected flow: which system supplies the value, and which field should receive it? Similar field names are a starting point for discussion, not proof that two fields represent the same business information.

1. Choose the source system. Decide whether this flow sends data from NetSuite to Salesforce or from Salesforce to NetSuite. Record that decision before building mappings.
2. Open the custom-sync configuration. In Salesforce Connector, go to Settings > Data Flows > Custom Data Sync.
3. Open the mapping area. On the Data Mappings page, use the Custom Record Types tab to configure field mappings.
4. Build the assignments. Configure mappings directly, or select Suggest Field Mappings with AI to add suggested mappings.
5. Review the business meaning. Check that each destination field represents the information its source field is intended to supply.

For the first test, consider a small, agreed set of assignments that you can verify clearly. This is a testing recommendation, not a documented limit on mappings. The goal is to make an incorrect assignment easier to identify, not to impose an unsupported configuration restriction.

Related reading: Salesforce data-source transfer overview. For this custom flow, explicitly record whether Salesforce supplies the values or receives them; do not assume changes travel both ways.

Worked example: prepare a NetSuite-to-Salesforce validation case

The following worksheet illustrates a configuration-and-test plan. It is not executable code, an import file, or a list of actual field IDs. Its descriptive labels stand in for fields you have confirmed in your account, and its acceptance checks are recommendations.

Custom sync validation worksheet

Business requirement:
Send an agreed reference value from a supported NetSuite record
 to an accessible Salesforce custom object.

Direction:
NetSuite to Salesforce

Readiness checks:
Licensed NetSuite Connector Platform account
Valid Salesforce connection
Access to selected Salesforce object and fields
Permission to configure data flows and view selected metadata
Available Salesforce custom-object field with:
  External ID enabled
  Unique enabled on that same field

Configuration location:
Settings > Data Flows > Custom Data Sync
Data Mappings > Custom Record Types

Illustrative field assignment:
Source: agreed NetSuite reference field
Destination: agreed Salesforce reference field
Test source value: SYNC-TEST-A
Expected destination value: SYNC-TEST-A

Mapping review:
Confirm the source and destination have the same business meaning.
Review any Suggest Field Mappings with AI suggestions.

Recommended record verification:
Select Post Record to synchronize and verify a record.
Compare the destination value with the expected value.
Accept this assignment only if the intended field contains SYNC-TEST-A.

Recommended release decision:
Enable automatic processing after the agreed verification passes.

The value SYNC-TEST-A is illustrative, not a Connector setting. Replace the descriptive labels with your confirmed field selections and choose a suitable test value. If the business requirement runs in the opposite direction, prepare the worksheet with Salesforce as the source and NetSuite as the destination.

The worksheet also makes review responsibilities explicit. The integration owner can confirm the direction and expected assignment, while the responsible administrators confirm access and field readiness. The tester then has an expected result to compare with the synchronized record rather than deciding what looks correct after the test.

Review AI suggestions and verify with Post Record

Suggest Field Mappings with AI adds suggested mappings. Review those suggestions against the same business requirement used for manually configured assignments: if this source field contains the test value, is this destination field the intended place for that information?

Use this recommended verification sequence:

1. Review the assignments. Compare each mapping with the agreed source, destination, and field meaning.
2. Choose a record with known source values. Write down the expected destination values before testing.
3. Select Post Record. Use Post Record to synchronize and verify a record.
4. Inspect the result. Compare the destination values with the expected assignments. If they differ, review the mappings before accepting the test.

For the worked example, acceptance means the agreed Salesforce destination field contains SYNC-TEST-A from the selected NetSuite source record. Finding a Salesforce record without checking the mapped value is not enough to validate that assignment.

Keep the conclusion proportional to the test. Verifying one assignment on one record provides evidence for that case; it should not replace review of the other assignments in the flow. This is a testing principle, not an additional product prerequisite.

Enable automatic processing and plan the handoff

A configured custom sync can be enabled for automatic processing. The recommended handoff is to do so after the integration owner accepts the field-level verification. Configuration completion alone is not evidence that each mapping expresses the intended requirement.

For an operational acceptance plan, retain the agreed direction, reviewed assignments, expected values, and record-verification observations. If you also need to demonstrate automatic processing, plan a separate observation of that mode rather than treating a Post Record test as proof of an automatic run.

These are recommended acceptance checks, not documented setup requirements. Do not build the plan around an assumed processing interval or conflict-resolution policy: the supplied source establishes neither.

Related reading: NetSuite Connector Platform Dashboard overview and setup. Keep the custom flow's source-to-destination checks explicit in your handoff notes.

FAQ

Can one custom data sync send changes in both directions?

No. Each custom sync runs in one direction: NetSuite to Salesforce or Salesforce to NetSuite. Choose the source system before configuring mappings.

What field settings does a Salesforce custom object require?

An available field on the custom object must have both External ID and Unique enabled. Both settings must be on the same field.

Where do I configure custom field mappings?

In Salesforce Connector, go to Settings > Data Flows > Custom Data Sync. On Data Mappings, use Custom Record Types, or select Suggest Field Mappings with AI to add suggestions.

Is Post Record required before automatic processing?

The source presents this as a recommended validation sequence, not a prerequisite. Review the mappings, use Post Record to synchronize and verify a record, and compare the destination values with the intended assignments before enabling automatic processing.