HRMS migration
Field-level mapping, validation, and rollback between Employment Hero and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Employment Hero
Source
Zoho Recruit
Destination
Compatibility
9 of 12
objects map 1:1 between Employment Hero and Zoho Recruit.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Employment Hero to Zoho Recruit is primarily a recruitment-module migration, not a full HRIS copy, because Zoho Recruit is a dedicated ATS and talent acquisition platform while Employment Hero bundles HR, payroll, and recruitment under one roof. We extract candidate profiles, job postings, and application history from Employment Hero's SmartMatch recruitment module and map them to Zoho Recruit's Candidate, Job Opening, and Client modules. Historical employee records that are not tied to recruitment are outside Zoho Recruit's data model and cannot migrate as candidate profiles; we flag these for the customer's HR review. Workflows, award configurations, and onboarding task templates do not migrate because they are tied to Employment Hero's HR-specific automation engine; we deliver a written inventory of these for the customer's admin to rebuild or reconfigure in Zoho Recruit's workflow builder.
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 Employment Hero 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.
Employment Hero
Candidate (SmartMatch module)
Zoho Recruit
Candidate
1:1Employment Hero's SmartMatch recruitment module stores candidate profiles including name, email, phone, resume, application status, and source. These map directly to Zoho Recruit's Candidate record. The candidate's current application stage in Employment Hero maps to the appropriate Zoho Recruit pipeline stage. We resolve the mandatory Last Name requirement in Zoho Recruit by populating any missing Last Name values with 'not provided' as required by Zoho Recruit's import specification, and we flag these records for customer review post-migration.
Employment Hero
Job Posting
Zoho Recruit
Job Opening
1:1Employment Hero job postings map to Zoho Recruit Job Opening records. We transfer job title, description (HTML content preserved), location, employment type, salary range, and job board distribution settings. Employment Hero's SmartMatch distribution settings require manual reconfiguration in Zoho Recruit because job board connectors differ between platforms.
Employment Hero
Application
Zoho Recruit
Candidate-Job Opening association
lossyEmployment Hero applications (candidate-to-job associations with status, interview scores, and notes) map to the relationship between a Zoho Recruit Candidate record and a Job Opening. Application status (applied, screened, interview, offer, hired, rejected) maps to Zoho Recruit's candidate status field and interview stage values. Interview feedback notes migrate as Zoho Recruit interview notes linked to the candidate.
Employment Hero
Client (Staffing Agency context)
Zoho Recruit
Client
1:1If the Employment Hero organisation operates in a staffing agency context with client companies tracked in the platform, those Client records map to Zoho Recruit's Client module. Client name, contact information, and associated job orders migrate as Zoho Recruit Client records with linked Job Openings.
Employment Hero
Custom Fields (candidate-scoped)
Zoho Recruit
Custom Fields
lossyEmployment Hero custom fields on candidate records are organisation-scoped. We retrieve the custom field schema via GET /api/v1/organisations/:id/custom_fields for the recruitment module, pre-create equivalent custom fields in Zoho Recruit via the Create New Field interface, and map field values during candidate import. Zoho Recruit supports custom fields on Candidate, Job Opening, Client, and Interview modules.
Employment Hero
Document (resume, cover letter)
Zoho Recruit
Attachments
1:1Candidate resume files and cover letters stored in Employment Hero migrate as attachments to the corresponding Zoho Recruit Candidate record. We preserve file names and original upload timestamps. Files are imported via Zoho Recruit's attachment upload API after the candidate record is created.
Employment Hero
Interview / Assessment record
Zoho Recruit
Interview
1:1Employment Hero interview records (scheduled, completed, feedback) map to Zoho Recruit Interview records linked to the Candidate and Job Opening. Interviewer name, scheduled time, interview type, and feedback scores transfer. Interview feedback text migrates as Zoho Recruit interview notes.
Employment Hero
Note (candidate-scoped)
Zoho Recruit
Notes
1:1Candidate-scoped notes in Employment Hero map to Zoho Recruit Notes on the Candidate record. Rich text formatting is preserved where supported. Notes attached to non-candidate records (such as employee onboarding notes) do not have a direct Zoho Recruit equivalent and are flagged for manual review.
Employment Hero
Team (recruitment team members)
Zoho Recruit
Users
1:1Employment Hero users with recruiter roles map to Zoho Recruit Users by email match. We extract all distinct user references on candidate and job records and reconcile against the Zoho Recruit User table. Users without matching Zoho Recruit accounts go to a reconciliation queue for admin provisioning before candidate import begins.
Employment Hero
Cost Centre (department attribution)
Zoho Recruit
Custom picklist or Zoho Recruit Department
lossyEmployment Hero Cost Centres represent departments or cost-attribution units used in rostering and payroll. If the customer requires cost-centre attribution on job postings or candidate assignments, we map these to a Zoho Recruit custom picklist field or to the Department module if the Professional or Enterprise edition is in use. Department configuration is created before candidate migration begins.
Employment Hero
Employee (non-recruitment HR records)
Zoho Recruit
Not supported in standard ATS model
1:1Employment Hero Employee records that are not associated with recruitment (historical payroll data, employment contracts, leave balances, award classifications) do not have a standard equivalent in Zoho Recruit because Zoho Recruit is a dedicated ATS, not an HRIS. We flag these records for the customer's HR team and recommend Zoho People as a parallel HR platform if the customer needs to preserve employee records alongside Zoho Recruit for recruitment. We do not force employee data into Zoho Recruit's Candidate model because that creates incorrect records.
Employment Hero
Award / Classification configuration
Zoho Recruit
Not supported
1:1Employment Hero award configurations (Australian industrial awards, UK pay frameworks) are HR-specific compliance records tied to payroll processing. Zoho Recruit does not store award configurations because it is an ATS, not a payroll platform. These records do not migrate. We deliver a written note listing any award dependencies on active job postings so the customer's HR admin can document them separately.
| Employment Hero | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Candidate (SmartMatch module) | Candidate1:1 | Fully supported | |
| Job Posting | Job Opening1:1 | Fully supported | |
| Application | Candidate-Job Opening associationlossy | Fully supported | |
| Client (Staffing Agency context) | Client1:1 | Fully supported | |
| Custom Fields (candidate-scoped) | Custom Fieldslossy | Mapping required | |
| Document (resume, cover letter) | Attachments1:1 | Mapping required | |
| Interview / Assessment record | Interview1:1 | Fully supported | |
| Note (candidate-scoped) | Notes1:1 | Fully supported | |
| Team (recruitment team members) | Users1:1 | Mapping required | |
| Cost Centre (department attribution) | Custom picklist or Zoho Recruit Departmentlossy | Fully supported | |
| Employee (non-recruitment HR records) | Not supported in standard ATS model1:1 | Fully supported | |
| Award / Classification configuration | Not supported1: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.
Employment Hero gotchas
API rate limit of 100 requests per minute caps bulk migrations
HR and Payroll platforms do not always synchronise automatically
Award classifications may not exist in the platform's out-of-box library
Custom fields are organisation-scoped with no inheritance between environments
Additional employing entities require explicit employee-to-entity mapping
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 candidate record audit
We audit the Employment Hero SmartMatch recruitment module, extracting all candidate records, job postings, applications, client records (if applicable), and custom field schemas. We run a Last Name completeness check on every candidate record and flag any missing values for pre-migration correction or for the 'not provided' substitution strategy. We assess the Zoho Recruit edition in place and budget API credits against the candidate volume to determine whether an edition upgrade is needed before migration.
Schema pre-build in Zoho Recruit
We create all required custom fields in Zoho Recruit for the Candidate, Job Opening, Client, and Interview modules before any data import. This includes any Employment Hero custom fields on candidates, custom picklists for department or cost-centre attribution, and any lookup relationships required. Custom fields are created via Zoho Recruit's field management interface, and we validate that the field types (text, picklist, date, numeric) match the Employment Hero source data to avoid type conversion errors during import.
User reconciliation and account provisioning
We extract every distinct Employment Hero user referenced on candidate records, job postings, and interview records and match by email against the Zoho Recruit User table. Users without a matching Zoho Recruit account go to a reconciliation queue. We ensure at least two Zoho Recruit users exist before migration begins. We also flag any Employment Hero users who may have existing Zoho Recruit accounts elsewhere that need to be closed.
Sandbox migration and reconciliation
We run a full migration into a Zoho Recruit sandbox environment (or a duplicate account set up for validation) using a representative subset of data. The customer's recruitment lead reconciles record counts (candidates in, job openings in, applications in), spot-checks 25-50 candidate records against Employment Hero source data, and validates that custom field values transferred correctly. Any field mapping corrections, missing field declarations, or pipeline stage adjustments happen in sandbox before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Zoho Recruit Users (validated), Job Openings (created first so candidates can be linked), Clients (if applicable), Candidates (with Last Name pre-resolved), Attachments (resumes and cover letters linked to candidates), Applications (candidate-to-job associations), Interviews (linked to candidate and job), Notes (linked to candidate). Each phase emits a row-count reconciliation report before the next phase begins. API calls are chunked and spaced to respect Zoho Recruit's credit limits and concurrency caps per the customer's edition.
Cutover, validation, and automation rebuild handoff
We freeze candidate creation in Employment Hero during the cutover window, run a final delta migration of any records created or updated during migration, then enable Zoho Recruit as the recruitment system of record. We deliver a written inventory of all active Employment Hero onboarding workflows, award configurations, and recruitment-specific automations requiring rebuild in Zoho Recruit's workflow builder. We do not rebuild these as part of the migration scope. We support a one-week hypercare window for reconciliation issues raised by the recruitment team.
Platform deep dives
Employment Hero
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 Employment Hero 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
Employment Hero: 20 requests per second and 100 requests per minute per organisation.
Data volume sensitivity
Employment Hero 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 Employment Hero to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Employment Hero 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 Employment Hero
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.