Migrate
Bring your hiring history with you.
Export from wherever you run recruiting today, map the columns once, and your candidates and jobs land in your own Postgres instance. No sync, no ongoing dependency on your old ATS.
How the import works.
01 / Export from your current ATS
Every ATS in this list supports a CSV export of candidates and jobs, and most also expose a REST API you can pull from directly. Either path works.
02 / Map the columns once
Harly's importer reads your CSV headers and lets you map them to Harly's fields (name, email, stage, job, resume link, tags). Save the mapping and reuse it for later batches.
03 / Review before you commit
The importer shows a preview of every row before writing anything, so you catch a bad column mapping before it touches your database.
04 / It's in your own Postgres
Once imported, candidate and job data lives in the Postgres instance you control. Nothing stays synced to your old ATS, and nothing routes through a third party.
Migrating from a specific ATS.
Export candidates and jobs as CSV from your account's reports panel, then re-import into Harly.
Compare Harly vs Workable
Pull candidate and job data through the Harvest API, or export a CSV from your admin reports, then map the columns into Harly.
Compare Harly vs Greenhouse
Export candidates as CSV, or call Ashby's public API directly, then bring the data into Harly the same way.
Compare Harly vs AshbyPull candidate and job records through Lever's REST API, or export a CSV from your account settings, then import into Harly.
Compare Harly vs LeverComing from something else? If it can export a CSV or exposes a REST API, the same two import paths below work regardless of which vendor you're leaving.
CSV importer
Upload a CSV of candidates or jobs from Settings, map each column to a Harly field, preview the rows, and commit. Save the mapping so the next batch takes one click instead of a full remap.
REST API
/v1/candidates,/v1/jobs, and/v1/applicationsaccept the same fields the CSV importer does. Script a one-off pull from your old ATS's API and push it straight in, no export file required.
FAQ
Before you migrate.
Will I lose interview notes or scorecards during migration?
That depends on what your current ATS lets you export. Most CSV exports cover candidates, jobs, and stage history; structured interview scorecards are less commonly included in a standard export. Check your source ATS's export or API docs for exactly which fields it exposes before you migrate.
Do I need to migrate everything at once?
No. The importer accepts as many CSV batches as you want to run, and the column mapping you save is reused for the next one. Migrate open roles first, then backfill historical candidates on your own schedule.
What if my current ATS doesn't have a clean CSV export?
Use the REST API instead. Harly's own API (/v1/candidates, /v1/jobs, /v1/applications) accepts the same fields a CSV import does, so anything you can pull programmatically from your old ATS can be pushed into Harly with a short script.
Does the import work for a job board's SEO history too?
No. A new Harly deployment gets fresh job board URLs. Set up redirects from your old job posting URLs to the matching Harly listings if search ranking on specific postings matters to you.
Ready when you are