Skip to content
Marketing ⇄ Database

Salesforce Marketing Cloud to SQL Server integration — real-time, two-way sync

Keep Salesforce Marketing Cloud and SQL Server 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 Salesforce Marketing Cloud and SQL Server

Give your team Salesforce Marketing Cloud's contacts, campaigns, and engagement in SQL Server: query them with SQL, push audiences built from your own data back to Salesforce Marketing Cloud, and skip the marketing API.

Salesforce Marketing Cloud holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in SQL Server, hard to get into campaigns without manual exports.

Stacksync mirrors Journeys (Journey Builder), Content Assets (Content Builder), Automations (Automation Studio), Tracking Events from Salesforce Marketing Cloud into Databases, Schemas, Tables, Views in SQL Server field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in SQL Server, from usage, orders, or account status, sync back into Salesforce Marketing Cloud to drive campaigns and ads, with Salesforce Marketing Cloud kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Mirror on-premises ERP data held in SQL Server into cloud CRM and support systems
  • 02 Feed a cloud warehouse from SQL Server continuously using native CDC instead of SSIS batch jobs
  • 03 Sync Contacts and Subscriber Key subscription status between Marketing Cloud and a CRM so suppression and opt-in state stay current before the next send.
  • 04 Stream Event Notification Service callbacks for transactional sends, bounces, opens, and clicks into a database in near real time alongside CRM contact records.

Common sync patterns

Keep contact attributes consistent

Lifecycle stage, subscription status, or plan maintained on either side stays current on the other, ending exports and dual data entry.

Query Salesforce Marketing Cloud like a database

Contacts, leads, audiences, and campaign metrics from Salesforce Marketing Cloud live in SQL Server as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.

Build audiences from your own data

Segments computed in SQL Server from product usage, orders, or account status sync into Salesforce Marketing Cloud as lists or audiences, so campaigns and ads target the people your data says they should.

What you can sync between Salesforce Marketing Cloud and SQL Server

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.

Salesforce Marketing Cloud objects SQL Server objects How this pairing syncs
Automations (Automation Studio) Scheduled or triggered workflows of import, query, extract, and send activities managed via /automation/v1/automations; SQL Query Activities read Data Views and write results into Data Extensions. Columns Field-level mapping targets with T-SQL types. Automations (Automation Studio) is specific to Salesforce Marketing Cloud and Columns to SQL Server — each maps to any object or custom field on the other side.
Tracking Events Sent, Open, Click, Bounce, Unsubscribe, and NotSent events retrieved through the SOAP tracking objects (SentEvent, OpenEvent, ClickEvent, BounceEvent) or the Automation Studio Data Views (_Sent, _Open, _Click, _Bounce) - the queryable record of engagement per send. Primary and Unique Keys Match keys for idempotent upserts and conflict handling. Tracking Events is specific to Salesforce Marketing Cloud and Primary and Unique Keys to SQL Server — each maps to any object or custom field on the other side.
Transactional Sends Triggered and transactional Email/SMS delivered through the Messaging API (/messaging/v1/email/messages/{key}); the Event Notification Service reports each message's disposition (delivered, bounced, opened, clicked). CDC Change Tables System-populated tables holding captured inserts, updates, and deletes for consumers. Transactional Sends is specific to Salesforce Marketing Cloud and CDC Change Tables to SQL Server — each maps to any object or custom field on the other side.
Data Extensions Custom relational tables that store subscriber, audience, and arbitrary business data; rows are read via GET /data/v1/customobjectdata or SOAP Retrieve and upserted via the synchronous rowset PUT or the async /data/v1/async/dataextensions rows endpoint. This is the primary two-way surface. Stored Procedures T-SQL logic that can validate or post-process synced rows. Data Extensions is specific to Salesforce Marketing Cloud and Stored Procedures to SQL Server — each maps to any object or custom field on the other side.
Contacts / Subscribers The contact model keyed by Subscriber Key, holding channel addresses and subscription status; managed through the Contacts API (/contacts/v1/contacts) and the SOAP Subscriber object, and referenced by every send and journey. Databases Instance-level databases that scope a sync's reads and writes. Contacts / Subscribers is specific to Salesforce Marketing Cloud and Databases to SQL Server — each maps to any object or custom field on the other side.
Journeys (Journey Builder) Multi-step automated flows read and managed via /interaction/v1/interactions; contacts are injected by firing an entry event to /interaction/v1/events with an EventDefinitionKey and contact data. Schemas Namespaces (dbo and custom) used to organize synced tables. Journeys (Journey Builder) is specific to Salesforce Marketing Cloud and Schemas to SQL Server — each maps to any object or custom field on the other side.

