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.
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.
01
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.
02
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.
03
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.
AI assistant
Set up NetSuite and Salesforce from Claude or ChatGPT
Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.
1. Add the Stacksync MCP server
Server URL
https://mcp.stacksync.com/mcp
In Claude
Open Customize → Connectors, select + Add, then Add custom connector.
Name it Stacksync and enter https://mcp.stacksync.com/mcp.
Select Connect, sign in to Stacksync and choose your workspace.
In ChatGPT
Open Settings → Apps → Advanced settings and turn on Developer mode.
Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
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
Source
Target
Field owner
Mapping notes
SourceNetSuite business Customer record ID
TargetLinked Salesforce Account record ID
Field ownerCRM and ERP administrators
Mapping notesRetain subsidiary and billing-relationship context; an account name alone cannot identify the financial customer.
SourceNetSuite Customer legal name
TargetDedicated Salesforce Account billing-name field
Field ownerNetSuite / finance
Mapping notesAn example custom field to configure. Preserve Salesforce’s sales-facing account name separately.
SourceSalesforce Contact phone and email
TargetNetSuite Contact phone and email
Field ownerSalesforce in this example
Mapping notesMap 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.
SuiteTalk REST and SOAP web services, plus SuiteQL queries
REST, SOAP, and Bulk APIs
Authentication
Token-Based Authentication
OAuth login via a Salesforce user
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.
Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used.
Read access
Available for supported records
Available for supported records
Write access
Available for supported records
Available 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Start with NetSuite Customer and Salesforce Accounts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
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.
Start with NetSuite Customer and Salesforce Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
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.
Start with NetSuite Contact and Salesforce Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the organization relationship and any owner or consent references required by the destination.
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.
Select Customer or Vendor with the correct legal entity, period, and currency.
Define a reporting relationship in Salesforce; do not equate customer records, ledger accounts, and posted transactions.
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.
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
Stacksync connects NetSuite and Salesforce with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Have a NetSuite administrator enable web services and token-based authentication, then create an integration record and access token. Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling. Use the pair worksheet to record ownership and acceptance criteria.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Start by reviewing Customer in NetSuite and Accounts in Salesforce. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
This pair can involve both record sync and process handoffs. Keep the Sales Order / Opportunities relationship explicit: copying fields and creating a downstream business transaction require different validation.
.png){kind=small}
