Skip to content
ERP / CRM · Two-way sync platform

NetSuite and Salesforce integration — two-way sync

Connect Salesforce customer context with NetSuite’s financial records. Keep supported customer and contact data aligned, with explicit mappings and a clear path to resolve rejected updates.

  • Field mappings and sync direction under your control
  • Inspect and resolve record errors in one dashboard
Two-way sync for supported objects
stacksync.com
NetSuite
Salesforce
Explore the workflow

Built for teams where self-serve, reliability and scale matter

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Example workflow based on connector documentation

Give sales and finance a connected customer record

Start with Account, Customer, and Contact data before adding order-to-cash automation. A shared customer identity makes downstream billing and sales workflows easier to reconcile.

  1. Link the right legal customer

    Pair the Salesforce Account with a NetSuite Customer that represents a business. Preserve both IDs and subsidiary context; use an explicit rule when one sales account has several billing relationships.

  2. Separate sales and finance ownership

    Map the NetSuite legal customer name to a dedicated writable Salesforce Account field. Map Salesforce Contact details to the corresponding NetSuite Contact, with sales owning those values in this example.

  3. Observe an update and its result

    Change one selected field, check the matched record, and use the Issues dashboard if a validation rule rejects it. Keep Closed Won → Sales Order orchestration separate from customer-record sync.

Example mapping

Field relationships and ownership

Bring finance-owned customer details into Salesforce

Download the mapping worksheet

CSV · No email required

The workflow shows a mapping design, not an account-tested configuration. NetSuite Customer and Contact have documented read/write support. Salesforce fields must be writable and available to the integration user. A Salesforce opportunity and a NetSuite sales order are related business records, not interchangeable objects.

Example field relationships and ownership
SourceTargetField ownerMapping notes
NetSuite business Customer record IDLinked Salesforce Account record IDCRM and ERP administratorsRetain subsidiary and billing-relationship context; an account name alone cannot identify the financial customer.
NetSuite Customer legal nameDedicated Salesforce Account billing-name fieldNetSuite / financeAn example custom field to configure. Preserve Salesforce’s sales-facing account name separately.
Salesforce Contact phone and emailNetSuite Contact phone and emailSalesforce in this exampleMap writable fields with compatible types and link the contact to the correct customer before syncing dependent records.

Expected result: Sales can see the correct billing identity while finance keeps control of the NetSuite customer record.

Sources and documentation

Reviewed

What records can you sync?

Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.

NetSuite

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Customer
  • Contact
  • Nexus
  • Tax Type
  • Sales Tax Item
  • Billing Schedule Customer Subsidiary Relationship
  • Vendor
  • Vendor Category
  • Employee
  • Other Name Category
  • Vendor Subsidiary Relationship
  • Project
  • Project Status
  • Project Task
  • Job Type
  • Task
  • Partner
  • Customer Status
  • Phone Call
  • Support Case
  • Calendar Event
  • Note Type
  • Message
  • Job Status
Reading: ✅ Supported. Updating this object: ✅ Supported.
  • Invoice
  • Sales Order
  • Check
  • Credit Card Charge
  • Credit Card Refund
  • Credit Memo
  • Currency Revaluation
  • Customer Deposit
  • Customer Payment
  • Customer Refund
  • Deposit
  • Deposit Application
  • Estimate
  • Expense Report
  • Intercompany Journal Entry
  • Advanced Intercompany Journal Entry
  • Item Fulfillment
  • Item Receipt
  • Journal Entry
  • Opportunity
  • Purchase Order
  • Transfer
  • Vendor Bill
  • Vendor Credit
  • Vendor Payment
✅ Supported. Confirm field permissions and sync direction.
  • All custom objects
Reading: ✅ Supported. Updating this object: 🔓 Request Access.
  • Account
  • Accounting Period
  • Bin Transfer
  • Currency Rate
  • Price Level
  • Term
  • Subsidiary
  • Contact Category
  • Contact Role
  • Customer Category
  • Customer Message
  • Department
  • Expense Category
  • Classification
  • Location
Reading: ✅ Supported. Updating this object: 🕜 Coming soon.
  • Lead
  • Case
Reading: 🔓 Request Access. Updating this object: 🔓 Request Access.
  • Saved Searches
Reading: ✅ Supported. Updating this object: Read-only object.
  • Published Reports
Reading: 🔓 Request Access. Updating this object: Read-only object.

Read the NetSuite connector guide

Salesforce

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Writable standard objects (subject to detection mode)
  • Writable custom objects (subject to detection mode)
See connector requirements. Confirm field permissions and sync direction.

Read the Salesforce connector guide

Connection essentials

Review how each system connects, detects changes, and permits access to your records.

View setup requirements and limits
Connection requirementNetSuiteSalesforce
Integration interfaceSuiteTalk REST and SOAP web services, plus SuiteQL queriesREST, SOAP, and Bulk APIs
AuthenticationToken-Based AuthenticationOAuth login via a Salesforce user
Change detectionRead and write support is documented by object; the source guide does not establish one change-detection method or frequency for every object.Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used.
Read accessAvailable for supported recordsAvailable for supported records
Write accessAvailable for supported recordsAvailable for supported records

