Real-time
Two-way sync
Changes in Salesforce or Success Factors instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Salesforce to Success Factors integration — real-time, two-way sync
Keep Salesforce and Success Factors 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 Salesforce and Success Factors
Keep the people who own accounts in Salesforce 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.
Salesforce 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 and Price Books, Custom Objects, Accounts, Contacts in Salesforce with Position, PerEmail and PerPhone, User, PerPerson 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 Salesforce keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
- 02 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
- 03 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.
- 04 Replicate EmpCompensation and EmpJob effective-dated history into a warehouse for headcount, attrition, and compensation reporting without CSV pulls.
Common sync patterns
Deactivate access when someone leaves
When Success Factors marks a worker as departed, the matching user in Salesforce 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.
Where Success Factors tracks people the business also engages: contacts stay in sync
A person recorded in Success Factors, such as a candidate or applicant, can create or update the matching contact in Salesforce, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
What you can sync between Salesforce and Success Factors
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 | Success Factors objects | How this pairing syncs | |
|---|---|---|---|
| Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | PerPerson Person-level container in Employee Central holding biographical data; effective-dated child entities (PerPersonal, PerEmail, PerPhone) hang off it. | Products and Price Books is specific to Salesforce and PerPerson to Success Factors — each maps to any object or custom field on the other side. | |
| Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | EmpEmployment Employment record tying a person to an employment period (hire, service dates); carries lastModifiedDateTime used for incremental polling. | Custom Objects is specific to Salesforce and EmpEmployment to Success Factors — each maps to any object or custom field on the other side. | |
| Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | EmpJob Effective-dated job info: position, department, manager, FTE, pay grade, cost center; the most-synced record for downstream HR and provisioning. | Accounts is specific to Salesforce and EmpJob to Success Factors — each maps to any object or custom field on the other side. | |
| Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | EmpCompensation Effective-dated pay and compensation; usually read into a warehouse for reporting, writable for comp updates as new dated slices. | Contacts is specific to Salesforce and EmpCompensation to Success Factors — 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. | 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. | Leads is specific to Salesforce and Foundation Objects (FODepartment, FOLocation, FOCostCenter) to Success Factors — 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. | Position Position Management records for headcount and requisition planning; synced with an ATS or ERP to keep positions and reqs aligned. | Opportunities is specific to Salesforce and Position to Success Factors — each maps to any object or custom field on the other side. |
How changes propagate between Salesforce and Success Factors
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.
Salesforce Success Factors Sub-second propagation
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 written to Success Factors through its API, with automatic retries and rate-limit backoff.
Success Factors Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Salesforce: Daily API request allocations vary by edition and license count.
- 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 Salesforce ⇄ Success Factors
Connect Salesforce and Success Factors for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesforce–Success Factors connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Salesforce or 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 Salesforce or Success Factors record.
Observability
Monitoring
Track your Salesforce ⇄ Success Factors sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Salesforce and Success Factors.
How the Salesforce and Success Factors connectors work
Salesforce
- Integration surface
- 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
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
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.
How it works
How to connect Salesforce to Success Factors — 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.
- 01
Connect your apps
Authenticate Salesforce and Success Factors with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Salesforce
connected
Success Factors
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Salesforce and Success Factors 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.
objects · Salesforce ⇄ Success FactorsCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Salesforce Success FactorsCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Salesforce and Success Factors integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Salesforce and Success Factors: authenticate both systems, choose the objects to sync (such as Salesforce's Products and Price Books and Custom Objects), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Salesforce: Non-writable objects, non-triggerable objects (trigger mode), and tables without a last_modified_data column (polling mode) cannot be synced yet. Success Factors: OData API calls are throttled at the tenant level (Access Limits for OData V2) and large reads must be paginated (default page size 1000); the legacy SFAPI / Compound Employee API is SOAP-based. Stacksync's field mapping accounts for these differences between Salesforce and Success Factors without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Salesforce and Success Factors records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Salesforce and Success Factors connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Salesforce–Success Factors integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Salesforce and Success Factors. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). On Success Factors: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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
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 537 integrations available for Salesforce and Success Factors.
Popular · 8 of 537
-
Salesforce ⇄ Smartrecruiters -
Salesforce ⇄ Ukg Pro -
Salesforce ⇄ Greenhouse -
Salesforce ⇄ Jobvite -
Success Factors ⇄ Veeva CRM -
Success Factors ⇄ Vtiger CRM -
Success Factors ⇄ Zoho SalesIQ -
Success Factors ⇄ ZoomInfo
No integrations match .
