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 perc olvasás · Frissítve: July 2026 · Expertini Editorial

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.

Melyik rendszerről vált?

Gépeljen a kereséshez — a szolgáltató kiválasztásakor megnyílik a hozzá tartozó migrálási útmutató. Minden útvonal ugyanahhoz az importálóhoz vezet, ugyanazokkal az átlátható kötegelt korlátokkal és duplikátumszűrési szabályokkal.

függőségi térkép — mi importálódik pontosan

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

Felület-tervrajz

A felület strukturális vázlata — panelek, hierarchia és interakciós lehetőségek. Egy megállapodás, nem képernyőkép.
Az Ön jelenlegi ATS-e
CSV / JSON / API exportálás
Beállítások → Adatexportálás, vagy kérdezze ügyfélszolgálatunkat — az adatok jogilag az Ön tulajdonát képezik.
A minta JSON-szerződés
jobs[]candidates[]applications[]
A mezőneveknek pontosan meg kell egyezniük a mintával; minden felesleges adat figyelmen kívül marad. Alakítsa át táblázatkezelővel, egy kis szkripttel vagy bármilyen intelligens asszisztenssel: „alakítsd át erre a formátumra”.
A(z) Expertini ATS rendszeren belül
állások → vázlatok jelöltek → tehetségbázis jelentkezések → tölcsér, szakaszok leképezve
E-mail alapján kiszűrt duplikációk · semmi sem kerül közzétételre az Ön jóváhagyása nélkül.
1. ábra — az áttelepítési folyamat: exportálás a jelenlegi rendszerből, átalakítás a minta JSON-szerződésnek megfelelően, importálás deduplikációval és automatikus szakasz-hozzárendeléssel.

Interakciós folyamat — állapotok, érvényesítések, visszajelzés

Az alábbi állapotok mindegyike szerveroldalon érvényesül; a felület csak jelzi, nem dönt róla.
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
2. ábra — interakciós folyamat: tengerészkék = állapotok, arany = szerveroldalon kikényszerített kapuk, zöld = megerősített kimenetelek; a címkék a határeseteket és azok visszajelzéseit sorolják fel.

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.

Gyakran ismételt kérdések

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.

Áttekintés

  • 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

Tekintse meg ezt a saját toborzásában: migrate from lever to expertini ats.

Hozzon magával egy valós munkaköri leírást egy 30 perces bemutatóra — ingyenes próbaidőszakkal.

Demó kérése
Expertini Intelligencia
Jelenleg online
Üdvözlöm! Az Expertini intelligens termékszakértője vagyok. Kérdezzen bátran megoldásainkról, kérjen útmutatást toborzási eszközeinkkel kapcsolatban, vagy egyszerűen írja meg, mit szeretne elérni — szívesen segítek a megfelelő irányba terelni. Fiókspecifikus problémák esetén írjon a(z) support@expertini.com címre.