Migrate from Recruitee: what moves, API key, limits
What Shuttio reads from Recruitee, where it lands in Ashby, Lever, Greenhouse, which permissions it needs and why, and what does not move.
Last updated: 20 November 2026
Shuttio connects to Recruitee with your company id and a personal API token. You make the token in Recruitee under Settings, Apps and plugins, Personal API tokens. The company id is the number in https://api.recruitee.com/c/<number>, or your subdomain (the part before .recruitee.com).
Object by object: What objects are supported for Recruitee migrations.
What Shuttio reads and moves
- Offers: Recruitee calls a job an offer. Published and internal offers arrive as open, draft, closed and archived ones as they are, each with its description, requirements, department, locations and the stages of its pipeline. An internal offer is marked in the details.
- Admins, departments, locations, sources and disqualification reasons (Recruitee's disqualify reasons): the reference lists. Admins and guests are the people who author notes and evaluations.
- Candidates: read from Recruitee's candidate search, oldest first. A deleted candidate is skipped.
- Placements: a placement is a candidate on one offer, in one stage. Shuttio makes one application per placement, with its stage, disqualification (reason, kind, who, date), hire date, job start date and time to hire.
- Activity: the candidate's activity stream gives the dated stage history for each offer. Every other entry of the stream, stage moves included, is listed in one dated Activity note on the first placement. A candidate with no placement has no Activity note.
- Notes: with their replies, written by admins or guests. A note whose visibility is not public stays private. A note tied to no offer goes on the first placement.
- Evaluations: Recruitee's interview results become feedback, with the form name, the rating, the score on its scale, the notes, the scorecard answers and the stage.
- Interview events: kind, start, an end taken from the duration, video link and each attendee's response.
- Offer letters: status, sent date, details and salary, on the application of their own offer.
- Files: the CV, the cover letter file and attachments. Candidate-level files stay on the candidate, files tied to an offer go on that offer's application, and a CV that is also an attachment is read once.
Where each thing lands
| Recruitee object | In Ashby | In Lever | In Greenhouse |
|---|---|---|---|
| Candidates | Its own object, or the one you already have with that name | Its own object, or the one you already have with that name | Its own object, or the one you already have with that name |
Notes, tasks, meetings, calls, files, owners and lists depend on the destination. This is the row for Recruitee, generated from the same tables the runner uses:
Into Ashby
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Recruitee | Candidates | Yes | No | No | No | No | Yes | Yes | No |
Into Lever
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Recruitee | Candidates | Yes | No | No | No | No | Yes | Yes | No |
Into Greenhouse
| From | Objects | Notes | Tasks | Meetings | Calls | Emails | Files | Owners | Lists |
|---|---|---|---|---|---|---|---|---|---|
| Recruitee | Candidates | Yes | No | No | No | No | Yes | Yes | No |
In Ashby, Lever and Greenhouse, notes and files move with the candidate; interviews and offers are written as notes, offers as private notes.
Each destination's own article says how its data is written: Ashby, Lever, Greenhouse.
The API key and why
| What | Why Shuttio needs it |
|---|---|
| Company id | The number in the API address, or the subdomain. Every API request goes to api.recruitee.com under that company's path. Shuttio accepts a pasted address and reduces it. |
| A personal API token | A token belongs to one user in one company and carries that user's permissions, so Shuttio reads only what that user can see. Recruitee's docs show no self-serve OAuth flow for this API, so a pasted token is the only way to connect. |
| A user whose role sees candidates and jobs | Shuttio reads one candidate and one offer before it saves the token, and refuses a token that cannot read both. |
A personal token carries the permissions of the user who made it, so make it as a user who can see every candidate you want moved. Shuttio sends the token only to Recruitee's own addresses (api.recruitee.com and file links on recruitee.com); file links on other storage hosts are fetched without it.
What Recruitee's API does not give
- Hidden identities: when Recruitee hides a candidate's identity from the token (unbiased hiring), the name and email arrive masked, and the application's details say so.
- Hidden evaluations: evaluations that Recruitee hides from the token (fair evaluations) are not moved. The details give how many.
- EEO answers: the API gives only whether a placement has EEO data, so no answers move. The details name the status and mark it not moved.
- Email conversations: not read.
- A candidate with no placement: the notes go into the candidate's profile. Interview events, evaluations and offer letters need a placement, and without one they are not moved; the profile says how many.
- Shapes the reference does not show: activities, custom fields, open-question answers and education are read tolerantly. A stage move that Shuttio does not recognise stays in the dated Activity note, not in the stage history.
- Files: a file over 30 MB is not copied.
Known limits
- Rate limit: Recruitee allows 1,000 requests a minute per token. Shuttio sends one every 80 ms, about 750 a minute. On a 429 it waits for Retry-After, and the run pauses if 429 keeps coming.
- Time: Shuttio makes about nine requests per candidate, so a large account takes hours, and the run pauses when Recruitee asks it to slow down.
Not answered here? Email help@shuttio.com.