Skip to content
Get a quote

Migrate to Zoho Recruit

Zoho Recruit is an edition-tiered applicant tracking system whose import success depends on pre-creating Modules, sequencing Hiring Pipeline stages, and mapping picklist values exactly before a single candidate row is loaded.

Short answer

FlitStack AI migrates employees, payroll, and benefits into Zoho Recruit from 200+ HR systems. Every field is mapped to Zoho Recruit's objects, history and associations come across, the Zoho Recruit setup is configured alongside, and the whole migration stays reversible in one click.

By

From Your system
DestinationZoho Recruit
200+ sources mapped into Zoho Recruit

What Zoho Recruit supports, and where its import tools stop

  • 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.
REST onlyAuthentication Token (legacy) / OAuth 2.0 (V2)
Rate limits500–30,000 requests/day by org edition; per-user ceiling of 250–1,000 requests/day (whichever is lower)
ObjectSupportNote
CandidatesfullCandidates is the core object in Zoho Recruit. Standard fields (name, email, phone, skills, status) are stable and map 1:1. Custom fields are supported in paid tiers. We preserve all candidate-associated attachments, notes, and activities at migration time.
Job OpeningsfullJob Openings (requisitions) map cleanly to our Jobs object. Tier gates apply to active job counts: Free=1, Standard=100, Professional=250, Enterprise=750 (agency) or 10/20 per recruiter (corporate). We flag tier violations during scoping.
Clients (Staffing Agencies)fullThe Clients module is agency-specific and holds external hiring-company records. It has standard fields plus custom fields in paid tiers. We migrate Clients as Organizations, preserving the Client-specific fields and any linked Contacts.
ContactsfullContacts hold hiring-manager or candidate-contact records. Standard CRM-style fields plus custom fields in paid tiers. Lookup relationships to Clients and Candidates are preserved via our reference field mapping.
UsersmappedUser records migrate as Assignees/Owners. Zoho caps user imports at 2000 records; we flag this ceiling and batch larger imports. Role-and-profile assignments (available in Professional/Enterprise) require remapping to the destination's permission model.
InterviewsfullInterviews are linked to Candidates and Job Openings. Standard fields (scheduled time, type, interviewer, feedback) are stable. We preserve interview-to-candidate associations via our linking table.
NotesfullNotes attach to Candidates, Job Openings, Clients, and Contacts. Free-text notes migrate as-is. Rich-text notes are preserved in HTML format where the destination supports it.
Tasks, Events, Calls (To-Dos)fullActivities in Zoho Recruit map to our Tasks object. Call logs, events, and tasks each retain their type discriminator. Available in Standard and above; Free edition does not include this module.
AttachmentsmappedAttachments require a specific folder hierarchy (Candidate/Client/Job ID subfolders) to re-associate with records. We preserve the original filenames and folder structure, then restore associations post-import. Files must be in the source zip archive to be picked up.
CampaignsmappedCampaigns hold sourcing initiatives linked to job boards or job openings. We map Campaigns to our Campaigns/Sourcing Initiatives object and preserve associations to Job Openings. Custom fields require pre-creation in the destination if the target plan supports them.
AssessmentsmappedAssessment results attach to Candidates. The assessment itself (questions, scoring rubrics) may require manual recreation in the destination depending on the target ATS's data model.
Custom FieldsmappedCustom fields are not available in the Free Edition. Lookup and formula fields require Professional or higher. We inspect the source account's edition during discovery and create matching custom fields in the target before migrating data.
Career Site (Job Board Integrations)noneCareer site configuration (templates, localized pages, job board posting settings) is Zoho Recruit platform configuration, not data. We do not migrate this. The published job listings themselves are captured as Job Opening records.
Workflows / Automation RulesnoneWorkflow rules, Blueprint automation, and assignment rules are Zoho Recruit configuration rather than record data. We do not migrate these. Customers should plan to rebuild critical automation in the destination.

The Zoho Recruit migration guide

Why teams migrate to Zoho Recruit

The four shapes a Zoho Recruit migration takes, and what makes the platform easier — or harder — than the category average.

Zoho Recruit is an applicant tracking system developed by Zoho Corporation, an India-based technology company founded in 1996 by Sridhar Vembu and Tony Thomas as AdventNet and headquartered in Chennai, with its US office in Austin, Texas1. Recruit ships in two editions — Corporate HR for in-house hiring teams and Staffing Agency for recruiting firms — and is sold both standalone and inside the broader Zoho One bundle.

The typical Zoho Recruit customer is a 5-to-500-employee hiring team or a 10-to-200-recruiter staffing agency buying on price and bundle economics. Pricing starts at $0 for the Forever Free edition (1 active job), $25 per user per month on Standard, $50 on Professional, and $75–$90 on Enterprise37. Zoho positions Recruit on a 50-percent-savings claim versus Bullhorn and JobDiva, with the same suite-discount story across People Plus and Zoho One.

The shapes of migration that land on Zoho Recruit fall into four patterns. First, Freshteam exits, accelerated by Freshworks' decision to discontinue Freshteam — Zoho ships a dedicated Freshteam-to-Recruit migration guide55. Second, Bullhorn and JobDiva exits, driven by per-recruiter pricing on the source side; Zoho explicitly lists Bullhorn, CATS, JobDiva and Workable as completed migration sources on its migration request page56.

Third, suite consolidation: replacing a Greenhouse-plus-Calendly-plus-DocuSign stack with Zoho Recruit plus Zoho Sign plus Zoho People inside Zoho One. Fourth, upgrades from spreadsheets, where small agencies move off shared Excel files onto a real ATS for the first time.

What makes migrating to Zoho Recruit easier than the category average is the Data Migration wizard itself — it auto-creates Modules that do not exist on the destination, auto-maps columns to fields, and accepts CSV, XLS, XLSX and VCF55. It also ships a built-in Resume Extractor that parses CVs into Candidate fields, and a Career Site that captures applicants post-cutover.

What makes it harder than the average is the edition-tier architecture, which gates Custom Modules, multiple Hiring Pipelines, and most advanced custom-field types behind Enterprise3739; the picklist value model that rejects values not on the destination dropdown11; and the Hiring-Pipeline-to-Status mapping rule that quietly reshuffles Modified Time on every record whose status gets remapped51.

Workflow Rules, Blueprint state machines, assignment rules and scoring rules do not import — they are rebuilt from documentation. Teams that scope the rebuild work up front finish on time; teams that assume parity do not.

Zoho Recruit's bundle economics get hiring teams in the door; the edition-tier architecture and Hiring-Pipeline-to-Status coupling decide whether they stay on schedule.

The Zoho Recruit data model you need to map into

Modules, Layouts, picklists, lookups, and the duplicate-check upsert keys you'll wire on every field — the destination schema decoded.

Zoho Recruit is built around Modules — the platform's term for what Greenhouse calls Objects and Bullhorn calls Entities. Each Module carries standard and custom fields, sits behind one or more Layouts, and connects to other Modules through Lookups and Multi-Select Lookups. Permission is governed by Profiles; record visibility by Roles.

Before mapping any source field, you need to know which destination Module the row belongs in, which Layout it inherits, and which value will serve as its duplicate-check key. The table below summarises the standard Modules a Zoho Recruit migration will touch1213.

ObjectWhat it storesRequiredTier
CandidatesJob seekers — the core ATS recordLast Name12All editions
ContactsHiring managers and client-side contacts (Staffing Agency)Last NameAll editions
ClientsCompanies the agency recruits for (Staffing Agency only)Client NameStaffing Agency edition
Job OpeningsOpen requisitions tied to a hiring pipelinePosting Title, Client (Staffing), Job Opening StatusAll editions; active-job cap varies by edition37
Applications / SubmissionsCandidate-to-Job association with its own stage historyCandidate, Job Opening, Application StatusAll editions; Applications module gated on plan
InterviewsScheduled interview events with interviewer scorecardsInterview Name, From Time, To Time, CandidateAll editions
Tasks / Calls / EventsActivity records on a parentSubject; times for EventsAll editions
VendorsExternal staffing agencies supplying candidatesVendor NameStaffing Agency edition
Offers / Assessments / Notes / DocumentsSub-records linked to Candidates or ApplicationsPer-module — see field requirementsAll paid editions; Offers gated on plan
Custom ModulesCustomer-defined record typesSchema defined first; per-field requirementsEnterprise (and Zoho One / People Plus)

Records get matched by what Zoho calls duplicate check fields — fields marked with the Do not allow duplicate values property. Email is the default duplicate check on Candidates and Contacts; Posting Title and Client on Job Openings. Once marked unique, the import upsert flow uses it to decide insert-versus-update14.

