Two-way sync
Changes in Lever or SAP Business ByDesign instantly reflect in both systems. No stale data, no manual imports.
Keep Lever and SAP Business ByDesign 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. SAP Business ByDesign 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 Sales Orders, Customer Invoices, Materials / Products, Purchase Orders in SAP Business ByDesign with Stages, Feedback, Interviews, Notes and Contacts 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 SAP Business ByDesign 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.
When a worker is hired, moved, or offboarded in Lever, the matching employee record in SAP Business ByDesign is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
A new person set up in Lever becomes an employee record in SAP Business ByDesign 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 SAP Business ByDesign roll up to the same structure Lever maintains.
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 | SAP Business ByDesign 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 Built-in CRM records synced with external sales tools when both are in use. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. | Purchase Orders Procurement documents exchanged with supplier systems. | Users is specific to Lever and Purchase Orders to SAP Business ByDesign — each maps to any object or custom field on the other side. | |
| Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. | Projects Project structures and tasks read for time and billing integrations. | Stages is specific to Lever and Projects to SAP Business ByDesign — 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. | Employees Worker records referenced by time, expense, and project data. | Feedback is specific to Lever and Employees to SAP Business ByDesign — 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. | Business Partners (Accounts) Customer and supplier master data synced with CRMs and procurement tools. | Interviews is specific to Lever and Business Partners (Accounts) to SAP Business ByDesign — 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. | Contacts Person records linked to accounts, aligned with CRM contact objects. | Notes and Contacts is specific to Lever and Contacts to SAP Business ByDesign — 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 SAP Business ByDesign through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls SAP Business ByDesign for changes on an incremental schedule, reading only records changed since the previous pass. Polling on last-changed timestamps.
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–SAP Business ByDesign connection.
Changes in Lever or SAP Business ByDesign instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Lever or SAP Business ByDesign 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 SAP Business ByDesign record.
Track your Lever ⇄ SAP Business ByDesign sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Lever and SAP Business ByDesign.
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 SAP Business ByDesign 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 SAP Business ByDesign 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 SAP Business ByDesign: authenticate both systems, choose the objects to sync (such as Lever's Opportunities and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Lever and SAP Business ByDesign: Where Lever is the worker system of record: one employee master; New hires ready to transact in SAP Business ByDesign; One org structure. When a worker is hired, moved, or offboarded in Lever, the matching employee record in SAP Business ByDesign is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
Lever: 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). SAP Business ByDesign: SOAP web services plus OData services for analytical and custom data access. Authentication: Basic authentication over TLS for service users; OAuth-based options exist for certain scenarios. Stacksync manages authentication, retries, and rate limits on both sides.
SAP Business ByDesign: Custom fields and custom OData services can be defined in the tenant, so integrations often work against tenant-specific service definitions rather than one fixed schema. Lever: Webhooks cover candidate and application lifecycle events but not every object, so entities such as Postings, Requisitions, and Offers still require polling. Stacksync's field mapping accounts for these differences between Lever and SAP Business ByDesign without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Lever and SAP Business ByDesign records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Lever and SAP Business ByDesign connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Lever–SAP Business ByDesign integration in-house.
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 516 integrations available for Lever and SAP Business ByDesign.