Skip to content
Human resources ⇄ Business productivity

Lever to Microsoft Dynamics 365 integration — real-time, two-way sync

Keep Lever 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.

  • 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 Lever and Microsoft Dynamics 365

Keep the people, teams, and status that Microsoft Dynamics 365 and Lever 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. Lever 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 Opportunities, Postings, Requisitions, Offers in Lever bi-directionally and in real time. A person added, moved, or offboarded in Lever 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 Lever 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 Sync cases with external ticketing or product systems so support works one queue.
  • 02 Replicate standard and custom Dataverse tables into a warehouse for reporting.
  • 03 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.
  • 04 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.

Common sync patterns

Org and team structure kept current

Department, team, and reporting-line changes from Lever 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 Lever, the queues, ownership, or approvals in Microsoft Dynamics 365 update to match, so work reaches whoever holds the role now.

Onboarding: access ready on day one

A new hire recorded in Lever creates the matching user in Microsoft Dynamics 365 with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

What you can sync between Lever and Microsoft Dynamics 365

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.

Lever objects Microsoft Dynamics 365 objects How this pairing syncs
Opportunities The core pipeline record for a candidate applying to a role; replaced the deprecated Candidates endpoint. Created via POST /opportunities and updated (stage, archive, links, tags, sources, files) through the API, and synced two-way with a database or HRIS. Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Cases (Incidents) Support records shared with ticketing tools and product databases. Interviews is specific to Lever and Cases (Incidents) to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Notes and Contacts Free-text Notes on Opportunities plus the underlying Contact (person) that dedupes multiple Opportunities; notes are posted via POST /opportunities/:id/notes and contact-level tags, sources, and links can be added back for attribution. Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. Notes and Contacts is specific to Lever and Quotes, Orders & Invoices to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Postings Job posting records with categories, apply URLs, workplace type, and requisition codes. Can be created via POST /postings and read into a warehouse for open-role reporting. Products Catalog records aligned with ERP item masters. Postings is specific to Lever and Products to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Requisitions Headcount/requisition records with custom requisition fields, tied to Postings; read via GET /requisitions and synced to an HRIS to reconcile approved headcount against open roles. Activities Emails, calls, and tasks captured for engagement analytics. Requisitions is specific to Lever and Activities to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.
Offers Offer records attached to an Opportunity with status and offer-form fields; exposed read-only through GET /opportunities/:id/offers, so they sync outbound to an HRIS or onboarding system when a candidate reaches the offer stage. Custom Tables Dataverse tables that carry business-specific entities through the same API surface. Offers is specific to Lever and Custom Tables to Microsoft Dynamics 365 — each maps to any object or custom field on the other side.

How changes propagate between Lever and Microsoft Dynamics 365

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.

Lever Microsoft Dynamics 365 Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryEach detected change is written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.

Microsoft Dynamics 365 Lever 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 Lever through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Lever: 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
What ships with Lever ⇄ Microsoft Dynamics 365

Connect Lever and Microsoft Dynamics 365 for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Lever–Microsoft Dynamics 365 connection.

Real-time

Two-way sync

Changes in Lever or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Lever or Microsoft Dynamics 365 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 Lever or Microsoft Dynamics 365 record.

Observability

Monitoring

Track your Lever ⇄ Microsoft Dynamics 365 sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Lever and Microsoft Dynamics 365.

How the Lever and Microsoft Dynamics 365 connectors work

Lever

Integration surface
REST Data API (api.lever.co/v1)
Authentication
API key over HTTP Basic auth (key as username, blank password) for internal integrations, or OAuth 2.0 with 1-hour access tokens for partner integrations (auth.lever.co)
Change detection
Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities
Capabilities
read · write · webhooks
Rate limits
10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
Lever setup guide

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
Microsoft Dynamics 365 setup guide
How it works

How to connect Lever to Microsoft Dynamics 365 — 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 Lever 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Lever connected
    Microsoft Dynamics 365 connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Lever 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Lever ⇄ Microsoft Dynamics 365
    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
    Lever Microsoft Dynamics 365
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Lever and Microsoft Dynamics 365 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 513 integrations available for Lever and Microsoft Dynamics 365.

Popular · 8 of 513
All Lever integrations All Microsoft Dynamics 365 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