HRMS migration

Migrate from Occupop to Zoho Recruit

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

Occupop logo

Occupop

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

83%

10 of 12

objects map 1:1 between Occupop and Zoho Recruit.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Occupop to Zoho Recruit is a schema remapping rather than a straight record copy. Occupop organizes hiring around Jobs, each defining a pipeline of Workflow Stages through which Candidates progress; Zoho Recruit uses a module-based model with Candidates as independent records linked to Job Openings, Clients, and Contacts. We resolve the structural difference by treating Occupop's Job-Candidate stage history as structured fields on Zoho Recruit's Candidate record and as stage values on the Job Opening. AI screening scores from Occupop migrate as a numeric Candidate field. We export CV files alongside candidate mappings and deliver them in Zoho Recruit's required Data/Attachments folder structure. Custom Fields migrate by pre-creating Zoho Recruit Layout Editor fields to match the Occupop schema. Board distribution history, offer records, and onboarding state do not have Zoho Recruit equivalents and are excluded from migration scope with a written reference export provided for manual re-entry. Occupop workflows do not migrate; we deliver a written automation inventory for the customer to rebuild in Zoho Recruit Workflow Rules.

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

Occupop logo

Occupop

What's pushing teams away

  • Advanced reporting and deep analytics lag behind enterprise HCM platforms, frustrating People teams that need custom dashboards or cross-pipeline trend analysis.
  • Occupop's feature set narrows as hiring needs scale beyond mid-market volume, pushing fast-growing companies toward platforms like Greenhouse, Lever, or Workday ATS.
  • Integration catalogue is smaller than competitors — teams with established HRIS, payroll, or background-check tools may face manual re-entry or custom integration work.
  • The acquisition by Cezanne HR (March 2025) introduces uncertainty about roadmap direction, pricing continuity, and long-term product independence, prompting some customers to evaluate alternatives proactively.

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

Each row shows how a Occupop 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.

Occupop

Job

maps to

Zoho Recruit

Job Opening

1:1
Fully supported

Occupop Jobs map to Zoho Recruit Job Openings. The job title, description, department, location, and active/closed status migrate directly. Zoho Recruit's Job Opening status field (Open, On Hold, Closed, Cancelled) maps from Occupop's job status. The original Occupop job ID is preserved in a custom field for audit traceability. Job Openings must be created before Candidate records are imported because Zoho Recruit links Candidates to Job Openings via a lookup field that must be resolved at import time.

Occupop

Candidate

maps to

Zoho Recruit

Candidate

1:1
Fully supported

Occupop Candidates map directly to Zoho Recruit Candidates. Core fields (name, email, phone, current company, current job title) migrate 1:1. Occupop's stage history within a Job maps to Zoho Recruit's Candidate-Job Opening association records with status values (Applied, Screening, Interview, Offer, Hired, Rejected) matching the destination stage names. Where stage names differ, we apply a mapping table defined during scoping. AI screening scores from Occupop land as a custom numeric field on the Zoho Recruit Candidate record.

Occupop

Workflow Stages

maps to

Zoho Recruit

Candidate Status per Job Opening

lossy
Fully supported

Occupop's per-Job ordered stage sequence (e.g. Applied, CV Review, Phone Screen, Interview, Offer) maps to Zoho Recruit's candidate status values within each Job Opening. We configure Zoho Recruit's candidate status picklist to match the Occupop stage names during migration scope. Stage probability weights (if present in Occupop) are not natively supported in Zoho Recruit and are delivered as structured notes on the Job Opening record for the customer to configure manually if needed.

Occupop

User

maps to

Zoho Recruit

User

1:1
Fully supported

Occupop Users (Admin, Hiring Manager, Recruiter, Viewer roles) map to Zoho Recruit Users by email match. Role mapping: Occupop Admin maps to Zoho Recruit Administrator profile; Occupop Recruiter maps to Zoho Recruit Recruiter role; Occupop Hiring Manager maps to Hiring Manager role. Note that Zoho Recruit's Free Edition is limited to 1 user; migrations requiring more users must select a paid tier. Users with Viewer-only access in Occupop may map to Zoho Recruit Standard role with restricted module permissions.

