Migrate from Recruiterflow to BambooHR

Recruiterflow Candidates split into two BambooHR destinations based on status. Candidates with a Placement in Recruiterflow (hired) map to BambooHR Employee records created during the onboarding handoff. Candidates without a Placement map to BambooHR Applicant records if the BambooHR ATS add-on is active; if ATS is not active, they map to an Employee record with a custom hiring_source__c field set to 'Recruiterflow Import' to preserve sourcing attribution. We resolve the split using Recruiterflow's candidate status and the presence of a Placement record. The original Recruiterflow candidate ID is stored in a custom field candidate_source_id__c for audit traceability.

Recruiterflow Contacts represent client relationships separate from candidates. BambooHR has no Contact or Account object for client relationships. We map Contacts to Employee records with a custom contact_type__c field set to 'Client Contact' and store the original Recruiterflow contact ID in contact_source_id__c. If the customer uses a separate CRM for client relationships, we flag this mapping as a manual-rebuild item rather than forcing client data into an HR record.

Recruiterflow Jobs map to BambooHR Job Openings only if the BambooHR ATS add-on is active on the destination account. Job fields (title, description, location, employment type) map to BambooHR Job Opening standard fields. If the ATS add-on is not purchased, Jobs are mapped to a custom job_posting__c custom field on a placeholder Employee record and flagged for the customer to configure in BambooHR after migration. Pipeline stages on Recruiterflow Jobs have no BambooHR equivalent and are noted as a manual-configuration item.

Recruiterflow Placements map to BambooHR Employee records with hire date, start date, and compensation data migrated as standard Employee fields. The placement status (active, terminated, extended) maps to BambooHR employment status. If BambooHR Onboarding is active, we create onboarding tasks linked to the new Employee record for each step the customer has tracked in the Placement. Placement fee and commission data migrate as custom fields on the Employee record because BambooHR does not have a native placement or commission tracking object.

Recruiterflow Companies represent client organizations with address, industry, and size data. BambooHR does not have a Companies or Accounts object. We store the most relevant Company data (name, industry, size) as custom fields on the Employee record of the associated Contact or hiring contact. Company associations for candidate-to-client relationships are stored as a custom field client_company__c on the Candidate/Employee record. If the customer maintains an active CRM for client data, we recommend not duplicating Company records in BambooHR and instead noting the migration of Company data as a reference-only item.

Recruiterflow Deals track revenue opportunities tied to Companies. BambooHR has no deal or opportunity object. Deal value, stage, and owner migrate as custom fields on the associated Company or Placement record where feasible. If the Deal has no associated Placement, the deal data is stored as a custom note attachment on the related Company custom field for audit purposes. We flag Deals as a manual-rebuild item for any CRM or billing system the customer adopts post-migration.

Recruiterflow custom fields on all six supported objects migrate to BambooHR custom fields on the corresponding Employee or Applicant record. Custom field type mapping: text to Short Text or Long Text, number to Number, date to Date, dropdown to Dropdown List, checkbox to National Yes/No, multi-select to Multiple Selection. We fetch the Recruiterflow custom field schema during scoping (via Recruiterflow support or UI export) and create matching BambooHR custom fields before migration. BambooHR custom fields are scoped per-employee and do not support object-level cross-referencing, so any Recruiterflow custom field referencing a lookup across objects is stored as a text field in BambooHR with the referenced record name.

Recruiterflow Users map to BambooHR Employee records that serve as the user identity. We resolve by matching email address. Any Recruiterflow User without a matching BambooHR Employee is held in the Owner reconciliation queue for the customer to provision before record import resumes. Recruiterflow User roles and permissions do not migrate because BambooHR permission sets are configured separately in the BambooHR admin UI.

Documents attached to Recruiterflow Candidates or Jobs migrate as BambooHR Employee Files. We download documents via Recruiterflow API, preserve the original filename and MIME type, and attach them to the corresponding Employee record under the Files tab. Documents associated with Placements attach to the resulting Employee record. If the ATS add-on is inactive and candidates are stored as Employees, their sourced candidate documents still attach to the Employee record under a 'Recruiting Documents' folder.

Recruiterflow Off-Limits records enforce client exclusivity compliance and are not exposed via a dedicated API endpoint. We identify Off-Limits candidates by scanning candidate tags and custom fields where the compliance boundary is stored, then create BambooHR Tags with a 'Off-Limits' prefix on the corresponding Employee or Applicant record. If no Off-Limits tag exists in the source, we ask the customer to confirm their Off-Limits list during scoping before migration.