How changes propagate between Salesforce Marketing Cloud and SQL Server

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Salesforce Marketing Cloud SQL Server Sub-second propagation

DetectionSalesforce Marketing Cloud notifies Stacksync of record changes through webhook events. The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback.

DeliveryEach detected change is applied to SQL Server as a row-level write, with types converted between the two schemas.

SQL Server Salesforce Marketing Cloud Sub-second propagation

DetectionChanges in SQL Server are captured at the source via change data capture — no polling loop against its API. SQL Server Native Change Data Capture (CDC).

DeliveryEach detected change is written to Salesforce Marketing Cloud through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Salesforce Marketing Cloud: Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
  • SQL Server: No API rate limits; throughput depends on instance resources, licensing tier, and connection limits.
What ships with Salesforce Marketing Cloud ⇄ SQL Server

Connect Salesforce Marketing Cloud and SQL Server for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesforce Marketing Cloud–SQL Server connection.

Real-time

Two-way sync

Changes in Salesforce Marketing Cloud or SQL Server instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Salesforce Marketing Cloud or SQL Server 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 Salesforce Marketing Cloud or SQL Server record.

Observability

Monitoring

Track your Salesforce Marketing Cloud ⇄ SQL Server sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Salesforce Marketing Cloud and SQL Server.

How the Salesforce Marketing Cloud and SQL Server connectors work

Salesforce Marketing Cloud

Integration surface
Two APIs on tenant-specific endpoints: a REST API (JSON over HTTPS) for Data Extensions, Journeys, Contacts, Content Builder, and Automations, plus a legacy SOAP API (ExactTarget WSDL) for tracking events and bulk Retrieve.
Authentication
OAuth 2.0 via an Installed Package (Client ID + Client Secret). Server-to-server uses the client_credentials grant and web apps use authorization_code, both against {subdomain}.auth.marketingcloudapis.com/v2/token. The 20-minute access token response also returns the account's rest_instance_url and soap_instance_url.
Change detection
The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback URL and subscription are registered and verified. There is no general data-change feed, so Data Extension and Data View syncs poll by date fields.
Capabilities
read · write · webhooks
Rate limits
Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.

SQL Server

Integration surface
SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers
Authentication
Database credentials entered as a connection string or as parameters (host/user/password) in the Create New Sync page
Change detection
SQL Server Native Change Data Capture (CDC); a DBA runs a one-time setup script with sysadmin privileges to enable CDC and create Stacksync wrapper procedures
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput depends on instance resources, licensing tier, and connection limits
SQL Server setup guide
How it works

How to connect Salesforce Marketing Cloud to SQL Server — 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 Salesforce Marketing Cloud and SQL Server 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
    Salesforce Marketing Cloud connected
    SQL Server connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Salesforce Marketing Cloud and SQL Server 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 · Salesforce Marketing Cloud ⇄ SQL Server
    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
    Salesforce Marketing Cloud SQL Server
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Salesforce Marketing Cloud and SQL Server integration FAQ

SECURITY

Security teams trust 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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 499 integrations available for Salesforce Marketing Cloud and SQL Server.

Popular · 8 of 499
All Salesforce Marketing Cloud integrations All SQL Server integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own