Migrate from Jobylon to Zoho Recruit

Jobylon Jobs map to Zoho Recruit Job Openings. Standard fields (title, department, location, employment type, description) migrate directly. Jobylon's per-company custom fields defined via /config/companies/{companyId}/job map to Zoho Recruit custom fields on the Job Opening module. We run schema discovery against the Jobylon configuration endpoint for each company before migration to capture the complete field list, including any fields that require Jobylon support activation. Published status maps to Zoho's Opening Status field (Open, Closed, On Hold).

Jobylon Applications map to Zoho Recruit Candidates. The Application ID is preserved as a custom field (source_application_id__c) for reconciliation. Application status maps to the Zoho Candidate status field, and the current Pipeline Stage from Jobylon maps to the Zoho Candidate's currentHiringPipeline stage. We preserve the full application timeline (all stage transitions with timestamps) as Zoho Candidate Activities or as a custom multi-line text field if the candidate's full stage history is required for audit.

Jobylon Candidates map directly to Zoho Recruit Candidates. Candidates may have multiple Applications across Jobs, so we deduplicate by email address and carry the full application history attached to the single Candidate record. GDPR fields (consent status, erasure date, data handling preferences) migrate as custom fields unless Zoho Recruit's privacy settings cover the requirement natively. Skills, languages, and certifications from Jobylon map to Zoho Candidate Skills and custom fields.

Jobylon Pipeline Stages are free-text per-company names with no global schema, while Zoho Recruit uses structured Hiring Pipeline stages. We map each source stage name to the closest Zoho stage (Applied, Screening, Interview, Offer, Hired, Rejected) and preserve the original stage name as a custom field on the Candidate record. Stages with inactive status and a Lost Reason attached map to Zoho's Rejected stage with the Loss Reason stored as a custom field. The customer reviews and approves the stage map before cutover to avoid process mismatches.

Jobylon Scorecards tied to Pipeline Stages record evaluator ratings. We export the scorecard schema (criteria names, rating scale) and each evaluator's rating value, preserving the evaluator name and timestamp. If Zoho Recruit's Evaluation module is active in the destination account, we map scorecards to Evaluations linked to the Candidate. If not, we carry ratings as custom fields on the Candidate record with a structured naming convention (scorecard_[evaluator]_[criteria]__c). The customer selects the strategy during scoping.

Jobylon custom fields are defined per-company via the Partner API configuration endpoint and are not globally standardised. We query /config/companies/{companyId}/job and /config/companies/{companyId}/application during discovery to capture the complete field list. Dynamic custom fields (secondary forms built on prior submissions) require manual activation by Jobylon support and may not appear in the API schema unless activated; we request confirmation of activation status before scoping. Each custom field maps to an equivalent Zoho Recruit custom field with type-matching (text, picklist, number, date).

Jobylon Users (recruiters, hiring managers, admins) map to Zoho Recruit Users. We resolve by email match. Any Jobylon User without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision. Permission-level differences between Jobylon's configurable permission tiers and Zoho's role-based access are documented for admin review post-migration. Active/inactive status carries forward.

Jobylon Lost Reasons are predefined classification labels attached when an Application moves to an inactive stage. We carry these as a tagged custom field on the Zoho Candidate record (loss_reason__c) rather than a native Zoho object, since Zoho Recruit does not have a standalone Lost Reason object equivalent. The customer can configure a picklist of rejection reasons in Zoho Recruit's Candidate module and map the source values during staging.

Free-text evaluator notes and assessor feedback from Jobylon export as structured comment records with author, timestamp, and content body. We map these to Zoho Recruit Notes attached to the Candidate record, preserving the original author name and the date of the feedback. If the customer uses Zoho Recruit's Activity Log, feedback migrates as an Activity record instead.

Jobylon offer letter documents are stored as attachments associated with Applications. The API exports attachment filenames and URLs but not document content. We preserve the attachment URLs as a custom field (offer_attachment_url__c) on the Zoho Candidate record and note that the customer's admin should download and re-upload offer PDFs to Zoho Recruit's document storage post-migration if full content is required in the destination system. If the customer uses Zoho Recruit's Offer management module, we configure Offer records with the candidate reference and a link to the uploaded document.

Jobylon exposes job requisition metadata including salary range, benefits, remote policy, and hiring team members. These map to Zoho Job Opening fields where native equivalents exist, or to custom fields on the Job Opening module. Benefits and compensation details that are multi-line text in Jobylon become structured custom fields in Zoho if the customer requires filtering and reporting on those dimensions.

If Jobylon maintains references to candidate employer history or client companies associated with a job, these map to Zoho Recruit's Client module. Client records are linked to Job Openings as the hiring organisation, and candidate employer references attach to the Candidate record. We handle deduplication by company name during import.