Migrate from Unatrix to Crelate

Unatrix Candidate records map directly to Crelate Contact records. Standard fields (name, email, phone, address, current_title, current_company) migrate 1:1 using Crelate's API v3 Contact endpoint. Unatrix custom properties on Candidate migrate to Crelate custom fields on Contact, which we pre-create during the schema design phase with matching field types (text, numeric, picklist, date). Active versus inactive status is preserved as a Contact status value. Candidate source attribution and tags migrate as Crelate tags under the Default category or a custom tag category.

Unatrix Qualifications are extracted skill and competence tags attached to Candidate records using a tenant-specific taxonomy. During scoping we discover the full taxonomy (skill names, categories, hierarchy depth) and build a normalization map to Crelate's tag structure. Each Unatrix qualification category becomes a Crelate tag category; qualification names become tag values. High-frequency qualifications that require structured reporting migrate as custom picklist fields on Contact rather than tags. The mapping is validated by sampling 25 Candidate records across different sourcing channels before bulk migration.

Unatrix Client records (representing companies or organizations as the CRM counterpart to Candidates) map to Crelate Company records. Company name, website, industry, size, address, and contact information migrate 1:1. Unatrix custom fields on Client migrate to Crelate custom fields on Company. Client status (active, inactive, prospect) maps to Crelate Company status. The Client-to-Job relationship is preserved as a tag or custom field on the Job/Opportunity during the subsequent import phase.

Unatrix Job records (representing open positions or requisitions) map to Crelate Opportunity records. Job name becomes Opportunity name; job description and requirements migrate as Opportunity description fields or custom fields. Job status (open, filled, closed, on hold) maps to Crelate Opportunity stage values, with the mapping defined during schema design. Required qualifications from the Job record migrate as tags on the Opportunity to support Crelate's search and filter functionality. Job-to-Client linkage (the parent organization for the requisition) resolves to the Company record created during the Company migration phase.

Unatrix Project is the staffing engagement object that ties a Candidate to a Job under a Client, capturing placement metrics and performance data. Crelate has no native Project object. We map Unatrix Projects to Crelate Opportunities using a split strategy: the core engagement metadata (client, job, candidate, placement date, fee, status) migrates as Opportunity fields and tags, and any extended metrics (submittal-to-placement ratio, client satisfaction score, etc.) migrate as custom fields on the Opportunity. If a single Unatrix Project links multiple Candidates to a single Job, each engagement creates a separate Opportunity with a shared custom field referencing the original Project ID for audit traceability.

Unatrix Interview schedules and team events (date ranges, assigned team members, location, status) migrate to Crelate Event records. The interview type and status map to Crelate Event custom fields or tags. Attendee mapping links to EventRelation records pointing to the resolved Contact (Candidate) and User (team member). Cancelled or rescheduled interviews migrate with their original timestamps and a status tag to preserve the scheduling history that recruiters reference during placement audits.

CVs and attachments stored against Unatrix Candidate records are extracted where accessible via the Unatrix REST API. We migrate document references (file name, upload date, file size, mime type) and associate them with the corresponding Crelate Contact record. Binary file content (PDF, DOCX) requires separate file handling: we extract the document references and store them in a designated location with a manifest mapping each file to its destination Contact ID. The Crelate Contact record carries a custom field document_reference__c pointing to the file location. CV parsing for skills extraction is not repeated in Crelate because the qualification normalization step covers that work.

Unatrix User accounts (sales managers, recruiters, administrators) map to Crelate User records by email match. Role-based permissions (recruiter, sales manager, admin) migrate as Crelate User Role assignments. Active versus inactive status is preserved to ensure that records owned by inactive users remain accessible in Crelate. We resolve users by email; any Unatrix User without a matching Crelate User goes to a reconciliation queue for the customer to provision before record migration resumes.

Unatrix supports custom fields on Candidate and Job objects, and an elaborate tagging system for qualifications. During discovery we identify every custom field definition in the source tenant, classify each by data type (text, numeric, date, picklist, boolean), and pre-create matching custom fields in Crelate on the appropriate core record (Contact for Candidate fields, Opportunity for Job fields, Company for Client fields). Picklist values from Unatrix migrate as Crelate picklist options. Boolean flags migrate as Crelate checkbox fields. Tag categories from Unatrix migrate as Crelate tag categories with the same names.

Unatrix KPI dashboards and report configurations are generated from raw placement data and do not export as self-contained objects. We do not migrate them. We migrate the underlying data records (Candidates, Jobs, Projects, engagement history) so that Crelate's native reporting can generate equivalent metrics post-migration. The customer receives a written list of Unatrix KPI definitions (placement rate, cost-per-hire, time-per-hire) mapped to Crelate reporting fields so their admin can rebuild dashboards in Crelate Analytics.

Unatrix tracks placement outcomes (candidate placed, job filled, start date, fee charged) as part of the Project record. We extract placement events and create Crelate Task records with TaskSubtype=Placement or a custom Activity type tag, linked to the Opportunity and Contact. Placement date and fee migrate as custom fields on the Task. This preserves the historical pipeline activity that staffing agencies use for revenue attribution and client reporting.

Unatrix preserves recruiter search history and match preferences as part of its Candidate-to-Job matching workflow. These are not standard API-exportable fields but represent valuable recruiter knowledge. We extract available match scores and saved search criteria where accessible via the REST API and store them as custom fields or tags on the Contact record (candidate_search_score__c, saved_search_criteria__c) so that the matching context is not entirely lost in the migration.