What objects are supported for Teamtailor migrations
What Shuttio moves out of Teamtailor: job, candidate, job application, movement, note and more. The table shows what each Teamtailor object becomes.
Last updated: 20 November 2026
Shuttio moves data out of Teamtailor. It does not write into Teamtailor. Out of Teamtailor, data goes into Ashby, Lever, Greenhouse.
What Teamtailor calls each object
| In Teamtailor | What Shuttio moves | Note |
|---|---|---|
| Job | Jobs | Every state. Listing all states needs an Internal or Admin key. |
| Candidate | Candidates | One email per candidate. All applications of a candidate come together. |
| Job application | Applications | Hired when its stage is of the hired type. |
| Movement | Stage history | Without movements, the history is the current stage at the date it was entered. |
| Note | Notes and feedback | A rated note becomes feedback. A private note stays private. |
| Interview and scorecard | Feedback | Read as feedback, with no scheduled time. One with no note and no scores is skipped. |
| Job offer | Offers | The latest offer of an application; earlier offers of the same application are not moved. |
| Answers and form answers | Answers | Go on the latest application, because they belong to the candidate. |
| EEO answers, emails, todos | Not moved | The API reference has no endpoint to read EEO answers or sent emails. |
In Ashby, Lever and Greenhouse, notes and files move with the candidate; interviews and offers are written as notes, offers as private notes.
For the permissions Shuttio needs and what does not move, see reading from Teamtailor.
← What objects are supported for SmartRecruiters migrationsWhat objects are supported for Close migrations →
Not answered here? Email help@shuttio.com.