Migrate from JazzHR to Expertini ATS
INTEGRATIONS · EXPERTINI ATS

Migrate from JazzHR to Expertini ATS

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

3 dakika za kusoma · Imesasishwa Julai 2026 · Uhariri wa Expertini

Leaving an ATS feels riskier than it is. Your data in JazzHR 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 JazzHR is a well-trodden one, not a special case.

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

Kwenye ukurasa huu

  1. Get your data out of JazzHR
  2. Reshape it to the sample JSON
  3. Upload in safe batches
  4. What lands where
  5. Mchoro wa kiolesura na mtiririko wa mwingiliano
  6. Maswali yanayoulizwa mara kwa mara

Unatoka mfumo gani?

Andika ili kutafuta — kuchagua mteja hufungua mwongozo maalum wa uhamiaji kwa ajili yake. Kila njia inafika kwenye kigeuzi kile kile, kikiwa na mipaka ya kundi ile ile ya uaminifu na kanuni za kuzuia marudio.

Ramani ya utegemezi ya — nini kinaletwa, haswa

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

Mchoro wa kiolesura cha

Mchoro wa kimuundo wa uso — paneli, uongozi, na uwezo wa mwingiliano. Mkataba, sio picha ya skrini.
ATS yako ya sasa
Hamisho la CSV / JSON / API
Mipohio → Usafirishaji wa data, au uliza msaada — data ni mali yako kisheria.
→
Mkataba wa sampuli ya JSON
jobs[]candidates[]applications[]
Majina ya nyanja lazima yalingane na mfano haswa; chochote cha ziada kinapuuzwa. Badilisha umbo na lahajedwali, hati ndogo, au msaidizi yeyote wa AI: “badilisha kwenda muundo huu”.
→
Ndani ya Expertini ATS
kazi → rasimu wagombea → bwawa la talanta maombi → faneli, hatua zilizopangwa
Imetolewa nakala rudufu kwa barua pepe · hakuna kinachochapishwa bila kubofya kwako.
Mchoro 1 — bomba la uhamiaji: hamisha kutoka kwa mfumo wako wa sasa, rekebisha kulingana na mkataba wa sampuli ya JSON, leta na uondoaji wa marudio na uchoraji wa ramani wa hatua otomatiki.

Mtiririko wa mwingiliano wa — hali, uthibitishaji, maoni

Kila hali iliyo hapa chini inatekelezwa upande wa seva; kiolesura kinaripoti, hakiamui.
Export from JazzHRCSV/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
Mchoro 2 — mtiririko wa mwingiliano: bluu ya bahari = majimbo, dhahabu = milango inayotekelezwa na seva, kijani = matokeo yaliyothibitishwa; lebo zinaorodhesha visa maalum na maoni yake.

01Get your data out of JazzHR

Export jobs and candidates from JazzHR — 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: JazzHR'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.

Maswali yanayoulizwa mara kwa mara

Do I need JazzHR'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 JazzHR?⌄
No. JazzHR is a trademark of its owner. This page describes Expertini's own import tool receiving a standard data export that belongs to you.

Kwa mtazamo wa haraka

  • 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

Usomaji unaohusiana

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.

Tazama migrate from jazzhr to expertini ats kwenye uajiri wako mwenyewe.

Leta maelezo halisi ya kazi kwenye onyesho la dakika 30 — jaribio la bure limejumuishwa.

Weka miadi ya onyesho
Expertini Intelligent
Mtandaoni sasa
Habari! Mimi ni Mtaalamu wa Bidhaa za Akili Bandia wa Expertini. Niulize chochote kuhusu suluhu z我们的, pata mwongozo kuhusu Zana zetu zozote za Kuajiri, au niambie tu unachojaribu kufanya — nitakuonyesha mwelekeo sahihi. Kwa masuala mahususi ya akaunti, tuma barua pepe kwa support@expertini.com.
Unapenda barua pepe? Wasiliana nasi →