Greenhouse to Ashby migration
Shuttio moves departments, offices, jobs, candidates and applications from Greenhouse into Ashby, with notes and files. A full migration is priced by record count, from $199 up to 50,000 records. It starts with a free sample of every object you tick (5 candidates with all their applications and everything attached), so you read the result in Ashby before the full run, and a rollback removes what it created.
- Can I move Greenhouse to Ashby?
- Yes.
- What moves:
- Departments, offices, jobs, candidates and applications, with notes and files.
- What doesn't:
- Known limits in Ashby; What a rollback leaves.
- Price:
- $199 up to 50,000 records, once per migration. The sample is free.
- How long:
- A free sample first, then the full run as one background job with live progress. The time depends on your record count and on Greenhouse's API request limits.
- Moves
- 5 kinds of record, plus notes and files
- Doesn’t move
- 2 things, each with the reason
- Connect
- Greenhouse: Harvest V3 (OAuth) credentials. Ashby: API key
- Price
- From $199. The sample is free
What Shuttio needs from Greenhouse
Shuttio only reads from the source. These are the permissions it asks for, and why.
| What | Why Shuttio needs it |
|---|---|
| Harvest V3 (OAuth) credentials | A Client ID and a Client Secret from Greenhouse, API Credentials, Create new API credentials, Harvest V3 (OAuth). Harvest v1 and v2 API keys stopped working on 31 Aug 2026. Shuttio checks the credentials against Greenhouse before it saves anything, and never writes to Greenhouse. |
| A Site Admin user | Greenhouse's list endpoints need a Site Admin as the authorizing user. By default the calls run as the integration's own user; you can type another user's id instead. |
| The read scopes | harvest:jobs:list, harvest:candidates:list, harvest:applications:list, harvest:notes:list, harvest:interviews:list, harvest:interviewers:list, harvest:job_interviews:list, harvest:offers:list, harvest:scorecards:list, harvest:scorecard_question_answers:list, harvest:scorecard_questions:list, harvest:scorecard_candidate_attributes:list, harvest:job_candidate_attributes:list, harvest:attachments:list, harvest:users:list, harvest:departments:list, harvest:offices:list, harvest:sources:list, harvest:rejection_reasons:list, harvest:job_interview_stages:list, harvest:job_owners:list, harvest:job_hiring_managers:list, harvest:openings:list, harvest:close_reasons:list, harvest:referrers:list, harvest:candidate_educations:list, harvest:candidate_employments:list and harvest:custom_field_options:list. A scope you leave out only leaves that data out, and the run says so. |
| EEOC scopes | harvest:eeoc:list, harvest:demographic_answers:list, harvest:demographic_questions:list and harvest:demographic_answer_options:list. They move the candidates' EEOC and demographic self-identification answers (gender, race or ethnicity, veteran and disability status, other questions) as one note on each application. Greenhouse restricts these scopes; without them the run goes on and says EEOC was not moved. |
Greenhouse allows a limited number of requests per 30 seconds; a large account takes hours, and the run pauses when Greenhouse asks it to slow down until you resume it. The secret is stored encrypted and deleted 14 days after the migration finishes. You can delete the credentials at any time in Greenhouse under API Credentials.
What changes on the way to Ashby
| What | What happens |
|---|---|
| What is read | Candidates are read in pages. For every 50 candidates Shuttio reads their applications, attachments, notes, scorecards, interviews, offers, stage history and EEOC rows, through Greenhouse's v3 API. |
| Files and EEOC answers | Attachments are read as files Shuttio downloads one at a time. EEOC answers are read as structured answers, question by question. |
| Emails | Emails Greenhouse logged on an application are read as notes of that application; Shuttio reads no mailbox. |
| A scope the credentials lack | When the API credentials lack the scope for one kind of data, that kind is left out and the run names the scope to add. Add it and run again. |
Where each Greenhouse object lands
Read from the code that runs the migration. Source column names are shown as the source reports them.
| Greenhouse object | Lands in |
|---|---|
| Jobs | Native: Created as drafts, with their department and location. A job with the same title is used as it is. |
| Candidates | Native: Matched by email, else created. A candidate you already have is linked and left untouched. |
| Applications | Native: With stage history, source, recruiter and rejection reason, and the original dates. |
| Notes | Native: Written as candidate notes, under the original author when Ashby has a user with the same email. |
| Feedback | Native: Written as application feedback, when your account has a shared feedback form with one text field. Without a shared feedback form with one text field: a note on the candidate. |
| Interviews | Note: A note on the candidate, dated at the interview start. Ashby cannot create a past interview. |
| Offers | Note: A note on the candidate with status, dates and fields. Ashby offers need your own offer form. |
| Files | Native: Uploaded as candidate files and resumes. A file the source no longer serves is named in the application's details note. |
| EEO answers | Private note: A private note on the candidate, with every answer including no answer. Ashby has no EEO fields in its API. |
A candidate is matched by email before it is created. A match is linked and left as it is, and a rollback does not remove it. Every source record is remembered, so a re-run or a Retry writes only what is missing.
Your own fields
Custom fields from the source are written in the details note, not as Ashby custom fields.
2 things that don’t move
Each has a reason. You would find them on day two, so they are here on day zero.
Limits of Ashby, the same for every source
Doesn't moveKnown limits in Ashby; What a rollback leaves. Each has its reason in Into Ashby: limits.
How the move runs
- 1
Connect
Choose the source and Ashby on the first step, then connect both. Ashby takes an Ashby API key, made in Ashby under Admin, Integrations, API keys.
- 2
Objects
The next step lists what moves. Nothing is ticked or unticked: a candidate comes with everything attached.
- 3
Sample
Run the sample: 5 candidates with all their applications and everything attached. Open them in Ashby and check.
- 4
Full run
Run the full migration, or roll the sample back.
Greenhouse also moves into
Import2 does not support Clarify or Odoo as a destination.
Price
A full migration into Ashby costs $199 up to 50,000 records and $3,799 up to 5,000,000. You pay once per migration, and the sample is free.
| Records in your source | One-time price |
|---|---|
| Up to 50,000 | $199 |
| Up to 100,000 | $399 |
| Up to 200,000 | $599 |
| Up to 500,000 | $799 |
| Up to 1,000,000 | $1,199 |
| Up to 5,000,000 | $3,799 |
| Over 5,000,000 | Email help@shuttio.com |
- Each candidate counts once, with everything attached to it: applications, notes, files and the rest. The count is shown before you pay.
- Filters do not lower the price: it counts everything in your source. You see your band before the full run starts and pay at Stripe Checkout; nothing is charged before that.
Greenhouse to Ashby with Shuttio or by hand
Against a manual CSV export: a CSV is one object per file and a record export has no notes, tasks or meetings in it, so a deal's company is a column you match by hand and its notes, tasks and meetings are not in the file. Shuttio reads Greenhouse through its API, creates records first and links them second, matches records already in Ashby instead of duplicating them, and lists every record's outcome.
Questions
How much does a Greenhouse to Ashby migration cost?
A full migration into Ashby costs $199 up to 50,000 records and $3,799 up to 5,000,000. You pay once per migration, and the sample is free. Filters do not lower the price: it counts everything in your source. You see your band before the full run starts and pay at Stripe Checkout; nothing is charged before that.
What does the free sample move?
5 candidates with all their applications and everything attached, with the notes, feedback, interviews, offers, files and EEO answers attached to them. It is a real write into Ashby, so it can be rolled back.
What does not move from Greenhouse to Ashby?
Known limits in Ashby; What a rollback leaves. Each has a reason on this page.
Can I undo the migration?
Yes, as far as Ashby's API allows. Applications are deleted. Candidates the migration created are anonymized: Ashby's API cannot delete a candidate. Candidates you already had are not touched. Jobs, tags, departments and locations the migration created are archived. Notes, files and feedback have no delete in Ashby's API. They stay on the anonymized candidates.
Does it change anything in Greenhouse, and what about records created while I migrate?
Shuttio only reads from Greenhouse. It never writes to it.
Do I set anything up in Ashby before the move?
Yes. Create the interview stages the source uses in the job's Ashby interview plan, and an Archived and a Hired stage. Create the archive reasons the source uses (Admin, Archive reasons). Create the sources you want matched (Ashby's API cannot create a source; a missing one is named in the application's details note). A row that needs one of these fails with a sentence that names what to create; create it, then Retry, and only the missing parts are written.
Move Greenhouse to Ashby in a free sample first.
Nothing is written to your new CRM until you have reviewed the objects and fields, and every CRM migration starts as a free sample: 5% of your companies, contacts or deals, 10 to 1,000 records, picked at random, with their linked records.