Real-time
Two-way sync
Changes in Recurly or Zuora instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance
Recurly to Zuora integration — real-time, two-way sync
Keep Recurly 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 Recurly and Zuora
Keep the customer, invoice, and payment records that Recurly and Zuora share consistent in real time, whether the two systems split your finance stack or one is replacing the other.
Two finance systems in one company usually means one of two setups. Either the systems divide the work, with one issuing invoices or serving a business unit while the other holds the books, or one is on its way out and both must stay accurate during the transition. In both cases, the customer, invoice, and payment records the two systems share start to drift the moment updates are keyed twice or moved by hand.
Stacksync syncs Billing Info, Measured Units and Usage, Accounts, Subscriptions in Recurly with Subscription, Rate Plan and Rate Plan Charge, Product and Product Rate Plan (Product Catalog), Invoice in Zuora bi-directionally and in real time. A record created or corrected in either system appears in the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.
That matters most at close. When both systems agree on who was billed, what was paid, and what is outstanding, reconciliation stops being a hunt for which copy of the truth is current.
Common use cases
- 01 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
- 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
- 03 Two-way sync of Accounts and Subscriptions with an operational Postgres database so product and finance teams read billing state in SQL while changes flow back into Zuora.
- 04 Master the Product Catalog (Products and Product Rate Plans) in a database or PIM and write pricing changes into Zuora.
Common sync patterns
Where Recurly issues invoices and Zuora holds the books
Invoices and payments recorded on the billing side land in the system of record automatically, so revenue is captured once and correctly.
Parallel run during a migration
When one system is replacing the other, keep both live and matching through the cutover, so no transaction falls between the last export and go-live.
One customer master
A customer's name, billing details, or payment terms corrected in either system update the other immediately, so the next invoice always uses current information.
What you can sync between Recurly 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.
| Recurly objects | Zuora objects | How this pairing syncs | |
|---|---|---|---|
| Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). | 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. | Billing Info is specific to Recurly and Rate Plan and Rate Plan Charge to Zuora — each maps to any object or custom field on the other side. | |
| Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | 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. | Measured Units and Usage is specific to Recurly and Product and Product Rate Plan (Product Catalog) to Zuora — each maps to any object or custom field on the other side. | |
| Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. | Payment Payment and refund transactions applied against invoices; read for cash application, dunning, and reconciliation reporting in the warehouse. | Accounts is specific to Recurly and Payment to Zuora — each maps to any object or custom field on the other side. | |
| Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Usage Metered consumption records; written into Zuora from a metering or warehouse pipeline so consumption-based charges are rated and invoiced. | Plans is specific to Recurly and Usage to Zuora — each maps to any object or custom field on the other side. |
How changes propagate between Recurly 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.
Recurly Zuora Sub-second propagation
DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.
DeliveryEach detected change is written to Zuora through its API, with automatic retries and rate-limit backoff.
Zuora Recurly 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 Recurly through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
- 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 Recurly ⇄ Zuora
Connect Recurly and Zuora for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Recurly–Zuora connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Recurly 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 Recurly or Zuora record.
Observability
Monitoring
Track your Recurly ⇄ Zuora sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Recurly and Zuora.
How the Recurly and Zuora connectors work
Recurly
- Integration surface
- REST API (V3, date-versioned; legacy V2 XML API also exists)
- Authentication
- API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
- Change detection
- Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
- Capabilities
- read · write · webhooks
- Rate limits
- Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
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 Recurly 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.
- 01
Connect your apps
Authenticate Recurly 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.
Recurly
connected
Zuora
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Recurly 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.
objects · Recurly ⇄ ZuoraCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Recurly ZuoraCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Recurly and Zuora integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Recurly and Zuora: authenticate both systems, choose the objects to sync (such as Recurly's Subscriptions and Invoices), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Recurly and Zuora connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Recurly–Zuora integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Recurly and Zuora. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Recurly: Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters. On Zuora: Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for event-driven changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Recurly side: Billing Info, Measured Units and Usage, Accounts, Subscriptions, plus custom fields where Recurly exposes them. On the Zuora side: Subscription, Rate Plan and Rate Plan Charge, Product and Product Rate Plan (Product Catalog), Invoice. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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.
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 496 integrations available for Recurly and Zuora.
Popular · 8 of 496
-
Recurly ⇄ Hyperline -
Recurly ⇄ Pigment -
Recurly ⇄ QuickBooks -
Recurly ⇄ Stripe -
Zuora ⇄ Braintree -
Zuora ⇄ Navan -
Zuora ⇄ Ramp -
Zuora ⇄ Rillet
No integrations match .
