Migrate from Recruit CRM & ATS to BambooHR

Recruit CRM Candidate records map to BambooHR Applicant records for active job applications. For candidates who have been placed (Deal status = won/closed), we map the candidate profile to a BambooHR Employee record using the placement data from the linked Deal. The Candidate source field maps to BambooHR's applicant source property. Custom fields on candidates (skills, certifications, salary expectations) are mapped to BambooHR's custom Applicant fields or custom tables linked to the Applicant object.

Recruit CRM Jobs map directly to BambooHR Jobs with status preserved (Open, On Hold, Closed). The job title, description, department, and location map to BambooHR standard fields. Recruit CRM's multiple job pipelines map to separate BambooHR Job postings if the organization uses department-specific hiring boards. Any custom fields on jobs (hiring manager, urgency tier, security clearance requirement) are mapped to BambooHR's custom job fields.

Recruit CRM Company records have no direct BambooHR equivalent. BambooHR is an HRIS without a client relationship management module. We flag Company records during scoping and present three options: archive to a CSV export for manual reference, migrate to a separate CRM post-BambooHR onboarding, or exclude from scope. The chosen strategy is confirmed before migration begins. Company records linked to placed candidates are noted in the Employee record notes field for audit continuity.

Recruit CRM Contacts (hiring managers, referrers, client contacts) have no BambooHR equivalent. Like Companies, Contacts are excluded from the standard migration scope. We extract Contact records to a structured CSV and deliver it alongside the migration for manual import into any future CRM. If a Contact is linked to a placed candidate, we preserve the association in the Employee notes or a custom Employee field for reference.

Recruit CRM Deals tracking placements and business transactions have no BambooHR equivalent. We do not migrate open Deals as operational records because BambooHR has no deal or opportunity object. For Deals with Closed-Won status, we flag the associated Candidate as hired and migrate the placement data to the corresponding BambooHR Employee record. For Deals with open status, we export them to a CSV with stage, value, and company association for the customer's admin to handle separately.

Recruit CRM Hotlists are curated candidate collections with custom names and saved search criteria. We extract the candidate IDs in each Hotlist and migrate them as tagged groups or lists in BambooHR's ATS. If the organization uses BambooHR's Applicant Status feature for internal pipeline tracking, we replicate the Hotlist names as status tags or custom fields on the Applicant records. The search criteria that defined the Hotlist do not migrate as logic; only the enrolled candidate IDs transfer.

Recruit CRM call logs (duration, outcome, linked candidate or contact) map to BambooHR notes attached to the corresponding Applicant or Employee record. We preserve the call date, duration in minutes, disposition (no answer, left voicemail, discussed), and the recruiter's name as the note author. Call logs linked to Candidates not yet in BambooHR are attached to the Applicant record at migration time after candidate-to-applicant ID resolution.

Recruit CRM meeting records with date, time, attendees, and outcome migrate to BambooHR notes or calendar events on the linked Applicant or Employee. For interviews scheduled in Recruit CRM, we migrate the meeting title, scheduled date, and outcome notes to the corresponding BambooHR applicant record. Attendee information is preserved in the note body if no dedicated attendee field is available in BambooHR.

Recruit CRM notes attached to candidates, companies, or jobs migrate as BambooHR notes on the corresponding Applicant or Employee record. We preserve the full note body, the note author, and the timestamp. Notes attached to Company or Contact records that have no BambooHR destination are exported to CSV with the linked record reference preserved for manual follow-up.

Recruit CRM tasks linked to candidates or jobs map to BambooHR's to-do items attached to the Applicant or Employee. Task status (open, completed), due date, and assignee migrate. Completed task history is preserved as completed items; open tasks are migrated as open to-dos for the responsible recruiter or HR admin to action post-migration. Task assignment resolves by matching the Recruit CRM owner email to the BambooHR user.

Recruit CRM custom fields are fully customer-defined and vary per organization. We extract the complete custom field schema during discovery, map each field to a BambooHR custom field (if the object supports it) or a custom table entry linked to the standard record. Note that BambooHR uses a custom tables model where custom fields for Employees and Applicants are configured separately; nested multi-level custom fields in Recruit CRM may require flattening or mapping to multiple custom table rows in BambooHR.

Candidate resumes and cover letters stored in Recruit CRM's Files API migrate to BambooHR as documents attached to the corresponding Applicant (for candidates) or Employee (for placed candidates). We extract files in parallel batches, preserving the original filename and file type. Company documents attached to Company records with no BambooHR destination are exported to a structured file archive with the company name as the folder.