Migrate from Lever to Expertini ATS
INTEGRATIONS · EXPERTINI ATS

Migrate from Lever to Expertini ATS

Move your jobs, candidates, and live pipeline out of Lever and into Expertini ATS in an afternoon — drafts first, deduplicated, with your funnel stages mapped automatically and nothing published without your click.

3 min lectură · Actualizat iulie 2026 · Echipa editorială Expertini

Leaving an ATS feels riskier than it is. Your data in Lever is legally yours, every mainstream system can export it, and Expertini's Third-Party ATS Import is built to receive exactly that export: jobs arrive as drafts so nothing goes live by accident, candidates land in the talent pool deduplicated by email, and your in-flight pipeline — who is at which stage on which job — is rebuilt rather than abandoned. The importer is the same one used for every migration source, so the path out of Lever is a well-trodden one, not a special case.

This page is the Lever-specific route through the general migration guide. Expertini ATS is an independent product; Lever is a trademark of its owner, and nothing here requires their cooperation — only the export they already provide to every customer.

Pe această pagină

  1. Get your data out of Lever
  2. Reshape it to the sample JSON
  3. Upload in safe batches
  4. What lands where
  5. Schița interfeței și fluxul de interacțiune
  6. Întrebări frecvente

Din ce sistem vă mutați?

Tastați pentru a căuta — selectarea unui furnizor deschide ghidul de migrare dedicat pentru acesta. Fiecare cale ajunge în același importator, cu aceleași limite oneste de lot și reguli de deduplicare.

Harta de dependență — ce anume se importă

Jobstitle, description, location, type, category, salary, experience & education levels — arrive as DRAFTS, nothing goes live by accident
Candidatesname, email, phone, title, location, skills, notes — into the talent pool, deduplicated by email
Applicationscandidate_email + job_external_id + stage + applied_at — rebuilds your funnel; foreign stage names ("phone screen", "offered", "onsite"…) map automatically, unrecognised ones land in Applied
Batch limits500 jobs and 2,000 candidates per upload — split bigger exports; duplicates are skipped, so overlapping batches are safe
CVsdon't travel through JSON — imported candidates carry their profile text; CVs can be added to records any time

Schieța interfeței pentru

Schemă structurală a interfeței — panouri, ierarhie și posibilități de interacțiune. Un contract, nu o captură de ecran.
ATS-ul dumneavoastră actual
Export CSV / JSON / API
Setări → Export de date sau solicitați asistenței — datele vă aparțin de drept.
→
Contractul JSON eșantion
jobs[]candidates[]applications[]
Numele câmpurilor trebuie să corespundă exact eșantionului; orice altceva în plus este ignorat. Reconfigurați cu un tabel, un mic script sau orice asistent inteligent: „convertește în acest format”.
→
În interiorul Expertini ATS
locuri de muncă → ciorne candidați → bază de talente aplicații → pâlnie, etape mapate
Deduplicat după e-mail · nimic nu se publică fără clic.
Fig. 1 — conducta de migrare: export din sistemul actual, adaptare la contractul JSON eșantion, import cu deduplicare și mapare automată a etapelor.

Flux de interacțiune — stări, validări, feedback

Fiecare stare de mai jos este impusă pe partea de server; interfața o raportează, nu o decide.
Export from LeverCSV/JSON/API export — usually Settings → Data export, or ask support; the data is legally yours
Reshape to the sample JSONspreadsheet save-as-JSON, a small script, or paste both files into an AI assistant: "convert to this format"
Upload & validatefield names must match the sample; anything extra is ignored, errors are named
Dedupe + stage mappingcandidates matched by email; foreign stage names map onto your pipeline automatically
Working pipelinejobs as drafts, talent pool populated, funnel rebuilt — review, then publish
Over the batch cap → split the file; overlapping batches are safe because duplicates skipUnknown stage name → lands in Applied, never lostField name mismatch → named validation error; nothing partial importsJobs import as drafts — nothing is published without your clickCVs can't ride in JSON — attach them to imported records afterwards
Fig. 2 — flux de interacțiune: bleumarin = stări, auriu = porți impuse de server, verde = rezultate confirmate; etichetele listează cazurile limită și feedbackul lor.

