HRMS migration

Migrate from Homerun to Zoho Recruit

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

Homerun logo

Homerun

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

83%

10 of 12

objects map 1:1 between Homerun and Zoho Recruit.

Complexity

CModerate

Timeline

1-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Homerun logo

Homerun

What's pushing teams away

  • Limited analytics and reporting mean HR teams with sophisticated workforce insights needs often outgrow the platform's built-in capabilities.
  • Growth-stage companies requiring advanced workflow automation or deep custom integrations find the feature set insufficient for complex use cases.

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 Homerun objects map to Zoho Recruit

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

maps to

Zoho Recruit

Candidate

1:1
Fully supported

Homerun 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

maps to

Zoho Recruit

Job Opening

1:1
Fully supported

Homerun 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

maps to

Zoho Recruit

Pipeline Stage

lossy
Fully supported

Homerun 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

maps to

Zoho Recruit

Employee (Corporate HR)

1:1
Fully supported

Homerun 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

maps to

Zoho Recruit

Time Off

1:1
Mapping required

Homerun 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

maps to

Zoho Recruit

Document Library

1:1
Fully supported

Employee 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

maps to

Zoho Recruit

User

1:1
Fully supported

Homerun 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

maps to

Zoho Recruit

Interview Feedback Form

1:1
Fully supported

Homerun 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

maps to

Zoho Recruit

Offer Letter

1:1
Fully supported

Homerun 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

maps to

Zoho Recruit

Candidate Timeline

1:1
Fully supported

Homerun'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

maps to

Zoho Recruit

Custom Field

lossy
Fully supported

Homerun 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

maps to

Zoho Recruit

Task, Event, Note

1:1
Fully supported

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

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.

Homerun logo

Homerun gotchas

High

60 requests per minute API rate limit

High

No bulk export endpoint

Medium

Analytics limitations documented in reviews

Medium

2025 HR module expansion changes migration scope

Low

No public data on tier-specific API availability

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

  • Homerun exports require paginated reads at 60 req/min with no bulk endpoint

    Homerun has no bulk export API. Every object type requires repeated paginated list endpoint calls, and the platform enforces a strict 60 req/min rate limit across all endpoints with no burst allowance. For accounts with large candidate pools, long employee histories, or extensive engagement timelines, we chunk the export into time-bounded windows and iterate nightly to avoid hitting the ceiling. Active integrations or active users on the source during migration share the 60 req/min budget, so we coordinate reduced request pacing or schedule exports outside business hours. This constraint extends migration timelines significantly compared to platforms with bulk export APIs.

  • Zoho Recruit requires Last Name on Candidates; records without it are skipped

    Zoho Recruit enforces Last Name as a mandatory field on Candidate records. Homerun candidate records may lack a last name if entered via a source that only captured a first name or a company name. Before import, we flag all candidate records missing a last name value and either request the customer populate them in Homerun or insert a placeholder value ('not provided') during the transform step. Records without any last-name value are skipped by Zoho Recruit's import engine and do not appear in the error log unless the customer downloads the import summary. We surface these records in our pre-import reconciliation report so no candidate is silently dropped.

  • Existing Zoho Recruit users cannot be imported into a company's org

    Zoho Recruit's import process rejects any user record that already has an active individual Zoho Recruit account. Those users must close their separate accounts before they can be imported into the company's Zoho Recruit org. We identify any Homerun team member whose email matches an existing Zoho Recruit account during scoping, flag them in the migration plan, and hold their User import until the separate account is closed. This step can introduce a coordination delay if team members have pre-existing Zoho Recruit trial or personal accounts.

  • Workflows, automations, and reporting configurations do not migrate

    Homerun Workflows (pipeline-triggered automation with email actions and stage transitions) and any reporting dashboards or custom analytics built on top of Homerun data do not migrate as code or configuration. Zoho Recruit Workflow Rules are a different model with different triggers, conditions, and action types. We deliver a written inventory of every active Homerun Workflow and recommended Zoho Recruit Workflow Rule equivalent for the customer's admin to rebuild. Reporting dashboards and analytics configurations are not migrated; the raw data is complete, but the customer's team rebuilds reports in Zoho Recruit's report builder or Zoho Analytics post-migration.

  • Homerun HR module eligibility must be verified before scoping employee data

    Before 2025, Homerun was an ATS without employee records. The HR module introduced Employees, Time Off, and document storage only recently. If the source Homerun account predates the HR module rollout, those object types have no data to migrate regardless of current account tier. We verify which modules were active during the period the migration scope covers by reviewing the source API response schema and comparing it against the HR module feature set. This prevents the migration plan from over-promising on object types that were never instantiated in the source account.

Migration approach

Six steps for a successful Homerun to Zoho Recruit data migration

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

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

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

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

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

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

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

Context on both ends of the pair

Homerun logo

Homerun

Source

Strengths

  • Visual design tools for job postings and career pages that genuinely differentiate employer branding.
  • Strong customer satisfaction scores and positive reviews on independent platforms.
  • All-in-one ATS plus HR platform reduces the number of tools a small team needs to manage.
  • Clean, modern interface that reduces onboarding time for hiring managers and recruiters.

Weaknesses

  • Analytics and reporting capabilities lag behind enterprise HRMS platforms with dedicated BI tools.
  • API has no bulk export endpoint; all reads use paginated list endpoints at 60 req/min.
  • Rate limit of 60 requests per minute makes large migrations require careful throttling and chunking.
  • Feature set is best suited to small and mid-market teams; larger organizations with complex workflows may find gaps.
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?

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

C

Overall complexity

Moderate migration

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

  • Object compatibility

    C

    3 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

    Homerun: 60 requests per minute per API key.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Homerun 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 Homerun to Zoho Recruit data migrations

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

Can't find your answer?

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 consultation

Most migrations complete in one to three weeks for accounts under 5,000 candidate records with Job Openings and basic engagement history. Accounts with over 10,000 candidates, active HR module data (Employees, Time Off, documents), or complex custom field schemas extend to four to eight weeks. The primary timeline driver is Homerun's 60 req/min API rate limit, which requires paginated export chunking and nightly iteration for large datasets. The 2025 HR module eligibility also affects scope: accounts without the HR module active have fewer object types to migrate, shortening the timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Homerun.
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