HRMS migration
Field-level mapping, validation, and rollback between Jobsoid and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Jobsoid
Source
Zoho Recruit
Destination
Compatibility
12 of 14
objects map 1:1 between Jobsoid and Zoho Recruit.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Jobsoid to Zoho Recruit is an ATS-to-ATS transition within the SMB tier, but the two platforms organize recruiting data differently. Jobsoid stores one Candidate record that can be assigned to multiple Jobs with a designated primary; Zoho Recruit models this as a Candidate record with a separate Job Application join that links each application to a specific Job Opening. We extract Jobsoid data via CSV and Excel exports (Jobsoid's public API exposes only Jobs and Lookup endpoints), restructure the multi-job candidate assignment into Zoho Recruit's candidate-job relationship, and upload through Zoho Recruit's native import interface. Activity history migrates as chronological notes from embedded activity blocks in candidate exports, not as an independent API resource. Custom pipeline stages, custom candidate fields, and resume attachments move with field-to-field mapping. We do not migrate Jobsoid Workflows, custom email templates, or job board postings as these are platform-specific configurations requiring rebuild in Zoho Recruit.
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 Jobsoid 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.
Jobsoid
Candidate
Zoho Recruit
Candidate
1:1Jobsoid Candidate records map directly to Zoho Recruit Candidate records. We extract all standard fields (name, email, phone, current title, current company, location, source, skill keywords, years of experience) via CSV or Excel export. Jobsoid allows one candidate to be assigned to multiple jobs with a designated primary; we carry all job assignment records and designate the primary in Zoho Recruit's Primary Job Opening field on the Candidate. Candidate Unique ID from Jobsoid is preserved as an external reference field.
Jobsoid
Candidate (multi-job assignment)
Zoho Recruit
Job Application
1:manyJobsoid's multi-job candidate assignment means one Candidate record may have 2-5 job applications across different openings. Zoho Recruit models this as a Candidate record with a separate Job Application record for each applied job. We split the source candidate export at migration time, generating one Job Application record per job assignment and linking it to both the Candidate and the corresponding Job Opening in Zoho Recruit. The primary job assignment receives the Primary Job Opening flag.
Jobsoid
Job Opening
Zoho Recruit
Job Opening
1:1Jobsoid Job records map to Zoho Recruit Job Opening records. We extract job title, job ID, job status (open/closed/draft), location, department, division, function, employment type, and job description. Jobsoid's Jobs API exposes published jobs and details; we map status directly and create Job Opening records before any candidate import so that the Job Application-to-Job Opening lookup is satisfied at load time.
Jobsoid
Location
Zoho Recruit
Location
1:1Jobsoid Location lookup records map to Zoho Recruit Location. Jobsoid auto-resolves addresses via Google Maps; we carry over the location name and full address string. Locations are created first during migration so that Job Opening records can reference them via lookup. If a location is only embedded in a Job Opening record without a standalone location lookup, we create the location entry in Zoho Recruit at the time of job import.
Jobsoid
Department
Zoho Recruit
Department
1:1Jobsoid Department lookup records map to Zoho Recruit Department. Jobsoid exposes departments at the organization level via its lookup API. We preserve the full department list and reassign affected Job Openings to their corresponding Zoho Recruit department at import time. Department acts as a filter on Job Opening reports in Zoho Recruit.
Jobsoid
Division
Zoho Recruit
Division
1:1Jobsoid Division lookup records (top-level organizational units) map to Zoho Recruit Division. We migrate the division hierarchy so that it is available as a filtering and grouping dimension in Zoho Recruit reports and Job Opening listings. If Zoho Recruit does not have a Division module pre-enabled in the customer's account, we recommend enabling it via Zoho Recruit Settings during the destination environment preparation phase.
Jobsoid
Function
Zoho Recruit
Function
1:1Jobsoid Function lookup records (e.g., Engineering, Sales, Marketing, Operations) map to Zoho Recruit Function. Functions categorize job types at a coarser level than Department. We preserve the full function list from Jobsoid and link them to the corresponding Job Openings in Zoho Recruit.
Jobsoid
Candidate Source
Zoho Recruit
Source (Candidate field)
1:1Jobsoid Candidate Source values (job board, referral, direct application, career site, etc.) map to Zoho Recruit's Source picklist on the Candidate record. We perform field-to-field mapping and flag any Jobsoid source labels that do not exist as values in the Zoho Recruit Source picklist, recommending additions during the destination environment preparation phase. Unrecognized values are mapped to the closest existing Zoho Recruit value with the original label preserved in a custom notes field.
Jobsoid
Activity (interviews, emails, notes)
Zoho Recruit
Activity + Notes
1:1Jobsoid does not expose activities as an independent API resource. Activity history (interview events, emails, notes) appears in the Activity section of each candidate profile. We extract activity text from candidate profile exports where available, or reconstruct a best-effort timeline from the activity block embedded in CSV/Excel candidate exports. We create Zoho Recruit Notes records for each activity entry, preserving the timestamp, activity type (interview/email/note), and description. If activity data is critical for the customer's reporting, we recommend exporting candidate profiles as PDFs before migration to capture the full activity history visually.
Jobsoid
Custom Candidate Field
Zoho Recruit
Custom Field
1:1Jobsoid custom candidate fields (e.g., Visa Status, Notice Period, Current Salary, Certification, Preferred Location) map to Zoho Recruit custom fields on the Candidate module. We create matching custom fields in Zoho Recruit during the destination environment preparation phase, using equivalent field types (text, number, date, picklist, checkbox). Field names are mapped one-to-one where names match; renamed or new custom fields in Jobsoid require manual field-to-field decisions during the mapping review phase.
Jobsoid
Pipeline (Recruitment Stage)
Zoho Recruit
Candidate Stage
lossyJobsoid uses fully customizable recruitment pipeline stages that vary per account (e.g., Application Received, Screening, Technical Round, HR Round, Offer, Hired). Zoho Recruit's Candidate Stages are configured at the org level with stage name, sequence order, and probability percentage. We map Jobsoid stages to Zoho Recruit Candidate Stages by sequence, and when the source has more stages than the destination supports, we recommend consolidation during scoping. The stage probability percentages from Jobsoid are carried over to Zoho Recruit stage configuration.
Jobsoid
Attachment / Resume
Zoho Recruit
Attachment
1:1Jobsoid allows resume and file uploads attached to candidate profiles. We extract binary attachments separately from record data during the export phase, storing files in a temporary file server with a manifest linking each file to its source candidate record. After candidate records are loaded into Zoho Recruit, we re-attach the files to the corresponding Candidate record using the Zoho Recruit Attachments API. The file name and original upload date are preserved. PDF resumes are prioritized for attachment relocation over image or document files.
Jobsoid
Interview Schedule
Zoho Recruit
Interview Activity
1:1Jobsoid integrates with email and calendar for interview scheduling, and interview records appear as activities on the candidate profile. We extract interview date, time, interview type, interviewer name, and meeting notes from the activity block in candidate exports. These map to Zoho Recruit Interview activity records linked to the Candidate and Job Application. Calendar invites (Google Calendar, Outlook) do not migrate as calendar events in Zoho Recruit; the interview details are preserved as a Zoho Recruit activity record with a notes field indicating the meeting link if present.
Jobsoid
Owner
Zoho Recruit
User
1:1Jobsoid Owner records (recruiters and hiring managers assigned to candidates and jobs) map to Zoho Recruit Users. We resolve owners by email address match against the Zoho Recruit user list. Any Jobsoid Owner without a matching Zoho Recruit User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Candidate records migrates by resolving the Zoho Recruit User ID at load time.
| Jobsoid | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Candidate | Candidate1:1 | Fully supported | |
| Candidate (multi-job assignment) | Job Application1:many | Fully supported | |
| Job Opening | Job Opening1:1 | Fully supported | |
| Location | Location1:1 | Fully supported | |
| Department | Department1:1 | Fully supported | |
| Division | Division1:1 | Fully supported | |
| Function | Function1:1 | Fully supported | |
| Candidate Source | Source (Candidate field)1:1 | Fully supported | |
| Activity (interviews, emails, notes) | Activity + Notes1:1 | Fully supported | |
| Custom Candidate Field | Custom Field1:1 | Fully supported | |
| Pipeline (Recruitment Stage) | Candidate Stagelossy | Fully supported | |
| Attachment / Resume | Attachment1:1 | Fully supported | |
| Interview Schedule | Interview Activity1:1 | Fully supported | |
| Owner | User1: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.
Jobsoid gotchas
No public Candidates API endpoint for write operations
Pipeline stage names and count vary per account
Activity history granularity is not independently exportable
Unlimited storage refers to file count, not retention policy
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 environment preparation
We audit the source Jobsoid account across objects: candidate count, job count, pipeline stage names and counts, custom candidate field list, candidate source labels, attachment volume, and owner assignments. We assess whether activity history is needed and whether PDF exports are required to capture complete activity records. On the destination side, we prepare the Zoho Recruit environment by enabling required modules (Divisions if not pre-enabled, custom fields matching the Jobsoid custom field list, Candidate Stages mapped to Jobsoid pipeline stages, and Source picklist values matching the candidate source labels). We review Zoho Recruit API access and import permissions for the migration user.
Data extraction from Jobsoid
We extract data from Jobsoid using CSV and Excel exports organized by object. The Jobs export provides the Job Opening records. The Candidates export provides the primary candidate records with all standard and custom fields. For candidates assigned to multiple jobs, we extract the full job assignment list to reconstruct the Job Application relationship in Zoho Recruit. Activity history is extracted from the embedded activity block in candidate profile exports, or reconstructed from PDF candidate exports if activity history completeness is critical. Attachments are downloaded separately and stored in a manifest-linked file store. All exports are audited for field completeness before transformation begins.
Data transformation and field mapping
We transform the extracted Jobsoid data into Zoho Recruit import format. The multi-job-to-Job-Application split is applied during transformation: each candidate with N job assignments generates N Job Application records in Zoho Recruit. Pipeline stages are mapped to Zoho Recruit Candidate Stages using the agreed consolidation mapping from scoping. Custom fields are mapped field-to-field using the custom field name match list. Source values are mapped to Zoho Recruit Source picklist values, with unmapped values flagged for picklist addition. Activity entries are formatted as Zoho Recruit Notes and Activity records with timestamps preserved. Owner email addresses are resolved against the Zoho Recruit User list, with unmatched owners queued for admin provisioning.
Sandbox validation and reconciliation
We run the first migration pass into a Zoho Recruit sandbox environment (or a trial account set up for validation) using a representative data subset. The customer's hiring operations lead reconciles record counts (Candidates in, Job Openings in, Job Applications in, custom field values populated, activity records present, attachments linked), spot-checks 20-30 random candidate records against the Jobsoid source, and signs off the mapping and transformation logic before production migration begins. Any field mapping corrections, stage consolidation adjustments, or custom field additions are implemented here.
Production migration and attachment relocation
We run production migration in dependency order: Job Openings (since Job Applications reference them), Locations and Departments (for Job Opening lookups), Candidates (with all standard and custom fields mapped), Job Applications (linked to Candidates and Job Openings), Activities and Notes (linked to Candidates), then Attachments (via Zoho Recruit Attachments API). Each phase emits a row-count reconciliation report before the next phase begins. Owner assignments are resolved using the pre-provisioned Zoho Recruit User list. Any records that fail import due to validation errors are logged, corrected, and retried in a catch-up batch.
Cutover, validation, and handoff
We freeze Jobsoid write access during the cutover window, run a final delta migration of any records created or modified during the migration window, then enable Zoho Recruit as the system of record. We deliver a written inventory of Jobsoid Workflows and custom email templates for the customer's admin to rebuild in Zoho Recruit's Blueprint and workflow rule builder. We support a one-week hypercare window where we resolve any record reconciliation issues raised by the recruiting team. We do not rebuild Jobsoid Workflows as Zoho Recruit workflow rules as part of the standard migration scope; that is a separate engagement.
Platform deep dives
Jobsoid
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 Jobsoid 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
Jobsoid: Not publicly documented.
Data volume sensitivity
Jobsoid 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 Jobsoid to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Jobsoid 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 Jobsoid
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.