Skip to content
Human resources ⇄ CRM

Success Factors to Xactly integration — real-time, two-way sync

Keep Success Factors 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.

  • 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 Success Factors and Xactly

Keep the people who own accounts in Xactly in step with the workforce records in Success Factors, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Xactly runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Success Factors. Success Factors is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.

Stacksync syncs Products & Customers, Orders, Credits, Transactions (Commission & Bonus) in Xactly with EmpJob, EmpCompensation, Foundation Objects (FODepartment, FOLocation, FOCostCenter), Position in Success Factors field by field, in real time, and in both directions. You decide which system owns which fields, so Success Factors stays authoritative on roles and org structure while Xactly keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Mirror commission Transactions and Credits into a data warehouse to power rep-facing dashboards and comp-plan analytics without manual exports.
  • 02 Sync Participants, Positions, Titles, and Quotas from an HRIS/HCM and planning tools into Xactly so the org hierarchy and targets stay aligned with headcount changes.
  • 03 Two-way sync of User and EmpJob (position, department, manager, cost center) into Postgres so provisioning, internal apps, and analytics read current org data in SQL while HR edits in SuccessFactors.
  • 04 Push new hires (PerPerson, EmpEmployment, EmpJob) into an ERP or payroll system so account, cost-center, and payroll setup fire on hire instead of manual Integration Center exports.

Common sync patterns

Ownership and territory follow the org chart

When a person changes team, manager, or region in Success Factors, their accounts and territory assignments in Xactly update to match, so pipeline stays with the right owner.

Deactivate access when someone leaves

When Success Factors marks a worker as departed, the matching user in Xactly is flagged or deactivated, so former employees do not keep CRM access after their last day.

One directory of people

A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.

What you can sync between Success Factors and Xactly

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.

Success Factors objects Xactly objects How this pairing syncs
EmpEmployment Employment record tying a person to an employment period (hire, service dates); carries lastModifiedDateTime used for incremental polling. 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. EmpEmployment is specific to Success Factors and Credits to Xactly — each maps to any object or custom field on the other side.
EmpJob Effective-dated job info: position, department, manager, FTE, pay grade, cost center; the most-synced record for downstream HR and provisioning. 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. EmpJob is specific to Success Factors and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side.
EmpCompensation Effective-dated pay and compensation; usually read into a warehouse for reporting, writable for comp updates as new dated slices. 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. EmpCompensation is specific to Success Factors and Participants (Payees) to Xactly — each maps to any object or custom field on the other side.
Foundation Objects (FODepartment, FOLocation, FOCostCenter) Org-structure master data (department, location, cost center, division); mastered elsewhere and written in, or read out to build org charts. 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. Foundation Objects (FODepartment, FOLocation, FOCostCenter) is specific to Success Factors and Positions & Titles to Xactly — each maps to any object or custom field on the other side.
Position Position Management records for headcount and requisition planning; synced with an ATS or ERP to keep positions and reqs aligned. Quotas / Targets Period quota and target values per position or plan; loaded from planning tools through Connect (write) and read for attainment reporting, so read and write. Position is specific to Success Factors and Quotas / Targets to Xactly — each maps to any object or custom field on the other side.
PerEmail and PerPhone Contact sub-entities under PerPerson; synced two-way with a directory or comms system to keep worker contact data current. Payment Summary (Payable) Approved payable amounts per participant per period; read as the output that feeds payroll and accounts payable, so effectively read-only. PerEmail and PerPhone is specific to Success Factors and Payment Summary (Payable) to Xactly — each maps to any object or custom field on the other side.

How changes propagate between Success Factors and Xactly

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.

Success Factors Xactly Sub-second propagation

DetectionSuccess Factors notifies Stacksync of record changes through webhook events. Polling on each entity's lastModifiedDateTime / lastModifiedOn (effective-dated entities require date-range handling).

DeliveryEach detected change is applied to Xactly as a row-level write, with types converted between the two schemas.

Xactly Success Factors Interval-based propagation

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

Rate-limit considerations

  • Success Factors: OData calls are throttled at the tenant level (Access Limits for OData V2); large reads must be paginated (default page size 1000) via $top/$skip or paging cursors.
  • Xactly: Xactly does not publish numeric per-second rate limits. The Connect platform enforces query concurrency and long-running-query limits, so large extracts are paged and heavy loads/queries run as asynchronous Connect jobs (submit, then retrieve results) rather than row-by-row calls; batch loads are the supported path for high volume.
What ships with Success Factors ⇄ Xactly

Connect Success Factors and Xactly for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Success Factors–Xactly connection.

Real-time

Two-way sync

Changes in Success Factors or Xactly instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Success Factors or Xactly 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 Success Factors or Xactly record.

Observability

Monitoring

Track your Success Factors ⇄ Xactly sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Success Factors and Xactly.

How the Success Factors and Xactly connectors work

Success Factors

Integration surface
OData V2 and V4 REST APIs (plus legacy SFAPI / Compound Employee SOAP API)
Authentication
OAuth 2.0 SAML Bearer Assertion — register an OAuth client for an API key (used as client_id), then exchange a signed SAML assertion for a short-lived access token; legacy HTTP Basic auth is being retired
Change detection
Polling on each entity's lastModifiedDateTime / lastModifiedOn (effective-dated entities require date-range handling); Intelligent Services can also push a fixed set of standard business events (e.g. Employee Hire) to a REST endpoint
Capabilities
read · write · webhooks
Rate limits
OData calls are throttled at the tenant level (Access Limits for OData V2); large reads must be paginated (default page size 1000) via $top/$skip or paging cursors.

Xactly

Integration surface
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.
Change detection
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.
Capabilities
read · write
Rate limits
Xactly does not publish numeric per-second rate limits. The Connect platform enforces query concurrency and long-running-query limits, so large extracts are paged and heavy loads/queries run as asynchronous Connect jobs (submit, then retrieve results) rather than row-by-row calls; batch loads are the supported path for high volume.
Xactly setup guide
How it works

How to connect Success Factors to Xactly — 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 Success Factors 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Success Factors connected
    Xactly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Success Factors 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Success Factors ⇄ Xactly
    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
    Success Factors Xactly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Success Factors and Xactly 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
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 529 integrations available for Success Factors and Xactly.

Popular · 7 of 529
All Success Factors integrations All Xactly 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