Into Ashby
What Shuttio writes into Ashby, where each part of a candidate's record lands, what to set up first, and what a rollback leaves.
Last updated: 7 Nov 2026
Sources that can move into Ashby: Greenhouse, Lever, Workable, Recruitee, SmartRecruiters, Teamtailor. A migration is free under 5,000 records in total: contacts, companies, deals, notes, activities and files together; otherwise it is priced by the number of candidates. The sample is free. See pricing.
Object by object: What objects are supported for Ashby migrations.
How the move runs
- 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.
- The next step lists what moves. Nothing is ticked or unticked: a candidate comes with everything attached.
- Run the sample: 5 candidates with all their applications and everything attached. Open them in Ashby and check.
- Run the full migration, or roll the sample back.
Where each thing lands
| Part of the record | How | In Ashby |
|---|---|---|
| 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. |
Native means a field or object of the destination holds it. Note means the destination has no place for it, so Shuttio writes it as text in a note, with the original date and author in the text. Nothing the source holds is dropped.
Set up first
- 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: only the missing parts are written.
Matching and re-runs
- 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.
Known limits
- Ashby's API has no setting for a job's open date, status or requisition id. They are written in the application's details note.
- Custom fields from the source are written in the details note, not as Ashby custom fields.
- Original authors need the key's "Allow acting on behalf of a user" permission. Without it, each note starts with the author's name and email.
Rollback
- 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.
How rollback works: Roll back.
Not answered here? Email help@shuttio.com.