HRMS migration
Field-level mapping, validation, and rollback between Homerun and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Homerun
Source
Zoho Recruit
Destination
Compatibility
10 of 12
objects map 1:1 between Homerun and Zoho Recruit.
Complexity
CModerate
Timeline
1-3 weeks
Overview
Moving from Homerun to Zoho Recruit is a multi-system migration that requires resolving the 60 req/min API rate limit on the export side, managing the absence of a bulk export endpoint on the source, and mapping Homerun's single Candidate object to Zoho Recruit's Candidates module with its mandatory Last Name requirement and its Clients module for agency-facing records. We migrate Job Openings with their pipeline stage configurations, Employees and Time Off (introduced in Homerun's 2025 HR module), scorecard ratings, and offer letters. Employee documents export as file metadata with content URLs for re-attachment in Zoho Recruit's Document Library. Workflows, automations, and reporting configurations do not migrate as code; we deliver a written inventory of active automations and recommended Zoho Recruit workflow equivalents for your admin to rebuild post-migration. Zoho Recruit's per-recruiter pricing model (starting at $25/user/month on Standard, $75/user/month on Enterprise) replaces Homerun's seat-based model, and active job slot limits differ by tier in the destination.
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 Homerun 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.
Homerun
Candidate
Zoho Recruit
Candidate
1:1Homerun Candidate records map to Zoho Recruit Candidates. The primary challenge is Zoho Recruit's mandatory Last Name requirement: any Homerun candidate record without a last name value is flagged during scoping and must be populated with 'not provided' or equivalent before import, or the record is skipped. We preserve the full application timeline, source attribution, pipeline stage, and any rating scores. Custom properties on Candidate migrate to Zoho Recruit custom fields (50 per module on Standard, 300 on Enterprise) created before import.
Homerun
Job Opening
Zoho Recruit
Job Opening
1:1Homerun Job Openings map directly to Zoho Recruit Job Openings. We map job title, description, department, location, and the pipeline stage configuration. Active job slot limits differ by tier in Zoho Recruit (1 on Free, 10 per recruiter on Standard, 20 per recruiter on Enterprise for Corporate HR; 1/100/250/750 for agency tiers). If the source account has more concurrent active jobs than the destination tier allows, we flag the excess during scoping and the customer either upgrades or archives resolved openings before migration.
Homerun
Pipeline Stage
Zoho Recruit
Pipeline Stage
lossyHomerun pipeline stage names and ordering map to Zoho Recruit's candidate pipeline stage values. We create the stage configuration in Zoho Recruit before candidate import, preserving the stage sequence and any stage-specific actions. If Homerun has more stages than the destination pipeline supports, we consolidate minor stages and document the mapping in the reconciliation report.
Homerun
Employee
Zoho Recruit
Employee (Corporate HR)
1:1Homerun Employee records (available only on accounts with the 2025 HR module active) map to Zoho Recruit's Employee module under Corporate HR. We map name, email, role, department, employment status, start date, and manager relationship. If the source account predates the HR module rollout, we scope the migration based on module configuration at migration time, not retrospectively, to avoid attempting to import records that were never created.
Homerun
Time Off
Zoho Recruit
Time Off
1:1Homerun Time Off balances and request history map to Zoho Recruit's Time Off module. Current-state balances migrate with effective dates and accrual rates. Historical accrual patterns are mapped as Time Off records with the accrual type and balance snapshot, as the destination system's accrual engine recalculates forward balances post-migration. Approval history migrates as read-only records.
Homerun
Document
Zoho Recruit
Document Library
1:1Employee documents stored in Homerun HR are exported as file metadata with content URLs and binary content. We handle large files through chunked retrieval. In Zoho Recruit, documents attach to the corresponding Employee or Candidate record via the Document Library. File versioning and folder sharing settings require manual reconfiguration post-import as Zoho Recruit's document model differs from Homerun's document storage structure.
Homerun
User
Zoho Recruit
User
1:1Homerun team member accounts map to Zoho Recruit Users by email. Role assignments and ownership relationships are preserved. A Zoho Recruit constraint: users who already have a separate individual Zoho Recruit account cannot be imported into a company's Zoho Recruit org; they must close the separate account first. We test API access for all object types during scoping and flag any 403 responses indicating tier restrictions or account conflicts.
Homerun
Scorecard
Zoho Recruit
Interview Feedback Form
1:1Homerun evaluation scorecards and their rating values map to Zoho Recruit Interview Feedback Forms. Scorecard answer values are normalized to the destination's rating schema, with evaluator comments preserved in free-text fields. Rating normalization may reduce granularity if the source uses a scale that exceeds the destination's standard rating fields; we document any precision loss in the mapping specification.
Homerun
Offer
Zoho Recruit
Offer Letter
1:1Homerun offer letters with compensation details, start dates, and conditional terms map to Zoho Recruit's Offer Letter functionality. We extract the offer content, compensation structure, and conditional clauses, mapping them into Zoho Recruit's offer template fields. Offer letter templates in Zoho Recruit (50 on Standard, 100 on Enterprise) are created as custom templates post-migration; the migrated offers themselves carry the historical data.
Homerun
Application History
Zoho Recruit
Candidate Timeline
1:1Homerun's full candidate application timeline (all stage transitions, notes, communications, and scorecards attached to a candidate) is reconstructed in Zoho Recruit as a chronological timeline of activities, notes, and interview records. Stage transitions map to Tasks or Events with a description field capturing the stage name and timestamp. This ensures the hiring team's historical context is intact in the destination.
Homerun
Custom Field
Zoho Recruit
Custom Field
lossyHomerun custom fields on any object are enumerated during scoping with their field IDs, data types, and picklist values. We create equivalent custom fields in Zoho Recruit before importing the parent object, matching data types (text, number, date, picklist, checkbox, etc.). Picklist values require explicit mapping if the source and destination picklists diverge. The 50 custom fields per module on Standard and 300 on Enterprise determine the maximum field count per object.
Homerun
Engagement: Call, Email, Meeting, Task, Note
Zoho Recruit
Task, Event, Note
1:1Homerun engagement records (calls, emails, meetings, tasks, notes) associated with Candidates or Job Openings map to Zoho Recruit's Tasks, Events, and Notes. Call engagements become Tasks with TaskSubtype=Call and duration preserved. Meeting engagements become Events with start time, end time, and attendee list. Notes map to Zoho Recruit Notes with the body and timestamp. Email content attaches to the Candidate or Job Opening record. We sequence engagements after their parent record (Candidate or Job Opening) is present in the destination to avoid orphaned entries.
| Homerun | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Candidate | Candidate1:1 | Fully supported | |
| Job Opening | Job Opening1:1 | Fully supported | |
| Pipeline Stage | Pipeline Stagelossy | Fully supported | |
| Employee | Employee (Corporate HR)1:1 | Fully supported | |
| Time Off | Time Off1:1 | Mapping required | |
| Document | Document Library1:1 | Fully supported | |
| User | User1:1 | Fully supported | |
| Scorecard | Interview Feedback Form1:1 | Fully supported | |
| Offer | Offer Letter1:1 | Fully supported | |
| Application History | Candidate Timeline1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| Engagement: Call, Email, Meeting, Task, Note | Task, Event, 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.
Homerun gotchas
60 requests per minute API rate limit
No bulk export endpoint
Analytics limitations documented in reviews
2025 HR module expansion changes migration scope
No public data on tier-specific API availability
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 module eligibility audit
We audit the source Homerun account across active modules (ATS only or ATS plus HR), object counts per type (Candidates, Job Openings, Employees, Time Off, Documents, Users, Scorecards, Offers), custom field schemas, pipeline stage configurations, and any active workflow definitions. For the destination, we verify the Zoho Recruit edition (Standard vs Enterprise for Corporate HR), active job slot limits, custom field capacity per module, and the number of existing Zoho Recruit User accounts that may conflict with migrating team members. The discovery output is a written migration scope confirming which object types are in scope and which require schema pre-creation in Zoho Recruit.
Schema pre-creation in Zoho Recruit
We create all required custom fields, picklist values, and pipeline stage configurations in Zoho Recruit before any data import begins. This includes mapping Homerun custom field names to Zoho Recruit field names with matched data types, creating the candidate pipeline stages in Zoho Recruit's matching order, and pre-configuring Offer Letter templates if the source has active offer records. We also verify that the Zoho Recruit edition supports the required module count (Employees, Time Off, Document Library) and that the active job slot allocation accommodates the source's current open positions.
User and owner reconciliation
We extract every distinct Homerun user referenced on any record (Candidate owner, Job Opening owner, Employee manager, etc.) and match by email against the Zoho Recruit User table. Any user with an existing individual Zoho Recruit account is flagged and held in a reconciliation queue until the separate account is closed. We also verify that at least two Users exist in the destination Zoho Recruit org (a Zoho Recruit import requirement). User provisioning is validated before candidate migration begins.
Paginated export with rate-limit throttling
We export all object types from Homerun's paginated API endpoints, throttling to the 60 req/min ceiling across all concurrent streams. Large object types (Candidates with long engagement histories, Employee records with document attachments) are chunked into time-bounded windows and iterated nightly. All pages are aggregated server-side before transformation. The export phase produces normalized CSV and JSON intermediates with source record IDs preserved for lookup resolution during import.
Transform, validation, and pre-import reconciliation
We transform exported records to match Zoho Recruit's schema: Last Name is populated or marked 'not provided' on all Candidate records; pipeline stage names are mapped to Zoho Recruit stage values; custom field picklist values are mapped to the destination picklist; Employee and Time Off records are linked via their manager relationships resolved from the User mapping. We run a pre-import reconciliation comparing record counts per object type against the source and surface any records that will be skipped (missing mandatory fields, unmatched owners) before proceeding to import.
Production import in dependency order
We run the production import in dependency order: Users first (validated), then Job Openings (parent to applications), Employees and Departments, Candidates (with Last Name validated and Account/Client lookup resolved), Time Off records, Documents (with file content retrieved and attached), Offer Letters, Scorecards via Interview Feedback Forms, and finally engagement history (Tasks, Events, Notes) linked to their parent Candidate or Job Opening. Each phase emits a row-count reconciliation report before the next phase begins. Any records rejected by Zoho Recruit's validation engine are logged with error reasons for correction and re-import.
Cutover, final validation, and automation rebuild handoff
We freeze Homerun 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 a post-migration reconciliation report comparing final record counts, spot-checking 25-50 records against the source for data accuracy. We deliver the Workflow and automation inventory document to the customer's admin with Zoho Recruit Workflow Rule recommendations for each. We support a one-week hypercare window for reconciliation issues. We do not rebuild Homerun Workflows as Zoho Recruit Workflow Rules inside the migration scope; that is a separate engagement or an internal admin task.
Platform deep dives
Homerun
Source
Strengths
Weaknesses
Zoho Recruit
Destination
Strengths
Weaknesses
Complexity grading
Moderate HRMS migration. 3 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Homerun and Zoho Recruit.
Object compatibility
3 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
Homerun: 60 requests per minute per API key.
Data volume sensitivity
Homerun 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 Homerun to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Homerun 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 Homerun
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.