01Get your data out of Lever

Export jobs and candidates from Lever — every mainstream ATS offers CSV, JSON, or API export, usually under a Settings → Data export area, and their support team will produce a full export on request if the interface doesn't cover something. You have a legal right to your own data, and data-protection law in most jurisdictions obliges the vendor to hand it over in a usable format. Ask for jobs, candidates, and applications (the links between the two) — three files or one, either works.

02Reshape it to the sample JSON

The importer accepts a simple, documented JSON shape with three arrays: jobs, candidates, and applications. A spreadsheet with a save-as-JSON step works; a small script works; and the fastest path for most teams is pasting their export and our sample file into any AI assistant with the instruction "convert to this format". Field names must match the sample exactly — anything extra is simply ignored, so over-complete exports are fine as-is.

03Upload in safe batches

Upload on the in-app import page. Limits per upload: 500 jobs and 2,000 candidates — split bigger exports into batches. Duplicates are skipped, not duplicated, so overlapping batches are safe and re-running an upload after a fix costs nothing. Validation errors name the exact field rather than failing silently.

04What lands where

Jobs import as drafts with title, description, location, type, category, salary, and experience and education levels — you review and publish on your own schedule. Candidates arrive in the talent pool with name, email, phone, title, location, skills, and notes, deduplicated by email. Applications rebuild your funnel: Lever's stage names — "phone screen", "offered", "onsite", and dozens more — map automatically onto your pipeline stages, and anything unrecognised lands safely in Applied. CVs can't travel through JSON: imported candidates carry their profile text, and CV files can be added to any record afterwards.

Întrebări frecvente

Do I need Lever's permission or help to migrate?⌄
No. You export your own data with the export function every customer has, reshape it to the sample format, and upload. No API keys, no vendor cooperation, no overlap period required.
Will anything go live during the import?⌄
No. Jobs arrive as drafts and are published only when you choose. Candidates and applications are internal records — nothing is emailed to anyone during an import.
What happens to my pipeline stages?⌄
Stage names from other systems map automatically onto your pipeline — "phone screen", "offered", "onsite" and many more are recognised. Unrecognised names land in Applied rather than being lost.
What about CVs?⌄
CV files can't ride inside JSON. Imported candidates carry their profile text (searchable immediately), and you can attach CV files to any record afterwards — individually or via the bulk CV drop.
Is Expertini affiliated with Lever?⌄
No. Lever is a trademark of its owner. This page describes Expertini's own import tool receiving a standard data export that belongs to you.

Pe scurt

  • Jobs, candidates, and the live funnel — all three migrate
  • Jobs arrive as drafts; nothing publishes without your click
  • Candidates deduplicated by email — re-runs are safe
  • Foreign stage names map automatically; unknowns land in Applied
  • 500 jobs / 2,000 candidates per upload — batch bigger exports
  • No vendor cooperation, API keys, or overlap period needed

Lectură conexă

Third-Party ATS ImportMove from Zoho Recruit, Greenhouse, Workable, Lever, iCIMS, JazzHR, Breezy, Manatal, Ceipal, or any other system — jobs, candidates, AND your live funnel, in one structured JSON upload. 🌱Migrate from GreenhouseMoving off Greenhouse? Bring your jobs, your candidates, and your live pipeline — including which stage every application was at — across in one structured upload. Migrate from WorkableLeaving Workable? Move jobs, candidates, and your live hiring funnel into Expertini in one upload — stages mapped, duplicates impossible, nothing published without review.

Vedeți migrate from lever to expertini ats în propriul proces de angajare.

Aduceți o descriere reală a jobului la o demonstrație de 30 de minute — proba gratuită inclusă.

Programați o prezentare
Expertini Intelligent
Online acum
Bună! Sunt expertul în produse inteligente Expertini. Întrebați-mă orice despre soluțiile noastre, primiți îndrumări despre oricare dintre instrumentele noastre de recrutare sau pur și simplu spuneți-mi ce încercați să faceți — vă voi îndruma în direcția corectă. Pentru probleme specifice contului, trimiteți un e-mail la support@expertini.com.
Preferați prin email? Contactați-ne →