HRMS migration

Migrate from 100Hires to Zoho Recruit

Field-level mapping, validation, and rollback between 100Hires and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.

100Hires logo

100Hires

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

92%

11 of 12

objects map 1:1 between 100Hires and Zoho Recruit.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

100Hires logo

100Hires

What's pushing teams away

  • Limited customization for reporting and workflow configurations frustrates teams that need tailored pipelines or advanced analytics beyond default views.
  • Users in G2 reviews mention the color scheme and UI aesthetics feel dated compared to newer ATS competitors with modern design.
  • Teams scaling beyond 100 candidates/month outgrow the free tier quickly, and pricing for higher volumes is opaque without a sales conversation.
  • Some review mentions of occasional performance slowdowns when managing large candidate pools or running multiple simultaneous job campaigns.
  • Absence of a public enterprise pricing tier forces mid-market companies into sales cycles that delay purchasing decisions.

Choosing

Zoho Recruit logo

Zoho Recruit

What's pulling them in

  • Lowest cost entry point of any major ATS — a free tier with Candidates, Clients, Contacts, Interviews, and a career site lets small teams validate before committing to a paid plan.
  • Deep Zoho ecosystem integration — if the team already uses Zoho CRM, Sheets, or Analytics, candidate data flows between modules without re-keying or third-party middleware.
  • Customizable pipelines and stages — both agency and corporate editions let users define custom pipeline stages and assign candidates through drag-and-drop visual boards.
  • AI-assisted features via Zia — resume parsing, candidate summarization, and job-candidate matching are built in on paid tiers, reducing manual screening time.
  • Job board aggregation at no extra cost — paid tiers include postings to major job boards, extending reach without purchasing separate job ad bundles.

Object mapping

How 100Hires objects map to Zoho Recruit

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

maps to

Zoho Recruit

Job Opening

1:1
Fully supported

100Hires 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

maps to

Zoho Recruit

Candidate

1:1
Fully supported

100Hires 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

maps to

Zoho Recruit

Candidate (pipeline stage assignment)

lossy
Fully supported

100Hires 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

maps to

Zoho Recruit

Interview

1:1
Fully supported

100Hires 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

maps to

Zoho Recruit

Assessment

1:1
Fully supported

100Hires 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

maps to

Zoho Recruit

Notes

1:1
Fully supported

100Hires 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

maps to

Zoho Recruit

Candidate (email thread)

1:1
Fully supported

100Hires 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

maps to

Zoho Recruit

User

1:1
Fully supported

100Hires 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

maps to

Zoho Recruit

Candidate (attachment)

1:1
Fully supported

100Hires 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)

maps to

Zoho Recruit

Skills, Departments, Locations

1:1
Mapping required

100Hires 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

maps to

Zoho Recruit

Campaign

1:1
Fully supported

100Hires 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

maps to

Zoho Recruit

Email Template

1:1
Fully supported

100Hires 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.

Gotchas + challenges

What specifically takes care here

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 logo

100Hires gotchas

Medium

Free tier candidate cap resets monthly and limits pipeline stages

Medium

Email nurture campaigns cannot be exported mid-flight

Low

Custom evaluation forms require manual schema alignment

Low

Chrome extension imports may duplicate Candidate records

Low

Career Site public URL is not transferable across accounts

Zoho Recruit logo

Zoho Recruit gotchas

High

Daily API rate limits are tier-gated and per-user capped

High

User import hard cap of 2,000 records

Medium

Attachment folder hierarchy must be preserved exactly

Medium

Resume parsing quota varies by plan and resets daily

Low

Custom fields unavailable in Free and Standard editions

