Migrate your eRecruiter data

Candidates are the primary applicant record in eRecruiter. We retrieve full candidate profiles via the API including contact details, work history, skills, and answers to application questions. We use the candidate's ExternalId for matching and fall back to email-based deduplication when no ExternalId is set.

Applications link a Candidate to a Job and carry status, stage, rating, and notes. We migrate application records as first-class objects, preserving the pipeline stage name and any custom application fields. Applications must reference valid Candidates and Jobs in the target system.

Job postings include title, description (HTML), location, department, employment type, and publication status. We migrate Jobs as independent records and re-publish them in the target ATS or deactivate them depending on the migration scope. Job-level reporting limitations in the source do not affect data transfer.

Company entities are imported or synchronized via the dedicated Company Import API endpoint using ExternalId matching. We handle both new record creation and updates to existing company records. Custom company properties migrate as custom fields in the destination.

User records include name, email, role, and department assignment. We map eRecruiter Users to Owner/User records in the destination ATS. Role naming differs between platforms, so we capture the eRecruiter role as a custom property in the target for auditability.

Department is a referenced entity on Jobs and Users. Some ATS platforms treat Departments as independent records; others handle it as a property on the Job. We detect the target's schema and migrate Departments either as a lookup table or as flat values depending on destination capability.

Location data on Jobs includes city, region, and country. We preserve all location fields as structured address components. If the destination supports multi-location job posting, we handle location mapping accordingly.

Documents attached to Candidates and Applications are identified by DocumentTypeName, Filename, and the parent record's ID. We transfer binary attachments provided the linked Candidate or Application exists in the target. Documents cannot be imported in isolation — they require a parent record to be present.

Structured evaluation ratings on Applications are not a separate object but are stored as part of the Application record or as linked feedback entries. We serialize scorecard data into structured custom fields in the destination so it remains parseable for reporting even when native scorecard objects are unavailable.

Both Candidate and Application records support custom fields in eRecruiter. We discover custom field schemas during the scoping phase and map them to equivalent custom properties in the destination. Field type conversion (dropdown to text, multi-select to comma-separated) is handled explicitly to prevent data loss.