Skip to content
CRM

Close to Salesforce integration — real-time, two-way sync

Keep Close and Salesforce in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

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
Why teams connect Close and Salesforce

Run Close and Salesforce side by side with the same accounts and contacts in both, whether they serve different teams or one is replacing the other.

Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.

Stacksync syncs Tasks, Custom Activities, Custom Fields, Users in Close with Opportunities, Cases, Campaigns, Tasks and Events in Salesforce in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.

Common use cases

  • Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
  • Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
  • Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
  • Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.

Post-acquisition consolidation

Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.

Migration with a parallel run

When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.

Divisional or regional split

Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.

What you can sync between Close and Salesforce

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Close objects Salesforce objects
Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce.
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated.
Users Sales reps referenced as owners on leads, opportunities, and activities. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP.
Smart Views Saved lead searches that can scope which records a segment-based sync pulls. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records.
Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines.
Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close.
What ships with Close ⇄ Salesforce

Connect Close and Salesforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Salesforce connection.

Real-time

Two-way sync

Changes in Close or Salesforce instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Close or Salesforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Close or Salesforce record.

Observability

Monitoring

Track your Close ⇄ Salesforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Close and Salesforce.

How the Close and Salesforce connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

Salesforce

Integration surface
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
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect Close to Salesforce — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Close and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Close connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Close and Salesforce objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Close ⇄ Salesforce
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Close Salesforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Close and Salesforce integration FAQ

SECURITY

Security teams love Stacksync

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
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Close and Salesforce.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.