Two-way sync
Changes in Microsoft Dynamics 365 or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep Microsoft Dynamics 365 and Smartrecruiters in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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. Smartrecruiters 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 Activities, Custom Tables, Accounts, Contacts in Microsoft Dynamics 365 with Interviews, Offers, Users, Approvals in Smartrecruiters bi-directionally and in real time. A person added, moved, or offboarded in Smartrecruiters 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 Smartrecruiters 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.
When someone is marked as leaving in Smartrecruiters, the matching account in Microsoft Dynamics 365 is deactivated or flagged, so departures do not leave open access behind.
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.
Department, team, and reporting-line changes from Smartrecruiters keep the groups, queues, or projects in Microsoft Dynamics 365 assigned to the right people.
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 | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. | Offers Offer records tied to an Application with status, custom offer fields, and offer documents; readable and writable, commonly synced to an HRIS on hire (documents endpoint limited to 2 requests/sec). | Accounts is specific to Microsoft Dynamics 365 and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Contacts Person records kept consistent with marketing, support, and data-warehouse copies. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Contacts is specific to Microsoft Dynamics 365 and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Leads Inbound records enriched and routed from external sources into sales queues. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Leads is specific to Microsoft Dynamics 365 and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. | Opportunities is specific to Microsoft Dynamics 365 and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Cases (Incidents) Support records shared with ticketing tools and product databases. | Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. | Cases (Incidents) is specific to Microsoft Dynamics 365 and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Quotes, Orders & Invoices is specific to Microsoft Dynamics 365 and Jobs to Smartrecruiters — 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.
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 Smartrecruiters through its API, with automatic retries and rate-limit backoff.
DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.
DeliveryEach detected change is written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365–Smartrecruiters connection.
Changes in Microsoft Dynamics 365 or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Microsoft Dynamics 365 or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Microsoft Dynamics 365 or Smartrecruiters record.
Track your Microsoft Dynamics 365 ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics 365 and Smartrecruiters.
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 Microsoft Dynamics 365 and Smartrecruiters 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 Microsoft Dynamics 365 and Smartrecruiters 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 Microsoft Dynamics 365 and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics 365's Accounts and Contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Microsoft Dynamics 365 and Smartrecruiters. 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 Smartrecruiters: Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Microsoft Dynamics 365 side: Activities, Custom Tables, Accounts, Contacts, plus custom fields where Microsoft Dynamics 365 exposes them. On the Smartrecruiters side: Interviews, Offers, Users, Approvals. 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.
Common patterns for Microsoft Dynamics 365 and Smartrecruiters: Offboarding: no standing access after a departure; One employee directory; Org and team structure kept current. When someone is marked as leaving in Smartrecruiters, the matching account in Microsoft Dynamics 365 is deactivated or flagged, so departures do not leave open access behind.
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 513 integrations available for Microsoft Dynamics 365 and Smartrecruiters.