Real-time
Two-way sync
Changes in Nutshell or Servicemax instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Nutshell to Servicemax integration — real-time, two-way sync
Keep Nutshell 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 Nutshell and Servicemax
Sync what happens in Servicemax with the customer records in Nutshell, in real time and in both directions.
The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Servicemax holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.
Stacksync connects Stock History, Accounts, Contacts, Cases in Servicemax to Notes, Products, Tags, Users in Nutshell with bi-directional, real-time sync. Activity and record changes in Servicemax update the matching contact or account in Nutshell, and CRM data flows the other way wherever Servicemax can store and use it.
Common use cases
- 01 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.
- 02 Keep Installed Products (SVMXC__Installed_Product__c) aligned with an asset or IoT database for warranty, entitlement, and service-history reporting.
- 03 Sync Nutshell leads into a warehouse or Postgres so small B2B teams can report on pipeline without exports.
- 04 Push closed-won leads to accounting software to trigger invoicing automatically.
Common sync patterns
Where Servicemax can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Nutshell sync into Servicemax, so people working there have the context without switching tools.
Where Servicemax supplies contact or company data
Enriched fields land directly on records in Nutshell, and refreshes keep them from going stale.
Where Servicemax processes payments
Charges, refunds, and subscription changes appear on the account in Nutshell, so revenue context lives with the relationship.
What you can sync between Nutshell 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.
| Nutshell objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Products Line items attached to leads, used to sync sold products into billing | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tasks Rep to-dos mirrored into external work-management or reporting systems | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Tasks is specific to Nutshell and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| Notes Free-text history attached to leads and contacts, replicated for a full timeline | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Notes is specific to Nutshell and Service Contracts to Servicemax — each maps to any object or custom field on the other side. | |
| Tags Segmentation labels mapped to lists or filters in downstream tools | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Tags is specific to Nutshell and Stock History to Servicemax — each maps to any object or custom field on the other side. | |
| Users Rep records used to resolve ownership when syncing assignments | Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | Users is specific to Nutshell and Accounts to Servicemax — each maps to any object or custom field on the other side. | |
| Leads Nutshell's deal object; synced as the pipeline record linked to people and companies | Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. | Leads is specific to Nutshell and Contacts to Servicemax — each maps to any object or custom field on the other side. |
How changes propagate between Nutshell 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.
Nutshell Servicemax Sub-second propagation
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
DeliveryEach detected change is written to Servicemax through its API, with automatic retries and rate-limit backoff.
Servicemax Nutshell 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 Nutshell through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Nutshell: 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 Nutshell ⇄ Servicemax
Connect Nutshell and Servicemax for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Nutshell–Servicemax connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Nutshell 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 Nutshell or Servicemax record.
Observability
Monitoring
Track your Nutshell ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Nutshell and Servicemax.
How the Nutshell and Servicemax connectors work
Nutshell
- Integration surface
- JSON-RPC API over HTTPS; a newer REST API is also offered
- Authentication
- HTTP Basic with account email and API key
- Change detection
- webhook subscriptions for record events, with polling as fallback
- Capabilities
- read · write · webhooks
- Rate limits
- subject to the platform's API rate limits
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 Nutshell 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.
- 01
Connect your apps
Authenticate Nutshell 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.
Nutshell
connected
Servicemax
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Nutshell 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.
objects · Nutshell ⇄ ServicemaxCustomers 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.
Nutshell ServicemaxCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Nutshell and Servicemax integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Nutshell and Servicemax: authenticate both systems, choose the objects to sync (such as Nutshell's Products and Tasks), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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.
-
Common patterns for Nutshell and Servicemax: Where Servicemax can store CRM context: fields kept current; Where Servicemax supplies contact or company data; Where Servicemax processes payments. Owner, lifecycle stage, or account details from Nutshell sync into Servicemax, so people working there have the context without switching tools.
-
Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. 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.
-
Servicemax: Custom SVMXC__ objects and fields must be visible and writable to the connecting Salesforce profile via field-level security and object permissions. Nutshell: Authentication uses HTTP Basic with an account email and API key, so no OAuth flow is required for server-to-server sync. Stacksync's field mapping accounts for these differences between Nutshell 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 Nutshell and Servicemax records are not retained after a sync operation.
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 425 integrations available for Nutshell and Servicemax.
Popular · 7 of 425
-
Nutshell ⇄ Zendesk -
Nutshell ⇄ Campfire -
Nutshell ⇄ Front -
Nutshell ⇄ Amazon Seller Central -
Servicemax ⇄ Xactly -
Servicemax ⇄ Gong -
Servicemax ⇄ Salesforce
No integrations match .
