HRMS migration

Migrate from Employment Hero to Zoho Recruit

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 logo

Employment Hero

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

75%

9 of 12

objects map 1:1 between Employment Hero and Zoho Recruit.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Employment Hero logo

Employment Hero

What's pushing teams away

  • Setup across multiple employing entities or companies requires duplicating configuration work, making multi-entity migrations slow and error-prone.
  • The HR and Payroll platforms do not always sync cleanly — information entered in one module can fail to propagate to the other, leading to items being missed from payroll runs.
  • Award and employment classification configuration can be absent from the out-of-box system and must be built manually, delaying go-live for businesses under non-standard industrial awards.
  • Reporting fields are limited and lack customisation, driving customers to spreadsheets for the workforce analytics they need.
  • Customer support historically required ticket submission only; chat support was added later and some reviewers still report slow escalation for urgent issues.

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

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)

maps to

Zoho Recruit

Candidate

1:1
Fully supported

Employment 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

maps to

Zoho Recruit

Job Opening

1:1
Fully supported

Employment 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

maps to

Zoho Recruit

Candidate-Job Opening association

lossy
Fully supported

Employment 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)

maps to

Zoho Recruit

Client

1:1
Fully supported

If 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)

maps to

Zoho Recruit

Custom Fields

lossy
Mapping required

Employment 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)

maps to

Zoho Recruit

Attachments

1:1
Mapping required

Candidate 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

maps to

Zoho Recruit

Interview

1:1
Fully supported

Employment 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)

maps to

Zoho Recruit

Notes

1:1
Fully supported

Candidate-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)

maps to

Zoho Recruit

Users

1:1
Mapping required

Employment 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)

maps to

Zoho Recruit

Custom picklist or Zoho Recruit Department

lossy
Fully supported

Employment 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)

maps to

Zoho Recruit

Not supported in standard ATS model

1:1
Fully supported

Employment 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

maps to

Zoho Recruit

Not supported

1:1
Fully supported

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

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.

Employment Hero logo

Employment Hero gotchas

High

API rate limit of 100 requests per minute caps bulk migrations

High

HR and Payroll platforms do not always synchronise automatically

Medium

Award classifications may not exist in the platform's out-of-box library

Medium

Custom fields are organisation-scoped with no inheritance between environments

Medium

Additional employing entities require explicit employee-to-entity mapping

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

  • Last Name is a mandatory field in Zoho Recruit

    Zoho Recruit requires a Last Name value on every Candidate record during import. If the Employment Hero candidate record lacks a last name, the import row is silently ignored. We audit all candidate records before migration and replace any missing Last Name values with 'not provided' per Zoho Recruit's documented import specification. We flag these records in the migration report so the customer's HR team can update them post-migration. This is a pair-specific gotcha: Employment Hero's SmartMatch module may accept candidate records with a first name only during intake forms, which creates an import failure in Zoho Recruit if not pre-handled.

  • API credit limits vary significantly by Zoho Recruit edition

    Zoho Recruit V2 uses a credit-based API system: Free edition allows 500 credits/day, Standard 5,000-100,000, Professional 10,000-500,000, and Enterprise 15,000-1,000,000. Bulk Write operations deduct 500 credits per initialisation. If the customer's Zoho Recruit edition has insufficient daily credits for the candidate volume, migration jobs will queue and extend the timeline. We budget API credits during scoping and recommend upgrading the Zoho Recruit edition before migration if the credit ceiling is too low for the candidate dataset size.

  • Cannot migrate users who already have a separate Zoho Recruit account

    Zoho Recruit's migration tool does not allow importing users who already hold a separate Zoho Recruit account in another organisation. If the customer's recruiters have existing Zoho Recruit accounts (for example, from a previous agency or as a trial), those accounts must be closed before the migration user import can proceed. We extract the user list from Employment Hero and cross-reference it against any known existing Zoho Recruit accounts, flagging conflicts for the admin to resolve before migration.

  • Minimum two users required before migration can begin

    Zoho Recruit requires at least two users in the account before the built-in migration tool can be used. If the account is provisioned with only one user, the migration wizard blocks the import step. We coordinate with the customer's Zoho Recruit admin to ensure a second user account exists (even if it is a temporary admin placeholder) before the migration phase begins.

  • Export ceiling of 20,000 records per module

    Zoho Recruit's export tool is limited to 20,000 records per module per export request, with a 48-hour download link validity. If the Employment Hero candidate database exceeds 20,000 records, we split the export into multiple requests and manage the download link expiration window. This is primarily relevant for staffing agencies with large historical candidate pools; standard corporate HR migrations typically fall well below this ceiling.

Migration approach

Six steps for a successful Employment Hero to Zoho Recruit data migration

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

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

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

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

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

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

Context on both ends of the pair

Employment Hero logo

Employment Hero

Source

Strengths

  • Generous free payroll tier in the UK with HMRC integration removes cost barrier for micro-businesses.
  • All-in-one HR, payroll, onboarding, and recruitment consolidates tools for SMEs without an IT department.
  • API supports OAuth 2.0 with documented endpoints for employees, custom fields, and cost centres.
  • Rich compliance tooling including award classifications and EOFY workflows for Australian regulatory requirements.
  • HeroForce enables global employment infrastructure without requiring customers to set up separate legal entities.

Weaknesses

  • Multi-entity setup is tedious — each employing entity or company duplicates configuration effort.
  • HR and Payroll modules do not always sync reliably, causing items to be missed from payroll runs if not manually verified.
  • Reporting is limited and inflexible; customers frequently resort to spreadsheets for workforce analytics.
  • Plan-gated features mean core capabilities like custom fields reports, advanced onboarding, and benefits administration require mid-to-premium tiers.
  • Setup for non-standard award classifications requires manual configuration not available in lower tiers.
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 Employment Hero 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

    Employment Hero: 20 requests per second and 100 requests per minute per organisation.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most ATS-focused migrations land between three and five weeks for accounts under 5,000 candidates and 200 active job postings with no custom modules. Migrations with large historical application records (over 10,000), custom candidate fields across multiple modules, or staffing agency volumes with client records and multiple job pipelines move to six to ten weeks because of sandbox validation time, custom field pre-build, and API credit budgeting for the destination edition.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Employment Hero.
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