Real-time
Two-way sync
Changes in Microsoft Dynamics 365 or Success Factors instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Human resources
Microsoft Dynamics 365 to Success Factors integration — real-time, two-way sync
Keep Microsoft Dynamics 365 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 Microsoft Dynamics 365 and Success Factors
Keep the people, teams, and status that Microsoft Dynamics 365 and Success Factors share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Each tool in Microsoft Dynamics 365 keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Success Factors is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Products, Activities, Custom Tables, Accounts in Microsoft Dynamics 365 with EmpEmployment, EmpJob, EmpCompensation, Foundation Objects (FODepartment, FOLocation, FOCostCenter) in Success Factors bi-directionally and in real time. A person added, moved, or offboarded in Success Factors creates or updates the matching user in Microsoft Dynamics 365 within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Microsoft Dynamics 365 captures details of its own, such as a corrected contact or a login identity, those can flow back to Success Factors in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
Common use cases
- 01 Keep opportunities and orders consistent with the ERP or billing system without manual re-entry.
- 02 Sync cases with external ticketing or product systems so support works one queue.
- 03 Keep Foundation Objects (department, location, cost center) aligned between SuccessFactors and an ERP so cost-center and org hierarchies match.
- 04 Write updated PerEmail, PerPhone, and User attributes back into SuccessFactors from an identity or directory system so contact data stays current.
Common sync patterns
One employee directory
A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.
Org and team structure kept current
Department, team, and reporting-line changes from Success Factors keep the groups, queues, or projects in Microsoft Dynamics 365 assigned to the right people.
Where Microsoft Dynamics 365 routes or assigns work by person: assignments follow the org
When someone changes teams or managers in Success Factors, the queues, ownership, or approvals in Microsoft Dynamics 365 update to match, so work reaches whoever holds the role now.
What you can sync between Microsoft Dynamics 365 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.
| Microsoft Dynamics 365 objects | Success Factors objects | How this pairing syncs | |
|---|---|---|---|
| Activities Emails, calls, and tasks captured for engagement analytics. | Position Position Management records for headcount and requisition planning; synced with an ATS or ERP to keep positions and reqs aligned. | Activities is specific to Microsoft Dynamics 365 and Position to Success Factors — each maps to any object or custom field on the other side. | |
| Custom Tables Dataverse tables that carry business-specific entities through the same API surface. | PerEmail and PerPhone Contact sub-entities under PerPerson; synced two-way with a directory or comms system to keep worker contact data current. | Custom Tables is specific to Microsoft Dynamics 365 and PerEmail and PerPhone to Success Factors — each maps to any object or custom field on the other side. | |
| Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. | 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. | Accounts is specific to Microsoft Dynamics 365 and User to Success Factors — each maps to any object or custom field on the other side. | |
| Contacts Person records kept consistent with marketing, support, and data-warehouse copies. | PerPerson Person-level container in Employee Central holding biographical data; effective-dated child entities (PerPersonal, PerEmail, PerPhone) hang off it. | Contacts is specific to Microsoft Dynamics 365 and PerPerson to Success Factors — each maps to any object or custom field on the other side. | |
| Leads Inbound records enriched and routed from external sources into sales queues. | EmpEmployment Employment record tying a person to an employment period (hire, service dates); carries lastModifiedDateTime used for incremental polling. | Leads is specific to Microsoft Dynamics 365 and EmpEmployment to Success Factors — each maps to any object or custom field on the other side. | |
| Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | EmpJob Effective-dated job info: position, department, manager, FTE, pay grade, cost center; the most-synced record for downstream HR and provisioning. | Opportunities is specific to Microsoft Dynamics 365 and EmpJob to Success Factors — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft Dynamics 365 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.
Microsoft Dynamics 365 Success Factors Sub-second propagation
DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.
DeliveryEach detected change is written to Success Factors through its API, with automatic retries and rate-limit backoff.
Success Factors Microsoft Dynamics 365 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 Microsoft Dynamics 365 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 Microsoft Dynamics 365 ⇄ Success Factors
Connect Microsoft Dynamics 365 and Success Factors for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365–Success Factors connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft Dynamics 365 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 Microsoft Dynamics 365 or Success Factors record.
Observability
Monitoring
Track your Microsoft Dynamics 365 ⇄ 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 Microsoft Dynamics 365 and Success Factors.
How the Microsoft Dynamics 365 and Success Factors connectors work
Microsoft Dynamics 365
- Integration surface
- REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
- Authentication
- Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities)
- Change detection
- Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties
- Capabilities
- read · write · CDC · webhooks
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 Microsoft Dynamics 365 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 Microsoft Dynamics 365 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.
Microsoft Dynamics 365
connected
Success Factors
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft Dynamics 365 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 · Microsoft Dynamics 365 ⇄ 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.
Microsoft Dynamics 365 Success FactorsCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft Dynamics 365 and Success Factors integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Dynamics 365 and Success Factors: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics 365's Activities and Custom Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Microsoft Dynamics 365: Change tracking returns only rows changed since a delta token, giving integrations an incremental read path without full re-pulls. Success Factors: OAuth 2.0 SAML Bearer Assertion is required (HTTP Basic auth is being retired); access tokens are short-lived and issued per registered API key. Stacksync's field mapping accounts for these differences between Microsoft Dynamics 365 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 Microsoft Dynamics 365 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 Microsoft Dynamics 365 and Success Factors connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Microsoft Dynamics 365–Success Factors integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Microsoft Dynamics 365 and Success Factors. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Microsoft Dynamics 365: Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties. 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 513 integrations available for Microsoft Dynamics 365 and Success Factors.
Popular · 8 of 513
-
Microsoft Dynamics 365 ⇄ Smartrecruiters -
Microsoft Dynamics 365 ⇄ Ukg Pro -
Microsoft Dynamics 365 ⇄ Greenhouse -
Microsoft Dynamics 365 ⇄ Jobvite -
Success Factors ⇄ Ironclad -
Success Factors ⇄ Servicemax -
Success Factors ⇄ Adobe Sign -
Success Factors ⇄ Asana
No integrations match .
