INTEGRATIONS · EXPERTINI ATS

Third-Party ATS Import

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

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

Switching applicant tracking systems usually stalls on one question: what happens to everything already in the old one? The Third-Party ATS Import app answers it with a deliberately simple contract. Download our sample JSON, reshape the export from your current system — Zoho Recruit, BambooHR, Greenhouse, Workable, Manatal, Ceipal, JazzHR, Breezy HR, Lever, iCIMS, or anything else that can export data — to match it, and upload. Jobs arrive as drafts you review before publishing; candidates join your talent pool with their details intact; and the applications array rebuilds your funnel, re-attaching each candidate to their job at the stage they were at.

The gap this closes is losing your pipeline history at the exact moment you are trying to improve it. A recruiter who abandons two years of sourced candidates starts the new system from zero. With the import, that accumulated talent pool becomes searchable from day one, feeds directly into talent sourcing workflows, and your open roles arrive with their applicants already in stages. The importer is a native part of Expertini ATS — one subscription, no migration consultants, no per-record fees.

Kwenye ukurasa huu

A format any system can produce
Drafts first, so nothing goes live by accident
The funnel moves too — stages mapped automatically
From upload to a working pipeline
Mchoro wa kiolesura na mtiririko wa mwingiliano
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 your current ATSCSV/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.

01A format any system can produce

Rather than maintaining brittle one-off connectors for every vendor's export quirks, the app publishes one documented JSON shape with a downloadable sample. Every mainstream ATS can export jobs and candidates as CSV or JSON; reshaping that export to the sample structure is a straightforward transform in a spreadsheet or a short script.

Because the format is open and documented, it also works for systems the registry never anticipated — an in-house tool, a shared spreadsheet, or a legacy database. If you can get your data out, you can get it in.

02Drafts first, so nothing goes live by accident

Imported jobs land as drafts, not published listings. That gives you a review step: fix titles, attach the right pipeline stages, add screening questions, and publish on your own schedule. Candidates are added to the talent pool; if your upload includes the applications array, each one is also placed into their job's pipeline at the imported stage — and any placement is yours to adjust afterwards.

03The funnel moves too — stages mapped automatically

The applications array is what makes this a migration rather than a copy: each row links a candidate (by email) to a job (by your old system's job id) at a stage, with the application date preserved. Other systems name stages freely — "phone screen", "onsite", "offered", "shortlisted" — so the importer maps roughly forty common stage vocabularies onto your Expertini pipeline automatically, and anything it doesn't recognise lands safely in Applied instead of failing the row. Day one in the new system looks like the last day in the old one.

04From upload to a working pipeline

After the upload you get a clear result: what was created, what was skipped, and why — for jobs, candidates, and applications separately. Publish your reviewed drafts individually or push a batch out with bulk job posting, then invite your team and pick up hiring where the old system left off. Most migrations are a single afternoon, not a quarter-long project.

Maswali yanayoulizwa mara kwa mara

Which systems can I migrate from?⌄

Any system that can export its data. Zoho Recruit, BambooHR, Greenhouse, Workable, Manatal, Ceipal, JazzHR, Breezy HR, Lever, and iCIMS are common starting points, but the importer accepts one documented JSON format, so any export you can reshape to the sample will work.

Does my hiring funnel come across?⌄

Yes — the applications array carries candidate email, job reference, stage, and applied date. Stage names from other systems map automatically onto your pipeline; unrecognised ones land in Applied rather than erroring.

Why do imported jobs arrive as drafts?⌄

So nothing goes live without your review. You check each job, adjust stages and screening questions, and publish deliberately — avoiding accidental duplicate live listings during the cut-over.

What candidate data comes across?⌄

Candidate details as provided in your export join your organisation's talent pool, where they are searchable and can be added to live pipelines. You control the fields by what you include in the JSON.

Does the import cost extra?⌄

No. It is included in every plan — sign up and run it yourself, with no per-record charges or paid migration service.

Kwa mtazamo wa haraka

One documented JSON format with a downloadable sample
Works with exports from any ATS or spreadsheet
Jobs arrive as reviewable drafts, not live posts
Candidates join a searchable talent pool
Applications rebuild your funnel — stages auto-mapped
Clear per-row report; re-uploads never duplicate
No per-record fees or migration consultants

Usomaji unaohusiana

Expertini Job Site ImportBring your whole Expertini job site account into the ATS — company profile, live listings, applications, candidates and their CVs, reviews, candidate alerts and followed candidates. Listings are adopted, never duplicated. 🌱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. Data ExportDownload everything your organisation owns as one structured JSON file, any time. No lock-in.

Tazama third-party ats import kwenye uajiri wako mwenyewe.

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

Weka miadi ya onyesho