Migrate your Smart Recruit Online data

The primary applicant object. Exposed via GET /candidates with standard fields (name, email, location) plus CustomField arrays. We map candidate IDs 1:1 and preserve application history. Concurrent rate limit of 1 for bulk GET /candidates means we chunk large exports in batches.

Job records represent open positions. Each Job object contains location, department, function, typeOfEmployment, experienceLevel, and CustomField arrays. We map job IDs and reference numbers between source and destination systems.

Postings are job advertisements linked to Jobs via jobAdId. We preserve the posting name, refNumber, releasedDate, and location data including remote flag. Multiple Postings can exist per Job in multi-channel distribution scenarios.

Application records link a Candidate to a Job with a current status. We migrate application status history, timestamps, and assigned Hirers. Status values must be mapped against the destination pipeline stage names.

Hirer objects represent internal users who create or own Jobs and Applications. We map Hirer records but user assignment rules differ between platforms — some ATS platforms assign by email, others by internal ID, requiring field-level mapping during migration.

SmartRecruiters uses configurable pipeline stages within Jobs. Stage names, order, and associated automations vary by tenant configuration. We extract the current stage definitions and map them to destination equivalents, flagging any custom stage logic.

Custom fields are stored as CustomField objects with fieldId, fieldLabel, valueId, and valueLabel. We capture all custom field definitions during scoping and apply value-label mapping at migration time. Enterprise tenants frequently have 20+ custom fields.

Workflow rules are configuration objects rather than data records. We do not migrate workflow definitions as data — instead we document the active workflows and provide an automation audit log to the customer for manual reconfiguration in the destination system.

Candidate email threads are accessible via the candidate detail endpoint. Thread integrity depends on the email having been sent through SmartRecruiters natively. External email imports may not be fully preserved.

Resume files and attachments associated with Candidates and Applications can be exported. File URLs require re-hosting since the source storage is SmartRecruiters-controlled. We preserve file metadata and original filenames.

Department and function are structured fields on Job objects with id and label. We migrate these as reference data, mapping to equivalent structures in the destination ATS.

Offer management is available on higher tiers. We migrate offer records including status and details where exposed via API, but offer templates and approval workflows require manual setup in the destination.