Applications, Interviews and Custom Modules have no natural unique key — create a custom single-line text field, mark Do not allow duplicate values, and populate from the source system's primary key. The upsert flow also accepts an explicit find_by field pattern to match against a foreign system's identifier without disturbing the internal Zoho Record ID23.

When you upsert, Zoho checks the duplicate-check field set: if a match exists, the record updates; if none, it inserts. You can also pass Zoho's internal Record ID directly when re-importing your own export — the Record ID is the canonical primary key and bypasses duplicate-check matching entirely. Custom field types determine validation, storage and edition availability.

Field typeLimitNotes
Single-line textUp to 255 charsPlain string; can be marked unique12
Multi-line textSmall / large variantsLarge variant gated on higher editions
Number / Decimal / Currency / PercentUp to 16 digitsCurrency respects org base-currency setup
Date / Date-TimeOrg timezoneLocale date format must match on import16
Picklist (single-select)Per-edition count limitDisplay value and reference value can differ11
Multi-Select PicklistPer-edition count limitSemicolon-delimited on import
LookupOne target ModuleOne-to-many; populated by lookup name or ID
Multi-Select LookupEnterprise and aboveEstablishes many-to-many via hidden linking module
File UploadMax 5 file-upload fields per form21For onboarding-doc-style uploads beyond five, use Attachments
Formula / Auto-Number / External-style IDHigher editionsFormula type fixed at creation; cannot be changed16

Relationships in Zoho Recruit model parent-child through Lookup fields and many-to-many through Multi-Select Lookup fields, which silently create a hidden linking Module visible in Developer Space. A Candidate has a Lookup to one Client (Staffing) and many Applications; a Job Opening has Lookups to one Client and many Applications.

There is no native cascade delete — deleting a parent does not delete children, which is a behaviour your Deluge or Workflow logic must reproduce if the source platform relied on it9.

Custom Modules participate in Lookups the same way standard modules do, with the same duplicate-check semantics. They are gated to Enterprise, Zoho One and People Plus editions, and their schema, Layouts and unique-ID fields must exist on the destination before any record can be imported49. Subforms are limited to one per module and migrate as child records, not parent-row payloads.

Pre-migration prep — the work before you touch Zoho Recruit

What must be true on the source, the destination, and across the team before the first row hits the Data Migration wizard.

The single best predictor of a clean Zoho Recruit migration is how much work happens on the source side before the first import button is pressed. Zoho's Data Migration documentation devotes most of its prep checklist to source-side hygiene — file format, date format, mandatory-field coverage, drop-down value alignment — because the wizard rejects rows quietly on any mismatch and surfaces the reasons in Import History after the fact22.

Zoho Recruit's Data Migration wizard is fast when the source file is clean and unforgiving when it isn't — pre-processing is where the time savings come from.

Treat the source export as raw material that must be shaped to Zoho's expected formats — emails lowercased, picklist labels converted to the values on Zoho's destination drop-downs, dates rewritten in the org locale format, currency stripped of symbols, owners resolved to Zoho user emails, and resume files staged for attachment.

Source-side prep

  • Audit and dedup the source database before export — Zoho's de-duplicate tool runs post-import and is slow on large candidate datasets. Catch case-only email duplicates and trailing-whitespace duplicates in the source export, not after they land.
  • Convert picklist display labels to the values that exist on the Zoho destination for every drop-down field — Candidate Status, Application Status, Lead Source, Industry, every Custom Picklist. The Data Migration wizard rejects values not in the destination picklist and surfaces a per-row error in the result CSV22.
  • Save every CSV as UTF-8 before upload. Non-UTF-8 files produce garbled accented characters in candidate names or full row rejection on Russian or Czech character sets20. Excel saves as Windows-1252 by default on Western locales — explicitly choose CSV UTF-8 on Save As.
  • Stamp a stable external ID on every candidate, job and application in the source export — a UUID or the source platform's primary key — so re-runs and reconciliation are deterministic. This value populates the Recruit field you mark as the upsert find_by field23.
  • Decide what is in scope for historical activities and resume files. Tasks, Calls and Events can be imported; resume files attach per record and count against tier-tied storage30. Backdated CV uploads are common; backdated Created Time is not51.
  • Ensure the Last Name column is populated on every Candidate, Contact and Client row. Last Name is a hard mandatory in Zoho Recruit and rows missing it are silently skipped — Zoho's own migration guide tells you to fill blanks with not provided or none55.

Destination-side prep

  • Provision Users, Profiles and Roles before importing — owner assignment falls back to the importing user if a referenced user email does not exist in Recruit, and historical attribution is broken for every affected record52.
  • Add at least one extra user before migration. Zoho's own checklist warns that the Data Migration wizard requires more than a single user in the destination account before it will let you start55. Bulk-import the remaining users via CSV under Setup → Users & Control → Users.
  • Pre-create every custom field on the right Module and Layout with the right type — Field Type cannot be changed after creation (you cannot turn a Text field into an Integer later)16.
  • Build the Hiring Pipeline, its Stages, and the Candidate Statuses mapped to each Stage before importing Applications. The Hiring Pipeline lives at Setup → Hiring Pipeline (or Setup → Customization → Hiring Pipeline on the older Applications module flow) and rejects rows whose status is not mapped to a stage51.
  • Define Custom Modules, their unique-ID fields, and their Lookups before importing. Custom Module schemas must exist before records of that type can be created, and Custom Modules are gated to Enterprise, Zoho One and People Plus editions49.

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every recruiter, hiring manager and client-facing user who touches the ATS. Train recruiters on Zoho's daily-workflow patterns, Application stage transitions and Blueprint enforcement before go-live, not after. A clean Freshteam-to-Recruit or Workable-to-Recruit migration of under 10,000 candidates lands inside one business day; a Bullhorn-to-Recruit with Custom Modules, Vendor portal and Submissions history runs two to four weeks.

Import mechanisms: UI wizard and Data Migration

Two paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at the edition-tier ceiling.

Zoho Recruit exposes two load paths and the right one depends on dataset size, Module mix, and whether the load must be re-run idempotently. The native Import wizard handles most one-shot migrations under a few hundred thousand records. The Data Migration wizard adds source-ATS auto-mapping.

Native Import wizard

The per-Module Import wizard lives at the top right of any Module list view, or under *Setup → Data Administration → Import*22. It accepts CSV (UTF-8), XLS, XLSX and VCF44. Each Module is imported as a separate file. The wizard maps columns to fields, lets you choose Skip / Overwrite / Clone behaviour for duplicates (Skip and Overwrite require paid editions), sets a Workflow Task, and runs a sample before committing the full file.

Specific to Recruit, the wizard exposes an Assign all imported Candidates to this Candidate Source dropdown — use it to stamp every row in a batch with its origin source (LinkedIn, Indeed, Employee Referral, Career Site) without populating the source column on every row22. There is also an Enable Manual Lead Approval option that holds imported candidates in a pre-assigned state until an admin signs off22.

Per-file limits are edition-tiered and run alongside Zoho's general CRM-family limits: CSV files up to a few MB on Free, larger files on paid editions, with the wizard splitting larger ranges across multiple batches. The right call: the Import wizard for one-shot loads under 100,000 records on standard Modules, or whenever you want a visual mapping review before commit.

Data Migration wizard

The Data Migration wizard, under Setup → Data Administration → Data Migration, is the larger-scope tool. It supports two source paths: Zoho Recruit (account-to-account transfer between two Recruit orgs) and Other ATS (CSV/zip upload with auto-Module-creation)55. The wizard inspects the uploaded files, proposes destination Modules, and creates any Module that does not exist on the target — driven by a button literally labelled +Create New Module on the field-mapping screen56.

Zoho's own marketing page lists Bullhorn, CATS, JobDiva and Workable as previously completed migration sources; the engine itself is source-agnostic as long as you can produce CSV56. The wizard is the right pick when the source is a one-shot CSV-shaped load and the team wants minimum manual mapping. It is the wrong pick when the migration requires repeated dry-runs over weeks or reconciliation against a parallel source-of-truth.

Third-party staging tools

Tools like Fivetran, Airbyte, Zoho DataPrep, Workato and Make sit between source and destination. They are used in two ways: (a) reverse-ETL where the source loads into a warehouse, gets transformed in SQL, then syncs into Recruit; and (b) staging-and-validate, where the tool handles type coercion, candidate-name normalisation and dedup before the result feeds the importer40.

Mapping your data into Zoho Recruit

The longest section — because field mapping is where almost every Zoho Recruit migration that fails actually breaks.

