Migrate your SmartRecruiters data

Postings are the primary top-level object in SmartRecruiters. Each Posting has a UUID, refNumber, location, department, function, experienceLevel, and typeOfEmployment. The Posting API exposes all published jobs as snapshots. We migrate postings 1:1 and preserve internal job IDs as cross-references for downstream candidate mapping.

Candidate is the core person record. The Candidate API supports import, export, read, and update operations. Required fields are firstName, lastName, and email. We map candidate history, tags, social profiles, and resume attachments. Consent decisions (GDPR) are carried over as structured fields at import time.

Applications link Candidates to Postings and represent a candidate's progression through pipeline stages. The Application API allows submission of new applications with screening answers and internal/external flags. We preserve stage history, rejection reasons, and source attribution during migration.

Custom fields are organization-scoped and use a fieldId/valueId/valueLabel structure. Their field definitions are fetched via the /configuration endpoint, and the values returned in candidate and posting responses. Since each organization defines its own custom field set, we always run a pre-migration field discovery pass to enumerate all fieldLabel and valueLabel pairs before mapping values to the destination schema.

Users represent hiring managers, recruiters, and admins. The User API enables extract and import of user data. User IDs and role assignments must be mapped to corresponding owner records in the destination ATS, as role terminology differs across platforms (e.g., Recruiter vs. Owner vs. Hiring Manager).

Departments are referenced by ID and label on Job Postings. The department object includes a description field. When migrating, we preserve the department hierarchy so job postings land in the correct organizational units in the destination system.

Hiring teams are assigned per job and include user IDs with roles. We map team assignments and preserve role-based access so the correct recruiters and hiring managers retain visibility over migrated jobs.

Scorecards capture structured evaluation data for candidates post-interview. The schema is not a standalone object returned by a dedicated endpoint but is embedded within candidate/evaluation records. We extract all scorecard fields and map them to equivalent custom fields or evaluation objects in the destination ATS.

Interview data includes scheduling information, interviewer assignments, and outcome notes. We map interview dates, interviewer names, and overall dispositions. When the destination ATS does not have a native Interview object, we collapse this data into candidate activity history or custom notes fields.

Offer records include compensation details, status, and candidate linkage. SmartRecruiters exposes offer data through the core candidate response structure. We migrate offer status and compensation details and map them to the destination ATS's offer or approval workflow.

Assessments are ordered via the /packages endpoint and delivered through third-party integrations in the SmartRecruiters Marketplace. Assessment packages and order records are integration-specific. We preserve assessment results where accessible via API, but results from vendor-integrated assessments may require separate export coordination.

Candidate attachments (resumes, cover letters, portfolio files) are accepted on application submission and stored against the candidate profile. We migrate file references and re-attach original files to the candidate record in the destination system, handling both binary blobs and hosted URL references.