Skip to content
CRM ⇄ Accounting and finance

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

Keep Salesforce and Zuora 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 and Zuora

Sync customers, invoices, and payment status between Zuora and Salesforce in real time, so sales sees the money and finance sees the relationship.

Finance and sales describe the same customers in different systems. Salesforce knows the relationship: who the contacts are and what is in motion with the account. Zuora knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.

Stacksync links Rate Plan and Rate Plan Charge, Product and Product Rate Plan (Product Catalog), Invoice, Payment in Zuora to Campaigns, Tasks and Events, Products and Price Books, Custom Objects in Salesforce with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.

Common use cases

  • 01 Push closed-won opportunities from Salesforce into Zuora as Accounts, Subscriptions, and Rate Plan Charges to automate the quote-to-cash handoff.
  • 02 Master the Product Catalog (Products and Product Rate Plans) in a database or PIM and write pricing changes into Zuora.
  • 03 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
  • 04 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.

Common sync patterns

Where Salesforce tracks deals: closed-won creates the finance record

A won opportunity creates or updates the customer in Zuora with the right billing details, so invoicing starts without re-keying.

Payment status on the account

Invoice and payment status from Zuora appears on the account in Salesforce, so reps see overdue balances before they promise the next order.

Billing detail changes flow back

When a contact or address is corrected in Salesforce, Zuora gets the update before the next invoice goes out.

What you can sync between Salesforce and Zuora

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 objects Zuora objects How this pairing syncs
Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Account (Billing Account) The customer billing entity holding contacts, payment methods, and billing settings; synced two-way as the parent record most other Zuora objects hang off. Contacts is specific to Salesforce and Account (Billing Account) to Zuora — each maps to any object or custom field on the other side.
Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. Subscription Recurring or usage-based subscription tied to an Account; read for revenue state and written when provisioning or changing plans from a CRM or app. Leads is specific to Salesforce and Subscription to Zuora — each maps to any object or custom field on the other side.
Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. Rate Plan and Rate Plan Charge The priced components inside a Subscription; synced so charge amounts, quantities, and effective dates stay aligned with the source system. Opportunities is specific to Salesforce and Rate Plan and Rate Plan Charge to Zuora — each maps to any object or custom field on the other side.
Cases Support records; synced with help desk tools or internal databases for escalation workflows. Product and Product Rate Plan (Product Catalog) The catalog of sellable products and their pricing; usually mastered elsewhere and written into Zuora, or read to map subscription charges. Cases is specific to Salesforce and Product and Product Rate Plan (Product Catalog) to Zuora — each maps to any object or custom field on the other side.
Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Invoice Billing documents generated from rate plan charges and order line items; typically read out into an ERP or GL for revenue recognition and reconciliation. Campaigns is specific to Salesforce and Invoice to Zuora — each maps to any object or custom field on the other side.
Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Payment Payment and refund transactions applied against invoices; read for cash application, dunning, and reconciliation reporting in the warehouse. Tasks and Events is specific to Salesforce and Payment to Zuora — each maps to any object or custom field on the other side.

How changes propagate between Salesforce and Zuora

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 Zuora Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

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

Zuora Salesforce Sub-second propagation

DetectionZuora notifies Stacksync of record changes through webhook events. Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for.

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

Rate-limit considerations

  • Salesforce: Daily API request allocations vary by edition and license count.
  • Zuora: Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
What ships with Salesforce ⇄ Zuora

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Salesforce or Zuora 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 or Zuora record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Salesforce and Zuora connectors work

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

Zuora

Integration surface
REST API (v1) with Object Query, Data Query, and AQuA bulk export; legacy SOAP API also available
Authentication
OAuth 2.0 client credentials (bearer token, 3600s expiry); access is governed by the Zuora role of the OAuth client's associated user, with no granular scopes
Change detection
Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for event-driven changes
Capabilities
read · write · webhooks
Rate limits
Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
How it works

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

    Choose tables

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

Salesforce and Zuora 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
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:

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 532 integrations available for Salesforce and Zuora.

Popular · 8 of 532
All Salesforce integrations All Zuora 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