Mapping is where every ATS migration earns its scars. Schema decisions in your mapping spreadsheet determine whether reports work on day two, whether Blueprint fires on day five, whether interview scorecards roll up on day fifteen, and whether recruiters trust the candidate database on day thirty.

Work Module by Module in import order: Users first, then Clients (Staffing) and Contacts so Job Openings can associate, then Job Openings, then Candidates, then Applications/Submissions, then Interviews, then Offers, then Activities and Notes, then Custom Modules. The Data Migration wizard enforces this implicitly with its module-detection step55; through the Import wizard, you enforce it by file order.

Candidates — the core ATS record

Candidates is the heart of every ATS migration. Zoho Recruit ships a built-in Resume Extractor that parses uploaded resume files into Candidate fields (Name, Email, Phone, Experience, Skills, Education) automatically58, but this only fires on resumes uploaded after the candidate record exists. The reliable pattern is to import a clean Candidates CSV first, then attach resume files in a second pass33.

Common source → Zoho Recruit Candidate mapping
SourceDestinationNote
emailEmail (duplicate check field)Lowercased pre-import; mark as duplicate check field for upsert14
first_name / last_nameFirst Name / Last NameLast Name is mandatory; rows missing it are silently skipped55
phone / mobilePhone / MobileNormalise to E.164; Recruit does not enforce a phone format
candidate owner / recruiterCandidate OwnerMap by Zoho user email; unresolved owners fall back to the importing user52
candidate statusCandidate Status (picklist)Must exist on destination Hiring Pipeline status list51
candidate sourceSource picklist (or wizard-level Assign Source)Use wizard dropdown to stamp source on a whole batch22
created_atCustom Date-Time field (e.g., Legacy Created Date)Created Time on Candidates is system-managed and cannot be overwritten51
external system primary keyCustom unique single-line text fieldMark Do not allow duplicate values; use as find_by field on upsert1423

Resume files and historical attachments

Resume files do not import in the CSV flow. The supported path is per-record attachment — one binary at a time, associated to the candidate by Record ID33. The per-record attachment cap is 20 MB total across all files on a Candidate record29, with email-template attachments capped at 3 MB29.

The File Upload field type is hard-capped at 5 fields per form21, so for onboarding flows that need 10+ documents (right-to-work, NDA, references, certifications, EEOC self-id), use general Attachments rather than File Upload fields.

Storage is edition-tiered: Free 256 MB, Standard 1 GB default plus 256 MB per new user, Professional 2 GB plus 512 MB per user, Enterprise 3 GB plus 1 GB per user30. Resume files at an average of 500 KB each consume storage fast — 5,000 resumes is roughly 2.5 GB before any attachments.

For large historical estates, the pattern most teams adopt is: keep originals in S3 or Zoho WorkDrive, store a deep link in a custom URL field on the Candidate record, and only inline-upload the current active subset.

Job Openings and the Hiring Pipeline

Recreate the Hiring Pipeline, its Stages, and every Candidate Status mapped to each Stage in Zoho before importing any Application or Submission. The Hiring Pipeline lives at Setup → Hiring Pipeline on accounts with the Applications module enabled, or Setup → Customization → Hiring Pipeline on the older version51. Default stages are Screening, Interview, Hired, Rejected and Archived; each stage owns a set of statuses (for example, Submitted to Client and Rejected by Client live under Client Review).

The mapping rule is one-way: a Candidate Status must be mapped to a Stage for that status to appear in the pipeline view51. Unmapped statuses are imported successfully into the Candidates module but disappear from pipeline reporting until mapped. Also note: *Mapping or unmapping a status changes the Modified Time field's value for every record with that status*51 — do all your pipeline-status remapping before the production import, not after.

Common source → Zoho Recruit Job Opening mapping
SourceDestinationNote
job_title / posting_titlePosting TitleMandatory; primary display field
job statusJob Opening Status (picklist)Map to existing values: In-progress, On-Hold, Filled, Cancelled
client / companyClient (Lookup, Staffing only)Import Clients first; populated by Client Name or ID
hiring_managerContact (Lookup)Import Contacts first; map by email or Record ID
salary rangeSalary (currency field)Strip currency symbols; respects org base currency
number_of_positionsNumber of PositionsInteger; controls forecasting and pipeline math
assigned recruiter(s)Job Opening Owner + User fieldOwner is the primary; co-recruiters via User field on Enterprise52

Applications / Submissions — stage transition history

Applications (the join record between a Candidate and a Job Opening) carry their own stage history through the Application Status field. Stage transition history does not migrate natively — Zoho only records the current Status and the Modified Time. To preserve historical stage-entry timestamps, create one Date-Time custom field per stage on the Applications module (Screening Entered, Phone Screen Entered, Onsite Entered, Offer Sent, Hired) and back-fill from the source export's stage transition log.

For Staffing Agency edition, Submissions to clients are tracked through the same Applications module with status values like Submitted to Client, Approved by Client, Rejected by Client — all of which the Hiring Pipeline groups under *Client Review*51. Preserve the source's submission-sent-to-client date in a custom Submission Date field; the current Application Status on import will not carry that timestamp.

Interviews and scorecards

Interviews live in their own Module with required fields Interview Name, From Time, To Time and a Lookup to the parent Candidate (and optionally Job Opening). Build a multi-file load: parent records first, then a separate Interviews file carrying the Candidate Record ID or External ID in the lookup column, with From Time and To Time in the org locale date-time format16.

Interviewer Assessments — Zoho's scorecard feature — supports three rating types: Star (1–5), Thumb (up/down), and Numerical57. These do not migrate as data; the scorecard template (sections, criteria, rating type) is configured in Setup → Customization → Assessments before the first interview record imports. Historical interviewer ratings from the source typically land as text in a custom Notes field per interview record, then go forward into Zoho's native rating system from the cutover date.

Candidate sources, EEOC and self-identification fields

Candidate Source is a picklist on the Candidate record (Indeed, LinkedIn, Employee Referral, Career Site, Vendor, Direct). For source taxonomy that needs more depth than a single picklist — campaign source plus medium plus referrer — add a Custom Picklist Source Detail alongside the standard Source field, and use field dependency mapping to gate the child values.

EEOC self-identification fields (Gender, Race/Ethnicity, Veteran Status, Disability Status) are not standard on Zoho Recruit — they are added as custom picklists on the Candidates module with the picklist values matching the US EEO-1 categories. Mark these fields as field-level-restricted to admin and EEOC-compliance roles via Profile permissions so they do not appear on recruiter views or careers-site form payloads. For HIPAA-adjacent health information, Zoho Recruit supports a health module flag that restricts export of fields tagged as health-relevant50.

Vendor portal and Career Site post-import

Staffing Agency edition exposes a Vendor portal where external recruiting agencies log in and submit candidates directly into the Vendors-owned section of the Candidates module58. Migrate Vendors first (Vendor Name, contact details, agreed split percentage), then send portal invitations after go-live — do not enable Vendor portal during the import window, or you will get duplicate candidate submissions racing against the historical load.

The Career Site is a white-label careers page that publishes Job Openings flagged Published with a unique URL; the Forms Builder captures applicants directly into the Candidates module. Both are configured post-migration; the application-from-career-site path will use a default Candidate Source value you set during configuration.

Audit trail, ownership and original timestamps

Zoho Recruit's standard Created Time and Modified Time fields are system-managed on most Modules and cannot be overwritten on import — they stamp to the moment the row was processed51. To preserve the original audit trail, create custom Date-Time fields Legacy Created Date and Legacy Modified Date on every Module and populate from the source export, then rewrite historical reports to filter on the legacy fields.

Record ownership during import works through a Field Mapping column on Owner — Zoho resolves the value against existing user email or user ID; rows whose owner cannot be resolved silently fall back to the importing user52. Pre-provisioning all users (including the deactivated ones from the source if you need their historical attribution) and adding their emails to the source export's Owner column is the only reliable defence.

Account-level Audit Log under Setup → Data Administration → Audit Log captures Add, Update, Delete, Import, Export, Lead Conversion, Rollback, Restore, and Find-and-Merge actions across Candidates, Clients, Contacts, Job Openings and Interviews, plus configuration changes to Workflows, Profiles and Layouts42. Files imported within the last 60 days appear in Import History; detailed added/updated/skipped lists are retained for 7 days post-import, after which only the aggregate counts remain41.

ATS-specific: Workflow, Blueprint, Zia AI, and Resume Extractor

