Skip to content
Accounting and finance ⇄ Business productivity

Recurly to Servicemax integration — real-time, two-way sync

Keep Recurly and Servicemax 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 Servicemax

Connect the financial records in Recurly with the work happening in Servicemax, so both stay current without exports or copy-paste.

Recurly holds the financial truth: who the customers are, what they were billed, what they paid. Servicemax is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.

Stacksync keeps Invoices, Transactions, Line Items, Coupons and Redemptions in Recurly and Stock History, Accounts, Contacts, Cases in Servicemax in sync, bi-directionally and in real time. Whatever records Servicemax keeps and whatever events it produces, the overlap with Recurly is mapped field by field, and a change on either side shows up on the other within seconds.

There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.

Common use cases

  • 01 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 02 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 03 Mirror Accounts and Contacts between ServiceMax and the CRM system of record so customer and site data stays consistent.
  • 04 Sync Work Orders (SVMXC__Service_Order__c) and Work Details bi-directionally with Postgres so ops and analytics teams read and write field-service data in plain SQL.

Common sync patterns

Where Servicemax handles customer conversations: billing context in view

Front-line teams see invoice and payment status from Recurly next to the customer they are helping, without logging into the finance system.

Where Servicemax collects payments or triggers charges: events land in Recurly

Payment and charge activity flows into Recurly as it happens, so the books reflect reality without manual reconciliation.

Where Servicemax tracks people or companies: one identity

A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.

What you can sync between Recurly and Servicemax

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 Servicemax objects How this pairing syncs
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. Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. Measured Units and Usage is specific to Recurly and Service Contracts to Servicemax — each maps to any object or custom field on the other side.
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. Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. Subscriptions is specific to Recurly and Stock History to Servicemax — 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. Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. Plans is specific to Recurly and Contacts to Servicemax — each maps to any object or custom field on the other side.
Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. Invoices is specific to Recurly and Cases to Servicemax — each maps to any object or custom field on the other side.
Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. Transactions is specific to Recurly and Products to Servicemax — each maps to any object or custom field on the other side.

How changes propagate between Recurly and Servicemax

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

Servicemax Recurly Sub-second propagation

DetectionChanges in Servicemax are captured at the source via change data capture — no polling loop against its API. Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object.

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.
  • Servicemax: Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count.
What ships with Recurly ⇄ Servicemax

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Servicemax

Integration surface
Salesforce REST, SOAP, and Bulk APIs (ServiceMax is a managed package on the Salesforce platform)
Authentication
Salesforce OAuth login via a user with API access; the connecting profile needs object and field permissions on ServiceMax's SVMXC__ objects
Change detection
Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled
Capabilities
read · write · CDC
Rate limits
Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count
How it works

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

    Choose tables

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

Recurly and Servicemax 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 506 integrations available for Recurly and Servicemax.

Popular · 7 of 506
All Recurly integrations All Servicemax 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