Skip to content
Human resources ⇄ ERP

Lever to Syspro integration — real-time, two-way sync

Keep Lever and Syspro 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 Syspro

Sync the workers, org structure, and cost centers that Syspro and Lever share in real time, so the people Lever manages stay current in the system that runs finance and operations.

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. Syspro 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 Purchase orders, Jobs (work orders), Bills of materials, AR invoices in Syspro with Opportunities, Postings, Requisitions, Offers 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 Syspro 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.

Common use cases

  • 01 Mirror customers and AR invoices into a CRM so sales sees credit and billing status on the account
  • 02 Extract job and WIP data into a warehouse for production and costing reports
  • 03 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.
  • 04 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.

Common sync patterns

Where Lever runs payroll: labor cost in the books

Pay and compensation data from Lever posts into Syspro as labor cost, so finance sees workforce spend without re-entering it by hand.

Where Lever is the worker system of record: one employee master

When a worker is hired, moved, or offboarded in Lever, the matching employee record in Syspro is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

New hires ready to transact in Syspro

A new person set up in Lever becomes an employee record in Syspro in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.

What you can sync between Lever and Syspro

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 Syspro 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. Bills of materials Product structures referenced when syncing manufacturing data. Opportunities is specific to Lever and Bills of materials to Syspro — 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. AR invoices Billing documents surfaced to CRMs and finance reporting. Postings is specific to Lever and AR invoices to Syspro — 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. GL journals Financial postings extracted for consolidation and analytics. Requisitions is specific to Lever and GL journals to Syspro — 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. Warehouses Stocking locations that scope inventory balances. Offers is specific to Lever and Warehouses to Syspro — each maps to any object or custom field on the other side.
Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Customers AR customer master records matched against CRM accounts. Users is specific to Lever and Customers to Syspro — 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. Suppliers AP supplier records synced with procurement and payment systems. Stages is specific to Lever and Suppliers to Syspro — each maps to any object or custom field on the other side.

How changes propagate between Lever and Syspro

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

Syspro Lever Interval-based propagation

DetectionStacksync polls Syspro for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

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.
  • Syspro: Throughput depends on the customer's server sizing; many deployments are on-premise.
What ships with Lever ⇄ Syspro

Connect Lever and Syspro for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Lever ⇄ Syspro 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 Syspro.

How the Lever and Syspro 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

Syspro

Integration surface
e.net Solutions business objects, exposed over REST and WCF interfaces in SYSPRO 8
Authentication
SYSPRO operator credentials exchanged for a session token
Change detection
Polling; the ERP does not expose a change feed to external consumers
Capabilities
read · write
Rate limits
Throughput depends on the customer's server sizing; many deployments are on-premise
How it works

How to connect Lever to Syspro — 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 Syspro 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
    Syspro connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Lever and Syspro 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 ⇄ Syspro
    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 Syspro
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Lever and Syspro 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 506 integrations available for Lever and Syspro.

Popular · 8 of 506
All Lever integrations All Syspro 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