HRMS migration
Field-level mapping, validation, and rollback between Occupop and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Occupop
Source
Zoho Recruit
Destination
Compatibility
10 of 12
objects map 1:1 between Occupop and Zoho Recruit.
Complexity
BStandard
Timeline
2-4 weeks
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a 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
Zoho Recruit
Job Opening
1:1Occupop 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
Zoho Recruit
Candidate
1:1Occupop 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
Zoho Recruit
Candidate Status per Job Opening
lossyOccupop'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
Zoho Recruit
User
1:1Occupop 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
Zoho Recruit
Attachments (linked to Candidate)
1:1Occupop 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
Zoho Recruit
Notes / To-Dos (Tasks, Events, Calls)
1:1Occupop 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
Zoho Recruit
Custom Fields (Layout Editor)
lossyOccupop 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
Zoho Recruit
Notes on Job Opening
1:1Occupop 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
Zoho Recruit
Custom Number Field on Candidate
1:1Occupop'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
Zoho Recruit
None
1:1Offer 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
Zoho Recruit
Campaign
1:1Zoho 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
Zoho Recruit
Client
1:1Zoho 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.
| Occupop | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Job | Job Opening1:1 | Fully supported | |
| Candidate | Candidate1:1 | Fully supported | |
| Workflow Stages | Candidate Status per Job Openinglossy | Fully supported | |
| User | User1:1 | Fully supported | |
| CV / Attachment | Attachments (linked to Candidate)1:1 | Fully supported | |
| Interview Feedback / Notes | Notes / To-Dos (Tasks, Events, Calls)1:1 | Fully supported | |
| Custom Fields | Custom Fields (Layout Editor)lossy | Mapping required | |
| Job Posting Distribution History | Notes on Job Opening1:1 | Mapping required | |
| AI Screening Score and Rank | Custom Number Field on Candidate1:1 | Fully supported | |
| Offer / Onboarding Records | None1:1 | Fully supported | |
| Campaign | Campaign1:1 | Fully supported | |
| Client | Client1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Occupop gotchas
Cezanne HR acquisition may change data residency and contract terms
Offer and onboarding data lives outside Occupop's ATS scope
Custom Fields schema varies by tenant and may require mapping
Job posting board-distribution history does not map to standard ATS fields
Zoho Recruit gotchas
Daily API rate limits are tier-gated and per-user capped
User import hard cap of 2,000 records
Attachment folder hierarchy must be preserved exactly
Resume parsing quota varies by plan and resets daily
Custom fields unavailable in Free and Standard editions
Pair-specific challenges
Migration approach
Discovery and 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.
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.
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.
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.
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.
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
Occupop
Source
Strengths
Weaknesses
Zoho Recruit
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Occupop and Zoho Recruit.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Occupop: Not publicly documented.
Data volume sensitivity
Occupop doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Occupop to Zoho Recruit migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Occupop
Other ways to arrive at Zoho Recruit
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.