Occupop

CV / Attachment

maps to

Zoho Recruit

Attachments (linked to Candidate)

1:1
Fully supported

Occupop CV files export as raw binary files linked to the Candidate record. We deliver CVs in Zoho Recruit's required migration folder structure: a Data folder containing CSVs that reference attachment filenames, and an Attachments folder containing the source files. Zoho Recruit's migration wizard resolves the link between CSV record and attachment file during import. Maximum 200 files per import batch with a 4 GB total zip size limit applies; we chunk large CV sets accordingly. Customers should verify that all source file references in the CSV resolve correctly before upload per Zoho Recruit's migration prerequisites.

Occupop

Interview Feedback / Notes

maps to

Zoho Recruit

Notes / To-Dos (Tasks, Events, Calls)

1:1
Fully supported

Occupop interview notes and scorecard responses are exported as structured text per Candidate per stage. Zoho Recruit does not have a native interview-feedback object with scorecard fields. We land interview notes as Zoho Recruit Notes linked to the Candidate record, and interview scores as custom numeric fields on the Candidate. Interview scheduling details migrate as Event records in Zoho Recruit with date, time, and location preserved. Scorecard evaluation criteria that cannot map to Zoho Recruit's standard fields are delivered as a structured sidecar export for manual reference.

Occupop

Custom Fields

maps to

Zoho Recruit

Custom Fields (Layout Editor)

lossy
Mapping required

Occupop Custom Fields are arbitrary key-value pairs on Candidate records with no fixed schema across tenants. Before migration, we inspect the source tenant's custom field definitions and pre-create equivalent fields in Zoho Recruit via the Layout Editor (Setup > Customization > Modules > Candidates > Layout Editor). Zoho Recruit field types are assigned based on value format: text values become Text fields, numeric values become Number or Long Integer fields, dates become Date fields, and multi-value selections become Multi-select Picklist fields. Custom fields are not available in Zoho Recruit Free Edition; the customer's target edition must be Standard or above.

Occupop

Job Posting Distribution History

maps to

Zoho Recruit

Notes on Job Opening

1:1
Mapping required

Occupop tracks which job boards (Indeed, LinkedIn, Glassdoor, Reed, etc.) a Job was distributed to and the posting date. Zoho Recruit has no native board-distribution history field. We export this data as a structured list per Job Opening and land it as a formatted Note attached to the Job Opening record. The customer uses this reference to re-create board distributions manually in Zoho Recruit's Job Opening posting interface.

Occupop

AI Screening Score and Rank

maps to

Zoho Recruit

Custom Number Field on Candidate

1:1
Fully supported

Occupop's AI screening assigns each Candidate a numeric score (0-100 scale) and a rank within the Job's candidate pool. We preserve both: the raw score lands as a custom numeric field (Zoho Recruit Number field type) on the Candidate record, and the rank within the job pool is preserved as an integer field or as a structured note. The score and rank are set during the Occupop export transform and carry through to Zoho Recruit import without transformation.

Occupop

Offer / Onboarding Records

maps to

Zoho Recruit

None

1:1
Fully supported

Offer letters, employment contracts, and onboarding workflow state live in Cezanne HR's broader suite post-acquisition and are not part of Occupop's ATS core export. We do not migrate offer or onboarding records. Customers should export these directly from Cezanne HR before initiating migration. Post-migration offer management in Zoho Recruit uses Zoho Recruit's Offer Letter Templates with e-signature feature, which the customer's admin configures independently.

Occupop

Campaign

maps to

Zoho Recruit

Campaign

1:1
Fully supported

Zoho Recruit's Campaign module supports candidate sourcing campaigns (referral programs, job fairs, agency sourcing drives). If the customer used Occupop campaign features or tagged candidate sources by campaign, these map to Zoho Recruit Campaign records. Campaign members (Candidates or Contacts) link to the Campaign via Campaign Member records. We include Campaign import in the standard migration sequence after Users and before Candidates per Zoho Recruit's documented import order.

Occupop

Client

maps to

Zoho Recruit

Client

