Built for the database you already own

Salesforce,
made queryable.

Subscribe to Salesforce changes and write them into Postgres, MySQL, or SQL Server in near real time. No Heroku dependency. No warehouse detour. No row-metered surprise.

See how it works

For application teams that want Salesforce data inside their own stack.

CRM SYNC / production LIVE
CONNECTION

Revenue sync

healthy
☁
CDC subscriptionSalesforce
Connected
Pg
DestinationPostgreSQL
us-east-1
Objects syncing12all selected
Event-to-write lag04sCDC stream active
Changes applied48,202last 24 hours
Change streamNOW --:--:--
Opportunity.StageNameNegotiation
Account.IndustrySoftware
Contact.Emailchanged
✓Schema mappedOpportunity → opportunity
↗4 sec latencyWithin your target
Works with the relational stack you trust
PostgreSQLMySQLAmazon RDSAzure SQLSupabase
01

The operational data gap

Salesforce is where the customer story lives.
Your product should be able to read it.

A

A database, not a data project.

Bring your existing Postgres, MySQL, or SQL Server. Your application gets familiar tables and indices—not a new warehouse to operate.

B

Only the objects that matter.

Map standard and custom objects, select the fields your app needs, and keep sensitive CRM data out of scope by default.

C

Make change a non-event.

Schema-aware syncs handle Salesforce changes with a clear log, retry controls, and a safe backfill path when you need it.

02

How the live mirror works

From record change to reliable local data.

CRM Sync combines a one-time backfill with a durable Change Data Capture subscription. Each event is written idempotently, checkpointed, and later reconciled—so your application can trust the rows it reads.

  1. 01
    Backfill selected objects

    Start with the fields and records your application actually needs.

  2. 02
    Subscribe to Salesforce CDC

    Receive create, update, delete, and undelete events for those objects.

  3. 03
    Write and checkpoint

    Apply an idempotent database write, then persist the replay position.

  4. 04
    Reconcile with confidence

    A scheduled check protects against long outages and schema changes.

LIVE CDC MIRRORRevenue sync
subscribed
☁
EVENT SOURCESalesforce
Pg
DATABASEPostgreSQL
Change event batch6 events received
Change eventsoperation → write
  • Opportunity006HL…2JUPDATE · stage
  • Account001HL…9AUPDATE · industry
  • Contact003HL…7MUPDATE · email
  • Case500HL…4PCREATE · status
  • Opportunity006HL…zQUPDATE · amount
  • Lead00QHL…6BDELETE · record
Applied rowspublic.salesforce_opportunity
idstage_nameamount
006HL…2JNegotiation$48,200
006HL…zQQualification$17,000
006HL…8KClosed Won$92,500
006HL…3CProspecting$8,400
Events received1,284
Rows applied1,284
Replay checkpointcurrent
03

From org to query in an afternoon

It feels less like ETL
and more like a connection.

  1. 01

    Connect your Salesforce org

    Authenticate with a dedicated integration user and pick a sandbox or production org.

    OAuth · read-only first
  2. 02

    Select objects & enable Change Data Capture

    Choose Account, Contact, and Opportunity—or the custom objects that drive your app—and subscribe only to those changes.

    CDC channel preview
  3. 03

    Point to the database you own

    Use an encrypted connection to your Postgres, MySQL, or SQL Server. We write predictable tables; you keep control.

    No data warehouse required
  4. 04

    Keep a live stream and safety net

    Checkpoint every event, replay after a short outage, and reconcile on a schedule so your product keeps trustworthy customer context.

    CDC + reconciliation
04

Deploy where the data lives

Managed cloud or
your own network.

Managed cloud fastest setup

We run the connector.

Connect a Salesforce org and database over encrypted connections. It’s the shortest route to a dependable production mirror.

Salesforce→CRM Sync Cloud→Your database
  • Managed operations and upgrades
  • Encrypted credentials and database connections
  • Best for cloud databases with approved network access
Customer network private path

Run the worker beside your database.

Deploy the CRM Sync worker in your VPC or on-premises environment. Your CRM data is written locally, without opening inbound database access.

Salesforce→CRM Sync worker→Local database
  • VPC, private subnet, or on-premises deployment
  • Outbound connection from your network
  • Best for regulated or network-isolated systems

The CRM Sync difference

Keep the familiar part.
Lose the lock-in.

Heroku Connect proved the pattern: Salesforce data belongs close to the application. CRM Sync makes that pattern portable—across your database, cloud, and team.

See the predictable pricing
What you needTypical ETLCRM Sync
Your own relational databaseSometimesAlways
Cloud or customer-network deploymentVaries by connectorBoth paths
Application-ready tablesConfiguration-heavyBuilt in
Costs that grow with every updateUsuallyNo MAR billing
Salesforce → database focusOne of many connectorsAll we do
05

Predictable, from day one

Pricing that doesn’t
punish a busy CRM.

MonthlyAnnual save 20%
Starter

For an internal tool or the first production sync.

$79/ database / mo
  • 1 Salesforce org
  • 1 database destination
  • Managed cloud connector
  • 15-minute pull sync
  • 250k monthly changes included
Most practical
Growth

For the customer-facing product team.

$349/ month
  • 2 Salesforce orgs
  • 3 database destinations
  • Managed cloud connector
  • Near-real-time CDC stream
  • 2M monthly changes included
  • Daily reconciliation
Scale

For teams that run critical workflows on CRM data.

$1,200/ month
  • Multiple orgs & destinations
  • Customer-network worker option
  • Priority CDC subscriptions
  • 10M monthly changes included
  • Custom channel design
  • SSO / audit logs

No per-row billing. CDC availability and event allocations depend on the Salesforce edition; we’ll verify both during setup. Included changes keep sync quality dependable, and we’ll flag headroom early before an expansion affects your bill.

A few useful answers

Less plumbing.
More confidence.

Which relational databases are supported?

PostgreSQL, MySQL, and SQL Server are the launch destinations. We design the mapping layer around normal relational tables so adding compatible managed variants, such as RDS or Supabase, stays straightforward.

Can it run in our VPC or on-premises network?

Yes. The default managed-cloud connector is built for speed. Scale also offers a CRM Sync worker that runs in your VPC or on-premises environment and uses an outbound connection from your network, so the database does not need inbound public access.

Is this a replacement for Heroku Connect?

It is built for the same application-data pattern, but is not tied to a Heroku app or a Heroku Postgres database. You bring the relational database and cloud environment you prefer.

How do you handle CRM access and sensitive fields?

Start with an integration user that has the least access necessary. Select objects and fields explicitly, use encrypted database connections, and keep a clear change log for sync activity.

Does it write changes back to Salesforce?

Two-way workflows belong in the Scale conversation because conflict handling is product-specific. The launch flow is a dependable Salesforce-to-database mirror, with write-back designed for teams that need it.

Implementation notes, not SEO filler

The questions engineers ask before a sync ships.

Concrete guides for choosing a destination, handling CDC recovery, and running the worker where your data lives.

Architecture guide

Salesforce → Postgres sync

Backfill, CDC, replay checkpoints, and the database tables your application reads.

Read the guide Comparison

Beyond Heroku Connect

What changes when the destination database and deployment model are yours to choose.

Compare approaches Reliability guide

Salesforce CDC, explained

A practical model for events, idempotent writes, outages, and reconciliation.

Understand the flow
See every implementation guide

A cleaner path from CRM to product

Make Salesforce useful
where your code runs.

Bring a database you already trust. We’ll help you configure the first sync.

Start a sync

Connect your database.

Tell us where the data needs to land. We’ll send the right setup path for your CRM Sync workspace.

Your email stays out of analytics.