Migrate from Phenom to BambooHR

Phenom Candidates map to BambooHR Job Applications within the BambooHR ATS module. Standard candidate fields (name, email, phone, address, LinkedIn URL) map to their BambooHR equivalents. We export the full Additional Fields payload per candidate and map these to BambooHR Employee Custom Fields or Candidate Custom Fields depending on whether the candidate has been hired. Any candidate records marked Rejected or Withdrawn in Phenom are included in the export with their status preserved for reconciliation.

Phenom Job records map to BambooHR Job Postings. We export job title, description, location, employment type, department, and job requirements. BambooHR's job posting structure is simpler than Phenom's; any complex job requirements stored as structured custom fields in Phenom become free-text or multiple-choice custom fields in BambooHR's Job Posting form.

Phenom Applications link Candidates to Jobs and contain status, stage progression, timestamps, and the candidate ID association. We export the full application record. When a candidate is hired, we link the BambooHR Job Application to the newly created BambooHR Employee record. Application status history migrates as a note or custom history field since BambooHR's ATS does not maintain a detailed application stage log.

Phenom Employee records map directly to BambooHR Employee records. The Employee Profile API in Phenom exports employee data including preferences, skills data, and tenure information. We map standard fields (name, hire date, department, job title, manager, employment status) to BambooHR's core Employee fields. Skills and tenure data that do not have a direct BambooHR equivalent become custom Employee Fields.

Phenom tag assignments export as a vocabulary list and per-candidate tag list. Tags used for candidate segmentation (source, level, clearance) map to BambooHR custom multi-select fields on the Employee record. Tags used for short-term categorization (interview status, interview round) map to BambooHR notes attached to the Job Application. The customer chooses the tag strategy during scoping based on how BambooHR's ATS module will be used.

Phenom Additional Fields are tenant-specific custom attributes on candidate profiles exposed via the Candidates API GET/PUT operations. We export the full Additional Fields payload per record. BambooHR custom fields enforce type constraints (text, date, dropdown, checkbox, etc.). If a Phenom Additional Field is free-text and BambooHR expects a picklist, we pre-create the picklist options in BambooHR during schema setup or map to a text-type custom field to avoid validation errors during import.

FitScore is Phenom's proprietary AI-generated candidate-to-job compatibility score built on its skills ontology. BambooHR has no AI matching or scoring engine. We export the underlying skills, experience, and qualification fields that contribute to FitScore as standard employee or candidate custom fields, then flag FitScore as a feature requiring evaluation post-migration. The customer documents FitScore thresholds and scoring rules in the migration manifest for manual re-evaluation or third-party AI tool integration.

Phenom Projects contain multiple Statuses defining the progression path for candidates through a workflow. These are modeling constructs, not flat pipeline fields. We export the complete workflow topology including stage names, ordering, and conditional routing as a JSON topology document. BambooHR's ATS does not support multi-stage workflow topologies; we deliver the Project inventory so the customer's admin can configure BambooHR's applicant pipeline stages manually. Custom routing logic that references Phenom-specific rules is documented for rebuild.

Phenom Campaign APIs manage one-to-many candidate outreach sequences with template content and send history. We export campaign structure, template content, and send history metadata as a written document. BambooHR supports standard email sending but has no campaign cadence or sequence automation. Email templates migrate as content files; the cadence logic requires rebuild in a dedicated sales engagement tool if the customer continues multi-step outreach. The campaign inventory document is included in the migration handoff package.

Phenom User and group management via SCIM exports users, their group assignments, and role associations. BambooHR does not have a separate user management model; employees in BambooHR are the users. We export Phenom users with their role assignments and map to BambooHR employees with the corresponding HR permissions (Admin, Manager, Employee). SCIM provisioning is not applicable in BambooHR since user access is tied directly to the employee record.