Workflow Rules, Blueprint state machines, Assignment Rules, Scoring Rules and Macros do not import. Recreate the source's process gates as Blueprint transitions in Setup → Process Management → Blueprint, mapping the source's stage-permission rules to Blueprint Transition Settings. Rebuild Assignment Rules under Setup → Automation → Assignment Rules. Validation Rules under Setup → Customization → Validation Rules enforce data quality at save time — recreate from documentation15.

Zia AI is Zoho's machine-learning layer for candidate matching, sentiment analysis and fit scoring. It learns from production data on the destination, so it does not import — give it 30 to 60 days of post-migration activity before relying on Zia scores in recruiter workflows. Deluge custom functions are the in-platform scripting layer and the right place to write post-migration glue logic (de-dup loops, batch-tagging, legacy-ID lookups, vendor-portal pre-checks).

Email integration with Zoho Mail, Gmail, Outlook or any IMAP inbox happens through RecruiterInbox configured per user post-migration32. Do not enable email sync during the import window, or you will get a flood of duplicate emails as the connector backfills against the same candidates you are loading.

The pitfalls that derail Zoho Recruit migrations

Specific failure modes — ranked by impact, each tied to the exact Zoho Recruit mechanism that breaks.

Validation and cutover

What to verify after the import job, in what order — and how to fail safely when something is wrong.

Validation is the bridge between the import finishing and recruiters being allowed in. The pattern that works on Zoho Recruit is three stages: a dry-run on 5–10 percent of records with stakeholder spot-checks; a production load with real-time monitoring of Import History per Module; and a 30-day post-migration data-quality audit. Recruiters verifying their own assigned candidates is the most reliable signal — they know what right looks like.

Build a reconciliation queries spreadsheet that compares source and destination on each count. Anything outside a 0.5 percent variance gets investigated before users get login access.

  • Total records per Module imported vs source — Import History under Setup → Data Administration → Import History lists added, updated and skipped counts per file for 60 days post-import41.
  • Total Candidates per Status vs source, and total Applications per Hiring Pipeline Stage — a non-trivial variance signals a status-not-mapped-to-stage problem51 or a picklist-value-not-on-destination skip.
  • Total Job Openings per Job Opening Status vs source — confirm Filled, In-progress, On-Hold and Cancelled counts match before recruiters start working open requisitions.
  • Total Interviews and Activities per Module (Tasks, Calls, Events) imported vs source — and a date-bucketed comparison to confirm From Time, To Time and Activity Date round-tripped through the locale date format16.
  • Lookup integrity per Module pair — count Candidates with a populated Application Lookup, Applications with a populated Job Opening Lookup, Job Openings with a populated Client Lookup (Staffing). Any null lookups indicate a parent-import order issue.
  • Owner distribution — group by Candidate Owner and confirm no Module landed with the import-running user owning the majority of records (the silent fallback signature)52.
  • Duplicate-check field integrity — count distinct Email on Candidates and Contacts, distinct Client Name on Clients; any duplicates indicate the dedup transform missed cases that Zoho's import then merged.
  • Resume file attachment count vs candidate count — confirm every Candidate that should have a resume actually has one attached, since the resume-upload pass runs after the Candidate import and can fail silently on storage-tier overflow30.

On top of reconciliation, run a manual spot-check protocol: pick 30 random candidates across Statuses and verify each field plus the attached resume against the source UI. Trace the full Lookup graph on five high-value Job Openings — Client, hiring-manager Contact, all Applications and their Candidates, scheduled Interviews. If a discrepancy shows up in three or more of the 30, halt the load, fix the root cause, and re-import by Record ID or External ID.

Zoho Recruit ships an Undo Import option directly inside Import History — entries from the last 60 days expose an Undo action that reverses the import for that file41. The catch is that detailed undo metadata (added / updated / skipped lists) is retained for only 7 days after the import, and after 30 days the import action is locked and confirmed automatically with no further undo41. Any rollback decision needs to happen inside the 7-day window.

After the 7-day window, your fallback is the same as on any ATS: export everything before the import, stamp every imported row with an Import Batch ID custom field, and bulk-delete by that batch ID if catastrophe strikes. Recycle Bin and Restore sit alongside Undo Import: deleted records can be restored individually or in bulk for 60 days before permanent purge42.

Audit Log under Setup → Data Administration → Audit Log tracks every Add, Update, Delete, Import, Export, Rollback and Restore action for the last 60 days, scoped by Administrator profile (full) or own-and-subordinate (other profiles)42. Export to CSV for longer retention before the 60-day window closes.

Cutover sequencing: (1) source ATS goes read-only and recruiters are notified; (2) final delta export captures every candidate, application and interview that changed during the test-import window; (3) delta is imported via the same Data Migration flow; (4) reconciliation runs against the delta; (5) recruiters get login access and a 48-hour hyper-care window with the migration lead on call; (6) source decommission is scheduled for 30 to 90 days out, never the same day.

Migration partners and tools

Authorized Zoho Partners, iPaaS vendors, specialist migration shops — what each is good for and how to choose.

The Zoho Partner Program credentials Authorized, Advanced and Premium Partners through certifications, customer count and revenue tiers, and exposes them through the Find a Zoho Partner directory at zoho.com/partners38. For Zoho Recruit specifically, partners with explicit Bullhorn-to-Recruit, JobDiva-to-Recruit, Workable-to-Recruit or Freshteam-to-Recruit practices tend to ship cleaner than generalist Zoho implementation shops.

Zoho also runs an in-house Recruit migration team reachable through the migration-request form at zoho.com/recruit/migration-request, which handles complex Bullhorn, CATS, JobDiva and Workable migrations directly, often at no incremental fee on Enterprise or Zoho One contracts56. The trade-off is throughput — the in-house team is best for clean source schemas and lighter customisation; deeper Custom Module work, Blueprint rebuilds, Vendor portal configuration and historical Application stage history tend to land with the certified-partner channel.

On the ETL and iPaaS side, Fivetran, Airbyte, Stitch, Workato, Make, Zoho Flow and Zoho DataPrep all sit alongside Zoho Recruit migrations40. Their role in a migration is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that converts picklist values and resolves owner emails, and the ongoing-sync layer that takes over once the one-time migration is complete.

Make and Workato are common picks where the migration is bundled with workflow rebuilds; Fivetran and Airbyte are more common where the warehouse is the long-term source of truth. Zoho DataPrep sits closest to the import boundary and is the right tool when the team wants AI-assisted dedup and standardisation directly inside the Zoho stack40.

Managed-migration cost ranges vary widely. A clean Freshteam-to-Recruit or Workable-to-Recruit move of under 10,000 candidates with no historical Submissions and standard Modules only often lands in the $2,500–$8,000 range with a setup fee plus per-Module pricing. A Bullhorn-to-Recruit project with Custom Modules, Vendor portal setup, Blueprint rebuilds, historical Applications and resume-file migration typically runs $15,000–$80,000 — driven by candidate count, custom-field complexity, historical depth, vendor multi-tenancy, and integration rebuild count.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Zoho Recruit migrations and handles the Hiring-Pipeline-to-Status mapping, picklist alignment, duplicate-check upsert wiring, Created-Time-to-Legacy-Date custom-field pattern, resume-file attachment pipeline, owner-resolution pre-checks, and the reconciliation work in Sections 5 and 7 of this guide. Pricing is fixed-fee based on candidate count and source ATS, with separate line items for Custom Modules, Vendor portal, historical Applications and Blueprint rebuilds.

This is one of several legitimate paths — the right choice depends on whether the team wants a Premium Partner, Zoho's in-house migration team, an iPaaS-first approach, or a specialist vendor. [Explore FlitStack →](/contact)

Zoho Recruit migration checklist

Sequenced punch list for moving applicant-tracking data into Zoho Recruit across Candidates, Job Openings, Applications, Interviews, and Offers — covering export, transform, sandbox test, cutover, and validation. Typical timeline: 4–12 weeks.

