Migrate from Phenom to Bullhorn ATS & CRM

Phenom Candidates map directly to Bullhorn Candidate records via the Candidates API and Bullhorn REST API respectively. Standard properties (name, email, phone, address, skills, experience) transfer 1:1. Additional Fields on each Candidate record map to Bullhorn custom fields on the Candidate entity. We export the full Additional Fields payload per candidate including tenant-specific attributes and preserve the original field labels in a migration manifest so the customer can verify mapping completeness.

Phenom Jobs map to Bullhorn JobOrder records. The Job Sync API export includes active and historical job postings, metadata, location data, and job requirements. Bullhorn JobOrder fields (title, description, employmentType, salary, address, clientCorporation) receive the corresponding Phenom fields directly. Job requirements stored as custom Additional Fields on Jobs map to Bullhorn custom fields on JobOrder.

Phenom Applications link Candidates to Jobs and map to Bullhorn JobSubmission records. The Applicants API export includes status, stage progression, timestamps, and the candidate ID association. We resolve the candidate foreign key to Bullhorn Candidate ID and the job foreign key to Bullhorn JobOrder ID at migration time. Application status maps to JobSubmission status with the original Phenom status preserved in a custom field for reconciliation.

Phenom Employee Profile records map to Bullhorn Employee records where the Bullhorn ATS edition supports employee management. The Employee Profile API export includes preferences, skills data, and tenure information. We map employee status (active, inactive, terminated) to the corresponding Bullhorn Employee status field. Employee skill data from Phenom maps to Bullhorn custom fields on Employee because Bullhorn does not have a native skills ontology.

Phenom Tag Management APIs export tag assignments and vocabulary per candidate. Bullhorn does not have a native Tag object; tags migrate to custom multi-select picklist fields on the Candidate entity. We export the full tag vocabulary, create a custom field per tag group (or consolidate into a single multi-select if the vocabulary is under 150 values), and map each candidate's tag assignments to the corresponding picklist values.

Phenom Additional Fields are tenant-specific custom attributes on candidate profiles exposed via the Candidates API. We export the full Additional Fields payload per candidate and map each to either a Bullhorn custom field (if under the entity field limit) or a Bullhorn Custom Object (if the limit is exceeded or the data is structured). Bullhorn Custom Objects require a Support ticket to provision and support up to 55 fields each depending on edition (Front Office Growth/Enterprise: 10 objects, ATS: 2 objects, ATS Growth: none). We coordinate Custom Object provisioning during the discovery phase.

Phenom FitScore is a proprietary AI-generated candidate-to-job compatibility score built on skills, experience, and qualifications. Bullhorn Amplify provides AI matching but is a separate add-on with a different scoring model. We export the underlying skills, experience, and qualification fields that drive the FitScore so they can be preserved in Bullhorn custom fields or used to configure Bullhorn Amplify matching rules. We document every record that carried FitScore data in the migration manifest with the original score value in a custom field phenom_fitscore__c for audit.

Phenom Projects contain multiple Statuses defining candidate progression paths through a workflow. Bullhorn does not have a native Project object; workflow stages map to Bullhorn pipeline stages on JobSubmission and Candidate entities. We export the complete workflow topology (stage names, ordering, conditional routing) and document it as a Bullhorn pipeline configuration plan with stage-to-stage mapping. Custom routing logic referencing Phenom-specific rules must be rebuilt by the customer's Bullhorn admin post-migration; we provide the written topology map as the rebuild reference.

Phenom Campaign APIs manage one-to-many candidate outreach sequences (email and SMS). Bullhorn has a native Campaign object for recruitment marketing campaigns. We export campaign structure, template content, and send history metadata from Phenom. Individual email and SMS message records are exported as engagement data. Bullhorn Campaigns do not natively support automated sequencing; we document the campaign structure so the customer's team can rebuild sequences using Bullhorn Automation or a third-party sales engagement tool.

Phenom User Management uses SCIM protocol at the User Management APIs. Bullhorn uses its own User entity with role-based access control. We export users, group assignments, and role associations from Phenom and map them to Bullhorn User records with corresponding Bullhorn role assignments. The customer provisions Bullhorn users manually or via SCIM; we coordinate the email-based owner matching during the user reconciliation phase.

The Phenom Prediction API predicts skills based on job titles and provided skill sets, storing results against candidate profiles. These predicted skill mappings export as structured data per candidate. Bullhorn does not have a native predicted skills model. We migrate predicted skills as Bullhorn custom fields on the Candidate record, tagging each field with the original Phenom prediction source (title-based or skills-based) in the field label for traceability.

Phenom tracks Companies as part of its CRM layer. Bullhorn uses ClientCorporation as the entity for recruiting clients (the companies staffing firms place talent with). We export Company records from Phenom and map them to Bullhorn ClientCorporation. The company name, address, industry, and contact associations migrate directly. Any company-specific custom fields map to Bullhorn custom fields on ClientCorporation.