Skip to content
Business productivity

Full Enrich to Servicemax integration — real-time, two-way sync

Keep Full Enrich 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 Full Enrich and Servicemax

Stop re-entering the same information in Full Enrich and Servicemax: Stacksync keeps the records they share consistent in real time, in both directions.

Two tools in the daily stack often hold overlapping information: the same people, the same companies, or the same pieces of work, described twice. The tools do different jobs, so consolidating is not the answer; the overlap just needs to stop drifting.

Stacksync syncs Phone numbers, Credits, Enrichment requests, Contacts in Full Enrich with Stock History, Accounts, Contacts, Cases in Servicemax in real time. You choose which records overlap, map the fields that should match, and pick a direction or let changes flow both ways. From then on, an update made in either tool is reflected in the other within seconds, without exports or copy-paste.

Because the sync is field-level, each tool keeps its own extras; only the shared data is held in agreement.

Common use cases

  • 01 Run waterfall enrichment over warehouse lead lists before importing them into outbound sequencers.
  • 02 Backfill missing phone numbers on aging CRM records on a schedule.
  • 03 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.
  • 04 Keep Installed Products (SVMXC__Installed_Product__c) aligned with an asset or IoT database for warranty, entitlement, and service-history reporting.

Common sync patterns

Where both tools track people or companies: one consistent record

Contact and company details corrected in either tool update the other, so nobody works from the old version.

Where one tool produces events: mirror them in the other

Payments, replies, messages, or tickets created in one tool can create or update matching records in the other, keeping context in one place.

Where Servicemax is where the team documents or plans: keep its data fed

Information that originates in Full Enrich stays current in Servicemax instead of going stale after a one-time paste.

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

Full Enrich objects Servicemax objects How this pairing syncs
Contacts The person inputs (name plus company or domain) sent for enrichment. Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Emails Returned addresses with verification status, written back to the CRM or database. Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. Emails is specific to Full Enrich and Accounts to Servicemax — each maps to any object or custom field on the other side.
Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. Phone numbers is specific to Full Enrich and Cases to Servicemax — each maps to any object or custom field on the other side.
Credits Account balance consumed on successful finds; monitored to pace sync jobs. Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. Credits is specific to Full Enrich and Products to Servicemax — each maps to any object or custom field on the other side.
Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. Work Orders SVMXC__Service_Order__c; the core field-service job record for install, repair, and maintenance; synced two-way with databases and pushed to ERPs at close. Enrichment requests is specific to Full Enrich and Work Orders to Servicemax — each maps to any object or custom field on the other side.
Enrichment results Completed records fetched by request ID or delivered via webhook. Work Details SVMXC__Service_Order_Line__c; line items on a Work Order for labor, parts used, and expenses; read out for billing or written back with usage. Enrichment results is specific to Full Enrich and Work Details to Servicemax — each maps to any object or custom field on the other side.

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

Full Enrich Servicemax Sub-second propagation

DetectionFull Enrich notifies Stacksync of record changes through webhook events. Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback.

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

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

Rate-limit considerations

  • Full Enrich: Subject to the platform's API rate limits and per-batch size constraints.
  • 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 Full Enrich ⇄ Servicemax

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Full Enrich and Servicemax connectors work

Full Enrich

Integration surface
REST API with asynchronous bulk enrichment endpoints
Authentication
API key (Bearer token)
Change detection
Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits and per-batch size constraints

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

    Choose tables

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

Full Enrich 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.

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 391 integrations available for Full Enrich and Servicemax.

Popular · 7 of 391
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.