HRMS migration
Field-level mapping, validation, and rollback between Unatrix and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Unatrix
Source
Zoho Recruit
Destination
Compatibility
9 of 12
objects map 1:1 between Unatrix and Zoho Recruit.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Unatrix combines ATS and CRM in a unified schema built around Candidates, Clients, Jobs, and Projects, with skills auto-extracted from CVs using a tenant-specific qualification taxonomy. Zoho Recruit separates these into standard ATS modules (Candidates, Job Openings, Clients, Interviews) with skill tagging managed through its own configurable fields. The structural difference that most affects migration is Unatrix's Project object, which has no native equivalent in Zoho Recruit and must be mapped to either a Custom Module or a Deal with structured custom fields. We coordinate a manual data export with Unatrix support since no bulk export API is publicly documented, then sequence the import starting with Users, then Candidates, then Clients, then Job Openings, preserving the Candidate-to-Job link through the Application junction object. Custom fields and skill taxonomy discovered during discovery are normalized against Zoho Recruit's field types before any data loads. Workflows, automations, and KPI dashboards do not migrate; we deliver a written inventory of these for the customer's admin to rebuild in Zoho Recruit's workflow builder.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Unatrix object lands in Zoho Recruit, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Unatrix
Users and Team Members
Zoho Recruit
Users
1:1Unatrix User records map to Zoho Recruit Users. We resolve by email match against the destination Zoho Recruit org's User table. Zoho Recruit requires at least two users in the destination account before migration can proceed. Users with an existing separate Zoho Recruit account must close that account before import; we flag these during scoping. Active versus inactive status, role assignments, and department hierarchy migrate as profile and role settings in Zoho Recruit.
Unatrix
Clients
Zoho Recruit
Clients
1:1Unatrix Client records map directly to Zoho Recruit Clients module. Client name, address, industry, website, and contact information transfer to the corresponding Zoho Recruit fields. The Client record must exist in Zoho Recruit before Job Openings that reference it can be imported, enforcing the Clients-first sequencing rule. Client-specific metadata (billing contact, contract terms stored in Unatrix custom fields) maps to Zoho Recruit custom fields configured during schema discovery.
Unatrix
Candidates
Zoho Recruit
Candidates
1:1Unatrix Candidate records map to Zoho Recruit Candidates. Standard fields (name, email, phone, current title, location) transfer 1:1. Zoho Recruit requires Last Name as a mandatory field for all Candidate imports; records without a Last Name value must be set to 'Not Provided' or a similar placeholder before import. We extract skills and qualifications from Unatrix and map them to Zoho Recruit's Candidate Skills section, applying the normalization map built during discovery.
Unatrix
Qualifications
Zoho Recruit
Candidate Skills
lossyUnatrix Qualifications are extracted from CVs and tagged using a tenant-specific taxonomy that varies between organizations. Zoho Recruit uses a configurable Skills field on the Candidate object without a mandatory hierarchy. During discovery we extract the full Unatrix qualification taxonomy (skill names, categories, and any hierarchical relationships), then build a normalization map that collapses the tenant taxonomy to flat skill tags in Zoho Recruit. Skills that have no equivalent in the destination become custom Candidate fields if the customer requests preservation.
Unatrix
Jobs
Zoho Recruit
Job Openings
1:1Unatrix Job records map to Zoho Recruit Job Openings. Job title, description, requirements, status, and assigned Client reference transfer to the corresponding Zoho Recruit fields. The Job-to-Client link is preserved through the Client Lookup field in Zoho Recruit, which requires the Client record to be imported first. Job status (open, filled, closed) maps to Zoho Recruit's Job Opening status field. Required qualifications on the Job are mapped to the Job Opening's skill requirements using the same normalization map applied to Candidate skills.
Unatrix
Projects
Zoho Recruit
Custom Module or Deal with Custom Fields
1:manyUnatrix Projects represent staffing engagements linking Candidates to Jobs under a Client, with placement metrics and performance data. Zoho Recruit has no native Project object, so we map this to a Custom Module (Enterprise tier) with custom fields for engagement metadata, or to a Deal with structured custom fields (Standard tier). The Project-Candidate-Job relationship is preserved as junction records in the Custom Module or as linked Deal-Candidate associations. We document the chosen structure during scoping and the customer's Zoho Recruit edition determines which approach applies.
Unatrix
Applications (Candidate-to-Job links)
Zoho Recruit
Applications
1:1Unatrix tracks candidate applications linking a Candidate to a Job through the Project engagement. Zoho Recruit has a native Application record that links Candidate to Job Opening with status (new, screening, interview, offer, hired, rejected) and submission date. We map Unatrix application records to Zoho Recruit Applications using Candidate email and Job reference as the dedupe key. Application status maps to the nearest Zoho Recruit Application status value; custom status stages in Unatrix require configuration in Zoho Recruit before import.
Unatrix
Interviews and Events
Zoho Recruit
Interviews
1:1Unatrix interview schedules with date ranges and assigned team members map to Zoho Recruit Interviews. Interview type (phone, video, onsite), scheduled date and time, interviewer assignment, and location transfer to the corresponding Zoho Recruit fields. We resolve interviewer assignments by email match to Zoho Recruit Users. Candidate and Job Opening references on the Interview link back to the migrated records via Lookup resolution.
Unatrix
Notes and Tasks
Zoho Recruit
Notes and Tasks
1:1Unatrix notes attached to Candidate, Job, or Client records migrate to Zoho Recruit Notes. We preserve the note body, author, created date, and the parent record reference. Tasks assigned to team members migrate to Zoho Recruit Tasks with Status (open, completed), Priority, Due Date, and Assigned To resolved by email match to Users. Notes and Tasks import after the parent record (Candidate, Job, Client) is confirmed in Zoho Recruit to satisfy Lookup requirements.
Unatrix
Documents (CVs and Attachments)
Zoho Recruit
Attachments
1:1Unatrix CVs and attachments stored against Candidate records are extracted as binary files. We migrate file names, content where accessible via the Unatrix REST API, and the Candidate association. Files are uploaded to Zoho Recruit's Document Library and linked to the corresponding Candidate record via Attachment records. Large binary file sets require chunked upload handling; we flag this during scoping if the candidate database includes a high volume of attachments.
Unatrix
Tags and Custom Fields
Zoho Recruit
Custom Fields
lossyUnatrix custom fields on Candidate and Job objects and the tagging system for qualifications are tenant-specific. We identify all custom field schemas during discovery, map them to Zoho Recruit custom fields of the equivalent type (text, number, date, picklist, checkbox), and configure the destination schema before data import. Zoho Recruit Standard tier supports up to 50 custom fields per module; Enterprise supports 300 per module. We flag any schema that exceeds the destination tier's limit for discussion before migration proceeds.
Unatrix
KPIs and Reports
Zoho Recruit
Reports and Dashboards
1:1Unatrix KPI dashboards and report configurations are generated from raw data and do not export as self-contained objects. We do not migrate these. We extract the underlying data records (Candidates, Jobs, Applications, placement metrics) so that equivalent reports can be rebuilt in Zoho Recruit's Standard Reports (included in Standard and Enterprise tiers) or Advanced Analytics with Zoho Analytics (Enterprise tier add-on). We deliver a written report inventory listing every Unatrix report with its data sources and recommended Zoho Recruit equivalent.
| Unatrix | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Users and Team Members | Users1:1 | Mapping required | |
| Clients | Clients1:1 | Fully supported | |
| Candidates | Candidates1:1 | Fully supported | |
| Qualifications | Candidate Skillslossy | Mapping required | |
| Jobs | Job Openings1:1 | Fully supported | |
| Projects | Custom Module or Deal with Custom Fields1:many | Mapping required | |
| Applications (Candidate-to-Job links) | Applications1:1 | Fully supported | |
| Interviews and Events | Interviews1:1 | Mapping required | |
| Notes and Tasks | Notes and Tasks1:1 | Fully supported | |
| Documents (CVs and Attachments) | Attachments1:1 | Mapping required | |
| Tags and Custom Fields | Custom Fieldslossy | Mapping required | |
| KPIs and Reports | Reports and Dashboards1:1 | Not supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Unatrix gotchas
No documented bulk export API endpoint
Qualification taxonomy is tenant-specific
Project object is not a standard CRM concept
Zoho Recruit gotchas
Daily API rate limits are tier-gated and per-user capped
User import hard cap of 2,000 records
Attachment folder hierarchy must be preserved exactly
Resume parsing quota varies by plan and resets daily
Custom fields unavailable in Free and Standard editions
Pair-specific challenges
Migration approach
Discovery and export coordination with Unatrix
We audit the Unatrix tenant across all objects (Candidates, Clients, Jobs, Projects, Qualifications, Users, Interviews, Notes, Tasks, Documents) and extract a full data inventory including record counts, custom field schemas, skill taxonomy structure, and any configured automations or reports. Since Unatrix has no documented bulk export API, we coordinate a manual export request with Unatrix support, define the export format (CSV or XML), and validate record counts against the data inventory before proceeding to transformation.
Zoho Recruit edition assessment and schema design
We assess the customer's target Zoho Recruit edition (Free, Standard at $25/user/month, or Enterprise) based on record volume, custom field count, and workflow requirements. We design the destination schema including custom fields (mapped from Unatrix custom fields and skill taxonomy), any Custom Module required for the Project object (Enterprise tier only), Job Opening Record Types if multiple hiring pipelines exist, and the skill normalization map for Qualifications. Schema is validated in a Zoho Recruit sandbox or trial account before production migration.
Transformation and normalization
We transform the Unatrix export data into Zoho Recruit CSV import format. This includes applying the qualification normalization map to all Candidate skill tags, splitting Project engagement data into the destination structure (Custom Module or Deal with custom fields), setting placeholder values for mandatory fields (Last Name) where Unatrix records lack them, and resolving any data type mismatches. The transformation output is a set of module-specific CSV files ready for Zoho Recruit's import wizard.
Sandbox migration and reconciliation
We run a full migration into the customer's Zoho Recruit trial or sandbox account using production-like data volume. The customer's team reconciles record counts against the Unatrix source, spot-checks 25-50 random records for field-level accuracy, and validates the Project-to-Custom-Module or Project-to-Deal mapping. Any transformation corrections happen here before production migration begins. Zoho Recruit's own migration tool can be used as a secondary validation step.
Production migration in dependency order
We run production migration following Zoho Recruit's recommended order: Users first (with the two-user minimum satisfied), then Candidates, then Clients, then Job Openings, then Applications (Candidate-to-Job links), then Interviews, Notes, and Tasks, then Document attachments, and finally the Project mapping (Custom Module or Deal). Each phase emits a row-count reconciliation report. Projects and engagement metadata are loaded last because they often have lookups to migrated Candidate, Job, and Client records.
Cutover, validation, and automation handoff
We freeze Unatrix writes during cutover, run a final delta migration of records modified during the migration window, then enable Zoho Recruit as the system of record. We deliver the workflow and report inventory document for the customer's admin to rebuild in Zoho Recruit Workflow Rules and Reports. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild Unatrix automations inside the migration scope; that work is handled by the customer's admin or a Zoho partner.
Platform deep dives
Unatrix
Source
Strengths
Weaknesses
Zoho Recruit
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Unatrix and Zoho Recruit.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Unatrix: Not publicly documented.
Data volume sensitivity
Unatrix doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Unatrix to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Unatrix to Zoho Recruit migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Unatrix
Other ways to arrive at Zoho Recruit
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.