HRMS migration
Field-level mapping, validation, and rollback between 100Hires and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
100Hires
Source
Zoho Recruit
Destination
Compatibility
11 of 12
objects map 1:1 between 100Hires and Zoho Recruit.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from 100Hires to Zoho Recruit is a platform consolidation for small teams that have outgrown the free tier or need deeper Zoho ecosystem integration. 100Hires organizes hiring around Jobs, Candidates, and Applications where each Application links a Candidate to a Job and flows through pipeline stages. Zoho Recruit uses a modular schema with separate Candidates, Job Openings, Clients, Contacts, and Interviews modules. We migrate the full object set (Candidates, Jobs, Applications, Interviews, Evaluations, Notes, Attachments, Skills, Departments, Locations, and Email Templates) and resolve the Application-to-pipeline mapping by creating Zoho Job Opening records first, then populating the Candidate pipeline with stage assignments and timestamps. We flag Nurture Campaigns as paused-at-export and deliver campaign definitions for re-activation in Zoho Recruit. Workflows, automations, and Reports do not migrate; we provide a written inventory of these for the customer's admin to rebuild in Zoho Recruit.
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 100Hires 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.
100Hires
Job
Zoho Recruit
Job Opening
1:1100Hires Job records map to Zoho Recruit Job Opening. We extract job title, description (HTML), department, location, pipeline stage definitions, and posting status. The Zoho Job Opening is created first in migration order so that its JobOpeningID is available as a lookup target when Application records are inserted. Job Opening status (Open, On Hold, Closed) maps directly from 100Hires posting status.
100Hires
Candidate
Zoho Recruit
Candidate
1:1100Hires Candidate records map to Zoho Recruit Candidate. Standard fields (name, email, phone, work history, skills from taxonomy) map directly. Any custom Candidate properties on 100Hires require field creation in Zoho Recruit before import; custom fields are not available in Zoho Recruit's Free Edition so we confirm the customer's Zoho Recruit edition during scoping. Last Name is a mandatory field in Zoho Recruit; Candidates without a last name in 100Hires receive a Last Name value of 'Not Provided' during import.
100Hires
Application
Zoho Recruit
Candidate (pipeline stage assignment)
lossy100Hires Application records link a Candidate to a Job and track pipeline stage progression with timestamps and rejection reasons. In Zoho Recruit there is no standalone Application object; the pipeline state is tracked as a stage assignment on the Candidate record tied to a specific Job Opening. We map 100Hires Application stage history to Zoho Candidate stage fields (Current Status, Job Applied For) and create stage transition records where Zoho supports them. The Application's disqualification reason migrates to the Candidate's rejection reason field.
100Hires
Interview
Zoho Recruit
Interview
1:1100Hires Interview records (scheduled date/time, interviewer User, interview type, calendar integration status) map to Zoho Recruit Interview. We preserve the Application and Candidate associations by resolving Candidate and Job Opening IDs at migration time. Interviewer assignment migrates by matching 100Hires User emails to Zoho Recruit User records.
100Hires
Evaluation
Zoho Recruit
Assessment
1:1100Hires custom evaluation scorecards attached to Interviews map to Zoho Recruit Assessment. 100Hires allows custom evaluation forms per interview type with variable rubrics (1-5 scale, pass/fail, or custom criteria). We export form definitions and all submitted scores but flag any custom scoring rubric that cannot map directly to Zoho's Assessment structure. The pre-migration audit produces a scorecard mapping table for the customer to confirm before Assessment records are inserted.
100Hires
Note
Zoho Recruit
Notes
1:1100Hires free-text Notes attached to Candidates or Applications map to Zoho Recruit Notes. Note body, author (User), and creation timestamp migrate directly. Author mapping resolves by matching 100Hires User email to Zoho Recruit User. Notes with no author receive the migration service account as creator.
100Hires
Message
Zoho Recruit
Candidate (email thread)
1:1100Hires Message records (email conversations tied to Candidates or Applications) migrate as email thread content on the Zoho Candidate record. We export message content and metadata (sent date, sender, recipient). Thread ordering is preserved by date. External email threads that originated in Gmail or LinkedIn and were imported into 100Hires via the Chrome extension may have truncated header information; we flag these for manual review post-migration.
100Hires
User
Zoho Recruit
User
1:1100Hires User records (recruiters and team members) map to Zoho Recruit Users. We resolve by email match. Zoho Recruit imposes a constraint: users who already have a separate Zoho Recruit account cannot be migrated and must close their individual Zoho Recruit account before their records can be imported into the company account. We identify these conflicts during the pre-migration audit and escalate to the customer's admin for resolution before migration begins.
100Hires
Attachment
Zoho Recruit
Candidate (attachment)
1:1100Hires Attachments (resumes, cover letters, portfolio files) linked to Candidates or Applications migrate as Zoho Recruit Candidate attachments. Binary files are downloaded and re-uploaded with filenames preserved and parent record associations intact. Zoho Recruit Enterprise edition includes Document Library with folder sharing and file versioning; lower editions support basic attachment linking. We confirm the customer's Zoho Recruit edition before setting attachment targets.
100Hires
Taxonomy (Skills, Departments, Locations)
Zoho Recruit
Skills, Departments, Locations
1:1100Hires maintains structured taxonomy lists for Skills, Departments, and Locations. We export these as flat lists and map them to Zoho Recruit equivalent taxonomy objects. Skills map to Zoho Recruit Skills. Departments map to Zoho Recruit Departments. Locations map to Zoho Recruit Locations or Job Opening location fields. Any taxonomy value with no Zoho Recruit equivalent is flagged in the pre-migration audit for the customer to confirm before import.
100Hires
Nurture Campaign
Zoho Recruit
Campaign
1:1100Hires Nurture Campaigns (automated email sequences to Candidates) migrate as Zoho Recruit Campaign records with step definitions and email template references documented for manual re-activation. Active in-flight campaigns cannot be safely migrated mid-sequence because recipient opt-out states and delivery timestamps are tightly coupled to 100Hires' email infrastructure. We export campaign names, step definitions, and email template content as a written handoff document. The customer confirms email consent records for all recipients before re-activating sequences in Zoho Recruit.
100Hires
Email Template
Zoho Recruit
Email Template
1:1100Hires Email Templates (body content, subject lines, placeholder tokens) migrate as Zoho Recruit Email Templates. We export templates as raw text with token syntax preserved, requiring the destination to parse and re-apply dynamic field mappings for Zoho Recruit's template variable syntax. Template assignment to specific Jobs or Candidates requires manual re-configuration post-import.
| 100Hires | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Job | Job Opening1:1 | Fully supported | |
| Candidate | Candidate1:1 | Fully supported | |
| Application | Candidate (pipeline stage assignment)lossy | Fully supported | |
| Interview | Interview1:1 | Fully supported | |
| Evaluation | Assessment1:1 | Fully supported | |
| Note | Notes1:1 | Fully supported | |
| Message | Candidate (email thread)1:1 | Fully supported | |
| User | User1:1 | Fully supported | |
| Attachment | Candidate (attachment)1:1 | Fully supported | |
| Taxonomy (Skills, Departments, Locations) | Skills, Departments, Locations1:1 | Mapping required | |
| Nurture Campaign | Campaign1:1 | Fully supported | |
| Email Template | Email Template1: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.
100Hires gotchas
Free tier candidate cap resets monthly and limits pipeline stages
Email nurture campaigns cannot be exported mid-flight
Custom evaluation forms require manual schema alignment
Chrome extension imports may duplicate Candidate records
Career Site public URL is not transferable across accounts
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 Zoho Recruit edition confirmation
We audit the source 100Hires account across tier (Free/Start/Advanced/Enterprise), active job count, candidate volume, application history depth, custom evaluation forms, active Nurture Campaigns, and user count. We pair this with confirmation of the customer's Zoho Recruit edition (Forever Free/Standard/Professional/Enterprise) to identify any field-migration constraints, particularly custom field limits (50/module on Standard, 300/module on Professional and Enterprise) and availability (custom fields absent on Free Edition). The discovery output is a written migration scope document listing all objects, record counts, and any blocking constraints.
Pre-migration data extraction and deduplication
We extract all 100Hires data modules in CSV format: Jobs, Candidates, Applications, Interviews, Evaluations, Notes, Attachments (as binary files with parent record metadata), Users, Skills/Departments/Locations taxonomy, Nurture Campaign definitions, and Email Templates. We run a deduplication pass on Candidate email addresses to resolve duplicates created by the 100Hires Chrome extension. We flag any candidate records missing mandatory Zoho Recruit fields (Last Name required) for value assignment before import. We also identify any 100Hires Users who already have a separate Zoho Recruit account and escalate to the customer for account closure before migration proceeds.
Zoho Recruit schema preparation and field mapping
We create any custom fields required in Zoho Recruit to receive 100Hires custom Candidate properties. We confirm field limits against the target edition and split custom fields across modules if per-module limits are approached. We create the field mapping document pairing each 100Hires field to its Zoho Recruit equivalent, documenting transformation rules (e.g., 100Hires Last Name 'Not Provided' substitution, pipeline stage name normalization). We map 100Hires Application pipeline stages to Zoho Candidate stage values and create the corresponding Job Opening pipeline configurations in Zoho Recruit before any Candidate data is inserted.
Sandbox import and reconciliation
We run a full migration into a Zoho Recruit sandbox or trial account using production-like data volume. The customer's team reconciles record counts (Candidates in, Job Openings in, Interviews in, Evaluations in), spot-checks 25-50 random Candidate records against the 100Hires source, and reviews the evaluation scorecard mapping. Any field mapping corrections are documented and applied before the production migration begins. This step also validates that the Zoho Recruit edition's field limits and custom field availability match what was confirmed in discovery.
Production migration in dependency order
We run production migration in record-dependency order: Job Openings first (so their IDs are available as lookup targets), then Skills/Departments/Locations taxonomy, then Candidates (with deduplication pass applied), then Interviews (with Candidate and Job Opening lookups resolved), then Evaluations (with Interview references resolved), then Notes, then Attachments (binary re-upload with parent record association). Nurture Campaign definitions and Email Template content are delivered as a written handoff document for manual re-activation and re-configuration in Zoho Recruit. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation rebuild handoff
We freeze 100Hires writes during cutover, run a final delta migration of any records modified during the migration window, then enable Zoho Recruit as the system of record. We deliver the Nurture Campaign and Email Template handoff document, the evaluation scorecard mapping table, and a written inventory of any 100Hires Workflows or automation rules that cannot migrate to Zoho Recruit's Workflow Rules or Blueprint model. We support a one-week hypercare window for reconciliation issues. Workflow rebuilds, Campaign sequence re-activation, and Career Site URL updates are outside standard migration scope and require a separate engagement or internal admin task.
Platform deep dives
100Hires
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 100Hires 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
100Hires: Not publicly documented on the official API reference page.
Data volume sensitivity
100Hires 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 100Hires to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your 100Hires 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 100Hires
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.