Skip to content
CRM / Data warehouse · Two-way sync platform

Salesforce and Snowflake integration — two-way sync

Keep supported Salesforce and Snowflake records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.

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

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

Company reporting workflow

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

Starting eventA change involving Salesforce Accounts or the proposed company table in Snowflake needs a defined result in the other system.

  1. Start with Salesforce Accounts and the proposed company table in Snowflake. Use the record-matching and field-ownership rules from your mapping worksheet.

  2. Resolve parent organizations, business units, and currency references before dependent transactions.

  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyUse two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

Review records and field ownership

Mapping essentials

Records and field ownership

Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.

Download the mapping worksheet

CSV · No email required

Example record relationships between Salesforce and Snowflake
Salesforce recordSnowflake recordRecord matchingField ownership
AccountsProposed record; confirm Stacksync object support.Reporting datasetProposed company tableProposed table; choose its name and schema.Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.Assign ownership separately for relationship details and finance-controlled billing details.
ContactsProposed record; confirm Stacksync object support.Reporting datasetProposed contact tableProposed table; choose its name and schema.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.Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.
OpportunitiesProposed record; confirm Stacksync object support.Reporting datasetProposed deal or opportunity tableProposed table; choose its name and schema.Keep the opportunity/deal ID separate from any later order or invoice ID.The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules.

Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.

Why teams connect Salesforce and Snowflake

Put your Salesforce and Snowflake data to work

Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one Salesforce and Snowflake workflow to test, define what success looks like, and decide who handles failed updates.

  • Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.

  • Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.

  • Land CRM and ERP records in Snowflake continuously so BI reflects business systems without nightly batch ETL

  • Activate modeled Snowflake tables by syncing scores and attributes back into CRM fields sales can act on

What records can you sync?

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

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

Snowflake

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Standard tables (including Permanent, Transient and Temporary tables)
✅ Supported. Confirm field permissions and sync direction.
  • Views (including materialized and non-materialized views)
🕘 Coming soon. Confirm field permissions and sync direction.
  • External tables
❌ Not supported. Confirm field permissions and sync direction.

Read the Snowflake connector guide

Connection essentials

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

View setup requirements and limits
Connection requirementSalesforceSnowflake
Integration interfaceREST, SOAP, and Bulk APIsSQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
AuthenticationOAuth login via a Salesforce userDedicated Snowflake service user + role with RSA key-pair authentication
Change detectionStacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used.The saved Stacksync guide does not specify the change-detection mechanism.
Read accessAvailable for supported recordsAvailable for supported records
Write accessAvailable for supported recordsAvailable for supported records

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

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
Snowflake
Integration interface
SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
Authentication
Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles
Change detection
The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Have an administrator run the documented setup script for a dedicated service user and role with RSA key-pair authentication.
  • Specify the correct warehouse, database, schema, and account identifier. Verify table grants for the service role.
  • Existing tables need a non-null primary key with a UUID_STRING() default, as specified in the connector guide.
Limitations to check
  • The saved support matrix excludes external tables and marks materialized and ordinary views as not yet supported.
  • Geography and geometry fields are excluded by the saved connector guide.
Technical documentation

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

Snowflake setup guide

Prepare Salesforce and Snowflake 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

Snowflake setup checklist
  • Have an administrator run the documented setup script for a dedicated service user and role with RSA key-pair authentication.
  • Specify the correct warehouse, database, schema, and account identifier. Verify table grants for the service role.
  • Existing tables need a non-null primary key with a UUID_STRING() default, as specified in the connector guide.

Setup guides: Authorize Snowflake

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 Snowflake 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

Reporting dataset

Accounts / Proposed company table in Snowflake (choose its name)

Plan a company dataset while preserving its source meaning.

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

Salesforce
Object support to establish
Snowflake
Your database schema
Record identity
Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.
Field ownership
Assign ownership separately for relationship details and finance-controlled billing details.

Fields to include

  • Source record ID
  • Legal or display name
  • Business-unit reference
  • Lifecycle status
Record dependencies
Resolve parent organizations, business units, and currency references before dependent transactions.
Validation
Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
Recovery
Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

References: Salesforce: Accounts documentation

Reporting dataset

Contacts / Proposed contact table in Snowflake (choose its name)

Plan a contact dataset while preserving its source meaning.

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

Salesforce
Object support to establish
Snowflake
Your database schema
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: Salesforce: Contacts documentation

Reporting dataset

Opportunities / Proposed deal or opportunity table in Snowflake (choose its name)

Plan a deal or opportunity dataset while preserving its source meaning.

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

Salesforce
Object support to establish
Snowflake
Your database schema
Record identity
Keep the opportunity/deal ID separate from any later order or invoice ID.
Field ownership
The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules.

Fields to include

  • Source deal ID
  • Stage
  • Amount and currency
  • Expected close date
  • Company reference
Record dependencies
Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Validation
Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
Recovery
Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

