Skip to content
Human resources ⇄ Database

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

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

Put your workforce data where your apps can reach it: TiDB 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. TiDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: PerPerson, EmpEmployment, EmpJob, EmpCompensation in Success Factors need to exist as queryable Sequences, Databases, Tables, Views in TiDB 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 Sequences, Databases, Tables, Views in TiDB with PerPerson, EmpEmployment, EmpJob, EmpCompensation 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 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas
  • 02 Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge
  • 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

Computed and operational fields flow back

Values assembled or corrected in TiDB 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 Sequences, Databases, Tables, Views in TiDB, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

What you can sync between Success Factors and TiDB

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 TiDB objects How this pairing syncs
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. Indexes Secondary indexes that keep incremental sync queries efficient. User is specific to Success Factors and Indexes to TiDB — each maps to any object or custom field on the other side.
PerPerson Person-level container in Employee Central holding biographical data; effective-dated child entities (PerPersonal, PerEmail, PerPhone) hang off it. Sequences Server-side ID generation relevant when external systems write rows. PerPerson is specific to Success Factors and Sequences to TiDB — each maps to any object or custom field on the other side.
EmpEmployment Employment record tying a person to an employment period (hire, service dates); carries lastModifiedDateTime used for incremental polling. Databases MySQL-style schemas addressed by any MySQL-compatible client. EmpEmployment is specific to Success Factors and Databases to TiDB — 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. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. EmpJob is specific to Success Factors and Tables to TiDB — 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. Views Logical views for shaping reads before syncing outward. EmpCompensation is specific to Success Factors and Views to TiDB — 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. Columns MySQL-compatible types mapped to fields in the paired system. Foundation Objects (FODepartment, FOLocation, FOCostCenter) is specific to Success Factors and Columns to TiDB — each maps to any object or custom field on the other side.

How changes propagate between Success Factors and TiDB

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 TiDB 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 TiDB as a row-level write, with types converted between the two schemas.

TiDB Success Factors Sub-second propagation

DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.

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.
  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Success Factors ⇄ TiDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

TiDB

Integration surface
MySQL wire protocol (SQL)
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
Capabilities
read · write · CDC
Rate limits
Throughput scales with cluster size rather than fixed API quotas
How it works

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

    Choose tables

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

Success Factors and TiDB 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 429 integrations available for Success Factors and TiDB.

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