1:1
Fully supported

Zoho Recruit maintains a separate Client module for agency or in-house recruitment contexts where the hiring organization manages relationships with external clients or agencies. If Occupop contained client-level records (e.g., hiring companies or agencies managing requisitions), these map to Zoho Recruit Client records with the client name, contact details, and status preserved. Client records must exist before any Candidate records that reference them are imported.

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.

Occupop logo

Occupop gotchas

Medium

Cezanne HR acquisition may change data residency and contract terms

Medium

Offer and onboarding data lives outside Occupop's ATS scope

Low

Custom Fields schema varies by tenant and may require mapping

Low

Job posting board-distribution history does not map to standard ATS fields

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

  • Zoho Recruit Free Edition excludes custom fields entirely

    Zoho Recruit's Free Edition has no custom field support. If the customer has configured any custom fields in Occupop (common for roles with bespoke data capture requirements), those fields cannot migrate into a Free Edition destination. We verify the target Zoho Recruit edition during scoping. Standard Edition and above support custom fields, but Lookup and formula fields are additionally gated behind Professional and Enterprise. We recommend at minimum Standard Edition for any migration with non-trivial custom field usage, and we pre-configure the Layout Editor fields before the migration run begins.

  • User import capped at 2,000 records per migration batch

    Zoho Recruit's migration documentation specifies that only the first 2,000 user records are imported in a single migration batch. For Occupop customers with larger hiring teams (common in multi-office or high-volume hiring organizations), we chunk the user export and run multiple import passes, maintaining email-based deduplication across passes. We also coordinate with the customer's Zoho admin to provision any users that cannot be auto-matched by email before resuming the migration run.

  • Attachment references must resolve or files are orphaned

    Zoho Recruit's migration wizard requires that CSV values containing source file references resolve to actual files in the Attachments folder. If a CSV row references a file that is missing, renamed, or in an incorrect folder structure, Zoho Recruit flags the record but may silently leave the attachment unmapped. We pre-validate the Data/Attachments folder structure before upload, delete any extraneous folders created during unzip, and verify that every CSV attachment reference has a corresponding file. The customer must review the module and field mapping status email that Zoho Recruit sends upon completion and confirm that attachment counts match the source export.

  • Cezanne HR acquisition changes contract and data terms mid-migration

    Occupop was acquired by Cezanne HR in March 2025. Migration scoping must account for the customer's current contract status, renewal date, and whether a Cezanne HR umbrella agreement now governs the data export. Offer records, employment contracts, and onboarding workflow state live in Cezanne HR's broader suite and are not accessible via Occupop's export. We flag these boundaries during discovery, direct customers to export from Cezanne HR directly for offer and onboarding data, and note any re-consent requirements that may apply under updated terms of service before data extraction begins.

  • Occupop workflows and job board automations do not migrate

    Occupop's workflow automation (stage-triggered actions, email notifications, task assignments) has no direct Zoho Recruit equivalent in migration. Zoho Recruit Workflow Rules provide event-triggered automation but use a different configuration model (triggers, conditions, instant actions, scheduled actions). We deliver a written inventory of every active Occupop workflow rule with its trigger, conditions, and actions, plus a recommended Zoho Recruit Workflow Rule equivalent. The customer's Zoho admin rebuilds these post-migration. Job board distribution automations (1-click posting schedules) are not migratable and must be reconfigured manually in Zoho Recruit's job posting interface.

Migration approach

