Migrate from Unatrix to Recruit CRM & ATS

Unatrix Clients (the CRM counterpart to Candidates, representing companies or organizations) map 1:1 to Recruit CRM Client records. The client name, industry, contact details, address, and status fields migrate directly. Client-to-Job relationships are preserved through the linking structure that Recruit CRM maintains natively between Clients and Job records.

Unatrix Job records (open positions or requisitions linked to a Client) map 1:1 to Recruit CRM Job records. Job status, description, required qualifications, salary range, and location fields migrate with standard field mapping. The Job-to-Client link is resolved by matching the Client external ID so the Recruit CRM relationship is satisfied at insert time.

Unatrix Candidate records (the core ATS object with profile information, qualifications, and application history) map 1:1 to Recruit CRM Candidate records. Standard profile fields (name, email, phone, location, experience, education) migrate directly. Active versus inactive status is preserved to maintain staffing pipeline continuity. Custom properties on the Candidate object are identified during discovery and mapped to Recruit CRM custom candidate fields.

Skills and qualifications auto-extracted from CVs in Unatrix using a tenant-specific taxonomy are normalized to Recruit CRM's skill objects during the transform phase. Each unique qualification name, category, and hierarchy from the tenant's taxonomy is mapped to a corresponding Recruit CRM skill tag. We build the full normalization map during discovery and validate it against a representative sample before full migration. The original Unatrix taxonomy value is preserved in a migration audit field alongside the normalized skill tag.

Unatrix Projects represent staffing engagements tying Candidates to Jobs under a Client, with placement performance metrics. Recruit CRM has no native Project object. We map each Unatrix Project to a Recruit CRM Deal record with the engagement metadata (project name, start date, end date, placement status, performance notes) stored as structured custom fields. The Project's linked Candidates and Jobs are stored as Deal-to-Candidate associations within Recruit CRM, preserving the full engagement context. This is the highest-complexity mapping in the migration and requires careful scoping during the discovery phase.

Unatrix interview schedules and team events with date ranges and assigned team members are extracted and mapped to Recruit CRM Activity or Event records linked to the corresponding Candidate and Job. Interview status, interviewer assignments, and outcome notes are preserved as structured fields. Where Recruit CRM's native event model does not fully capture Unatrix interview metadata, we extend the activity record with custom fields identified during schema mapping.

CVs and attachments stored against Unatrix Candidate records are extracted with their file names, content, and candidate associations. We preserve the file associations in Recruit CRM by linking uploaded documents to the migrated Candidate record. Binary files require separate file transfer; document content is associated via the Candidate's document library in Recruit CRM. Where the Unatrix REST API exposes document content directly, we include it in the migration package; if content requires a separate download step, we coordinate with the Unatrix support team to retrieve it.

Unatrix user accounts (sales managers, recruiters, and administrators with role-based permissions) are mapped to Recruit CRM users by email match. Active versus inactive status is preserved. Role and permission data from Unatrix is reviewed during discovery and translated into Recruit CRM's role model. Users without matching Recruit CRM accounts are held in a reconciliation queue for the customer's admin to provision before record import completes.

Unatrix supports custom fields on Candidate objects beyond the standard profile fields. We identify all custom field schemas during the discovery phase, map each to a corresponding Recruit CRM candidate custom field, and pre-create the destination schema before any data import. Multi-value tag fields from Unatrix migrate to multi-select picklist fields in Recruit CRM. The custom field definitions and their current values across all Candidate records are included in the migration scope.

Unatrix supports custom fields on Job objects for capturing job-specific attributes beyond standard fields. We identify the full Job custom field schema during discovery and map each to a corresponding Recruit CRM Job custom field. Pre-creation of the destination custom field schema happens before Job record import. Any picklist values used in Unatrix custom fields are translated to matching Recruit CRM picklist values or free-text fields as appropriate.

Unatrix KPI dashboards and report configurations are generated from underlying data and do not export as self-contained objects. We do not migrate KPI dashboards or report configurations. We do extract the raw data records (Candidate application counts, placement history, time-to-hire metrics) so that Recruit CRM's reporting tools can be configured by the customer's team post-migration to recreate the relevant metrics.