Pair-specific challenges

  • Duplicate Candidates from Chrome extension imports

    100Hires Chrome extension imports from LinkedIn, Gmail, and AngelList can create duplicate Candidate profiles when the same person was also added manually or via another source. We run a deduplication pass on Candidate email addresses before export. Where matching records exist, we merge by preferring the record with the most complete profile data. Any remaining duplicates are flagged with source attribution (Chrome extension vs manual entry) so the customer's admin can merge or discard duplicates in Zoho Recruit post-import.

  • Nurture Campaign sequences cannot be exported mid-flight

    Nurture Campaigns in progress cannot be safely migrated mid-sequence because recipient opt-out states and delivery timestamps are tightly coupled to 100Hires' email infrastructure. We export campaign definitions and paused state as a written handoff document. Campaign email template content migrates as raw text, but the cadence sequencing requires manual re-configuration in Zoho Recruit. Customers must confirm email consent records for all recipients before re-activating sequences in Zoho Recruit to maintain CAN-SPAM and GDPR compliance.

  • Custom evaluation forms require explicit rubric mapping

    100Hires allows custom evaluation scorecards per interview type with variable rubrics such as 1-5 scales, pass/fail, or bespoke criteria. We export form definitions and all submitted scores, but scoring rubrics must be explicitly mapped to Zoho Recruit Assessment equivalents. Unmapped custom criteria are flagged in the pre-migration audit with a scorecard mapping table for the customer to confirm before import. Evaluation criteria that have no Zoho Recruit equivalent require either accepting a simplified mapping or creating a custom Assessment form in Zoho Recruit first.

  • Users with existing Zoho Recruit accounts cannot be migrated

    Zoho Recruit's migration documentation states that users who already have a separate Zoho Recruit account cannot be imported into the company account. These users must close their individual Zoho Recruit account before their records can be part of the migration. We identify conflicting user emails during the pre-migration audit and escalate to the customer's admin for resolution. Migration cannot proceed past the user provisioning phase until all conflicting accounts are closed.

  • Custom fields not available in Zoho Recruit Free Edition

    100Hires supports custom properties on Candidates, Jobs, and Applications at all paid tiers. Zoho Recruit's Free Edition (Forever Free) does not support custom fields. If the customer imports 100Hires custom Candidate properties into a Zoho Recruit Free Edition account, those fields will be silently dropped. We confirm the customer's Zoho Recruit edition during scoping. If custom fields are present in the source data and the customer intends to use the Free Edition, we recommend upgrading to Standard or Professional before migration begins.

Migration approach

Six steps for a successful 100Hires to Zoho Recruit data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

100Hires logo

100Hires

Source

Strengths

  • Free tier with no credit card required and generous candidate limits for small teams to get started.
  • G Suite integration for calendar-based interview scheduling without leaving the platform.
  • Job board auto-posting to LinkedIn, ZipRecruiter, and Indeed with one click.
  • Chrome extension enables direct resume import from LinkedIn, Gmail, and AngelList profiles.
  • AI screening and candidate matching reduce manual resume review time for active job reqs.

Weaknesses

  • Limited customization for reporting, pipelines, and workflow configurations beyond defaults.
  • UI aesthetics and color options flagged as dated by multiple reviewers on G2 and Capterra.
  • Advanced AI features gated behind the Advanced paid tier with opaque pricing.
  • Rate limits on free tier: 5 emails/day, 3 interviews/day cap restrict migration scope.
  • No public REST API documentation detail on bulk export endpoints or pagination behavior.
Zoho Recruit logo

Zoho Recruit

Destination

Strengths

  • Free tier includes full candidate management with a hosted career site, making it viable for very small staffing operations.
  • Multi-edition architecture splits agency and corporate HR workflows, with tier-gated features that scale predictably with headcount.
  • Per-user API rate limits (500–1000/day) are generous for mid-size migrations compared to competitors that gate by total org quota.
  • Zoho's own data migration tool supports CSV import from Bullhorn, CATS, Jobdiva, and Workable, validating interoperability with common ATS formats.
  • 45-day money-back guarantee and 15-day full-feature trial reduce financial risk for teams evaluating the platform.

Weaknesses

  • Free edition excludes custom fields, lookup relationships, and formula fields, making data model extensibility unavailable until a paid tier is purchased.
  • Resume parsing quotas are capped: 250/day on Standard, 500/day on Professional, unlimited only on Enterprise — bulk imports of large candidate pools will hit these limits.
  • No bulk/batch API endpoint for inserts or updates — large migrations rely on looping single-record API calls within daily rate limit windows.
  • Custom modules cannot be imported from external ATS; only standard modules (Users, Candidates, Clients, etc.) are in the supported migration list.
  • Attachments require a rigid folder hierarchy to re-associate with records, and any deviation in folder structure during extraction causes silent disassociation.

Complexity grading

How hard is this migration?

Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across 100Hires and Zoho Recruit.

  • Object compatibility

    B

    1 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    100Hires: Not publicly documented on the official API reference page.

  • Data volume sensitivity

    B

    100Hires doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your 100Hires to Zoho Recruit migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about 100Hires to Zoho Recruit data migrations

Answers to the questions buyers ask most during 100Hires to Zoho Recruit migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and four weeks for accounts under 5,000 Candidates, 200 Jobs, and 500 Applications with no active Nurture Campaign sequences or complex custom evaluation rubrics. Migrations with large application histories (over 20,000 pipeline stage transition records), multiple active Nurture Campaigns requiring sequencing documentation, custom evaluation forms with non-standard rubrics, or candidates across multiple taxonomy categories move to four to eight weeks because of deduplication passes, scorecard mapping confirmation, and campaign handoff documentation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from 100Hires.
Land in Zoho Recruit, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day