Architecture

Compare integration approaches

Choose the approach that fits your record model, field ownership, and connected systems.

Oracle NetSuite’s Salesforce Connector

Evaluate the vendor connector when the central requirement is Closed Won opportunity → NetSuite Sales Order, with order and fulfillment information returned to Salesforce.

Considerations: Oracle’s documented order return flow applies to orders created from Salesforce opportunities and requires configured lookups. Compare that transaction flow with the customer-record sync shown here.

Stacksync managed sync

Configure ongoing record sync in Stacksync: select objects and direction, edit field mappings, and inspect or retry rejected records in one dashboard.

Considerations: Your team defines record identity and business ownership. Supported objects, writable fields, and account permissions determine the available configuration.

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

  • SOC 2 Type II
  • ISO 27001
  • HIPAA BAA
  • GDPR
  • CCPA
  • DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

NetSuite
Integration interface
SuiteTalk REST and SOAP web services, plus SuiteQL queries
Authentication
Token-Based Authentication (TBA): enable REST Web Services (and SOAP Web Services) + Token-Based Authentication in NetSuite, create an integration record to get Consumer ID/Secret
Change detection
Read and write support is documented by object; the source guide does not establish one change-detection method or frequency for every object.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Have a NetSuite administrator enable web services and token-based authentication, then create an integration record and access token.
  • Provide the account ID, consumer credentials, and token credentials through the Stacksync connection form. Check object-specific read and write access.
Limitations to check
  • Write coverage varies: the saved support matrix marks several accounting objects as Coming soon and custom-object writes as Request Access.
  • NetSuite Account is an accounting object; do not map it to a CRM Account merely because the names resemble each other.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

NetSuite setup guide
Salesforce
Integration interface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling.
  • Test in a sandbox and make the intended objects and fields visible to the connected user.
Limitations to check
  • Object eligibility depends on write access and the selected detection mode. Non-triggerable objects cannot use trigger mode.
  • Read-only and formula fields need separate handling; a Salesforce platform capability does not establish support for every object.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Salesforce setup guide

Prepare NetSuite and Salesforce access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

NetSuite setup checklist
  • Have a NetSuite administrator enable web services and token-based authentication, then create an integration record and access token.
  • Provide the account ID, consumer credentials, and token credentials through the Stacksync connection form. Check object-specific read and write access.

Setup guides: Authorize NetSuite

Salesforce setup checklist
  • Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling.
  • Test in a sandbox and make the intended objects and fields visible to the connected user.

Setup guides: Authorize Salesforce

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the NetSuite and Salesforce planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

See Stacksync in action · Review current pricing

Record identity and field ownership

Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.

Download the mapping worksheet · CSV, no email required

Customer identity

Customer / Accounts

Before linking NetSuite Customer to Salesforce Accounts, check whether the customer is an individual or a company. Match the correct record type in each system.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

NetSuite
Documented record · Read: ✅ Supported. Write: ✅ Supported.
Salesforce
Object support to establish
Record identity
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership
Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

  • Source customer ID
  • Person/company classification
  • Legal entity or business unit
  • Destination identity reference
Record dependencies
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

References: NetSuite: Customer documentationSalesforce: Accounts documentation

Customer identity

Customer / Contacts

Before linking NetSuite Customer to Salesforce Contacts, check whether the customer is an individual or a company. Match the correct record type in each system.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

NetSuite
Documented record · Read: ✅ Supported. Write: ✅ Supported.
Salesforce
Object support to establish
Record identity
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership
Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

  • Source customer ID
  • Person/company classification
  • Legal entity or business unit
  • Destination identity reference
Record dependencies
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

References: NetSuite: Customer documentationSalesforce: Contacts documentation

Record matching

Contact / Contacts

Compare whether NetSuite Contact and Salesforce Contacts describe the same contact in your business.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

NetSuite
Documented record · Read: ✅ Supported. Write: ✅ Supported.
Salesforce
Object support to establish
Record identity
Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.
Field ownership
Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.

Fields to include

  • Source person ID
  • Display name
  • Email address
  • Organization reference
  • Consent state
Record dependencies
Resolve the organization relationship and any owner or consent references required by the destination.
Validation
Test an email change, two records sharing an email, and a person associated with multiple organizations.
Recovery
Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

References: NetSuite: Contact documentationSalesforce: Contacts documentation

Business process

Sales Order / Opportunities

Approved sales handoff: Salesforce Opportunities provides context for NetSuite Sales Order. These are related records, not equivalent entities.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

NetSuite
Documented record · ✅ Supported
Salesforce
Object support to establish
Record identity
Link the originating deal ID to a newly assigned order ID; do not reuse the deal ID as an order number.
Field ownership
Define the approval event and the customer/product data required to create an order. A sales stage alone must not authorize every order.