Six steps for a successful Occupop to Zoho Recruit data migration

  1. Discovery and target edition assessment

    We audit the source Occupop tenant for candidate volume, active and closed job count, custom field definitions (inspecting the actual key-value schema per tenant), user count and role distribution, CV attachment file count and total size, interview feedback volume, and any active workflow configurations. We pair this with a Zoho Recruit edition assessment: Free Edition covers 1 user with no custom fields; Standard covers small teams with basic custom fields; Professional covers multi-user teams with lookup fields, custom modules, and advanced workflow rules. The discovery output is a written migration scope with a Zoho Recruit edition recommendation and a preliminary field map covering every Occupop custom field.

  2. Zoho Recruit Layout Editor field pre-configuration

    Before any data is imported, we configure Zoho Recruit's Layout Editor for the Candidate and Job Opening modules. This includes creating custom fields to match every Occupop custom field (with appropriate Zoho Recruit field types: Text, Number, Date, Multi-select Picklist, etc.), setting up candidate status picklist values to match Occupop's stage names per pipeline, and configuring any required lookup fields (Candidate to Job Opening, Candidate to Client). This step runs in the customer's Zoho Recruit sandbox or trial environment first to validate before production configuration is applied.

  3. Sandbox migration and reconciliation

    We run a full migration into a Zoho Recruit sandbox or trial account using a representative data sample. The customer spot-checks candidate records (name, email, AI score, stage history), job opening records (title, description, status), user accounts (role assignments), and attachment links. We correct any field mapping discrepancies in the sandbox before committing to production migration. This is the critical step for catching custom field type mismatches and stage name mapping errors before they affect live data.

  4. CV and attachment folder preparation

    We prepare CV files in Zoho Recruit's required migration structure: a Data folder containing the CSV with candidate record data and attachment filename references, and an Attachments folder containing the source CV files with filenames matching the CSV references exactly. We verify that no extraneous folders are created during zip/unzip and that file references in the CSV resolve to files in the Attachments folder. We chunk large attachment sets into batches of 200 files per Zoho Recruit's stated limit and verify each batch's import result before proceeding.

  5. Production migration in Zoho Recruit's documented sequence

    We run production migration following Zoho Recruit's recommended import order: Users first (with 2,000-record batch handling for large teams), then Campaigns (if applicable), then Candidates (with stage history and AI scores mapped), then Clients (if applicable), then Contacts, then Job Openings (with stage status values resolved), then association records (Candidate-to-Job Opening links), then Notes and To-Dos (Tasks, Events, Calls), then Attachments. Each phase emits a row-count reconciliation report showing source count versus destination count. Board distribution history and interview scorecards land as Notes attached to the relevant records.

  6. Cutover, validation, and automation handoff

    We freeze Occupop write access during cutover and run a final delta migration of any records created or modified during the migration window. We deliver the board distribution history as a structured reference document, the workflow inventory with Zoho Recruit Workflow Rule rebuild recommendations, and the Offer/Onboarding records reference export from Cezanne HR. We support a one-week post-go-live window to resolve data quality issues. Zoho Recruit Workflow Rules, automations, and job board re-posting configurations are not migrated as code and are the customer's admin's responsibility post-handoff.

Platform deep dives

Context on both ends of the pair

Occupop logo

Occupop

Source

Strengths

  • Unlimited user seats regardless of plan, eliminating per-seat cost surprises for growing hiring teams.
  • AI screening scores and ranks candidates against job descriptions, reducing manual CV triage for high-volume roles.
  • 1-click multi-channel job posting consolidates distribution to Indeed, LinkedIn, Glassdoor, and niche boards in a single action.
  • Clean, centralized dashboard surfaces every step of each open role's pipeline without switching views.
  • 2-week free trial with no credit card lowers evaluation friction for SMB buyers.

Weaknesses

  • Reporting and analytics lack the depth needed by People teams accustomed to custom BI dashboards or cross-pipeline trend views.
  • Smaller integration catalogue than enterprise competitors; customers on niche HRIS or background-check tools may need custom workarounds.
  • Advanced features (custom workflows, advanced analytics, some API capabilities) are gated behind higher tiers or future roadmap items.
  • Post-acquisition roadmap uncertainty may concern customers who need long-term product stability guarantees.
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 Occupop 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

    Occupop: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Occupop to Zoho Recruit migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Migrations under 5,000 Candidates and 500 Job Openings with a straightforward custom field schema typically complete in two to four weeks. Migrations exceeding 20,000 Candidates, hundreds of active Job Openings, complex multi-field custom schemas, or large CV attachment libraries (over 500 files) extend to five to eight weeks because of Layout Editor pre-configuration time, multi-batch attachment processing, and stage-history transformation work per candidate record.

Adjacent paths

Related migrations to explore

Ready when you are

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