Migrate from Journeyfront to Zoho Recruit

Journeyfront Jobs map directly to Zoho Recruit Job Opening records. We extract job title, description, location, department, employment type, and job board posting status from Journeyfront's job data. The Zoho Job Opening module uses standard fields for these attributes, and we map any custom job fields to Zoho's custom field infrastructure. Job board posting status requires manual reconfiguration in Zoho Recruit because integration credentials are not exported from Journeyfront.

Journeyfront Candidate records map to Zoho Recruit Candidate with full field coverage including contact information, work history, screening responses, assessment scores, interview ratings, and pipeline stage. We preserve all candidate associations to the parent Job Opening. Zoho Recruit's Candidate module requires Last Name as a mandatory field — candidates without a last name value in Journeyfront are assigned 'Not Provided' per Zoho's import specification to prevent record rejection.

Journeyfront assessment scores migrate as structured custom fields on the Zoho Recruit Candidate record. Each distinct assessment dimension from Journeyfront (company-specific calibration dimensions such as retention prediction, job performance, screening category scores) maps to a named custom field in Zoho Recruit. The predictive model that generated these scores does not export — we flag all assessment records during scoping and deliver a written note that baseline scoring requires re-establishment in Zoho Recruit's custom field or third-party assessment integration.

Journeyfront's customizable screening questions (varying by job and client in BPO contexts) migrate as custom fields on the Zoho Recruit Candidate record. We extract question text, answer type, and the candidate's response value. Question rubrics and scoring logic (client-specific in BPO deployments) are documented in the migration output for manual setup in Zoho Recruit's custom field infrastructure. Complex multi-question screening recipes with conditional branching do not migrate as logic and require rebuild as Zoho Recruit form or workflow rules.

Journeyfront pipeline stages are customizable per job or workflow, particularly in BPO contexts with client-specific hiring processes. Stage names, order, and stage-specific automation triggers are extracted and remapped to Zoho Recruit's Job Opening stage conventions. Zoho Recruit uses a standard stage template (Applied, 1st Interview, 2nd Interview, Offer, Hired, Rejected) with custom field options per stage. We map Journeyfront's stage names to the nearest Zoho equivalent and flag any stages that have no direct Zoho equivalent for admin review. Stage automation triggers require rebuild as Zoho Recruit Blueprint rules.

Journeyfront Interview records (interviewer assignment, scheduled date/time, scorecards, recommendation, and notes) map to Zoho Recruit Interview records. Interviewer assignment maps to Zoho Recruit User records by email match. Scorecard responses migrate to Zoho's interview evaluation fields, and any free-text notes migrate as interview comments. We preserve the relationship between the interview record and the parent Candidate and Job Opening.

Journeyfront Offer records (position, compensation details, offer status, and candidate response) map to Zoho Recruit Offer records. Offer status values (Pending, Accepted, Declined, Withdrawn) map to Zoho's offer status field equivalents. Compensation details migrate as structured fields in Zoho Recruit's offer module. Any offer attachments (offer letters, addenda) migrate as file records linked to the Offer.

Journeyfront Users, Hiring Managers, and Interviewers map to Zoho Recruit User records by email lookup. Role assignments (recruiter, hiring manager, interviewer, observer) from Journeyfront map to Zoho Recruit's role-based permissions structure. We resolve owner references across Candidates, Jobs, Interviews, and Offers during migration. Any Hiring Team Member without a matching Zoho Recruit User account enters a reconciliation queue for the customer to provision before record import completes.

Journeyfront workflow automation rules (stage triggers, score thresholds, time-delay actions) are documented in the migration output as written specifications for Zoho Recruit Blueprint rebuild. Zoho Recruit's Blueprint and Workflow modules use a different automation model than Journeyfront, and direct rule translation is not possible. We extract rule definitions (trigger event, conditions, actions, order) from Journeyfront and deliver a structured document that maps each rule to the nearest Zoho Recruit Blueprint equivalent with implementation notes for the customer's admin.

Journeyfront's analytics dashboards (turnover reduction percentages, tenure improvement metrics, SLA performance scores) are dynamically generated from raw records and do not export as flat data. We recommend exporting PDF or CSV snapshots of key Journeyfront reports before migration cutoff as a manual preparation step. All underlying candidate, assessment, and interview data migrates normally. Post-migration reporting uses Zoho Recruit's standard analytics on the migrated data.

Journeyfront's 400-plus integrations with job boards, background check vendors, and HRIS systems are configured via API credentials within the platform. These credentials and endpoint configurations are not included in data exports and do not migrate. Job board posting integrations, background check connections, and HRIS sync settings require manual reconfiguration in Zoho Recruit after migration. We deliver a written inventory of all detected Journeyfront integrations with recommended Zoho Recruit equivalents for the customer's admin to implement.

Journeyfront candidate activity records (notes, internal comments, communication history) migrate as Zoho Recruit Candidate Activity records linked to the parent Candidate. Activity timestamps are preserved to maintain the chronological record of candidate interactions. Activity type mapping (note, email, call log, status change) translates to Zoho Recruit's activity type field. Communication body content migrates as plain text or rich text depending on the source format.