Skip to content
Human resources

Connect Success Factors to any app with two-way sync.

Two-way sync Success Factors across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in Success Factors.

These objects sync between Success Factors and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Success Factors exposes them.

User
Core identity/User entity behind role-based permissions; a model distinct from Employee Central, synced two-way with a directory or IdP and downstream apps.
PerPerson
Person-level container in Employee Central holding biographical data; effective-dated child entities (PerPersonal, PerEmail, PerPhone) hang off it.
EmpEmployment
Employment record tying a person to an employment period (hire, service dates); carries lastModifiedDateTime used for incremental polling.
EmpJob
Effective-dated job info: position, department, manager, FTE, pay grade, cost center; the most-synced record for downstream HR and provisioning.
EmpCompensation
Effective-dated pay and compensation; usually read into a warehouse for reporting, writable for comp updates as new dated slices.
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.
Position
Position Management records for headcount and requisition planning; synced with an ATS or ERP to keep positions and reqs aligned.
PerEmail and PerPhone
Contact sub-entities under PerPerson; synced two-way with a directory or comms system to keep worker contact data current.
API surface

How Stacksync connects to Success Factors.

The connector runs on Success Factors's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
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.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
What ships with Success Factors

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

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

Real-time

Two-way sync

Changes in Success Factors instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Success Factors connector.

SuccessFactors is the HR system of record for mid-market through large enterprise, owned by HRIS admins and HR operations. Employee Central holds the worker master: PerPerson, EmpEmployment, EmpJob, compensation, and Foundation Objects like departments, locations, and cost centers. Because payroll, provisioning, ERP, and reporting all depend on current worker and org data, it's the source downstream systems read from and, for hires and org changes, write back to.

  • HRIS admins
  • HR operations
  • People analytics / HR data teams
  • IT identity & provisioning
  • SAP integration developers

  1. 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.

  2. 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.

  3. Replicate EmpCompensation and EmpJob effective-dated history into a warehouse for headcount, attrition, and compensation reporting without CSV pulls.

  4. Keep Foundation Objects (department, location, cost center) aligned between SuccessFactors and an ERP so cost-center and org hierarchies match.

  5. Write updated PerEmail, PerPhone, and User attributes back into SuccessFactors from an identity or directory system so contact data stays current.

  6. 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 keeps editing in SuccessFactors.

All Success Factors integrations

Pick the system you need to keep in sync with Success Factors. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 45

ERP · 38

Database · 50

Data warehouse · 29

Business productivity · 40

Accounting and finance · 17

How it works

Set up Success Factors in minutes, without APIs.

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 with its 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
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Success Factors objects to sync — Stacksync auto-detects the schema, 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
    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 database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Success Factors connector FAQ

What can I sync with the Success Factors connector?

Success Factors's core objects — User, PerPerson, EmpEmployment, EmpJob and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Success Factors?

Via OData V2 and V4 REST APIs (plus legacy SFAPI / Compound Employee SOAP API), authenticated with 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. Changes are detected as follows — 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. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Success Factors connector two-way?

Yes. Changes made in Success Factors propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Success Factors integration take to set up?

Most Success Factors integrations go live in minutes: authenticate Success Factors and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Success Factors data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Success Factors data is encrypted in transit, and a zero-persistent-storage architecture means 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.

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
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