Two-way sync
Changes in Azure Synapse Analytics or Success Factors instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Synapse Analytics 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.
Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Success Factors is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Azure Synapse Analytics next to everything else the company measures.
Stacksync syncs Position, PerEmail and PerPhone, User, PerPerson from Success Factors into tables in Azure Synapse Analytics continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Azure Synapse Analytics, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Success Factors where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
Segments, rollups, or risk flags computed in Azure Synapse Analytics sync back onto the matching records in Success Factors, where the HR team sees them in the system they already use.
People and organization records from Success Factors arrive in Azure Synapse Analytics as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
Analysts combine Success Factors's workforce records with finance, product, or operational data already in Azure Synapse Analytics for reporting the HR system cannot produce on its own.
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.
| Azure Synapse Analytics objects | Success Factors objects | How this pairing syncs | |
|---|---|---|---|
| SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | 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. | SQL pools is specific to Azure Synapse Analytics and Foundation Objects (FODepartment, FOLocation, FOCostCenter) to Success Factors — each maps to any object or custom field on the other side. | |
| Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | Position Position Management records for headcount and requisition planning; synced with an ATS or ERP to keep positions and reqs aligned. | Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Position to Success Factors — each maps to any object or custom field on the other side. | |
| External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. | PerEmail and PerPhone Contact sub-entities under PerPerson; synced two-way with a directory or comms system to keep worker contact data current. | External tables is specific to Azure Synapse Analytics and PerEmail and PerPhone to Success Factors — each maps to any object or custom field on the other side. | |
| Views Curated projections used when downstream tools should not read base tables directly. | 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. | Views is specific to Azure Synapse Analytics and User to Success Factors — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that separate staging, integration, and presentation layers. | PerPerson Person-level container in Employee Central holding biographical data; effective-dated child entities (PerPersonal, PerEmail, PerPhone) hang off it. | Schemas is specific to Azure Synapse Analytics and PerPerson to Success Factors — each maps to any object or custom field on the other side. | |
| Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | EmpEmployment Employment record tying a person to an employment period (hire, service dates); carries lastModifiedDateTime used for incremental polling. | Materialized views is specific to Azure Synapse Analytics and EmpEmployment to Success Factors — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.
DeliveryEach detected change is written to Success Factors through its API, with automatic retries and rate-limit backoff.
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 Azure Synapse Analytics as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Success Factors connection.
Changes in Azure Synapse Analytics or Success Factors instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Synapse Analytics or Success Factors data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Synapse Analytics or Success Factors record.
Track your Azure Synapse Analytics ⇄ Success Factors sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Success Factors.
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.
Authenticate Azure Synapse Analytics 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.
Pick the Azure Synapse Analytics 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Azure Synapse Analytics and Success Factors: authenticate both systems, choose the objects to sync (such as Azure Synapse Analytics's SQL pools and Tables (dedicated SQL pool)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Synapse Analytics and Success Factors connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Synapse Analytics–Success Factors integration in-house.
Yes — Stacksync ships production-grade connectors for both Azure Synapse Analytics and Success Factors. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Azure Synapse Analytics: Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers. 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 Azure Synapse Analytics side: Views, Schemas, Materialized views, SQL pools, plus custom fields where Azure Synapse Analytics exposes them. On the Success Factors side: Position, PerEmail and PerPhone, User, PerPerson. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 541 integrations available for Azure Synapse Analytics and Success Factors.