Migrate from PCRecruiter to BambooHR

PCRecruiter People records with candidate activity map to BambooHR Applicant records in the Hiring module. We extract the full candidate profile including name, contact info, work history, education, and custom fields, then load via BambooHR's Import Tool or API. If BambooHR ATS is not licensed, candidates are preserved in a structured spreadsheet for manual entry or future ATS activation. The PCRecruiter candidate status (Active, Placed, Archived) maps to BambooHR Hire Date or Application Status fields.

PCRecruiter People records functioning as client contacts (not candidates) do not have a direct BambooHR equivalent because BambooHR is employee-focused and does not have a client or company object. We provide two options during scoping: (1) load client contacts as Employee records in BambooHR with a custom field contact_type__c set to 'External', or (2) preserve as a structured CSV for manual CRM entry in a separate tool. The customer chooses during scoping.

PCRecruiter Company records have no direct BambooHR equivalent. We create a custom BambooHR field (previous_company_id__c or similar) on the Employee record to store the source Company reference, preserving the affiliation link. If BambooHR ATS is licensed, the Company name maps to the Job's Hiring Company field or a custom field for reporting purposes. The full Company hierarchy (parent-subsidiary) cannot migrate as structured relationships in BambooHR.

PCRecruiter Position records map to BambooHR Job postings in the Hiring module. Position title, description, requirements, location, and employment type transfer as Job fields. PCRecruiter pipeline stage definitions do not map to BambooHR's standardized hiring stages (Applied, Phone Screen, Interview, Offer, Hired, Rejected); we document the original PCRecruiter stage progression as a note on the Job record and in the handoff spreadsheet for the customer's admin to rebuild manually.

PCRecruiter Placement records represent successful hires with billing information, start dates, employee details, and client associations. We map Placements to BambooHR Employee records by creating the employee in BambooHR with hireDate and jobTitle populated from the Placement. The billing rate, client association, and commission fields from PCRecruiter Placement have no BambooHR standard equivalent; we create custom fields (billing_rate__c, client_association__c, commission_amount__c) on the Employee record to preserve this data.

PCRecruiter Activity records (emails, calls, meetings, notes) logged against People or Positions do not have a structured BambooHR equivalent. The BambooHR Employee Timeline supports limited notes, and BambooHR ATS does not store full candidate activity history. We migrate the most recent 3-5 meaningful notes per candidate as Employee or Applicant notes, and flag the full activity history as a gap. The customer receives a CSV export of all activity history for manual reference or archival.

Resume files and documents attached to PCRecruiter People records migrate to BambooHR Applicant attachments via the BambooHR Attachments API. We preserve file associations to the correct Applicant record and maintain the original filename. Documents attached to Companies or Positions without a direct BambooHR equivalent are bundled into a ZIP archive linked to the corresponding Employee or Job record as a custom attachment.

PCRecruiter tags on People, Companies, and Positions migrate to BambooHR's Employee Tags feature. Tags are preserved as a flat taxonomy and recreated as BambooHR tags on the corresponding Employee or Applicant record. If a tag applies to a Company rather than a Person, it is stored in a custom Employee field (previous_tags__c) for reference.

PCRecruiter User accounts map to BambooHR Employee records with active User accounts. We resolve PCRecruiter Owner assignments on People, Positions, and Placements to the corresponding BambooHR User by email match. Owners without a matching BambooHR User go to a reconciliation queue for the customer's admin to provision before record import. PCRecruiter role permissions do not migrate to BambooHR role assignments.

PCRecruiter custom fields on Person, Company, Position, and Placement records map to BambooHR custom fields on Employee, Applicant, or Job records. We extract the full custom field schema from PCRecruiter, compare against BambooHR's supported field types (text, dropdown, date, number, checkbox, file upload), and flag any unsupported field types (such as multi-select picklists or calculated fields) for customer decision on how to handle. Dropdown values require explicit translation when PCRecruiter picklist options differ from BambooHR options.