References: Salesforce: Opportunities documentation

Reporting dataset

Leads / Proposed prospect or lead table in Snowflake (choose its name)

Plan a prospect or lead dataset while preserving its source meaning.

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

Salesforce
Object support to establish
Snowflake
Your database schema
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: Salesforce: Leads documentation

Reporting dataset

Cases / Proposed support case or ticket table in Snowflake (choose its name)

Plan a support case or ticket dataset while preserving its source meaning.

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

Salesforce
Object support to establish
Snowflake
Your database schema
Record identity
Retain the ticket ID and distinguish parent tickets, follow-ups, and merged cases.
Field ownership
Agree which queue controls status and assignee; keep private comments distinct from public replies.

Fields to include

  • Source ticket ID
  • Requester reference
  • Status
  • Priority
  • Assigned team
Record dependencies
Resolve requester, organization, team, and status references before ticket updates.
Validation
Test a merged ticket, a private note, a reopened case, and an attachment with restricted access.
Recovery
Check whether a reply or notification was already sent before replaying ticket actions.

References: Salesforce: Cases documentation

Reporting dataset

Products and Price Books / Proposed product or catalog item table in Snowflake (choose its name)

Plan a product or catalog item dataset while preserving its source meaning.

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

Salesforce
Object support to establish
Snowflake
Your database schema
Record identity
Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Field ownership
Assign ownership for catalog content, price, and stock separately.

Fields to include

  • Source product ID
  • SKU or variant reference
  • Description
  • Unit of measure
  • Price-list reference
Record dependencies
Resolve units, variants, categories, and applicable price lists before order lines.
Validation
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Recovery
Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

References: Salesforce: Products and Price Books documentation

Compare integration approaches

Use Salesforce Accounts and Snowflake Proposed company table in Snowflake (choose its name) for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.

Stacksync managed sync

Best fit
Two-way sync for supported objects. Choose the records, writable fields, and permissions for your workflow.
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 the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. 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 Snowflake 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 Accounts / Proposed company table in Snowflake (choose its name), update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider when Salesforce and Snowflake need a transformation, approval, or action outside a direct record sync.
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 / Snowflake 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 scenarios and expected results

Company reporting workflow

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

Starting event: A change to the selected Accounts or Proposed company table in Snowflake (choose its name) record needs a defined result in the other system.

  1. Start with Salesforce Accounts and Snowflake Proposed company table in Snowflake (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve parent organizations, business units, and currency references before dependent 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: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

If it fails: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

Contact reporting workflow

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

Starting event: A change to the selected Contacts or Proposed contact table in Snowflake (choose its name) record needs a defined result in the other system.

  1. Start with Salesforce Contacts and Snowflake Proposed contact table in Snowflake (choose its name). 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.

Deal or opportunity reporting workflow

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

Starting event: A change to the selected Opportunities or Proposed deal or opportunity table in Snowflake (choose its name) record needs a defined result in the other system.

  1. Start with Salesforce Opportunities and Snowflake Proposed deal or opportunity table in Snowflake (choose its name). Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Map the customer and sales pipeline before the opportunity; map stage values deliberately.
  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 a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.

If it fails: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

Plan the customer lifecycle across Salesforce and Snowflake

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

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

  1. Select the relevant Accounts or Contacts records and identify whether the downstream relationship is a person, a company, a deal, or a reporting row.
  2. Define which lifecycle transitions are informative and which should request a downstream action. Keep conversion and merge history connected to stable IDs.
  3. 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.

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.

Accounts / Proposed company table in Snowflake (choose its name)

Test case

Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

Expected result

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

Contacts / Proposed contact table in Snowflake (choose its name)

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.

Opportunities / Proposed deal or opportunity table in Snowflake (choose its name)

Test case

Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.

Expected result

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

Leads / Proposed prospect or lead table in Snowflake (choose its name)

Test case

Convert a test lead after the first load and verify that it does not create a duplicate person or orphan its activity.

Expected result

The expected prospect or lead 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 company change

Investigate

Inspect Salesforce Accounts and Snowflake Proposed company table in Snowflake (choose its name), their IDs, and the destination error.

Next action

Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

Rejected or repeated contact change

Investigate

Inspect Salesforce Contacts and Snowflake Proposed contact table in Snowflake (choose its name), 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.

Rejected or repeated deal or opportunity change

Investigate

Inspect Salesforce Opportunities and Snowflake Proposed deal or opportunity table in Snowflake (choose its name), their IDs, and the destination error.

Next action

Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

A record type or update is unavailable

Investigate

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

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

Salesforce Snowflake 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 Snowflake. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Snowflake Salesforce Timing depends on the connected systems

Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.

Apply updatesSelected writable fields update in Salesforce. 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

Salesforce and Snowflake integration FAQ

Further reading

Guides and resources

Next step

See your workflow in Stacksync

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

See Stacksync in action Explore plans and pricing