What objects are supported for Workable migrations
What Shuttio moves out of Workable: job (shortcode), candidate, activity, event, offer, requisition and more. The table shows what each Workable object becomes.
Last updated: 20 November 2026
Shuttio moves data out of Workable. It does not write into Workable. Out of Workable, data goes into Ashby, Lever, Greenhouse.
What Workable calls each object
| In Workable | What Shuttio moves | Note |
|---|---|---|
| Job (shortcode) | Jobs | All four states. Closed means a job used internally or confidentially. |
| Candidate | Candidates and one application each | One Workable candidate is one job. The same person on two jobs is two candidates in Workable and one candidate in the destination, matched by email. |
| Activity | Stage history, notes, feedback | Comment is a note, message is an email note, rating is feedback, the rest is one dated note. An entry the standard role cannot read stays private. |
| Event | Interviews | Cancelled events are read and marked canceled. |
| Offer | Offers | Read only for a candidate whose activity or stage shows an offer. Offer documents move as files. |
| Requisition | Job details and fields | Needs the r_requisitions scope and a Hiring Plan. |
| Member and recruiter | Users | Used to credit authors and panels; matched by email. |
| EEO answers, talent pool | Not moved | Workable's API reference has no endpoint for either. |
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 Workable.
← What objects are supported for Lever migrationsWhat objects are supported for Recruitee migrations →
Not answered here? Email help@shuttio.com.