Two-way sync
Changes in Lever or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Keep Lever and Dynamics 365 Business Central in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Lever is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Dynamics 365 Business Central runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.
Stacksync syncs Vendors, Items, Sales Orders, Sales Invoices in Dynamics 365 Business Central with Requisitions, Offers, Users, Stages in Lever field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Dynamics 365 Business Central keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.
A new person set up in Lever becomes an employee record in Dynamics 365 Business Central in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Dynamics 365 Business Central roll up to the same structure Lever maintains.
Manager and reporting-hierarchy changes in Lever keep expense and purchase approval chains in Dynamics 365 Business Central pointed at 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.
| Lever objects | Dynamics 365 Business Central objects | How this pairing syncs | |
|---|---|---|---|
| Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. | Vendors Supplier master data synced with procurement and AP automation tools. | Stages is specific to Lever and Vendors to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. | Items Product and inventory records aligned with e-commerce and warehouse systems. | Feedback is specific to Lever and Items to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. | Sales Orders Order headers and lines created from external channels and read back for fulfillment status. | Interviews is specific to Lever and Sales Orders to Dynamics 365 Business Central — 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. | Sales Invoices Billing documents synced to CRMs and payment platforms. | Notes and Contacts is specific to Lever and Sales Invoices to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| 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. | Purchase Orders Procurement documents exchanged with supplier-facing systems. | Opportunities is specific to Lever and Purchase Orders to Dynamics 365 Business Central — 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. | General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | Postings is specific to Lever and General Ledger Entries to Dynamics 365 Business Central — 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.
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 Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Lever–Dynamics 365 Business Central connection.
Changes in Lever or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Lever or Dynamics 365 Business Central data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Lever or Dynamics 365 Business Central record.
Track your Lever ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Lever and Dynamics 365 Business Central.
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 Lever and Dynamics 365 Business Central 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 Lever and Dynamics 365 Business Central 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 Lever and Dynamics 365 Business Central: authenticate both systems, choose the objects to sync (such as Lever's Stages and Feedback), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Lever and Dynamics 365 Business Central. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Lever: 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. On Dynamics 365 Business Central: API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Dynamics 365 Business Central side: Vendors, Items, Sales Orders, Sales Invoices, plus custom fields where Dynamics 365 Business Central exposes them. On the Lever side: Requisitions, Offers, Users, Stages. 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 Lever and Dynamics 365 Business Central: New hires ready to transact in Dynamics 365 Business Central; One org structure; Reporting lines drive approvals. A new person set up in Lever becomes an employee record in Dynamics 365 Business Central in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
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 509 integrations available for Lever and Dynamics 365 Business Central.