Skip to content
Human resources ⇄ ERP

Lever to SuiteAnalytics integration — real-time data sync

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

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

SuiteAnalytics is a read-only source: Stacksync reads its data in real time and delivers it into Lever, so Lever always reflects the current state of SuiteAnalytics — without exports, scripts, or schedulers.

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. SuiteAnalytics 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.

Common use cases

  • 01 Give internal tools a read replica of item and inventory data without hitting SuiteScript governance limits
  • 02 Join ERP data with CRM data in Postgres for quote-to-cash and revenue visibility
  • 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

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 SuiteAnalytics is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

New hires ready to transact in SuiteAnalytics

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

One org structure

Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in SuiteAnalytics roll up to the same structure Lever maintains.

What you can sync between Lever and SuiteAnalytics

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 SuiteAnalytics 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. All custom objects Synced with incremental and full sync per the Stacksync docs. Opportunities is specific to Lever and All custom objects to SuiteAnalytics — 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. Nexus Synced with incremental and full sync per the Stacksync docs. Postings is specific to Lever and Nexus to SuiteAnalytics — 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. Tax Type Synced with incremental and full sync per the Stacksync docs. Requisitions is specific to Lever and Tax Type to SuiteAnalytics — 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. Sales Tax Item Synced with incremental and full sync per the Stacksync docs. Offers is specific to Lever and Sales Tax Item to SuiteAnalytics — 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. Billing Schedule Customer Subsidiary Relationship Synced with incremental and full sync per the Stacksync docs. Users is specific to Lever and Billing Schedule Customer Subsidiary Relationship to SuiteAnalytics — 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. Account Synced with incremental and full sync per the Stacksync docs. Stages is specific to Lever and Account to SuiteAnalytics — each maps to any object or custom field on the other side.

How changes propagate between Lever and SuiteAnalytics

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 SuiteAnalytics Sub-second propagation

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

DeliverySuiteAnalytics does not accept inbound record writes, so this direction carries requests rather than records: SuiteAnalytics's output flows back as field updates on the originating Lever records.

SuiteAnalytics Lever Interval-based propagation

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

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.
  • SuiteAnalytics: Concurrency and query load are governed by the NetSuite account's Connect service allowances rather than per-request rate limits.
What ships with Lever ⇄ SuiteAnalytics

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

SuiteAnalytics

Integration surface
SQL over ODBC, JDBC, and ADO.NET (SuiteAnalytics Connect)
Authentication
NetSuite Token-Based Authentication: create an integration record (Consumer ID + Consumer Secret), an access token (Token ID + Token Secret), a role with SuiteAnalytics Connect and SuiteAnalytics Connect - Read All
Change detection
Not stated in the docs
Capabilities
read
Rate limits
Concurrency and query load are governed by the NetSuite account's Connect service allowances rather than per-request rate limits
SuiteAnalytics setup guide
How it works

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

    Choose tables

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

Lever and SuiteAnalytics 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 388 integrations available for Lever and SuiteAnalytics.

Popular · 8 of 388
All Lever integrations All SuiteAnalytics 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