Migrate from JOIN to Zoho Recruit

JOIN Jobs map to Zoho Recruit Job Openings. JOIN job fields (title, description, department, location, employment type, posting status) map directly to Zoho Recruit equivalent fields. Job Openings must be imported before Candidates to satisfy the parent-record dependency for application linkage. JOIN posting credits and board distribution settings are not portable; we document the full job board distribution list per job so the customer's admin can re-establish postings in Zoho Recruit's job board module post-migration.

JOIN Candidate records map 1:1 to Zoho Recruit Candidates. Contact information, work history, education, skills tags, and source attribution migrate directly. JOIN's lifecycle stage property migrates to a Zoho Recruit custom text field (join_original_lifecycle__c) since Zoho Recruit does not have a native lifecycle stage concept on Candidates. We handle Zoho Recruit's mandatory Last Name field: candidates without a surname receive a placeholder value ('Not Provided') that can be corrected manually post-migration or flagged in the reconciliation report.

JOIN Applications (the join table linking Candidate to Job, with applied date, referral source, and rejection/offer flags) map to Candidate records in Zoho Recruit where the application details are stored as sub-records or custom fields. Applied date migrates to a custom date field join_applied_date__c. Rejection and offer flags become Zoho Recruit Candidate status values. Referral source from JOIN maps to the Source field in Zoho Recruit, preserving the candidate sourcing attribution.

JOIN does not enforce a universal stage schema; each job can have a custom stage sequence. We extract the full stage list per job during the scan phase and build a customer-specific mapping table against Zoho Recruit's stage editor for each Job Opening. Where the destination plan has fewer stages, we collapse intermediate stages and preserve stage-entry dates as metadata. The customer approves the stage mapping table before any Job Opening records are created in Zoho Recruit.

Interview evaluations stored in JOIN as structured feedback or free-text notes migrate to Zoho Recruit Interview Feedback records. Where JOIN stores evaluations as JSON with rating fields, we flatten the structure into readable text and attach it to the corresponding Interview record in Zoho Recruit. Free-text interview notes from JOIN migrate as Zoho Recruit Notes attached to the relevant Candidate or Interview record.

JOIN employer-defined custom fields on Jobs map to Zoho Recruit custom fields on Job Openings. We extract the full custom field schema during the scan phase, confirm field types (text, picklist, numeric, date), and create equivalent custom fields in Zoho Recruit via Setup > Customization > Modules before Job Opening import begins. Any custom fields that cannot be matched due to Zoho Recruit edition restrictions (Lookup and formula fields require Professional or above) are flagged for the customer to resolve before migration.

JOIN employer-defined custom fields on Candidates require manual equivalence review and customer confirmation before mapping. We surface all detected custom fields at scoping, and the customer specifies the intended Zoho Recruit equivalent. Unmapped custom fields land as free-text custom properties in Zoho Recruit and can be restructured post-migration. Multi-select picklist fields from JOIN map to Zoho Recruit Multi-Select Picklist fields where the field types are confirmed as equivalent.

Candidate resume files and attached documents are exported from JOIN and uploaded to Zoho Recruit as binary attachments linked to the Candidate record. JOIN's internal ID-based filenames are normalised to a consistent convention (CandidateName_PositionTitle_Date) during export to prevent filename collisions in bulk uploads and ensure files are identifiable upon ingestion. The Customer must confirm Zoho Recruit edition limits on storage and attachment uploads before migration.

JOIN Owners referenced on Candidate and Application records map to Zoho Recruit User records by email address match. We extract all distinct owner IDs during the scan, and the customer provisions matching User records in Zoho Recruit before migration begins. Owners without a matching Zoho Recruit User go to a reconciliation queue; migration cannot proceed past Candidate import until all OwnerId references are resolved.

JOIN does not expose email threads, scheduled interview events, or activity log entries through a documented API endpoint. We coordinate a CSV export of the activity timeline from the JOIN dashboard before cutover. The CSV is structured as a custom ingestion file: emails become Zoho Recruit Notes with a join_activity_type__c = 'Email' tag; calls and tasks become Zoho Recruit Tasks; interviews become Zoho Recruit Interview records with date and outcome preserved. This approach preserves the activity context in a readable format without requiring Zoho Recruit's native activity logging to reconstruct the history.

On the Zoho Recruit Staffing Agency edition, JOIN company data from Candidate employer associations can be mapped to Client records with Contact records as children. This mapping is optional and only applicable if the customer is moving to the Staffing Agency edition. If the customer selects the Corporate HR edition, employer data from JOIN Candidates migrates as custom fields on the Candidate record rather than as separate Client and Contact modules.

Interview records from JOIN (candidate name, job, scheduled date, interviewer, interview type, outcome) map directly to Zoho Recruit Interview records. Interview scheduling details from JOIN migrate as Zoho Recruit Interview fields. Interviewer assignments resolve via the User mapping by email. Outcome and feedback from JOIN's interview evaluation fields map to Zoho Recruit's Interview Feedback form fields.