Migrate from Greenhouse
INTEGRATIONS · EXPERTINI ATS

Migrate from Greenhouse

Moving off Greenhouse? Bring your jobs, your candidates, and your live pipeline — including which stage every application was at — across in one structured upload.

3 min leestijd · Bijgewerkt juli 2026 · Expertini Editorial

Greenhouse is a capable enterprise ATS, and teams that leave it usually do so over cost and complexity, not capability. What keeps them from moving is the data: years of jobs, thousands of sourced candidates, and — the part every migration tool ignores — the live funnel, who is at phone screen, who is at offer. Expertini's Third-Party ATS Import moves all three: jobs arrive as reviewable drafts, candidates join a searchable talent pool, and applications re-attach each candidate to their job at the stage they were at, with common Greenhouse stage names mapped onto your pipeline automatically.

The migration is self-serve and honest about what it is: Greenhouse lets you export your own data (it's your legal right), you reshape that export to our documented JSON sample — a spreadsheet exercise or a ten-minute script — and upload. No migration consultants, no per-record fees, no quarter-long project plan. Greenhouse is a trademark of its owner; this page describes moving your own data out of your own account, which no vendor can gatekeep.

Van welk systeem stapt u over?

Typ om te zoeken — het selecteren van een leverancier opent de speciale migratiehandleiding ervoor. Elk pad leidt naar dezelfde importfunctie, met dezelfde eerlijke batchlimieten en regels voor ontdubbeling.

Afhankelijkheidskaart — wat er precies wordt geïmporteerd

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

Interface-blauwdruk

Structureel schema van de interface — panelen, hiërarchie en interactiemogelijkheden. Een contract, geen screenshot.
Uw huidige ATS
CSV- / JSON- / API-export
Instellingen → Gegevensexport, of vraag ondersteuning — de gegevens zijn juridisch van u.
Het voorbeeld-JSON-contract
jobs[]candidates[]applications[]
Veldnamen moeten exact overeenkomen met het voorbeeld; al het overige wordt genegeerd. Pas het aan met een spreadsheet, een klein script of een intelligente assistent: “converteer naar dit formaat”.
Binnen Expertini ATS
vacatures → concepten kandidaten → talentpool sollicitaties → funnel, fasen toegewezen
Ontdubbeld op e-mail · niets wordt gepubliceerd zonder uw klik.
Fig. 1 — het migratieproces: exporteren vanuit uw huidige systeem, omvormen naar het JSON-voorbeeldcontract, importeren met ontdubbeling en automatische fasekoppeling.

Interactiestroom — statussen, validaties, feedback

Elke onderstaande status wordt aan de serverzijde afgedwongen; de interface rapporteert deze alleen en bepaalt deze niet.
Export from GreenhouseCSV/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 — interactiestroom: marineblauw = statussen, goud = door de server afgedwongen poorten, groen = bevestigde resultaten; tags tonen de randgevallen en hun feedback.

01What comes across, piece by piece

Jobs: title, description, location, employment type, salary data, experience and education levels — landing as drafts so nothing goes live before you review it. Candidates: name, email, phone, title, location, skills, and notes, deduplicated by email into the talent pool where CV parsing and search make them findable again. Applications: the funnel itself — candidate, job, stage, and application date — so your pipeline view on day one in Expertini looks like your pipeline view on the last day in Greenhouse, not an empty board.

02How stage names translate

Greenhouse workspaces name stages freely — "Phone Screen", "Onsite", "Offer", "Take-Home". The importer maps roughly forty common stage vocabularies onto Expertini's pipeline stages automatically (phone screen → screening, onsite → interview, offered → offer, and so on), and anything unrecognised lands safely in Applied rather than failing the row. You can move any application afterwards — the point is that nobody starts from zero.

03How to run it, step by step

One: export from Greenhouse — jobs and candidates via its own export tools or a data request. Two: download our sample JSON from the import page and reshape your export to match it; the sample shows all three arrays (jobs, candidates, applications) with every field named. Three: upload. You get a per-row report — imported, duplicate, invalid, and why — and re-uploading never creates duplicates, so batching a large migration is safe. Most teams finish in an afternoon.

04After the move

Imported candidates flow into the same candidate database as new applicants — searchable, taggable, scoreable with resume scoring against your open roles. Publishing your reviewed draft jobs distributes them across Expertini's network at no per-posting fee, and your team picks up the funnel exactly where Greenhouse left off.

Veelgestelde vragen

Can I really export my data from Greenhouse?
Yes — your data is yours, and Greenhouse provides export paths. If your plan gates a full export, their support must still hand over your data; the reshape-to-JSON step is the same either way.
Does the funnel really come across?
Yes — the applications array links each candidate (by email) to a job (by your old system's job id) at a stage, and stage names map onto Expertini's pipeline automatically. Unrecognised names land in Applied rather than erroring.
What about CVs?
CV files can't travel through JSON, but candidates arrive with their profile text, and CVs can be attached any time — including in bulk from a Dropbox or OneDrive folder via the cloud CV import.
What does the migration cost?
Nothing beyond the subscription — the importer is included on every plan, with no per-record fees. See pricing.

In één oogopslag

  • Jobs, candidates, AND the live funnel — stages preserved
  • Greenhouse stage names auto-mapped onto your pipeline
  • Jobs arrive as drafts — nothing publishes without review
  • Candidates deduplicated by email into a searchable talent pool
  • Per-row import report; re-uploads never duplicate
  • Self-serve, one afternoon, no migration fees

Bekijk migrate from greenhouse op uw eigen wervingsproces.

Breng een echte vacaturetekst mee naar een demo van 30 minuten — inclusief gratis proefperiode.

Boek een demo
Expertini Intelligentie
Nu online
Hallo! Ik ben Expertini's intelligente productexpert. Stel me gerust alle vragen over onze oplossingen, krijg begeleiding bij elk van onze Hiring Tools, of vertel me gewoon wat u wilt doen — ik wijs u de juiste richting op. Voor accountspecifieke kwesties kunt u mailen naar support@expertini.com.