Skip to content
Human resources ⇄ Accounting and finance

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

Keep Success Factors and Workday 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 Workday

Keep the employee, department, and cost records that Workday and Success Factors share consistent in real time, so the finance system and the people system stop drifting apart.

Workday runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Success Factors runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.

Stacksync syncs Custom Reports (RaaS), Workers, Organizations, Positions in Workday with PerPerson, EmpEmployment, EmpJob, EmpCompensation in Success Factors bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.

Common use cases

  • 01 Keep supervisory-organization hierarchies aligned with planning and workforce tools that model the same structure.
  • 02 Sync worker records from Workday into IT and identity systems so hires, transfers, and terminations provision access automatically.
  • 03 Write updated PerEmail, PerPhone, and User attributes back into SuccessFactors from an identity or directory system so contact data stays current.
  • 04 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.

Common sync patterns

Status changes propagate

A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.

People-driven costs land in finance

Compensation, reimbursements, or other costs tied to a person on the Success Factors side flow into Workday for posting, so the books reflect what people actually cost without manual re-entry.

New person becomes a known record in finance

When someone is added in Success Factors, a matching employee or payee record appears in Workday, ready for payroll, expenses, or cost allocation without anyone rekeying the details.

What you can sync between Success Factors and Workday

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 Workday objects How this pairing syncs
Position Position Management records for headcount and requisition planning; synced with an ATS or ERP to keep positions and reqs aligned. Positions Job seats synced with recruiting and planning tools. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
EmpEmployment Employment record tying a person to an employment period (hire, service dates); carries lastModifiedDateTime used for incremental polling. Payroll Results Completed pay data exported to finance and benefits systems. EmpEmployment is specific to Success Factors and Payroll Results to Workday — 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. Suppliers Workday Financials vendor records aligned with procurement tools. EmpJob is specific to Success Factors and Suppliers to Workday — 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. Customers and Invoices Financials receivables objects synced for billing visibility where Workday Financials is used. EmpCompensation is specific to Success Factors and Customers and Invoices to Workday — 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. Journal Entries Accounting entries imported from external subledgers into Workday Financials. Foundation Objects (FODepartment, FOLocation, FOCostCenter) is specific to Success Factors and Journal Entries to Workday — 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. Custom Reports (RaaS) Tenant-defined reports exposed as web service endpoints, often the practical read surface for syncs. PerEmail and PerPhone is specific to Success Factors and Custom Reports (RaaS) to Workday — each maps to any object or custom field on the other side.

How changes propagate between Success Factors and Workday

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

Workday Success Factors Interval-based propagation

DetectionStacksync polls Workday for changes on an incremental schedule, reading only records changed since the previous pass. Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment.

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.
What ships with Success Factors ⇄ Workday

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Success Factors ⇄ Workday 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 Workday.

How the Success Factors and Workday 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.

Workday

Integration surface
SOAP Workday Web Services (WWS), a REST API, and Reports-as-a-Service (RaaS) endpoints for custom reports
Authentication
OAuth 2.0 for the REST API; integration system users with WS-Security or certificate-based auth for SOAP
Change detection
Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment; no general webhook surface
Capabilities
read · write
How it works

How to connect Success Factors to Workday — 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 Workday 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
    Workday connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Success Factors and Workday 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 ⇄ Workday
    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 Workday
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Success Factors and Workday 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 495 integrations available for Success Factors and Workday.

Popular · 8 of 495
All Success Factors integrations All Workday 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