Migrate from 100Hires to BambooHR

100Hires Candidates with active Applications map to BambooHR Applicant records tied to the corresponding Position. Candidates who have been hired (Application status = Hired) map to both an Applicant record (for the hire record) and an Employee record in BambooHR for onboarding. The 100Hires pipeline stage at the time of hire is preserved as a custom text field candidate_original_stage__c on both records for audit and reporting continuity. Candidates with no Application (sourced but never applied) create Applicant records with a Source value only and no Position linkage.

100Hires Jobs map to BambooHR Positions. Job title, department, location, and description transfer as Position name, department, location, and description fields. The 100Hires job status (Active/Paused/Closed) maps to BambooHR Position status (Open/Paused/Closed). Job board posting distribution settings (LinkedIn, Indeed, ZipRecruiter) are documented in the export but require reconfiguration in BambooHR's Job Posting settings because BambooHR does not natively auto-post to the same board network.

100Hires Applications link a Candidate to a Job with a pipeline stage, timestamps, and rejection reason. BambooHR Applicants are linked to Positions with an Application Status field (Applied, Rejected, Withdrawn, Offer Extended, Hired). We map 100Hires pipeline stages to BambooHR Application Status values, preserving the last stage date as appliedDate and any rejection reason in the applicationNotes field. Applications that progressed through multiple stages retain the final stage only in BambooHR; stage-by-stage history is written to a custom multi-line text field application_stage_history__c.

100Hires Interviews (scheduled dates, times, interviewers, interview types) map to BambooHR Interview records linked to the corresponding Applicant. Interviewer names resolve by email match to BambooHR User records. Calendar integration status (G Suite sync flags) is documented but not migrated because BambooHR's calendar integration handles this natively. Interview type (phone screen, technical, behavioral) transfers as interviewType.

100Hires Evaluation scorecards submitted by interviewers map to BambooHR Applicant Ratings. Custom evaluation criteria (e.g., 1-5 rubric, pass/fail, weighted scores) are exported with their form definitions and written to a pre-migration audit document. We migrate submitted scores as rating values and flag any custom criteria that do not have a direct BambooHR equivalent in the scorecard notes. Customers configure BambooHR's scorecard fields or partner with BambooHR to define custom rating criteria post-migration.

100Hires Notes attached to Candidates or Applications transfer to BambooHR Note records linked to the corresponding Applicant or Employee. Note body content, author (User), and creation timestamp migrate directly. Notes attached to Candidates with no Application create Notes linked to the Applicant record only. Notes attached to hired Candidates (Employee context) link to the Employee record for ongoing HR documentation.

100Hires Users (recruiters and team members) map to BambooHR User records resolved by email match. Role and permission assignments do not transfer because BambooHR's role model is destination-specific. We flag any 100Hires Users that do not have a corresponding BambooHR User in a reconciliation queue for the customer's admin to provision before Applicant migration begins. HR admin vs recruiter role differences are documented for post-migration reconfiguration.

100Hires Attachments (resumes, cover letters, portfolio files) linked to Candidates or Applications download as binary files and re-upload to BambooHR under the corresponding Applicant record. Filenames are preserved. Files linked to hired Candidates (Employee context) attach to the Employee record for onboarding document storage. We verify file type compatibility with BambooHR's supported upload formats during the pre-migration audit.

100Hires Nurture Campaigns are email sequences with defined steps, timing, and recipient logic. We export campaign definitions and email template body content as raw text with token syntax preserved, but in-flight campaigns are paused before migration and cannot be safely transferred mid-sequence because recipient opt-out states and delivery timestamps are tightly coupled to 100Hires' email infrastructure. Active campaign status and step definitions are written to a Campaign Inventory document for the customer to re-activate manually in BambooHR or a dedicated email cadence tool post-migration.

100Hires Email Templates (subject lines, body content, placeholder tokens) export as raw text with dynamic field tokens preserved in original syntax. Templates re-import into BambooHR Email and Offer Letter Templates manually, with tokens re-mapped to BambooHR's dynamic field syntax. Customers review each template post-migration to confirm placeholder substitution works correctly in BambooHR's template editor.

100Hires structured taxonomy for Skills, Departments, and Locations exports as flat lists. We map these to BambooHR custom fields on the Employee record (for Skills and Location) and Department configuration. Any unresolvable taxonomy values (e.g., a 100Hires skill not representable as a BambooHR custom field value) are flagged in the pre-migration audit for the admin to resolve or archive.

100Hires Career Site job listings and hosted pages export as content documents (job titles, descriptions, requirements) but the public URL is tied to the 100Hires account and cannot be transferred. BambooHR's Employee Portal and Careers section require manual content rebuild. We provide a Career Site Content Export with all job listing HTML and content in a structured format for the customer's admin to re-enter into BambooHR's careers page or an external careers platform of choice.