Two-way sync
Changes in Jobvite or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.
Keep Jobvite and Microsoft Dynamics 365 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. Jobvite 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 Employee, Attachment, Offer, Candidate in Jobvite bi-directionally and in real time. A person added, moved, or offboarded in Jobvite 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 Jobvite 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.
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 Jobvite keep the groups, queues, or projects in Microsoft Dynamics 365 assigned to the right people.
When someone changes teams or managers in Jobvite, the queues, ownership, or approvals in Microsoft Dynamics 365 update to match, so work reaches whoever holds the role now.
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.
| Jobvite objects | Microsoft Dynamics 365 objects | How this pairing syncs | |
|---|---|---|---|
| Employee Employee roster pushed through POST /employee (Onboard sync), used for referral matching and internal-mobility job postings. | Custom Tables Dataverse tables that carry business-specific entities through the same API surface. | Employee is specific to Jobvite and Custom Tables to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Attachment Resumes, cover letters, and files attached to a candidate; synced out to object storage or a document management system. | Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. | Attachment is specific to Jobvite and Accounts to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Offer Offer state tied to an application (extended, accepted, declined); read out for offer-acceptance reporting and written to downstream comp or HR systems. | Contacts Person records kept consistent with marketing, support, and data-warehouse copies. | Offer is specific to Jobvite and Contacts to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Candidate Read from the candidate feed (GET /candidate) and written back via POST /candidate/updateCandidates to change status, notes, and disposition on each record. | Leads Inbound records enriched and routed from external sources into sales queues. | Candidate is specific to Jobvite and Leads to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Requisition (Job) Job openings created or updated through POST /job and read from GET /jobFeed; maps to opening tables in an ATS reporting warehouse. | Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | Requisition (Job) is specific to Jobvite and Opportunities to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Application Links a candidate to one requisition with its workflow state; read for pipeline reporting and status written back through the candidate update call. | Cases (Incidents) Support records shared with ticketing tools and product databases. | Application is specific to Jobvite and Cases (Incidents) to Microsoft Dynamics 365 — 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.
DetectionJobvite notifies Stacksync of record changes through webhook events. A candidate hired webhook, configured per customer by a Jobvite rep, POSTs to a custom URL on hire/offer-accepted events.
DeliveryEach detected change is written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
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 Jobvite through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Jobvite–Microsoft Dynamics 365 connection.
Changes in Jobvite or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Jobvite or Microsoft Dynamics 365 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Jobvite or Microsoft Dynamics 365 record.
Track your Jobvite ⇄ Microsoft Dynamics 365 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Jobvite and Microsoft Dynamics 365.
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 Jobvite and Microsoft Dynamics 365 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 Jobvite and Microsoft Dynamics 365 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 Jobvite and Microsoft Dynamics 365: authenticate both systems, choose the objects to sync (such as Jobvite's Employee and Attachment), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Microsoft Dynamics 365 side: Products, Activities, Custom Tables, Accounts, plus custom fields where Microsoft Dynamics 365 exposes them. On the Jobvite side: Employee, Attachment, Offer, Candidate. 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 Jobvite and Microsoft Dynamics 365: One employee directory; Org and team structure kept current; Where Microsoft Dynamics 365 routes or assigns work by person: assignments follow the org. 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.
Jobvite: REST API (JSON) with candidate, requisition (job), and employee feed endpoints under https://api.jobvite.com/{version}. Authentication: API key (api) and secret (sc) plus company ID (companyId), sent in request headers since Jobvite's April 1, 2024 move from URL-query to header-based auth. Credentials are provisioned per customer by Jobvite Support. Microsoft Dynamics 365: 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). Stacksync manages authentication, retries, and rate limits on both sides.
Microsoft Dynamics 365: Authorization may be blocked by a 'Need admin approval for this app' screen requiring a Microsoft directory admin to grant consent to the Stacksync app before syncing can begin. Jobvite: The API is rate-limited to roughly 15 requests per minute and 850 per hour (reset at midnight Pacific), with per-endpoint daily caps, so high-volume backfills must be throttled and batched. Stacksync's field mapping accounts for these differences between Jobvite and Microsoft Dynamics 365 without custom code.
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 Jobvite and Microsoft Dynamics 365.