Migrate your Recruitee data

Jobs are the primary organizational unit in Recruitee's data model. We migrate job records including title, department, location, and status. The Start plan's 5 active job post limit is a migration scoping constraint we account for when prioritizing which jobs to import first.

Candidates are the core person records. We preserve name, email, phone, social profiles, CV/resume files, and source attribution. Custom candidate properties map directly unless the field name conflicts with a standard field in the destination system.

Applications link a Candidate to a Job with a specific stage and timestamp. We preserve this relationship and the application creation date, which is critical for rebuilding pipeline velocity analytics in the destination ATS.

Recruitee's pipeline stages are customizable per Job, meaning the same stage name can exist with different order or criteria across jobs. We extract stage configurations per pipeline and map them to the destination's stage model, flagging any that require custom stage creation.

Scorecards contain structured ratings, interviewer identity, and free-text comments. Recruitee's scorecard schema uses attribute-level ratings that vary by organization. We serialize scorecards as structured notes attached to the application, preserving attribute, rating, and interviewer in a parseable format.

Talent pools are organized candidate collections used for future roles. We migrate pool membership including the candidate ID and pool name. Pool-level notes and tags attached to the pool itself are included in the export.

Offer records include status, salary details, start date, and candidate linkage. We preserve the offer-to-candidate relationship and status history so offer analytics can be rebuilt in the destination system.

Custom fields on Candidates, Jobs, and Applications require field-level mapping to the destination schema. We extract the full custom field list via the API and map each to the target system's equivalent or create custom fields where no standard match exists.

File attachments (resumes, cover letters, portfolio items) are stored in Recruitee's document store. We export them and re-upload to the destination, using filename and candidate ID to establish linkage. Large file attachments may require chunked transfer for stability.

Workflow automations define triggers, conditions, and actions that run inside Recruitee. These are platform-native constructs that cannot be exported as portable data. We document the automation logic so teams can manually rebuild equivalent rules in the destination system.

User records include name, email, role, and department assignment. We map users to the destination system, though role terminology differs. Admin, Recruiter, and Hiring Manager roles in Recruitee map to equivalents in most destination ATS platforms.

Departments are organizational units used to classify jobs and team members. We migrate department records and preserve the job-to-department linkage so reporting by department is consistent after migration.

Notes are free-text entries attached to candidate profiles. Activity history includes stage changes, emails sent, and interview events. We export notes with timestamp and author attribution; the destination must support a notes field or equivalent activity log structure.