Fields to include

  • Source record reference
  • Destination record reference
  • Approved handoff state
  • Duplicate-detection key
Record dependencies
Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Validation
Repeat the approved handoff and verify that it locates the existing order; test a reopened deal without silently cancelling fulfillment.
Recovery
Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

References: NetSuite: Sales Order documentationSalesforce: Opportunities documentation

Record matching

Lead / Leads

Compare whether NetSuite Lead and Salesforce Leads describe the same prospect or lead in your business.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

NetSuite
Documented record · Read: 🔓 Request Access. Write: 🔓 Request Access.
Salesforce
Object support to establish
Record identity
Retain the lead ID and record its relationship to any converted contact or company.
Field ownership
Choose which system may qualify or convert the lead; do not infer identical lifecycle stages.

Fields to include

  • Source lead ID
  • Qualification status
  • Owner reference
  • Conversion reference
Record dependencies
Resolve owner and campaign references and decide how conversion changes the identity relationship.
Validation
Convert a test lead after the first load and verify that it does not create a duplicate person or orphan its activity.
Recovery
Repair the lead-to-contact conversion link before replaying later updates.

References: NetSuite: Lead documentationSalesforce: Leads documentation

Business process

Case / Tasks and Events

Support-to-work-item handoff: NetSuite Case provides context for Salesforce Tasks and Events. These are related records, not equivalent entities.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

NetSuite
Documented record · Read: 🔓 Request Access. Write: 🔓 Request Access.
Salesforce
Object support to establish
Record identity
Retain separate ticket and task IDs with an explicit relationship; several tasks may resolve one ticket.
Field ownership
Choose which ticket conditions create a work item and which task outcomes may update the support case.

Fields to include

  • Source record reference
  • Destination record reference
  • Approved handoff state
  • Duplicate-detection key
Record dependencies
Resolve requester, organization, team, and status references before ticket updates.
Validation
Escalate the same ticket twice, close one of several tasks, and verify that private ticket content is not copied into a public work item.
Recovery
Check whether a reply or notification was already sent before replaying ticket actions.

References: NetSuite: Case documentationSalesforce: Tasks and Events documentation

Workflow scenarios and expected results

Customer sync test

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Customer or Accounts record needs a defined result in the other system.

  1. Start with NetSuite Customer and Salesforce Accounts. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve person or company type, legal entity, business role, and any billing account before transactions.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Customer sync test

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Customer or Contacts record needs a defined result in the other system.

  1. Start with NetSuite Customer and Salesforce Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve person or company type, legal entity, business role, and any billing account before transactions.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Contact sync test

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Contact or Contacts record needs a defined result in the other system.

  1. Start with NetSuite Contact and Salesforce Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve the organization relationship and any owner or consent references required by the destination.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an email change, two records sharing an email, and a person associated with multiple organizations.

If it fails: Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

Reconcile NetSuite business records with Salesforce

Validate the selected objects and operations even where connector-level direction is documented.

Starting event: A finance-owned record in NetSuite needs operational visibility through Accounts or Contacts.

  1. Select Customer or Vendor with the correct legal entity, period, and currency.
  2. Define a reporting relationship in Salesforce; do not equate customer records, ledger accounts, and posted transactions.
  3. Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Customer / Accounts

Test case

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Expected result

The expected customer relationship is preserved with no duplicate action or unintended write.

Customer / Contacts

Test case

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Expected result

The expected customer relationship is preserved with no duplicate action or unintended write.

Contact / Contacts

Test case

Test an email change, two records sharing an email, and a person associated with multiple organizations.

Expected result

The expected contact relationship is preserved with no duplicate action or unintended write.

Sales Order / Opportunities

Test case

Repeat the approved handoff and verify that it locates the existing order; test a reopened deal without silently cancelling fulfillment.

Expected result

The expected deal or opportunity relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated customer change

Investigate

Inspect NetSuite Customer and Salesforce Accounts, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated customer change

Investigate

Inspect NetSuite Customer and Salesforce Contacts, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated contact change

Investigate

Inspect NetSuite Contact and Salesforce Contacts, their IDs, and the destination error.

Next action

Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

A record type or update is unavailable

Investigate

Check the NetSuite and Salesforce connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between NetSuite and Salesforce

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

NetSuite Salesforce Timing depends on the connected systems

Detect changesRead and write support is documented by object; the source guide does not establish one change-detection method or frequency for every object.

Apply updatesSelected writable fields update in Salesforce. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Salesforce NetSuite Timing depends on the connected systems

Detect changesStacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.

Apply updatesSelected writable fields update in NetSuite. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Update timing and record limits
  • Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
FAQ

NetSuite and Salesforce integration FAQ

Further reading

Guides and resources

Next step

See your workflow in Stacksync

Walk through your NetSuite and Salesforce records, field mappings, and requirements with an integration engineer.

See Stacksync in action Explore plans and pricing