Two-way sync
Changes in Salesforce or Xactly instantly reflect in both systems. No stale data, no manual imports.
Keep Salesforce and Xactly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Two CRMs in one company is more common than anyone plans for: an acquisition brings its own system, regions or business units standardize differently, or a migration is under way and both are live. In every case, some of the same companies and people exist in both systems, and every day of manual double entry pushes the copies further apart.
Stacksync syncs Contacts, Leads, Opportunities, Cases in Salesforce with Credits, Transactions (Commission & Bonus), Participants (Payees), Positions & Titles in Xactly in real time and in both directions, with field-level mapping and matching on identifiers you choose. Update a record in either CRM and the other reflects it within seconds.
Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.
When one CRM is replacing the other, run both fully live until cutover, with no snapshot gap and no data freeze.
Where each CRM serves a different team or region, sync just the shared accounts and contacts so handoffs and cross-sell work.
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.
| Salesforce objects | Xactly objects | How this pairing syncs | |
|---|---|---|---|
| Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Products & Customers Product and customer/account master used in crediting rules and reporting; loaded and updated from CRM/ERP through Connect (write) and read for lookups, so read and write. | Contacts is specific to Salesforce and Products & Customers to Xactly — each maps to any object or custom field on the other side. | |
| Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Orders Sales order and transaction records loaded into Incent as the raw input for crediting and calculation; created and updated through Connect load and ETL steps (write) and read back for reconciliation, so read and write. | Leads is specific to Salesforce and Orders to Xactly — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Credits Crediting records that tie an order to a participant and position; system-calculated credits are read, while manual and adjustment credits are loaded through Connect, so read and write. | Opportunities is specific to Salesforce and Credits to Xactly — each maps to any object or custom field on the other side. | |
| Cases Support records; synced with help desk tools or internal databases for escalation workflows. | Transactions (Commission & Bonus) Calculated commission and bonus line items produced by Incent's calculation engine; read as the output of comp runs for reporting and downstream payout, so effectively read-only results. | Cases is specific to Salesforce and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side. | |
| Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | Participants (Payees) Sales reps and payees keyed to positions; loaded and updated from HRIS/HCM source data through Connect (write) and read for roster reporting, so read and write. | Campaigns is specific to Salesforce and Participants (Payees) to Xactly — each maps to any object or custom field on the other side. | |
| Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. | Positions & Titles Org-hierarchy positions and titles that credits and quotas roll up to; loaded and maintained through Connect (write) and read to resolve the hierarchy, so read and write. | Tasks and Events is specific to Salesforce and Positions & Titles to Xactly — 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.
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
DeliveryEach detected change is applied to Xactly as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Xactly for changes on an incremental schedule, reading only records changed since the previous pass. No CDC log for external tools to consume.
DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesforce–Xactly connection.
Changes in Salesforce or Xactly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Salesforce or Xactly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Salesforce or Xactly record.
Track your Salesforce ⇄ Xactly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Salesforce and Xactly.
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 Salesforce and Xactly 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 Salesforce and Xactly 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 Salesforce and Xactly: authenticate both systems, choose the objects to sync (such as Salesforce's Contacts and Leads), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). On Xactly: No CDC log for external tools to consume. Incremental sync uses SQL predicates on modified/last-updated timestamp columns (for example WHERE modified_date > watermark) against Connect's queryable objects, or scheduled Connect ETL Pipelines that pull deltas since the last run. Xactly Connect has no outbound HTTP webhooks, so change detection is pull/ETL-based. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Salesforce side: Contacts, Leads, Opportunities, Cases, plus custom fields where Salesforce exposes them. On the Xactly side: Credits, Transactions (Commission & Bonus), Participants (Payees), Positions & Titles. Stacksync auto-detects both schemas and converts types between the two systems.
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 Salesforce and Xactly: Post-acquisition consolidation; Migration with a parallel run; Divisional or regional split. Keep both CRMs accurate while the merged team decides on a target system, instead of freezing one and losing months of updates.
Salesforce: REST, SOAP, and Bulk APIs. Authentication: OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode. Xactly: Xactly Connect REST API v2 (JSON), plus ODBC/JDBC drivers over the same ANSI-SQL data model. Incent data is exposed as SQL-queryable objects (for example xactly_order, xactly_credit, xactly_transaction, xactly_payment); data is loaded and extracted through Connect load/query steps and server-side ETL Pipelines. The base host is region/pod-specific (for example https://<pod>.xactlycorp.com). Authentication: OAuth 2.0 via the Xactly Connect API Gateway (bearer tokens issued on behalf of an Xactly Incent user), with HTTP Basic authentication using a dedicated Xactly Connect service-user's credentials also supported for the Connect REST API v2. The connecting user needs Connect/API access plus the relevant object permissions in Incent. Stacksync manages authentication, retries, and rate limits on both sides.
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 560 integrations available for Salesforce and Xactly.