Migrate from Recruit ATS by HR Cloud to BambooHR

Recruit ATS Job postings map to BambooHR Job Openings. We extract job title, description (as HTML), location, department, employment type, and status (open/closed/archived). BambooHR Job Openings include an EEO survey section; we do not migrate EEO responses from Recruit ATS unless the customer explicitly requests it and confirms the compliance retention obligation in the destination. Custom request fields attached to the job posting migrate as text fields in the BambooHR Job Opening description unless the customer configures a BambooHR custom field in advance.

Recruit ATS Candidate records map to BambooHR Candidate records in the Hiring module. Contact information (name, email, phone, address), work history, and education migrate directly. The primary resume file migrates as a BambooHR document attachment. Knock-out question responses from Recruit ATS migrate as text fields on the BambooHR Candidate record; they do not map to a structured screening schema in BambooHR ATS because BambooHR does not have a native knock-out question feature.

The Recruit ATS Application (the junction object between Candidate and Job) maps to the BambooHR Application attached to a Job Opening. We transfer applied date, current stage assignment, source channel (referral, job board, direct), and rejection reason if applicable. Stage assignment is set as a placeholder because BambooHR stage names differ from Recruit ATS; we document the stage mapping in the migration manifest for the customer's admin to assign after stage configuration in BambooHR.

Recruit ATS pipeline stages are fully custom with ordinal positions stored in the API. BambooHR ATS uses a fixed set of stages (Applied, Interview, Offer, Hired, Rejected) that administrators configure in Hiring Settings. We extract the ordinal position and stage name from Recruit ATS and produce a written stage mapping document that maps each HR Cloud stage to the closest BambooHR stage. This is a manual configuration step that the customer's BambooHR admin must complete before or during migration because BambooHR does not expose stage configuration via its public API.

Recruit ATS Tags applied to Candidates and Jobs migrate as BambooHR Tags on the corresponding Candidate and Job Opening records. Tags are simple string labels in both systems; we transfer the full tag set as arrays. Multi-tag records are handled as multiple tag assignments. BambooHR tags are scoped to the Hiring module and do not extend to employee records unless the customer enables tag inheritance in BambooHR settings.

Standard-type custom fields (text, number, date, checkbox) from Recruit ATS migrate as custom employee fields in BambooHR HRIS if they apply to the employee record, or as text fields on the Job Opening or Candidate record if they are recruiting-specific. The customer must pre-create any desired custom fields in BambooHR because BambooHR ATS does not expose custom field creation via API. We provide a field creation guide with API names and types as part of the pre-migration deliverable.

Recruit ATS entity-type custom fields that link a Candidate to another Candidate or Job record cannot migrate to BambooHR ATS because BambooHR does not support cross-record lookup fields in its Hiring module. We detect these fields during the pre-flight audit, preserve the linked-record IDs in a dependency map, and document each linkage as a manual re-linkage step for the customer's admin post-migration. Any entity-type field that points to a non-HR object is flagged as out-of-scope.

Resume files, cover letters, and uploaded documents attached to Candidates and Jobs migrate as BambooHR documents. We preserve the original filename and MIME type. Large attachments exceeding BambooHR's file size limits are flagged for chunking or alternative storage (a shared document link). BambooHR stores documents against the Employee record after hire; during the ATS phase, documents attach to the Candidate record.

Notes attached to Candidates migrate as BambooHR Notes on the Candidate record. We preserve the note body as plain text, the original author name, and the original timestamp. BambooHR does not support threaded note discussions; all notes land as flat entries in the candidate timeline. We do not migrate internal Recruit ATS user comments that are not attached to a Candidate or Job record.

Recruit ATS automation rules (knock-out question triggers, SMS sequences, email automations) are not exposed via the HR Cloud public API. We cannot migrate them as structured data. During the pre-flight audit, we produce a written automation registry listing every active rule with its trigger, conditions, actions, and frequency. The customer's BambooHR admin uses this registry to rebuild automations using BambooHR's built-in email templates, any enabled integrations (such as Checkr for background checks or Enboarder for onboarding), or a third-party workflow tool. We flag any compliance-critical automations separately so they are not deprioritized.