Migrate from Phenom to Crelate

Phenom Candidates map directly to Crelate Contacts. We export the full Candidate record including standard properties (name, email, phone, address) and all Additional Fields (Phenom's tenant-specific custom attributes). During import, each Additional Field is created as a Crelate custom field on Contact via Settings | Core Records | Contacts, matching the original field type (Text, Number, Picklist, Date, etc.) and preserving the Logical Name for API access. The Crelate Contact's primary phone, email, and address fields are populated from the Candidate's corresponding properties.

Phenom Jobs map to Crelate Job records. We export active and historical job postings including title, description, location data, department, employment type, and job requirements. Job status (Open, Closed, Draft) maps to Crelate's Job status field. Multi-location jobs are exported as separate Job records per location and linked via the job's parent identifier.

Phenom Applications link a Candidate to a Job and include status, stage progression, timestamps, and source tracking. We export the full application record and import it as a Crelate Application linked to the migrated Contact and Job records. Application status (Applied, Screening, Interviewing, Offer, Hired, Rejected) maps to Crelate's application status values. We preserve stage timestamps and source attribution fields.

Phenom Employee Profiles (accessible via Employee Profile APIs) include preferences, skills data, and tenure information. We export the full employee profile and map it to a Crelate Contact record with a custom employee-type flag field. Skills data migrates to a Crelate custom field or tag set depending on whether the customer wants skills as structured picklist values or free-text tags. Employee record migration is scoped separately from candidate migration since the employee profile schema is distinct.

Phenom Tag Management APIs export all tag assignments per candidate. Crelate's API supports Tags on various record types with a key per tag category. We export the complete tag vocabulary (all tag names per category) and recreate it in Crelate, then link each Contact to its original tags during migration. Tags used for source attribution, clearance levels, or skills classification migrate as Crelate Tags on the Contact record.

Phenom Additional Fields represent tenant-specific custom attributes on candidate profiles. The Candidates API exposes these as a structured payload per candidate. We export every unique Additional Field definition (name, type, options for picklists) and pre-create matching custom fields in Crelate under Settings | Core Records | Contacts before any Contact data is loaded. Field types map: Phenom Text to Crelate Short Answer, Phenom Number to Crelate Numeric, Phenom Picklist to Crelate Picklist, and Phenom Date to Crelate Date.

Phenom Projects contain multiple Statuses defining candidate progression through a workflow. We export the complete workflow topology including stage names, ordering, and any conditional routing metadata documented in the Phenom Knowledgebase. Crelate Recruiting Workflows are configured via Settings | Workflows and require manual setup of each stage, entry criteria, and automation triggers. We deliver a written workflow mapping document that maps each Phenom Project to a Crelate Workflow with stage-to-stage correspondence. Conditional routing logic is documented as a rebuild requirement for the customer's Crelate admin.

FitScore is Phenom's proprietary AI-generated candidate-to-job compatibility score built on its skills ontology. Crelate has no direct FitScore equivalent; the nearest feature is the AI Co-Pilot introduced in 2025 (Business Plus and Enterprise). We export every Candidate record carrying a FitScore value and preserve the score as a custom field (fit_score__c) on the migrated Crelate Contact, along with the underlying skills and qualification fields that drove the score. We document which migrated candidates have FitScore history so the customer can evaluate Crelate Co-Pilot re-matching post-implementation.

Phenom Campaign APIs manage one-to-many candidate outreach sequences. We export campaign structure, template content, and send history metadata. Individual email and SMS message logs (send timestamp, recipient, template used) migrate as Activity records (tasks) on the Contact. Active campaign sequences (cadences) do not have a Crelate equivalent at the Automation level; we document the campaign structure in a written handoff so the customer can rebuild outreach sequences in Crelate's Automation and Sequencing feature (Business Plus tier).

Phenom Communication APIs export individual email and SMS messages, call logs, meeting records, and notes attached to candidates. We map call engagements to Crelate Activities with a call-type flag, emails to activities with email-type flag, meetings to activities with meeting-type flag, and notes to Crelate Note records linked via the Contact. Activity timestamps and subject lines preserve the original Phenom engagement date and description. This migration uses Crelate's REST API with activity creation endpoints and respects the 60 RPM rate limit on the Business plan.

Phenom User and Group Management APIs (SCIM-based) export users, group assignments, and role associations. We match Phenom users to Crelate users by email address. Any Phenom user without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before Contact import resumes. Role and group assignments are documented as Crelate User Role and Permission Set mappings for post-migration configuration.

The Phenom Prediction API predicts skills based on job titles and provided skill sets, storing predicted skills against candidate profiles. We export all predicted skill mappings and either map them to a Crelate custom multi-select picklist field (predicted_skills__c) or as Tags on the Contact depending on the customer's preference for structured vs. free-text skill data. Predicted skills are AI-generated by Phenom and do not have a native Crelate equivalent; we preserve them as data rather than as active matching logic.