Can you integrate Lever with Microsoft Dynamics 365?

Explore a Lever and Microsoft Dynamics 365 integration with a Stacksync engineer. Stacksync support for Lever is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

Can Lever and Microsoft Dynamics 365 sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the Lever and Microsoft Dynamics 365 initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Lever account, edition, environment, and business objects the integration must access. Provide the Dynamics CRM environment URL and authorize the Stacksync app with Microsoft sign-in. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Lever to Microsoft Dynamics 365 sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map Lever fields to Microsoft Dynamics 365?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a Lever and Microsoft Dynamics 365 integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the Lever and Microsoft Dynamics 365 pilot start with?

Start by reviewing Opportunities in Lever and Opportunities in Microsoft Dynamics 365. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

Human resources / Business productivity · Two-way sync platform

Lever and Microsoft Dynamics 365 integration

Plan how Lever and Microsoft Dynamics 365 should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

Lever

Microsoft Dynamics 365

Review the integration scope

Built for teams where self-serve, reliability and scale matter

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

Proposed workflow

Deal or opportunity sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving Lever Opportunities or Microsoft Dynamics 365 Opportunities needs a defined result in the other system.

Start with Lever Opportunities and Microsoft Dynamics 365 Opportunities. Use the record-matching and field-ownership rules from your mapping worksheet.
Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between Lever and Microsoft Dynamics 365
Lever record	Microsoft Dynamics 365 record	Record matching	Field ownership
OpportunitiesProposed record; confirm Stacksync object support.Record matching	OpportunitiesProposed record; confirm Stacksync object support.	Keep the opportunity/deal ID separate from any later order or invoice ID.	The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

Lever

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Opportunities Postings Requisitions Offers Users Stages	Confirm support for this record type and the direction you need.

Discuss Lever requirements

Microsoft Dynamics 365

Read and write support varies by record

Record types covered in the setup guide

Record types	Coverage and requirements
Standard entities	Requires account access and compatible change tracking. Confirm field permissions and sync direction.
Custom entities	Requires API exposure and compatible change tracking. Confirm field permissions and sync direction.

Read the Microsoft Dynamics 365 connector guide

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits

Connection requirement	Lever	Microsoft Dynamics 365
Integration interface	REST Data API (api.lever.co/v1)	REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
Authentication	Confirm the credentials, API plan, and permissions required for Lever.	Microsoft OAuth sign-in
Change detection	Confirm how Stacksync detects changes for this connector and the objects you need.	Incremental sync uses Dynamics Change Tracking; custom entities need Track Changes enabled.
Read access	Confirm with Stacksync	Available for supported records
Write access	Confirm with Stacksync	Available for supported records

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

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

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:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Lever

Integration interface: REST Data API (api.lever.co/v1)
Authentication: Confirm the credentials, API plan, and permissions required for Lever.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the Lever account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Lever, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for Lever and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Technical documentation

Lever vendor API documentation

Microsoft Dynamics 365

Integration interface: 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: Incremental sync uses Dynamics Change Tracking; custom entities need Track Changes enabled.
Read access: Available for supported records
Write access: Available for supported records

Setup requirements

Provide the Dynamics CRM environment URL and authorize the Stacksync app with Microsoft sign-in.
For custom entities, enable Track Changes in Power Apps/Dataverse before validating incremental updates.

Limitations to check

Custom-entity change tracking must be enabled before incremental changes can be captured.

Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Microsoft Dynamics 365 setup guide

Prepare Lever and Microsoft Dynamics 365 access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

Lever setup checklist

Identify the Lever account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Lever, including read/write support, authentication, and initial-load limits.

Microsoft Dynamics 365 setup checklist

Provide the Dynamics CRM environment URL and authorize the Stacksync app with Microsoft sign-in.
For custom entities, enable Track Changes in Power Apps/Dataverse before validating incremental updates.

Setup guides: Authorize Dynamics 365 CRM

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the Lever and Microsoft Dynamics 365 planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Record matching

Opportunities / Opportunities

Compare whether Lever Opportunities and Microsoft Dynamics 365 Opportunities describe the same deal or opportunity in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Lever: Object support to establish
Microsoft Dynamics 365: Object support to establish
Record identity: Keep the opportunity/deal ID separate from any later order or invoice ID.
Field ownership: The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules.

Fields to include

Source deal ID
Stage
Amount and currency
Expected close date
Company reference

Record dependencies: Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Validation: Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
Recovery: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

References: Lever: Opportunities documentation Microsoft Dynamics 365: Opportunities documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Opportunities / Opportunities to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Keep the opportunity/deal ID separate from any later order or invoice ID. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your Lever and Microsoft Dynamics 365 record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Opportunities / Opportunities, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when Lever and Microsoft Dynamics 365 need a transformation, approval, or action outside a direct record sync.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit: Consider for a one-time Lever / Microsoft Dynamics 365 migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Deal or opportunity sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Opportunities or Opportunities record needs a defined result in the other system.

Start with Lever Opportunities and Microsoft Dynamics 365 Opportunities. Use the record-matching and field-ownership rules from your mapping worksheet.
Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.

If it fails: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

Worker lifecycle planning for Lever and Microsoft Dynamics 365

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A worker joins, moves, or leaves in Lever; a downstream process in Microsoft Dynamics 365 needs the approved context.

Identify the worker and employment record represented by Opportunities or Users. Retain effective dates and organizational scope.
Determine what Accounts or Contacts represents: an operational task, a user identity, or a reporting row. Define a relationship; do not map these records as if they were the employee itself.
Require the process owner to approve any access, payroll, or account action and assign an exception owner.

Expected result: Rehires and concurrent assignments keep distinct employment context; delayed updates do not reverse a newer effective state.

If it fails: Inspect employment identity and effective dates before retrying the downstream action.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Opportunities / Opportunities

Test case

Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.

Expected result

The expected deal or opportunity relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated deal or opportunity change

Investigate

Inspect Lever Opportunities and Microsoft Dynamics 365 Opportunities, their IDs, and the destination error.

Next action

Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

A record type or update is unavailable

Investigate

Check the Lever and Microsoft Dynamics 365 connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between Lever and Microsoft Dynamics 365

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Lever Microsoft Dynamics 365 Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Microsoft Dynamics 365.

Microsoft Dynamics 365 Lever Direction requires confirmation

Detect changesIncremental sync uses Dynamics Change Tracking; custom entities need Track Changes enabled.

Apply updatesConfirm that Stacksync can create or update the records you need in Lever.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.
Custom-entity change tracking must be enabled before incremental changes can be captured.

FAQ