0. Decide & Plan9 tasks
  • Choose the Zoho Recruit edition before any provisioning. Pick between Corporate HR (in-house hiring) and Staffing Agency (Clients and Vendors modules). The edition gates Custom Modules, Multi-Select Lookup, User fields, Blueprint, Sandbox, and storage ceilings (Free 256 MB, Standard 1 GB, Professional 2 GB, Enterprise 3 GB).If skipped: Choosing Corporate HR when the operation is staffing locks Clients and Vendors out, forcing a re-purchase and re-provision.
  • Document the in-scope Zoho Recruit Modules. List every standard Module to load: Candidates, Contacts, Clients, Job Openings, Applications, Interviews, Offers, Vendors, Tasks, Events, Calls, plus any Custom Modules to be created.If skipped: Late-discovered Modules force schema changes mid-migration and trigger re-runs of upstream transform jobs.
  • Define the historical-data scope window. Decide how many years of closed Job Openings, hired Candidates, archived Applications, completed Interviews, and stored resumes are in scope. Decide whether resume binaries are in scope or stay in legacy archive.
  • Decide the audit-timestamp strategy. Zoho Recruit stamps Created Time and Modified Time at the moment of insert and does not let bulk imports override them. Pick one strategy: capture source CreatedDate in a custom Date field per Module, or accept that Created Time equals migration date.If skipped: Without a decision, every report shows every candidate created on cutover day, which destroys time-to-fill and source-of-hire trends.
  • Document data-residency and compliance requirements. Zoho operates regional data centers (US, EU, IN, AU, JP, CN, CA). Confirm which DC the org must live in, whether GDPR enablement is required for candidate PII, and whether HIPAA scope applies (Recruit supports HIPAA flag for healthcare staffing).If skipped: Provisioning in the wrong DC cannot be reversed by moving data later — it requires a fresh org and a second migration.
  • Name a single accountable migration owner (DRI). One person signs off on Phase 0, Phase 4 sandbox results, and Phase 6 reconciliation. No committee.
  • Set the cutover date, time, and source-system freeze window. Avoid windows that overlap with active req openings, scheduled interview panels, or offer-extension deadlines.
  • Write the success criteria. Concrete pass/fail statements: total Candidate count matches source within 0.1 percent, every open Job Opening has the correct Hiring Pipeline stage counts, every recruiter can log in and see assigned candidates.If skipped: Without written criteria, the migration drags on indefinitely because nobody can declare it done.
  • List explicitly out-of-scope items. Examples: source-system custom dashboards (rebuild manually), source-system Workflow Rules (rebuild in Zoho), deleted records in the legacy recycle bin, audit logs older than 60 days from the source.
1. Pre-Migration Prep27 tasks
  • Export current record counts per source object as a baseline. Capture exact counts for Candidates, Job Openings, Applications, Interviews, Offers, Clients, Contacts, Vendors. This is the reference number for Phase 6 reconciliation.If skipped: Without a baseline, you cannot prove what was lost in transit.
  • Run deduplication on source Candidates using email as the match key. Email is the system-defined duplicate-check field on the Candidates module. Resolving duplicates upstream is faster than untangling them after load.If skipped: Duplicate Candidates post-load split resume history and interview feedback across two records.
  • Run deduplication on source Clients using company name plus domain. Pick one canonical Client record per company; merge child Contacts and Job Openings onto it.
  • Standardize email casing and trim whitespace across all email fields. Convert to lowercase. Strip leading/trailing spaces. Email is the default duplicate-check field on Candidates and Contacts.
  • Normalize phone numbers to E.164 with country code. Pick one format and apply it uniformly across Candidates, Contacts, and Clients before export.
  • Identify and fix records missing Zoho Recruit mandatory fields. Last Name is mandatory on Candidates and Contacts. For records with no last name, populate with 'not provided' or 'none' before export, otherwise Zoho Recruit silently skips the row.If skipped: Rows with empty mandatory fields are silently skipped by the importer and do not appear in the destination.
  • Inventory custom fields on the source ATS. Export name, type, picklist values, validation rules, and whether the field is required. This becomes the source side of the Phase 3 mapping spreadsheet.
  • Document source Hiring Pipeline stages and Candidate statuses. Zoho Recruit models the pipeline as Stages containing one or more Candidate Statuses. Export the full source list so destination stage definitions can be built in Phase 1b.If skipped: Missing source statuses cause Application rows to land in the default Screening stage instead of the correct historical stage.
  • Inventory source resume binaries and confirm storage volume. Count file objects and total GB. Compare against the chosen edition's storage cliff (Free 256 MB, Standard 1 GB, Professional 2 GB, Enterprise 3 GB plus per-user adders).If skipped: Loading 50 GB of resumes into a Professional org (2 GB default) saturates storage and blocks new uploads.
  • Provision the production Zoho Recruit org in the chosen data center. Confirm the DC URL (.com, .eu, .in, .com.au, .jp, .com.cn, .ca) matches the Phase 0 residency decision.
  • Provision a Sandbox org on Enterprise editions where available. Use a configuration plus sample-data clone so Layouts, Hiring Pipeline, Profiles, and Roles align with intended production config before any test load.If skipped: Skipping a sandbox forces every test to happen in production where recruiter users see test candidates.
  • Add at least two Users before any import. Zoho Recruit's Data Migration tool requires at least two user accounts. Create destination Users with email matching source-system user emails so Owner fields resolve.If skipped: Single-user orgs cannot start a Data Migration job — the wizard blocks until a second user is added.
  • Build the Role hierarchy and Profiles before any import. Roles control record-sharing scope; Profiles control field-level permissions. Records load against whatever Profile rules exist at insert time.
  • Set org-level Currency, Time Zone, Fiscal Year, and Date Format. These affect how imported timestamps and currency values on Offers are parsed. Lock them before any sandbox test.If skipped: Changing time zone after import does not retroactively re-stamp records and creates an off-by-N-hours bug on every interview timestamp.
  • Create Custom Modules required by the source schema. Use Setup > Customization > Modules. Custom Modules are gated to Enterprise+. Decide naming, primary field, and singular/plural labels now — these are hard to change later.
  • Create every custom field on every Module before any import. Zoho Recruit cannot create destination fields on the fly during bulk import. Importing into a field that does not exist drops the column silently.If skipped: Silent column drops are the single most common cause of Phase 6 reconciliation gaps.
  • Create every picklist value any record will use, including Candidate Status values. Use Setup > Customization > Modules > {Module} > Field properties. Capture both display label and reference value — bulk imports key off the reference value.If skipped: Unknown picklist values are rejected row-by-row and the row is skipped.
  • Configure Field Dependency mappings before import. If parent picklist controls child picklist values, set the dependency in Setup > Customization > Modules > Map Dependency Fields per Module. Dependencies are scoped per Module — set them on every Module that uses them.
  • Mark Email and any source-unique-ID column as Unique fields on Candidates and Contacts. Setup the field as a Unique field so Zoho's importer offers it as a duplicate-check option. This drives Skip/Overwrite/Clone behavior on rerun.If skipped: Without a Unique field, the importer cannot match incoming rows to existing records and inserts duplicates on every rerun.
  • Build the Hiring Pipeline with all required Stages. Setup > Customization > Hiring Pipeline. Add custom stages beyond the defaults (Screening, Hired, Rejected, Archived). Map every Candidate Status to a stage — unmapped statuses do not appear in the pipeline.If skipped: Applications referencing a status that is not mapped to a stage land outside the pipeline view and become invisible to recruiters.
  • Configure Validation Rules to match source data shape. If source allows years-of-experience over 50 but destination Validation Rules cap at 50, the row is rejected. Loosen rules during import or pre-filter source values.
  • Configure field-level permissions per Profile. Hide or mark read-only any sensitive field (EEOC self-identification, salary expectations) that should be restricted per Profile.
  • Pause all Workflow Rules, Assignment Rules, Macros, and Blueprint state transitions. Inserts during bulk load otherwise trigger workflows that fire candidate auto-emails, move Applications into the wrong Blueprint state, or assign records via round-robin.If skipped: An active candidate-welcome workflow during a 10,000-Candidate load emails every candidate at cutover.
  • Disable email-notification recipients on Modules being imported. Turn off Notify Owner and any subscription-based email triggers during the import window.
  • Announce the source-system freeze window to all recruiters and hiring managers. Pin the announcement in chat and email it at T-7 days, T-1 day, and T-1 hour.
  • Schedule training sessions on Zoho Recruit basics segmented by role. Recruiters, hiring managers, interviewers, and admins need different content. Aim for sessions within 5 business days of cutover.
  • Designate first-responder support contacts for the 48 hours post-cutover. At least one Zoho Recruit admin on call. Name them publicly.
