Skip to content
Accounting and finance ⇄ Business productivity

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

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

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

Rillet 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 Charge, Reimbursement, Custom Field, Account in Rillet and Cases, Products, Work Orders, Work Details in Servicemax in sync, bi-directionally and in real time. Whatever records Servicemax keeps and whatever events it produces, the overlap with Rillet 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 Push billing events from a product or usage-metering system into Rillet for revenue recognition.
  • 02 Sync AR and collection status back to customer success tools ahead of renewals.
  • 03 Keep Installed Products (SVMXC__Installed_Product__c) aligned with an asset or IoT database for warranty, entitlement, and service-history reporting.
  • 04 Consolidate Service Contracts and entitlement data into a warehouse for renewal forecasting and SLA compliance dashboards.

Common sync patterns

Where Servicemax is a docs or knowledge workspace: reference data kept fresh

Figures teams rely on, like customer status or outstanding balances, stay current wherever Servicemax surfaces them instead of going stale after a one-time paste.

Where Servicemax handles customer conversations: billing context in view

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

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

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

What you can sync between Rillet 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.

Rillet objects Servicemax objects How this pairing syncs
Account Synced with incremental and full sync per the Stacksync docs. 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.
Vendor Synced with incremental and full sync per the Stacksync docs. Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. Vendor is specific to Rillet and Service Contracts to Servicemax — each maps to any object or custom field on the other side.
Invoice Synced with incremental and full sync per the Stacksync docs. Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. Invoice is specific to Rillet and Stock History to Servicemax — each maps to any object or custom field on the other side.
Credit Memo Synced with incremental and full sync per the Stacksync docs. Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. Credit Memo is specific to Rillet and Contacts to Servicemax — each maps to any object or custom field on the other side.
Bill Synced with incremental and full sync per the Stacksync docs. Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. Bill is specific to Rillet and Cases to Servicemax — each maps to any object or custom field on the other side.
Journal Entry Synced with incremental and full sync per the Stacksync docs. Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. Journal Entry is specific to Rillet and Products to Servicemax — each maps to any object or custom field on the other side.

How changes propagate between Rillet 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.

Rillet Servicemax Sub-second propagation

DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.

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

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

Rate-limit considerations

  • Rillet: Subject to the platform's API rate limits.
  • 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 Rillet ⇄ Servicemax

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Rillet and Servicemax.

How the Rillet and Servicemax connectors work

Rillet

Integration surface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
Change detection
Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
Capabilities
read · write · CDC · webhooks
Rate limits
Subject to the platform's API rate limits.
Rillet setup guide

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 Rillet 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 Rillet 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
    Rillet connected
    Servicemax connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Rillet 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 432 integrations available for Rillet and Servicemax.

Popular · 7 of 432
All Rillet 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