HRMS migration
Field-level mapping, validation, and rollback between Recruitee and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Recruitee
Source
Zoho Recruit
Destination
Compatibility
11 of 12
objects map 1:1 between Recruitee and Zoho Recruit.
Complexity
BStandard
Timeline
4-6 weeks
Overview
Moving from Recruitee to Zoho Recruit is a schema-stability migration because Recruitee's pipeline stages are customizable per Job, while Zoho Recruit uses a single hiring pipeline per Job Opening. We extract each pipeline's stage order and criteria during discovery, configure Zoho Recruit stage picklists to match, and map candidate-application relationships across. Scorecard data from Recruitee embeds attribute-level ratings inside application activity rather than as standalone records; we serialize each scorecard as a structured note with parseable attribute-rating pairs so historical evaluation data survives the migration. We flag the Last Name mandatory field constraint immediately since Recruitee's candidate model does not enforce this, and we pre-populate missing values as 'not provided' before any Zoho Recruit import attempt. Workflow automations, CareersHub career site content, and stage configurations do not migrate as code; we deliver a written inventory of automation logic for your team to rebuild in Zoho Recruit Workflow Rules and a CareersHub content archive for manual republishing.
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 Recruitee 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.
Recruitee
Job
Zoho Recruit
Job Opening
1:1Recruitee Jobs map to Zoho Recruit Job Openings with title, department, location, and status preserved. Recruitee's Start plan 5-job-active limit is a migration-scoping constraint; we count active jobs before migration and recommend upgrading to Zoho Recruit Standard (10 active jobs per recruiter license) if job volume exceeds the limit. Job status (active, paused, closed) maps directly to Zoho Recruit status. Each Recruitee job may carry a distinct pipeline with its own stage order; we extract stage configurations per job and configure Zoho Recruit stage picklists before import.
Recruitee
Candidate
Zoho Recruit
Candidate
1:1Recruitee Candidates map to Zoho Recruit Candidates with name, email, phone, social profiles, and source attribution preserved. Critical migration constraint: Zoho Recruit requires Last Name as a mandatory field; Recruitee's candidate model does not enforce this. We pre-scan candidate records, populate missing Last Name values as 'not provided' before import, and flag records with no email address for manual review since Zoho Recruit uses email as a primary deduplication key.
Recruitee
Application
Zoho Recruit
Job Application
1:1Recruitee Applications link a Candidate to a Job with a specific stage and timestamp. We preserve this relationship in Zoho Recruit by resolving both the Candidate ID and Job Opening ID at migration time, then setting the application stage to the mapped Zoho Recruit stage. Application creation date migrates as a custom field or note since Zoho Recruit tracks application submission internally but does not expose the original submission timestamp as a standard field.
Recruitee
Pipeline Stage
Zoho Recruit
Hiring Pipeline Stage
lossyRecruitee's pipeline stages are customizable per Job, meaning the same stage name (for example, 'Phone Screen') can exist at different positions or with different criteria across pipelines. We extract every distinct pipeline-stage combination during discovery, group them by stage sequence, and configure Zoho Recruit's Hiring Pipeline stage picklist to include all unique stage names. Stage order is preserved via the pipeline configuration in Zoho Recruit.
Recruitee
Interview Scorecard
Zoho Recruit
Interview Feedback Form (serialized as Note)
1:1Recruitee interview scorecards store attribute-level ratings (for example, 'Technical Skills: Strong Yes') attached to a specific interviewer and timestamp, embedded in application activity rather than as standalone objects. Zoho Recruit's Interview Feedback Form module captures structured evaluations, but Recruitee's variable schema does not map directly. We serialize each scorecard as a structured note with parseable attribute-rating pairs (interviewer, date, attributes, overall recommendation) so historical evaluation data is preserved and searchable in Zoho Recruit even without native scorecard objects.
Recruitee
Talent Pool
Zoho Recruit
Candidate Tag + Candidate List
1:1Recruitee Talent Pools are organized candidate collections used for future roles. We migrate pool membership by mapping each pool name to a Zoho Recruit Candidate Tag and creating tag associations against the candidate records. Pool-level notes and tags attached to the pool itself migrate as structured notes on the first candidate in each pool with a reference to the pool name for rebuild.
Recruitee
Offer
Zoho Recruit
Offer Letter
1:1Recruitee Offer records include status, salary details, start date, and candidate linkage. We map these to Zoho Recruit Offer Letters with status, compensation details, and start date preserved. The offer-to-candidate relationship is maintained via the Zoho Recruit candidate record. Offer status history migrates as a custom note if the destination requires the full status timeline.
Recruitee
User (Team Member)
Zoho Recruit
User
1:1Recruitee User records include name, email, role, and department assignment. We map users to Zoho Recruit Users by email match. Zoho Recruit migration documentation states that users with an existing separate Zoho Recruit account cannot be migrated; they must close that account first. Recruiter and Hiring Manager roles in Recruitee map to Zoho Recruit standard roles; Admin maps to Zoho Recruit Administrator. Any user without a matching Zoho Recruit account goes to a reconciliation queue for your admin to provision before record import resumes.
Recruitee
Department
Zoho Recruit
Department
1:1Recruitee Departments are organizational units used to classify jobs and team members. We migrate department records and preserve the job-to-department linkage so reporting by department is consistent after migration. Zoho Recruit's Department Hierarchy feature is available from Standard tier onward.
Recruitee
Custom Field
Zoho Recruit
Custom Field
1:1Custom fields on Candidates, Jobs, and Applications require explicit field-level mapping to Zoho Recruit equivalents. We extract the full custom field list via Recruitee's API, map each to a Zoho Recruit custom field (50 per module on Standard, 300 on Professional/Enterprise), and create any missing fields in the destination before import. Field type mapping handles Recruitee's text, number, date, and dropdown types against Zoho Recruit's corresponding field types.
Recruitee
Attachment
Zoho Recruit
Attachment / Document
1:1File attachments (resumes, cover letters, portfolio items) stored in Recruitee's document store export as files with candidate ID metadata. We re-upload attachments to Zoho Recruit and link them to the corresponding candidate record using filename and candidate ID as the linking key. Zoho Recruit's document library, folder sharing, and file versioning are available from Standard tier onward.
Recruitee
Note and Activity History
Zoho Recruit
Note
1:1Recruitee Notes are free-text entries attached to candidate profiles. Activity history includes stage changes, emails sent, and interview events. We export notes with timestamp and author attribution and create Zoho Recruit Note records linked via ContentDocumentLink to the parent Candidate or Job Opening. Activity type (stage change, email, interview) is preserved as a structured note prefix for filtering in Zoho Recruit's notes interface.
| Recruitee | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Job | Job Opening1:1 | Fully supported | |
| Candidate | Candidate1:1 | Fully supported | |
| Application | Job Application1:1 | Fully supported | |
| Pipeline Stage | Hiring Pipeline Stagelossy | Fully supported | |
| Interview Scorecard | Interview Feedback Form (serialized as Note)1:1 | Fully supported | |
| Talent Pool | Candidate Tag + Candidate List1:1 | Fully supported | |
| Offer | Offer Letter1:1 | Fully supported | |
| User (Team Member) | User1:1 | Fully supported | |
| Department | Department1:1 | Fully supported | |
| Custom Field | Custom Field1:1 | Fully supported | |
| Attachment | Attachment / Document1:1 | Fully supported | |
| Note and Activity History | Note1:1 | Fully 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.
Recruitee gotchas
Start plan active job post limit constrains migration scope
Workflow automations are not exportable as portable data
Scorecard schemas vary by organization and require structured serialization
Parallel-run delta management during migration window is manual
CareersHub career site data requires separate export handling
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 migration scope audit
We audit Recruitee's source data across Jobs, Candidates, Applications, Talent Pools, Offers, pipeline stage configurations, custom fields, and user accounts. We extract candidate records with a pre-scan for missing Last Name values, identify all distinct pipeline stage names across jobs, count active jobs against Recruitee's plan limits, and inventory active workflow automations for the rebuild inventory document. We pair this with a Zoho Recruit edition assessment: Standard ($25/user/month) covers most migrations with 10 active jobs per recruiter license; Professional ($50/user/month) adds 250 active jobs and AI candidate matching; Enterprise ($75/user/month) adds 750 active jobs and custom roles. Discovery output is a written migration scope including the stage consolidation map and the mandatory-field remediation plan.
Zoho Recruit schema setup and stage configuration
We provision the destination schema in Zoho Recruit before any data import. This includes creating custom fields to match the Recruitee custom field inventory (within Zoho Recruit's per-module limits), configuring the unified Hiring Pipeline stage list from the extracted stage consolidation map, setting up departments matching Recruitee's organizational structure, and provisioning user accounts for each Recruitee team member. We configure departments before jobs, users before candidates, and job openings before applications to satisfy Zoho Recruit's dependency order. Schema setup occurs in a Zoho Recruit sandbox or staging environment first for validation.
Candidate pre-processing and mandatory-field remediation
We pre-process all candidate records before import. Missing Last Name values are populated as 'not provided'. Records missing both name and email are flagged for manual resolution. Duplicate email addresses are detected and the most recent Recruitee record is retained. Source attribution, social profiles, and custom candidate properties are mapped to their Zoho Recruit equivalents. Pre-processed candidate records are validated against Zoho Recruit's mandatory field requirements before the import file is generated.
Sandbox migration and reconciliation
We run a full migration into Zoho Recruit using a sandbox or the production account with a small subset of records. Candidate count, job opening count, application count, offer count, and talent pool membership are reconciled against the Recruitee source. We validate that stage mappings resolve correctly for applications across different pipelines. Scorecard serialization is spot-checked for parseable attribute-rating pairs. Your HR admin reviews the sandbox output and signs off before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Departments first, then Users (with email-match reconciliation for existing Zoho Recruit accounts), then Job Openings (with unified stage mapping), then Candidates (with mandatory-field remediation applied), then Applications (with stage resolution per job), then Offers, then Talent Pool membership (via tag associations), then Attachments (re-uploaded and linked by candidate ID), then Notes and Activity History. Each phase emits a row-count reconciliation report. Workflow automation logic is documented in a separate inventory file during this phase, not migrated.
Cutover, delta capture, and rebuild handoff
We freeze writes in Recruitee during cutover, run a final delta migration of any candidates, applications, or notes created during the migration window (typically 24-48 hours), and enable Zoho Recruit as the system of record. We deliver the workflow automation inventory document to your team for rebuild in Zoho Recruit Workflow Rules. We deliver the CareersHub content archive for manual republishing to Zoho Recruit's Branded Career Site. We support a one-week hypercare window where we resolve reconciliation issues raised during the first week of live operation.
Platform deep dives
Recruitee
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 Recruitee 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
Recruitee: Not publicly documented; estimated moderate limits based on plan tier.
Data volume sensitivity
Recruitee exposes a bulk API — large-volume migrations stream efficiently.
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 Recruitee to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Recruitee 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 Recruitee
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.