Two-way sync
Changes in Pigment or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep Pigment 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.
Pigment 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 Users and permissions, Applications, Metrics, Dimension lists in Pigment and Work Orders, Work Details, Installed Products, Service Contracts in Servicemax in sync, bi-directionally and in real time. Whatever records Servicemax keeps and whatever events it produces, the overlap with Pigment 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.
Payment and charge activity flows into Pigment as it happens, so the books reflect reality without manual reconciliation.
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.
Front-line teams see invoice and payment status from Pigment next to the customer they are helping, without logging into the finance system.
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.
| Pigment objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Tables Row-based transactional data loaded into models from source systems | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Tables is specific to Pigment and Service Contracts to Servicemax — each maps to any object or custom field on the other side. | |
| Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Scenarios is specific to Pigment and Stock History to Servicemax — each maps to any object or custom field on the other side. | |
| Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | Data imports is specific to Pigment and Accounts to Servicemax — each maps to any object or custom field on the other side. | |
| Users and permissions Access controls governing which model areas a sync can touch | Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. | Users and permissions is specific to Pigment and Contacts to Servicemax — each maps to any object or custom field on the other side. | |
| Applications Planning models organized by domain such as finance, sales, or workforce | Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. | Applications is specific to Pigment and Cases to Servicemax — each maps to any object or custom field on the other side. | |
| Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Metrics is specific to Pigment and Products to Servicemax — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is written to Servicemax through its API, with automatic retries and rate-limit backoff.
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 Pigment through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Pigment–Servicemax connection.
Changes in Pigment or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Pigment or Servicemax data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Pigment or Servicemax record.
Track your Pigment ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Pigment and Servicemax.
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.
Authenticate Pigment 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.
Pick the Pigment 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Pigment and Servicemax: authenticate both systems, choose the objects to sync (such as Pigment's Tables and Scenarios), map fields visually, and changes propagate both ways in milliseconds — no code required.
Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Servicemax: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Pigment: Pigment's model is multidimensional: metrics are sliced by dimension lists, so inbound records must map to those dimensions rather than flat columns. Servicemax: Polling orders incremental changes by each object's SystemModstamp or LastModifiedDate; objects without a modified timestamp or API write access cannot sync incrementally. Stacksync's field mapping accounts for these differences between Pigment and Servicemax without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Pigment and Servicemax records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Pigment and Servicemax connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Pigment–Servicemax integration in-house.
Yes — Stacksync ships production-grade connectors for both Pigment and Servicemax. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 416 integrations available for Pigment and Servicemax.