Migrate from RECRU to BambooHR

RECRU candidate records map to BambooHR application records within the ATS module. Each candidate creates one application linked to a BambooHR job. We preserve all parsed CV fields (name, email, phone, skills, work history), custom candidate properties as key-value pairs, tags as flat label arrays, and the AI-generated match score in a custom float field labeled recru_match_score__c with a note that the scale is proprietary to RECRU and not calibrated against any BambooHR scoring system.

RECRU job requisitions map directly to BambooHR jobs. Title, description, department, location, salary range, and status transfer. Pipeline stage names and order from RECRU map to BambooHR application statuses; if BambooHR uses a predefined status set, we map to the closest equivalent and flag any RECRU stages with no clear destination match.

RECRU pipeline stage names and their sort order migrate as BambooHR application statuses. BambooHR allows custom status labels but uses a fixed set of internal statuses. We map RECRU stage names to BambooHR status labels and document any stages that have no direct equivalent so the customer's admin can rename or consolidate statuses post-migration.

RECRU user accounts (recruiters, hiring managers, admins) map to BambooHR employee records with the employment status set to Active. We resolve RECRU owner assignments on candidates and jobs to the corresponding BambooHR employee record by email match. Any RECRU user without a BambooHR employee record goes to a reconciliation queue for the customer's admin to provision.

RECRU custom candidate properties added by the tenant migrate as BambooHR custom fields on the Application object if the destination account supports custom ATS fields in the current plan tier. We extract field name, type, and values and create equivalent fields in BambooHR, falling back to a JSON-encoded text field for complex types that BambooHR does not support.

RECRU email threads and message logs attached to candidate records migrate as a flattened activity log entry per message. The original thread structure is not preserved in BambooHR; each message becomes a separate note or activity record with the sender, recipient, timestamp, and body content. We render rich-text body content and attach any embedded file references as separate attachment records.

RECRU interview records carrying date, interviewer, duration, and outcome map to a custom interview tracking field in BambooHR if the destination account uses a third-party scheduling integration. BambooHR does not have a native standalone interview object; we create a structured note record attached to the application with interview metadata fields and link it to the interviewer employee record.

RECRU evaluation scorecards submitted by interviewers migrate as JSON objects attached to the application record as structured notes. BambooHR does not have a native scorecard object, so evaluation ratings, interviewer feedback, and recommendation fields are encoded in a structured format for human readability and potential future integration with a BambooHR-compatible form tool.

Tags applied to candidates in RECRU migrate as flat label arrays attached to the application record in BambooHR. Tag names are preserved verbatim. BambooHR supports tags on employee records and we apply the same tagging logic to the application record in the ATS module.

RECRU workflow automation rules are exported as a structured JSON document with a human-readable summary of each rule's trigger, conditions, and actions. BambooHR's workflow builder uses a simpler approval-based model and does not support multi-step conditional branching. We flag which RECRU rules have a direct BambooHR equivalent and which require manual redesign. The customer rebuilds these in BambooHR post-migration.