Migrate from Phenom to Recruit CRM & ATS

Phenom Candidates map directly to Recruit CRM Candidate records. We export the full Candidates API payload including standard properties (name, email, phone, location, source) and all Additional Fields (tenant-specific custom attributes) per candidate. The Additional Fields payload is mapped to Recruit CRM custom fields configured in the destination before import. Candidate tags from Phenom transfer to Recruit CRM tag assignments. FitScore values export as a custom numeric field with a companion text field holding the scoring rationale for admin review.

Phenom Jobs map to Recruit CRM Job postings. We export job title, description, location, department, employment type, requirements, and status (active, closed, on-hold) via the Job Sync API. Historical jobs with closed status migrate as archive records in Recruit CRM. Job requirements fields map to Recruit CRM job custom fields if the destination has structured requirement fields configured.

Phenom Applications link Candidates to Jobs and are accessible via the Applicants API. We export application status, stage progression, submission date, and the candidate-ID and job-ID associations. Applications are imported after both Candidates and Jobs exist in Recruit CRM to satisfy foreign key dependencies. Historical stage progression timestamps migrate as activity entries against the application record.

Phenom Employee Profile APIs export employee records including preferences, skills data, and tenure information. We map employees to Recruit CRM Employee records if the destination tenant has employee management enabled, or to Candidate records if the migration scope treats internal candidates separately. Skills data from Phenom employee profiles exports as structured fields for reuse in job matching on the destination.

Tag Management APIs export all tag vocabulary and candidate-tag assignments from Phenom. We create equivalent tags in Recruit CRM and reapply assignments to the migrated candidate records. Tag vocabulary is preserved as-is; if duplicate tag names exist across departments, we namespace them with a prefix to prevent collision during import.

Phenom Additional Fields are tenant-specific custom attributes on candidate profiles exported via GET/PUT on the Candidates API. We map each Additional Field to a Recruit CRM custom field of matching type (text, number, date, picklist, checkbox). Field-level dependencies or conditional-display logic in Phenom does not transfer; Recruit CRM custom field visibility is set to unrestricted during migration and can be scoped by the admin post-import.

Phenom Projects with embedded Statuses define candidate progression paths and conditional routing. These are modeling constructs without a direct Recruit CRM equivalent. We export the complete workflow topology including stage names, ordering, stage-to-stage transitions, and any conditional routing rules as a structured JSON document. Recruit CRM pipeline stages are configured flat per job; the customer uses the exported topology as a reference to design equivalent stages. Custom routing logic requires rebuild in Recruit CRM workflows.

Campaign structure, template content, and send history metadata export from Phenom Campaigns API. Individual email and SMS message logs are accessible via Communications API. We map campaign names, target segments, and template subject lines to Recruit CRM Campaigns. Send history and engagement metrics export as reference data; Recruit CRM does not replicate Phenom's campaign automation, so the campaign inventory is delivered as a rebuild reference for the customer's admin.

Phenom User and group management via SCIM exports users, group assignments, and role associations. We match Phenom users to Recruit CRM users by email. The customer's Recruit CRM admin provisions the destination users before migration so OwnerId references resolve at import time. Inactive Phenom users migrate with inactive status in Recruit CRM to preserve historical assignment.

FitScore numeric values export as a custom field on the candidate record in Recruit CRM. The underlying skills, experience, and qualifications that drive the score export as structured fields mapped to Recruit CRM custom fields. Recruit CRM does not generate AI matching scores natively; the exported skills data provides the basis for manual or third-party re-matching on the destination. We flag every candidate with a FitScore value in the migration manifest for customer review.

The Prediction API exports predicted skills generated at candidate intake from job titles and provided skill sets. These are stored as structured attributes against candidate profiles. We export predicted skill mappings and map them to Recruit CRM custom fields on the candidate record. Predicted skills are not automatically applied to new job matching on the destination; the customer's admin uses them as reference data during candidate review.