Migrate from eRecruiter to BambooHR

eRecruiter Candidates map to BambooHR Employee records as the primary HRIS object. BambooHR does not maintain a separate Candidate object outside of the hiring workflow; Candidates from eRecruiter who are not yet hired become BambooHR Applicants linked to the Job. We map eRecruiter contact fields (name, email, phone, address) to BambooHR Employee fields using the standard field names, and preserve the original eRecruiter Candidate ID in a custom field erecruiter_candidate_id__c for audit. GDPR consent flags migrate to BambooHR's custom field model.

eRecruiter Applications map to BambooHR Applicant records within the BambooHR ATS Hiring module. Each Application links to the corresponding Job (BambooHR Job) and Applicant (Candidate). Application stage, status, rating, and custom application fields migrate as Applicant custom fields. We resolve the Job reference in BambooHR before writing Applications so that the parent lookup is satisfied at insert time.

eRecruiter Jobs map to BambooHR Job records. We migrate title, description (HTML preserved), location, department, employment type, and publication status. Historical closed jobs migrate as inactive Job records in BambooHR. We flag any customer whose historical job count exceeds their BambooHR ATS tier cap (Core 5, Pro 25, Elite 50 simultaneous open jobs) before migration so that tier upgrade decisions are made before cutover rather than during.

eRecruiter Company entities (typically employer companies rather than candidate employers) map to organizational context within BambooHR. If the customer uses Companies to track client employers, we map these to BambooHR's department and division structure or flag them as requiring a custom field. eRecruiter's Company Import API uses ExternalId matching for updates.

eRecruiter Users map to BambooHR User accounts. Role naming differs between platforms; we capture the eRecruiter role name in a custom field erecruiter_role__c and the customer maps it to the appropriate BambooHR permission role during scoping. User provisioning requires active BambooHR User licenses, which the customer supplies before migration.

eRecruiter Department is a referenced entity on Jobs and Users. We detect whether BambooHR is configured with Departments as independent records or as a property on the Job, then migrate accordingly. Departments must be created before Jobs that reference them.

Location data (city, region, country) migrates as structured address components on the Job record in BambooHR. If the customer uses multi-location job posting in eRecruiter, we map each location to a separate BambooHR Location record and associate it with the Job.

Candidate document attachments in eRecruiter are identified by DocumentTypeName, Filename, and the parent Candidate's ID. We transfer binary attachments by first resolving the target Employee record ID in BambooHR, then uploading the file to the corresponding Employee document section. Documents without a valid parent Employee reference (orphaned attachments) are flagged for manual review. This dependency requires Candidates to be migrated before their attachments.

Application attachments (resumes, cover letters, portfolio files) migrate to BambooHR Applicant file attachments. We resolve the target Applicant record ID before uploading. The Job must be migrated and the Applicant record created before Application attachment migration begins.

Structured evaluation ratings on eRecruiter Applications are stored as part of the Application record or as linked feedback entries. We serialize scorecard data into custom fields on the BambooHR Applicant record. Field type mapping (rating scales to picklist or number) is validated during scoping.

eRecruiter custom fields on Candidates migrate to BambooHR Employee custom fields. CV Parsing output (experience duration, education level, skills tags, language proficiency) requires discovery during scoping because parsed field names vary by CV template and parsing version. We treat all CV Parsing fields as custom fields, validate the target schema, and flag any field type mismatches before migration.

eRecruiter custom fields on Applications migrate to BambooHR Applicant custom fields. We discover the full custom field schema during scoping, map field types to their BambooHR equivalents (text, number, date, picklist), and validate that all required fields are populated before the first Applicant insert.