Migrate from RecruitBPM to BambooHR

Only candidates who have been hired or placed migrate as BambooHR Employee records. Hired candidates from RecruitBPM Placement records carry name, email, phone, hire date, job title, and compensation into BambooHR Employee. Unplaced candidates do not map to a BambooHR standard object and require a separate decision during scoping: either map as an inactive Employee record with a status flag, store in a BambooHR custom field group, or exclude from the HRIS migration entirely. Resume files migrate as attachments to the Employee record.

RecruitBPM Client records (organizations the staffing agency places talent into) have no equivalent in BambooHR's HRIS model. We map Client name, industry, and primary contact to a custom field group on the Employee record of the hiring manager, or store as a Company-level Note in BambooHR if the customer has multiple placements at the same Client. Client relationship history (meeting notes, communications) migrates as Employee-level activity notes.

RecruitBPM Job Orders (requisitions tied to a Client) do not map to a standard BambooHR object. We map active Job Order details to a custom text field on the Employee record of the hiring manager or to a Note with a 'Job Order' category. Historical Job Order status and requirements are preserved as notes; the pipeline stage progression is not transferable to BambooHR's workflow model.

RecruitBPM Placements (confirmed hires with start date, compensation, fee, and Client link) map to BambooHR Employee records. The placement start date becomes the BambooHR hire date, compensation details map to BambooHR pay rate and pay type fields, and placement fee information (if the agency tracks it for billing) maps to a custom field. We resolve the Candidate-to-Employee reference and the Client reference at migration time.

RecruitBPM Talent Pools (skill- or certification-based candidate collections) have no native BambooHR equivalent. We map pool membership to BambooHR Employee Lists (a grouping feature) or to custom tags on Employee records if BambooHR lists are not available in the customer's tier. Pool engagement history (outreach, responses) migrates as notes on the Employee record. Talent pool segmentation logic is documented for rebuild in BambooHR's tagging system.

RecruitBPM Interview records (scheduled time, interviewer, format, outcome notes) migrate as notes on the corresponding BambooHR Employee record. Video interview links and recorded interview URLs are preserved as text fields. Interview scheduling workflows from RecruitBPM are not transferable to BambooHR's onboarding model and are documented for rebuild.

RecruitBPM Assessment results (custom screening forms and evaluation scores) migrate as custom fields or structured notes on the BambooHR Employee record. Assessment schema definitions vary by tenant and require custom field creation in BambooHR before data import. Assessment form builders from RecruitBPM do not migrate; we deliver a written form-schema map for the customer to rebuild in BambooHR's custom form tool.

RecruitBPM Activity records (emails, calls, SMS, voicemails, notes tied to Candidates and Clients) migrate as BambooHR Notes attached to the corresponding Employee record. Activity type taxonomy maps to a Note category field. Rich text formatting and file attachments preserve where the target field supports them. Automated outreach sequences and engagement logs are documented as notes but are not transferable as automated workflows.

RecruitBPM customizable pipeline stages for Job Orders reflect a staffing agency's specific hiring workflow and have no equivalent in BambooHR's HRIS model. We document the original pipeline stage names and counts as part of the Job Order mapping, but the stage progression is not a transferable construct. If BambooHR's onboarding workflow builder is in use, stages map to onboarding task lists.

RecruitBPM custom fields across Candidates, Clients, and Job Orders require pre-creation in BambooHR before migration. We extract the full custom field definition set during scoping, map each to a BambooHR equivalent field type (text, number, date, dropdown, checkbox), and create the destination custom fields in BambooHR via the API before record import. Custom field IDs in BambooHR must be fetched per tenant via GET /v1/meta/fields and cannot be hardcoded across customers.

RecruitBPM platform users (recruiters, admins) who own records and drive workflows map to BambooHR User accounts by email match. User name, email, and role transfer directly. Recruiter assignment on Candidate, Job Order, and Placement records resolves via this user mapping. Permissions and team structures from RecruitBPM are not transferable; BambooHR's permission model is scoped per admin, manager, and employee role.

Resume files, contracts, onboarding documents, and other attachments stored in RecruitBPM migrate as binary attachments to the corresponding BambooHR Employee record. We verify file format compatibility (PDF, DOCX, TXT are standard; proprietary formats may require conversion). Attachment metadata (filename, upload date, file size) preserves where BambooHR's attachment model supports it.