Can Salesforce and ServiceNow sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the Salesforce and ServiceNow initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling. Identify the ServiceNow account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Salesforce to ServiceNow sync run?

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

Will existing duplicates merge automatically?

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.

How do I map Salesforce fields to ServiceNow?

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.

What should I do if a record fails to sync?

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.

What does a Salesforce and ServiceNow integration cost?

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.

Which records should the Salesforce and ServiceNow pilot start with?

Start by reviewing Cases in Salesforce and Tasks in ServiceNow. 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.

CRM / Business productivity

Salesforce and ServiceNow integration

Plan how Salesforce and ServiceNow should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

Salesforce

ServiceNow

Review the integration scope

Teams building with Stacksync

Plan the connection your business needs

Explore a Salesforce and ServiceNow integration with a Stacksync engineer. Stacksync support for ServiceNow is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

01 / Business process

Start with one meaningful update

Identify the record that changes in Salesforce or ServiceNow, where it needs to appear, and which team depends on it.

02 / Data access

Establish the available connection

Bring the objects, account editions, and required directions. An engineer can review the connector path, permissions, and field access.

03 / Success criteria

Define a result you can verify

Agree on record matching, acceptable delay, expected volume, and how your team will resolve failed updates.

Explore the technical references

Technical referenceAvailable documentation, candidate record relationships, and questions for your technical review.

What records can you sync?

Explore the record types and read/write requirements for each system.

SalesforceRead and write support varies by recordWritable standard objects (subject to detection mode) · Writable custom objects (subject to detection mode)

Record types covered in the setup guide

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

Read the Salesforce connector guide

ServiceNowConnection and object support require review

Record types to review with Stacksync

Record type	Coverage and requirements
Incidents	Confirm support for this record type and the direction you need.
Change Requests	Confirm support for this record type and the direction you need.
Problems	Confirm support for this record type and the direction you need.
Service Catalog Requests	Confirm support for this record type and the direction you need.
Configuration Items (CMDB)	Confirm support for this record type and the direction you need.
Users and Groups	Confirm support for this record type and the direction you need.

Discuss ServiceNow requirements

Connection requirements and limits

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

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

ServiceNow

Integration interface: REST API (Table, Import Set, and Aggregate APIs); SOAP remains for legacy integrations
Authentication: Confirm the credentials, API plan, and permissions required for ServiceNow.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Limitations to check

Confirm Stacksync support for ServiceNow and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare your technical review

Use the worksheets and reference checks to capture record identity, ownership, and the result your business expects.

Implementation reference

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet

CSV · No email required · Record matching, ownership, and test cases

Business processCases Tasks

Support-to-work-item handoff: Salesforce Cases provides context for ServiceNow Tasks. These are related records, not equivalent entities.

Salesforce: Object support to establish
ServiceNow: 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

References: Salesforce: Cases documentation

Record matchingTasks and Events Tasks

Compare whether Salesforce Tasks and Events and ServiceNow Tasks describe the same task or work item in your business.

Salesforce: Object support to establish
ServiceNow: Object support to establish

Record identity

Use a stable task/work-item ID and preserve its project or parent-ticket reference.

Field ownership

Choose the owner of task status and assignment; destination workflow states may require an explicit transition.

Fields to include

Source task ID
Parent reference
Assignee
Status
Due date

References: Salesforce: Tasks and Events documentation

Architecture decision

Choose how to connect your systems

Choose a method around one example record and the update your business needs. Use Cases / Tasks to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Retain separate ticket and task IDs with an explicit relationship; several tasks may resolve one ticket. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your Salesforce and ServiceNow record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Cases / Tasks, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider explicit orchestration for the Cases / Tasks handoff.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit: Consider for a one-time Salesforce / ServiceNow migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow reference

From a business event to the right update

Open a workflow to see its trigger, record relationships, and expected result.

Support case or ticket process handoff

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

Start with Salesforce Cases and ServiceNow Tasks. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve requester, organization, team, and status references before ticket updates.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Escalate the same ticket twice, close one of several tasks, and verify that private ticket content is not copied into a public work item.

If it fails: Check whether a reply or notification was already sent before replaying ticket actions.

Task or work item sync test

Starting event: A change to the selected Tasks and Events or Tasks record needs a defined result in the other system.

Start with Salesforce Tasks and Events and ServiceNow Tasks. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve project, user, and parent-item references before the task.
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 a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones.

If it fails: Reconcile the destination state before retrying a transition to avoid reopening completed work.

Plan the customer lifecycle across Salesforce and ServiceNow

Starting event: A customer-facing change in Salesforce needs operational context in ServiceNow.

Select the relevant Accounts or Contacts records and identify whether the downstream relationship is a person, a company, a deal, or a reporting row.
Define which lifecycle transitions are informative and which should request a downstream action. Keep conversion and merge history connected to stable IDs.
Choose a representative reopened deal, changed contact identity, or reassigned account to test the handoff before expanding.

Expected result: The relationship survives a lifecycle change without creating a duplicate customer or triggering an unintended business action.

If it fails: Inspect merge/conversion history and existing destination records before replaying a lifecycle transition.

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

Rejected or repeated support case or ticket change

Investigate

Inspect Salesforce Cases and ServiceNow Tasks, their IDs, and the destination error.

Next action

Check whether a reply or notification was already sent before replaying ticket actions.

Rejected or repeated task or work item change

Investigate

Inspect Salesforce Tasks and Events and ServiceNow Tasks, their IDs, and the destination error.

Next action

Reconcile the destination state before retrying a transition to avoid reopening completed work.

A record type or update is unavailable

Investigate

Check the Salesforce and ServiceNow 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.

How updates move between Salesforce and ServiceNow

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

Salesforce ServiceNow Direction requires confirmation

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

Apply updatesConfirm that Stacksync can create or update the records you need in ServiceNow.

ServiceNow Salesforce Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Salesforce.

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.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare Salesforce and ServiceNow 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.

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

ServiceNow setup checklist

Identify the ServiceNow account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for ServiceNow, including read/write support, authentication, and initial-load limits.

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 Salesforce and ServiceNow planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Security and control for your integrations

Use SSO and SCIM to manage access, secure connection options to reach your systems, and record-level retry and revert controls to resolve sync errors.

Explore security controls

FAQ