2. Source Export17 tasks
  • Export Candidates as CSV with all standard and custom fields. Include source primary key as a column so it can be loaded into the destination External ID custom field. Include Candidate Source, Candidate Status, Owner email, and resume file pointer.
  • Export Job Openings as CSV with all fields plus the Client lookup. Include Job Opening ID, Job Title, Posting Title, Status, Number of Openings, Target Date, and assigned recruiters.
  • Export Applications as CSV with Candidate ID, Job Opening ID, Candidate Status, and Submission status. Applications are the junction between Candidates and Job Openings in Zoho Recruit. Each row binds one Candidate to one Job Opening with a status snapshot.If skipped: Exporting Applications without both foreign keys forces manual re-association at scale, which is error-prone.
  • Export Interviews as CSV with parent Candidate/Application/Job Opening lookups, datetime, interviewer, and outcome. Include interview type (Phone Screen, On-site, Panel), location, and any scorecard linkages.
  • Export Offers as CSV with Candidate ID, Job Opening ID, offer status, salary, start date, and expiry.
  • Export Clients and Contacts as separate CSVs with the Client → Contact lookup preserved (Staffing Agency edition). Skip if the destination is Corporate HR edition.
  • Export Vendors and Vendor-submitted candidates if running Staffing Agency edition.
  • Export Tasks, Events, and Calls as three separate CSVs. Each has a different schema in Zoho Recruit. Include the parent record ID (What ID / Who ID equivalents).
  • Export Notes as a CSV linked to their parent record IDs. Note content can include line breaks and quotes; ensure the exporter quotes correctly. Note character cap in Zoho Recruit is 32000 per note.
  • Export Email message history with parent record associations. Zoho Recruit has no native bulk import for past emails into the candidate timeline. Plan to load them into a custom Email Log Module or attach as Notes with an Email Date custom field.If skipped: Treating email history as a standard Note loses the threading and sender metadata.
  • Export resume metadata: file name, size, MIME type, and parent Candidate ID. Separate file from metadata; both are required at re-upload time.
  • Download resume binaries and any other attachments to a staging bucket. Per-record attachment cap in Zoho Recruit is 20 MB total per record across all files. Flag any oversize file for the Phase 3 decision.If skipped: Files larger than the per-record cap silently leave the Candidate unlinked from their own resume.
  • Export interview scorecards and assessment results. Zoho Recruit supports Star, Thumb, and Numerical rating types on Interviewer Assessments. Export source ratings as a per-assessment row so they can be mapped to the destination rating type.
  • Export the full User list with email, role, profile, and active/inactive flag.
  • Export source Hiring Pipeline stages and Candidate Status definitions as a reference document. This becomes the source side of the Status-to-Stage mapping in Phase 3.
  • Capture screenshots of source dashboards, reports, and Workflow Rules. These do not migrate. They will be rebuilt manually in Phase 7.
  • Record the exact UTC timestamp of each export. This is the baseline for the Phase 5 delta export.
3. Transform & Map34 tasks
  • Build a master mapping spreadsheet covering every source field. Columns: Source Module, Source Field, Source Type, Destination Module, Destination Field, Destination Type, Transformation Rule, Required (Y/N), Upsert Key (Y/N), Notes.If skipped: Without a single mapping document, transform logic drifts between engineers and reconciliation finger-pointing becomes unavoidable.
  • Confirm field-type compatibility row by row. Zoho Recruit does not let you change field type after creation. A source Currency field cannot be loaded into a destination Picklist field — either change the destination field type now or transform the source value.If skipped: Importing a Currency value into a Picklist field returns 'Import Failed Abruptly' and the entire job halts.
  • Decide upsert key per Module. Typical pattern: Email on Candidates and Contacts; source primary key in an External ID custom field on Job Openings, Applications, Interviews, and Offers.
  • Decide what to do with source fields that have no destination equivalent. Three options per field: drop, create a custom field, or concatenate into Description/Notes.
  • Resolve every picklist value mismatch. Source 'Submitted to Hiring Manager' → Destination 'Submitted to Client'. Build a value-translation lookup that maps every distinct source value to a valid destination value before export. Watch the distinction between picklist reference value and display label (shown in UI).If skipped: Mismatched picklist values cause row-level skips at insert time, with the row reported in the import error log but not loaded.
  • Map Profiles and Roles between source and destination. Source 'Recruiter' → Destination 'Standard Recruiter' Profile, for example. This drives the Owner assignment in Phase 5.
  • Convert all dates and datetimes to the format declared at import time. The Data Migration wizard asks for date format and time format up front. Choose mm/dd/yyyy or yyyy-MM-dd, then transform every source file to match exactly.If skipped: Date-format mismatches at import time cause every Date column to land null or rejected.
  • Re-encode every CSV as UTF-8. Zoho Recruit importer requires UTF-8. Files exported from older systems often land as Windows-1252 or UTF-16; verify with a hex check on the byte-order mark.If skipped: Non-UTF-8 files cause accented characters to corrupt to mojibake on Candidate names.
  • Normalize salary and offer-currency values to the org default currency or include per-record currency code. For multi-currency orgs (Enterprise+), include the currency code per row. For single-currency orgs, pre-convert at the historical FX rate.
  • Truncate text fields that exceed Zoho Recruit character limits. First Name caps at 40 characters, Last Name at 80, City at 30, Email at 100. Decide whether to truncate or split oversize source values into a paired Description field.If skipped: Rows exceeding field width are skipped during bulk import with INVALID_DATA errors.
  • Escape commas, quotes, and newlines in long-text fields. RFC 4180 quoting: wrap any field containing a comma or newline in double quotes and double any embedded double quotes.
  • Split combined Name fields into First Name and Last Name where the destination Module requires it. Candidates, Contacts, and Vendors store Last Name as the mandatory field.
  • Compress resume archives into ZIP and pre-stage them by parent Candidate ID. Staging by parent ID lets you script the re-upload deterministically.
  • Pre-split large CSV files into multiple import jobs. Zoho Recruit's bulk import has per-job size and record ceilings. Split source exports accordingly before zip.If skipped: Oversize zip files throw an error before any record is loaded.
  • Validate that the CSV delimiter is comma, semicolon, colon, or pipe. The bulk importer auto-detects the delimiter from the header row but only supports those four.
  • Implement the historical-timestamp strategy chosen in Phase 0. Zoho Recruit does not let bulk imports override Created Time / Modified Time. Populate a 'Source Created Date' custom Date field per Module instead, and use it for time-to-fill and source-of-hire reporting.If skipped: Reporting on Created Time shows every record dated to migration day, which destroys time-series trend analysis on hiring velocity.
  • Decide the Owner assignment strategy and encode it on every export row. Option A: best-match by email against the Zoho User list. Option B: assign everything to a single 'Data Migration' user. Option C: use an Assignment Rule. Pick one and apply uniformly.
  • Decide the resume-attachment strategy. Option A: re-upload binaries into each Candidate record (counts against storage). Option B: store binaries in external storage and link via a URL custom field. Option B preserves storage quota.If skipped: Re-uploading 50 GB of resumes into a Professional org (2 GB cap) saturates storage and blocks new uploads.
  • Decide whether to use Resume Extractor on re-uploaded resumes. Resume Extractor parses uploaded resumes into Candidate fields (skills, education, work history). If source records already have these fields populated, decide whether to let Resume Extractor overwrite them or skip the parse on import.If skipped: Re-parsing resumes after migration overwrites human-curated Candidate fields with parser output, which is often less accurate.
  • Resolve Candidate → Job Opening junctions via the Applications module. Zoho Recruit models the many-to-many relationship between Candidates and Job Openings through Applications. Load order: Candidates → Job Openings → Applications. Each Application row references both parent IDs.If skipped: Out-of-order loads leave Application rows with broken Candidate or Job Opening lookups and no error message.
  • Resolve many-to-many relationships via Multi-Select Lookup fields where needed. Multi-Select Lookup is Enterprise+. On lower editions, create a junction Custom Module with two lookups instead.If skipped: Attempting to model many-to-many on Standard or Professional editions silently flattens to one-to-many and loses associations.
  • Map source Candidate Statuses to Zoho Recruit Hiring Pipeline stages. For every distinct source status, write the matching destination Candidate Status and the Hiring Pipeline Stage it maps to (Screening, Submission, Interview, Offer, Hired, Rejected, Archived, or custom). Map every status — unmapped statuses do not show up in the pipeline.If skipped: Applications referencing an unmapped status fall outside the pipeline view and become invisible to recruiters.
  • Re-upload resume binaries to Candidate records after Candidate inserts. Resume Extractor parses an uploaded resume into Candidate fields when enabled. Decide pre-load whether to suppress Resume Extractor on bulk re-uploads to avoid overwriting transferred field values.If skipped: Letting Resume Extractor run on every re-uploaded resume overwrites the transferred Skill, Experience, and Education fields with parser output.
  • Build the Submissions pipeline as Candidate → Application → Interview → Offer. Each step is a separate Module in Zoho Recruit. The Application binds a Candidate to a Job Opening. The Interview hangs off the Application. The Offer hangs off the Candidate plus Job Opening.
  • Reconstruct stage-transition history via custom per-stage Date-Time fields. Zoho Recruit auto-captures Modified Time on status changes going forward but does not let you backfill stage-transition history. Create custom Date-Time fields per pipeline stage (e.g., Date Reached Screening, Date Reached Interview, Date Hired) and populate them during transform from source history.If skipped: Pipeline velocity reports for periods before cutover will be empty because Modified Time is overwritten on every subsequent status change.
  • Map Candidate Source field values to the destination picklist or Assignment Rule. Candidate Source drives source-of-hire reporting. The import wizard offers an 'Assign all imported Candidates to this Candidate Source' option for bulk-tagging during load. Map distinct source values (Indeed, LinkedIn Recruiter, ZipRecruiter, Naukri, Referral, Career Site) to destination picklist entries.If skipped: Source-of-hire dashboards break if source values land as free text instead of picklist entries.
  • Create EEOC self-identification fields as custom restricted fields. Race, Gender, Veteran Status, and Disability Status data should live in Zoho Recruit as custom fields with Profile-level read restrictions so only HR Compliance Profiles can view them. Load the values once these fields and permissions exist.If skipped: Loading EEOC data into an unrestricted field exposes protected-class data to every recruiter, creating an EEO violation.
  • Enable the HIPAA flag on Modules that store protected health information. For healthcare staffing, mark modules containing PHI as HIPAA-protected via Setup > Compliance > HIPAA Compliance. This restricts export of those modules to specific Profiles.
  • Map interview scorecards to Zoho Recruit's Star, Thumb, or Numerical rating type. Pick one rating type per assessment template. A 1–5 source scale maps cleanly to Star Rating. A binary pass/fail maps to Thumb Rating. A free-form score maps to Numerical Rating with min/max.If skipped: Mixing rating types within one assessment template forces a manual choice at every interview and breaks score-roll-up reports.
  • Encode Interview Scheduling fields: datetime, interviewer, location, type. Zoho Recruit's Interviews module stores interview type (Phone, In-person, Video) as a picklist. Map source types accordingly.
  • Map Offers fields: salary, start date, expiration, offer status. Offer status picklist typically includes Pending, Extended, Accepted, Declined, Rescinded, Expired. Confirm destination values match source workflow.
  • Decide how to handle source vendor submissions (Staffing Agency edition). Vendor-submitted candidates can be loaded as Candidates with a Vendor lookup populated, or as records under a separate Vendor Submissions Custom Module. Decide before transform.
  • Identify Multi-Select Picklist fields and pre-split values with semicolons. The bulk importer expects multi-select values as a semicolon-delimited string within a single CSV cell.
  • Translate source email-marketing opt-out flags into Zoho Recruit's Email Opt Out. Honor candidate unsubscribes before any career-site or campaign integration sync.If skipped: Loading opted-out candidates as opted-in is a CAN-SPAM and GDPR violation.
