Skip to content
Accounting and finance ⇄ ERP

Recurly to Rootstock ERP integration — real-time, two-way sync

Keep Recurly and Rootstock ERP 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 Rootstock ERP

Keep Recurly and Rootstock ERP agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.

A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.

Stacksync syncs Transactions, Line Items, Coupons and Redemptions, Billing Info in Recurly with Receipts and Shipments, Salesforce Accounts and Contacts, Sales Orders, Work Orders in Rootstock ERP in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 02 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.
  • 03 Sync inventory availability by site to e-commerce storefronts so promised dates reflect real stock.
  • 04 Push confirmed sales orders to a 3PL or WMS and write shipment confirmations back to Rootstock.

Common sync patterns

One customer and vendor master

Where both systems keep records of the same organizations, corrections made in either propagate to the other.

Subsidiary to headquarters

Where Recurly serves a business unit and Rootstock ERP is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

Where Recurly handles billing: invoices land in Rootstock ERP

Invoices and payment activity from the billing side post through to the enterprise system automatically.

What you can sync between Recurly and Rootstock ERP

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 Rootstock ERP objects How this pairing syncs
Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Work Orders Manufacturing execution records synced to MES, scheduling, and analytics tools. Transactions is specific to Recurly and Work Orders to Rootstock ERP — each maps to any object or custom field on the other side.
Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Purchase Orders Procurement documents synced with supplier portals and AP systems. Line Items is specific to Recurly and Purchase Orders to Rootstock ERP — each maps to any object or custom field on the other side.
Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Items / Products The manufacturing item master, kept aligned with e-commerce and PLM systems. Coupons and Redemptions is specific to Recurly and Items / Products to Rootstock ERP — each maps to any object or custom field on the other side.
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). Bills of Material Multi-level product structures read for costing and planning integrations. Billing Info is specific to Recurly and Bills of Material to Rootstock ERP — 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. Inventory Balances On-hand quantities by site and location, synced to storefronts and WMS. Measured Units and Usage is specific to Recurly and Inventory Balances to Rootstock ERP — 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. Receipts and Shipments Inbound and outbound transactions synced to logistics and 3PL systems. Accounts is specific to Recurly and Receipts and Shipments to Rootstock ERP — each maps to any object or custom field on the other side.

How changes propagate between Recurly and Rootstock ERP

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 Rootstock ERP 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 Rootstock ERP through its API, with automatic retries and rate-limit backoff.

Rootstock ERP Recurly Sub-second propagation

DetectionChanges in Rootstock ERP are captured at the source via change data capture — no polling loop against its API. Salesforce Change Data Capture on Rootstock custom objects where enabled (entity selection limits apply).

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.
  • Rootstock ERP: Consumes the Salesforce org's daily API request allocation, shared with other integrations.
What ships with Recurly ⇄ Rootstock ERP

Connect Recurly and Rootstock ERP for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Recurly–Rootstock ERP connection.

Real-time

Two-way sync

Changes in Recurly or Rootstock ERP instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Recurly or Rootstock ERP 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 Rootstock ERP record.

Observability

Monitoring

Track your Recurly ⇄ Rootstock ERP 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 Rootstock ERP.

How the Recurly and Rootstock ERP 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.

Rootstock ERP

Integration surface
Salesforce Platform APIs (REST, SOAP, Bulk) — Rootstock data lives in Salesforce custom objects
Authentication
OAuth 2.0 (standard Salesforce connected app flows)
Change detection
Salesforce Change Data Capture on Rootstock custom objects where enabled (entity selection limits apply); SOQL polling on SystemModstamp as fallback
Capabilities
read · write · CDC
Rate limits
Consumes the Salesforce org's daily API request allocation, shared with other integrations
How it works

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

    Choose tables

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

Recurly and Rootstock ERP 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 403 integrations available for Recurly and Rootstock ERP.

Popular · 7 of 403
All Recurly integrations All Rootstock ERP 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