Real-time
Two-way sync
Changes in Reltio or Success Factors instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Human resources
Reltio to Success Factors integration — real-time, two-way sync
Keep Reltio 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 Reltio and Success Factors
Put your workforce data where your apps can reach it: Reltio and Success Factors share the same people, positions, and org structure in real time.
Success Factors is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Reltio is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: PerEmail and PerPhone, User, PerPerson, EmpEmployment in Success Factors need to exist as queryable Relations, Crosswalks, Interactions, Matches (Potential Matches) in Reltio before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs Relations, Crosswalks, Interactions, Matches (Potential Matches) in Reltio with PerEmail and PerPhone, User, PerPerson, EmpEmployment in Success Factors field by field, in real time. You decide which system owns which fields — Success Factors typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
Common use cases
- 01 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
- 02 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
- 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
Org and structure stay aligned
Groups, departments, managers, and reporting lines from Success Factors stay consistent in Reltio, so hierarchy-driven logic and permissions don't drift.
Computed and operational fields flow back
Values assembled or corrected in Reltio write onto the matching record in Success Factors where those fields are writable, keeping the people system enriched.
Mirror people records into the database
Records maintained in Success Factors land as queryable Relations, Crosswalks, Interactions, Matches (Potential Matches) in Reltio, so internal apps and dashboards read live data instead of a periodic export.
What you can sync between Reltio 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.
| Reltio objects | Success Factors objects | How this pairing syncs | |
|---|---|---|---|
| Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. | EmpEmployment Employment record tying a person to an employment period (hire, service dates); carries lastModifiedDateTime used for incremental polling. | Activity Log is specific to Reltio and EmpEmployment to Success Factors — each maps to any object or custom field on the other side. | |
| Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. | EmpJob Effective-dated job info: position, department, manager, FTE, pay grade, cost center; the most-synced record for downstream HR and provisioning. | Data Change Requests (DCR) is specific to Reltio and EmpJob to Success Factors — each maps to any object or custom field on the other side. | |
| Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. | EmpCompensation Effective-dated pay and compensation; usually read into a warehouse for reporting, writable for comp updates as new dated slices. | Reference Data (RDM) is specific to Reltio and EmpCompensation to Success Factors — each maps to any object or custom field on the other side. | |
| Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. | 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. | Entities is specific to Reltio and Foundation Objects (FODepartment, FOLocation, FOCostCenter) to Success Factors — each maps to any object or custom field on the other side. | |
| Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. | Position Position Management records for headcount and requisition planning; synced with an ATS or ERP to keep positions and reqs aligned. | Relations is specific to Reltio and Position to Success Factors — each maps to any object or custom field on the other side. | |
| Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. | PerEmail and PerPhone Contact sub-entities under PerPerson; synced two-way with a directory or comms system to keep worker contact data current. | Crosswalks is specific to Reltio and PerEmail and PerPhone to Success Factors — each maps to any object or custom field on the other side. |
How changes propagate between Reltio 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.
Reltio Success Factors Interval-based propagation
DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.
DeliveryEach detected change is written to Success Factors through its API, with automatic retries and rate-limit backoff.
Success Factors Reltio 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 Reltio through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
- 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 Reltio ⇄ Success Factors
Connect Reltio and Success Factors for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–Success Factors connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Reltio 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 Reltio or Success Factors record.
Observability
Monitoring
Track your Reltio ⇄ 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 Reltio and Success Factors.
How the Reltio and Success Factors connectors work
Reltio
- Integration surface
- Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
- Authentication
- OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
- Change detection
- Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
- Capabilities
- read · write
- Rate limits
- Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
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 Reltio 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 Reltio 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.
Reltio
connected
Success Factors
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Reltio 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 · Reltio ⇄ 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.
Reltio Success FactorsCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Reltio and Success Factors integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Reltio and Success Factors: authenticate both systems, choose the objects to sync (such as Reltio's Activity Log and Data Change Requests (DCR)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Reltio 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 Reltio and Success Factors connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Reltio–Success Factors integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Reltio and Success Factors. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Reltio: Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks. 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.
-
On the Reltio side: Relations, Crosswalks, Interactions, Matches (Potential Matches), plus custom fields where Reltio exposes them. On the Success Factors side: PerEmail and PerPhone, User, PerPerson, EmpEmployment. Stacksync auto-detects both schemas and converts types between the two systems.
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 431 integrations available for Reltio and Success Factors.
Popular · 7 of 431
-
Reltio ⇄ Lever -
Reltio ⇄ Paylocity -
Reltio ⇄ Ukg Ready -
Success Factors ⇄ IBM AS/400 -
Success Factors ⇄ IBM Informix -
Success Factors ⇄ InfluxDB -
Success Factors ⇄ InterSystems IRIS
No integrations match .
