Lever to HubSpot
Lever is a cloud ATS and recruiting CRM. Its core model is Contacts, Opportunities (one per candidacy), Postings and Requisitions.
Lever data can move into HubSpot, landing mainly in Sales Hub. 1 of 7 mapped objects move directly (Contacts (candidate person)); 4 items need manual work and 2 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Lever
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<5k contacts
Contacts and deals only.
Mid migration
5k-50k contacts
Includes notes, resumes and a vacancy object.
Large migration
>50k contacts
Heavy files, custom objects and a hybrid run with Lever.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Lever: what you need to get in, what lands in HubSpot, and what will not.
REST/JSON Data API (v1) at api.lever.co/v1, plus a public Postings API
An API key generated in Lever, with scopes and confidential-data access as needed. OAuth needs a Lever-issued client ID and secret.
A Super Admin generates API keys under Settings > Integrations and API > API Credentials. Reading confidential postings, opportunities and requisitions needs a key with confidential access.
10 requests/second per API key steady state, bursts to 20, token bucket, 429 on breach. Application POSTs are limited to 2/second.
Choose your route
How will you move the data?
No native connector was found.
- You need: An API key generated in Lever, with scopes and confidential-data access as needed. OAuth needs a Lever-issued client ID and secret.
- Permission: A Super Admin generates API keys under Settings > Integrations and API > API Credentials. Reading confidential postings, opportunities and requisitions needs a key with confidential access.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Data API: GET /opportunities, with cursor pagination (limit up to 100) and sub-resources such as notes, feedback, offers, forms, files and resumes
- Visual Insights dashboard CSV downloads (analytics data only)
- Lever account manager data export files (CSVs, profile_cards.json, a resume folder), as seen in another vendor's Lever migration guide
- Community scripts that dump opportunities and resumes to JSON/CSV
- Webhooks for ongoing change events
Limits: 10 requests/second per API key steady state, bursts to 20, token bucket, 429 on breach. Application POSTs are limited to 2/second.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Lever
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts (candidate person) | Contacts | yes | A Lever Contact is the unique person. Map name, email, phone, location, tags, source and links, and keep the Lever contact ID in a custom property. |
| Opportunities (candidacies) | Deals | partial | Each opportunity is one candidacy for one posting, and a person can have several. Map them to Deals in a custom pipeline, with stage and archive reason as properties. Deal-per-opportunity is an analyst design choice, not a documented path. |
| Postings / Requisitions | Custom objects | manual | Postings and requisitions are available via the API. A HubSpot Custom object (for example Vacancy) would need to be designed and loaded. Custom objects need an Enterprise subscription (unsourced). |
| Notes | Notes | partial | Notes are retrievable per opportunity via the API. They must be associated to the contact or deal on import. |
| Resumes and files | Files | partial | Resumes and files are listed in the API export. They must be downloaded and re-uploaded to HubSpot, then attached to records. |
| Interview feedback, panels, offers, forms | Custom objects | manual | There is no native equivalent in HubSpot. Archive as PDF/JSON or flatten into properties or notes. |
| Client companies / BD pipeline | Companies | no | Lever is an ATS and its documented model has no client or BD objects. Client data would come from other sources such as a spreadsheet. |
What to expect
These are Lever application features, not exportable data. HubSpot has no ATS equivalent, so they need retention or replacement.
They are only returned if the API key has confidential access.
Lever's Contact-to-Opportunity model has no one-to-one HubSpot object.
The status models differ between systems.
There is no single bulk resume download in the UI, so use the API or a support export.
Feedback, offers and compliance records may need retention outside HubSpot.
Carry over consent and source fields, and set retention rules before import.
Run below 10 requests/second with exponential backoff, and use incremental pulls by updated date.
Dedupe on the Contact ID and email before import.
Use a Super Admin API key for a one-off migration.
Use /opportunities.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
The API, auth and rate limits are backed by Lever's developer docs. Object mapping to HubSpot is analyst judgement because no HubSpot-published Lever connector or guide was found. Governance, residency and certifications are not sourced.
Sources
Related migrations
Frequently asked questions
How do I migrate Lever to HubSpot?
1. Have a Super Admin generate a Lever API key with the needed scopes and confidential access. 2. Inventory opportunities, postings, requisitions, tags, sources, archive reasons and custom fields. 3. Decide which opportunities become Deals and which contacts are candidates versus clients. 4. Create HubSpot custom properties for the Lever contact ID and opportunity ID.
What data can move from Lever to HubSpot?
These objects move directly: Contacts (candidate person). Check the mapping table for partial and manual items.
What does not move from Lever to HubSpot?
Lever workflow automation, interview scheduling and sourcing/job-site distribution and Confidential postings, opportunities and requisitions. Plan to rebuild or retire these.
How long does a Lever to HubSpot migration take?
Small (<5k contacts): 2-4 weeks. Mid (5k-50k contacts): 4-8 weeks. Large (>50k contacts): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Lever?
An API key generated in Lever, with scopes and confidential-data access as needed. OAuth needs a Lever-issued client ID and secret. A Super Admin generates API keys under Settings > Integrations and API > API Credentials. Reading confidential postings, opportunities and requisitions needs a key with confidential access.
What compliance issues apply when moving Lever data?
Check: Hiring and EEO/diversity data, Candidate PII (GDPR/CCPA) and Possible offer and compensation data. Agree consent, retention and access rules before exporting.
Moving Lever into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner