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분 · 2026년 7월 업데이트됨 · 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.

어떤 시스템에서 이전하시나요?

검색어를 입력하세요. 벤더를 선택하면 전용 마이그레이션 가이드가 열립니다. 모든 경로는 동일한 가져오기 도구로 연결되며, 동일하고 투명한 일괄 처리 한도 및 중복 제거 규칙이 적용됩니다.

종속성 맵 — 정확히 어떤 항목이 가져와지는지

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

인터페이스 청사진

서피스의 구조적 도식 — 패널, 계층 구조 및 인터랙션 어포던스입니다. 단순한 스크린샷이 아닌 명세입니다.

현재 사용 중인 ATS

CSV / JSON / API 내보내기

설정 → 데이터 내보내기를 이용하거나 지원팀에 문의하세요 — 데이터의 법적 소유권은 귀하에게 있습니다.

→

샘플 JSON 계약

jobs[]candidates[]applications[]

필드 이름은 샘플과 정확히 일치해야 하며, 추가 항목은 무시됩니다. 스프레드시트, 간단한 스크립트 또는 지능형 어시스턴트에 “이 형식으로 변환해 줘”라고 요청하여 데이터를 재구성하십시오.

→

Expertini ATS 내부

채용 공고 → 임시 저장 후보자 → 인재 풀 지원서 → 퍼널, 단계 매핑됨

이메일 기준 중복 제거 · 직접 클릭하기 전에는 아무것도 게시되지 않습니다.

그림 1 — 마이그레이션 파이프라인: 현재 시스템에서 내보내기, 샘플 JSON 규격에 맞게 재구성, 중복 제거 및 자동 단계 매핑과 함께 가져오기.

상호작용 흐름 — 상태, 유효성 검사, 피드백

아래의 모든 상태는 서버 측에서 적용됩니다. 인터페이스는 이를 보고할 뿐 직접 결정하지 않습니다.

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

그림 2 — 상호작용 흐름: 남색 = 상태, 금색 = 서버 적용 게이트, 녹색 = 확인된 결과; 태그는 엣지 케이스와 해당 피드백을 나타냅니다.

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.

자주 묻는 질문

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.

한눈에 보기

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

실제 채용에서 migrate from greenhouse을(를) 확인해 보세요.

실제 직무 기술서를 지참하여 30분 데모에 참여해 보세요. 무료 체험판이 포함되어 있습니다.

데모 예약