4. Sandbox Test Migration14 tasks
  • Load a 1–5 percent representative sample of every in-scope Module into the Sandbox. Use Setup > Data Administration > Data Migration for the wizard. Match the production method exactly.
  • Validate field-by-field on 10 random Sandbox Candidates. Open each record in the UI and compare every field to the source export. Document any discrepancy.If skipped: Sampling fewer than 10 records misses field-level drops that only surface on certain Candidate subtypes.
  • Test the Candidate Status to Hiring Pipeline Stage mapping across every stage. Load Applications with every distinct source status and confirm each lands in the correct pipeline stage.If skipped: An untested status discovered in production leaves Applications outside the pipeline and invisible to recruiters.
  • Test picklist reference values against display labels. Confirm the value lands in the right picklist option by inspecting the underlying stored value, not just the rendered UI label.
  • Test datetime timezone handling on at least 3 Interview records. Pick interviews scheduled near midnight to surface off-by-one-day errors.
  • Test special-character handling: emoji, accents, quotes, newlines on Candidate names and notes. Pick at least 5 source records containing each.If skipped: Character-encoding bugs are invisible until a recruiter opens the Candidate and sees mojibake.
  • Test resume upload on at least 25 Candidates. Verify file integrity (size matches source) and that the resume appears in the related list on the Candidate.
  • Test whether Resume Extractor overwrites populated fields. Upload a resume to a Candidate that already has Skills populated. Confirm the Phase 3 decision (let it overwrite vs suppress) actually works.If skipped: If Resume Extractor unexpectedly overwrites fields, every Candidate's transferred data is silently degraded.
  • Confirm the Phase 3 audit-trail strategy actually worked. Spot-check the 'Source Created Date' custom field is populated on every record.
  • Have a recruiter spot-check Candidate and Application records in Sandbox. Real users find issues data engineers miss: missing scorecards, wrong status names, lost Job Opening associations.
  • Have a hiring manager spot-check Interview and Offer records in Sandbox. Validate interview panels, scorecard ratings, and offer-letter fields against source records.
  • Test EEOC field permissions per Profile. Log in as a non-Compliance Profile and confirm EEOC fields are hidden. Log in as Compliance and confirm visibility.If skipped: EEOC field permission misconfiguration leaks protected-class data to every recruiter.
  • Capture timing for every import job for production planning. Job submit → completion times let you size the production cutover window realistically.
  • Get written sign-off on Sandbox results before scheduling production cutover. Email or ticket; do not proceed on verbal approval.If skipped: Verbal sign-offs evaporate when reconciliation surfaces an issue post-cutover.
5. Production Cutover12 tasks
  • Confirm source-system freeze. Inspect source-system audit logs to verify no record-modifying activity in the last hour.
  • Take the final delta export of every in-scope object. Same exporter as Phase 2, same field set, new timestamp suffix on filenames.If skipped: Skipping the delta loses every Candidate, Application, and Interview created between Phase 2 export and cutover.
  • Confirm Workflow Rules, Assignment Rules, Macros, and Blueprints are paused. Spot-check the Setup UI. Inadvertent activation between Phase 1 and Phase 5 is a common cause of surprise side effects.If skipped: An active candidate-welcome workflow at cutover sends thousands of accidental candidate emails in minutes.
  • Load Users first (or confirm Users were created in Phase 1). Users must exist before any Owner field can resolve. Confirm at least two active Users exist before any Data Migration job.
  • Load parent Modules before child Modules. Order: Clients → Contacts → Vendors → Job Openings → Candidates → Applications → Interviews → Offers → Tasks/Calls/Events/Notes → resume attachments. Each layer references IDs created in the previous layer.If skipped: Out-of-order loads leave lookup fields blank with no error and require a second pass to repair.
  • Use Insert-or-Update (upsert) keyed off the unique field for every load step that supports it. Specify duplicate_check_fields explicitly (e.g., Email for Candidates) so reruns are idempotent.If skipped: Insert-only loads on partial failure create duplicate Candidates on retry.
  • Capture the import job ID, row count, and error log for every load step. Store these in a cutover run-book alongside timestamp and operator name.
  • Cross-check destination row counts against source row counts at each step. Stop the cutover if any per-Module count differs by more than the agreed tolerance (typically 0.1 percent).If skipped: Pushing through with an unexplained count delta makes Phase 6 reconciliation impossible.
  • Upload resume binaries to each Candidate record. Loop over the Phase 3 stage bucket by parent Candidate ID. Watch the 20 MB per-record total cap.
  • If any step fails, halt — diagnose — fix the transform — re-run idempotently. Never push partial data through to the next step. Import History supports Undo within 30 days, after which the action is locked.
  • Re-enable Workflow Rules, Assignment Rules, Macros, and Blueprints after all loads complete. Document the exact reactivation time in the run-book.
  • Snapshot the production org backup immediately after cutover completes. This is your rollback point if Phase 6 surfaces a fatal issue. Within 30 days, Import History also allows per-job Undo.If skipped: Without a clean post-load snapshot or a tracked Import History job, partial rollback requires per-record manual cleanup.
6. Validate27 tasks
  • Compare total record count per Module: source vs Zoho Recruit. Use the destination list-view count to count records. Investigate any delta beyond the agreed tolerance.If skipped: Unexplained deltas typically trace to skipped picklist values, missing mandatory fields, or status-to-stage mismatches.
  • Compare active Candidate count between source and destination. Filter both systems to Candidates not in Rejected or Archived status. Sums must match.
  • Compare open Job Opening count and per-status counts. Job Opening Status (Open, On Hold, Closed, Cancelled) must show matching counts on each side.
  • Compare Applications per Hiring Pipeline stage. Iterate every Stage and compare source-stage counts to destination-stage counts. Catches Candidate Status to Stage mapping errors.If skipped: Stage-count mismatches typically trace to unmapped source statuses landing in default Screening.
  • Compare Interview counts and scheduled-vs-completed split.
  • Compare Offer counts by status (Pending, Extended, Accepted, Declined).
  • Spot-check 25–50 randomly selected records field-by-field. Pick records across Modules, owners, and stages. Open each in the UI and compare against the source export.
  • Verify all External ID values are populated. Query destination records with null External ID. Any null breaks future incremental syncs.If skipped: Null External IDs force every subsequent upsert to treat the record as new, creating duplicates.
  • Verify a sample of Candidate → Application → Job Opening chains. Pick 20 random Candidates and confirm their Applications resolve to the correct Job Opening with the correct Candidate Status.
  • Verify Interview → Application → Candidate chains. Sample 20 Interviews; confirm parent Application and Candidate both resolve.If skipped: Orphaned Interviews sit in the global Interviews view but never appear in the Candidate timeline.
  • Verify Offer → Candidate and Offer → Job Opening lookups. Sample 20 Offers; confirm both lookups resolve and offer status is correct.
  • Verify Client → Job Opening → Application chains (Staffing Agency edition). Pick 20 random Clients and confirm their Job Openings carry the correct submitted Candidates.
  • Verify resume files open and download correctly. Click 10 random resumes per source year; confirm file integrity and that file size matches source.
  • Verify Tasks, Calls, and Events attach to the correct parent record. Open the parent record's related list and confirm activity counts match source.
  • Confirm the 'Source Created Date' custom field is populated everywhere. Run a filtered list-view query: count of records where the custom date is null should equal zero.
  • Verify EEOC fields are hidden from non-Compliance Profiles. Log in as a Standard Recruiter and confirm Race, Gender, Veteran Status, and Disability Status fields are not visible.If skipped: EEOC field exposure to non-Compliance Profiles is an EEO violation.
  • Run a GDPR data-subject check on Candidates and Contacts. Enable Compliance Settings if required; verify Data Privacy section appears on each record.
  • Confirm HIPAA flag is set on modules containing protected health information. Setup > Compliance > HIPAA. Verify export restriction is active for the flagged modules.
  • Export the Zoho Recruit Audit Log for the cutover window. Capture as SOC 2 evidence of who imported what when. Audit Log retains the last 60 days of actions per Setup > Data Administration > Audit Log.If skipped: Audit logs older than 60 days are not retained in the Audit Log view; pulling them now is cheap, retrieving them later may not be possible.
  • Have 3–5 recruiters validate their day-to-day workflows in production. Hands-on: open a Job Opening, screen a Candidate, schedule an Interview, submit a scorecard, extend an Offer. Document every snag.
  • Have a hiring manager validate the Hiring Pipeline widget on Dashboard. Confirm pipeline counts match recruiter-side view and that Candidate Statuses surface correctly per stage.
  • Run reports from the source and from Zoho Recruit side by side. Pick the 5 reports the business actually uses (Time-to-Fill, Source-of-Hire, Open Reqs, Offer Acceptance Rate). Confirm totals reconcile.
  • Validate Career Site integration if used. Confirm new applications from the Career Site land in the correct Job Opening and trigger the correct Workflow Rules.
  • Validate Vendor portal access (Staffing Agency edition). Log in as a Vendor and confirm visible Job Openings and submission flow match expectations.
  • Validate the Zoho Recruit mobile app shows migrated data correctly. Mobile uses different rendering paths and can surface field-permission bugs the web app hides.
  • Document every UAT issue with severity and owner.
  • Get written sign-off from the migration sponsor. Email or ticket with the success-criteria document attached and each criterion marked pass.If skipped: Proceeding without sign-off leaves the project in a perpetual 'almost done' state.
7. Post-Migration Cleanup16 tasks
  • Communicate go-live to all recruiters, hiring managers, and interviewers. Login URL, who-to-ask-for-help, link to the role-specific training recording.
  • Run live training sessions segmented by role. Recruiters, hiring managers, interviewers, and admins each get a 30–60 minute focused session.
  • Set the source ATS to read-only and announce the date. Read-only prevents accidental new writes that would never reach Zoho Recruit.
  • Rebuild Workflow Rules in Zoho Recruit. Workflow Rules do not migrate from any source system. Use the Phase 2 screenshots as the spec.
  • Rebuild Assignment Rules and round-robin distribution.
  • Rebuild Blueprint state machines for any process that needs them. Blueprint requires Enterprise+. Recreate state transitions matching the Hiring Pipeline stage flow.
  • Rebuild Macros recruiters use day to day. Bulk-update common actions like 'Move to Interview Scheduled' should be replicated as Macros for recruiter efficiency.
  • Rebuild dashboards and standard reports. Reports do not migrate. Recreate the most-used 5–10 first (Time-to-Fill, Source-of-Hire, Open Reqs by Recruiter), then expand.
  • Rebuild any Deluge custom functions or scheduled jobs from the source automations. Source-system scripts (Apex, custom code) have no direct port; rewrite in Deluge.
  • Re-enable job-board integrations. Indeed, LinkedIn Recruiter, ZipRecruiter, Naukri, and any other source boards. Run each in dry-run mode first to confirm no duplicate Candidates land against migrated records.If skipped: Job-board re-sync without External-ID checks duplicates every Candidate that applies again post-cutover.
  • Re-enable Career Site and Forms Builder forms. Test a real application submission end-to-end before announcing.
  • Re-enable Vendor portal access (Staffing Agency edition).
  • Schedule a 30-day post-migration retrospective. Capture what went well, what didn't, and update the migration runbook for the next org.
  • Document the source-system decommission date. Typical pattern: 90 days read-only, then archive the final export to long-term storage and cancel the subscription.
  • Archive all source-system exports and Zoho Recruit migration logs to long-term storage. Retain per the legal-hold and retention policies from Phase 0. Note that Zoho Recruit Audit Log retains only 60 days.If skipped: Discarding exports too early eliminates forensic options if a data-quality issue surfaces months later.
  • Close the migration project formally. Final status report, lessons-learned doc, project closure.

Questions, answered

Migrating to Zoho Recruit: questions

How long does migration to Zoho Recruit take?

A small-agency migration with under 5,000 candidates and standard Modules runs one to two business days end-to-end using the Data Migration wizard. A mid-market project with Custom Modules, Blueprint rebuilds, Vendor portal and historical Applications runs two to four weeks of elapsed time, including validation, training, and a hyper-care window.

Can I migrate from Bullhorn to Zoho Recruit?

Yes — Bullhorn is one of the most common Zoho Recruit migration sources, listed by Zoho alongside CATS, JobDiva and Workable as a completed-migrations source on the migration request page. The Bullhorn Entity model (Candidate, JobOrder, Submission, Placement) maps to Candidates, Job Openings, Applications and Offers. Plan for picklist-value alignment and Vendor portal rebuild.

Can I migrate from Freshteam to Zoho Recruit?

Yes, and Zoho ships a dedicated Freshteam-to-Recruit migration guide because Freshworks is discontinuing Freshteam. Standard objects map cleanly: Freshteam Candidates and Jobs become Recruit Candidates and Job Openings. Users, Departments and Custom Fields must be pre-created on the destination side, and Last Name has to be populated on every row.

Does Zoho Recruit preserve original timestamps on import?

Partially. Activity Date on Tasks, Calls and Events, plus From Time and To Time on Interviews, can be backdated and show on the timeline correctly. But Created Time and Modified Time on Candidates, Job Openings, Applications and most Modules are system-managed and stamp to the import date. Use custom Legacy Created Date fields.

Can I migrate Custom Modules to Zoho Recruit?

Yes, but Custom Modules require an Enterprise, Zoho One or People Plus subscription. The schema, Layouts, fields and Lookups for each Custom Module must exist before any record of that type can be imported. Custom Module records load via the native Import wizard or the Data Migration wizard.

What happens to candidate stage history and application transitions during migration?

Build the Hiring Pipeline, its Stages, and the Candidate Statuses mapped to each Stage before importing Applications — unmapped statuses successfully load on the record but disappear from pipeline reporting. Stage transition history does not auto-preserve; export per-stage entry timestamps from the source into custom Date-Time fields on Applications.

Is there an undo or rollback for Zoho Recruit imports?

Yes — Import History under Setup, Data Administration exposes an Undo action on entries from the last 60 days, but detailed added/updated/skipped lists are retained for only 7 days and the import auto-locks after 30 days. Beyond that window, stamp every imported row with a custom Import Batch ID field instead.

Get a quote

Moving to Zoho Recruit?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Zoho Recruit setup with you, then send a quote.

Get a quote