Migrate from Cascade to Zoho Recruit

Cascade Plans map to Zoho Recruit Job Openings when the plan represents a hiring goal or open role. When a Plan represents a strategic initiative rather than a job requisition, we create a custom module (e.g., Strategic_Plan__c) to hold the goal data. The Plan title becomes Job Opening Title; Plan description migrates to the job description field; Plan owner maps to the Zoho Recruit hiring manager via user email lookup. Start and end dates from the Plan become the Expected Start Date and Application Deadline on the Job Opening.

Cascade Projects require a domain decision during scoping. If the Project represents a hire (e.g., 'Senior Engineer Role - Q2'), it maps to a Zoho Recruit Job Opening. If the Project represents an initiative within a hiring plan (e.g., 'Campus Recruitment Drive - Engineering'), it maps to a Candidate record with the parent Job Opening in a lookup field. We use the Project name, status, owner, and team associations to populate the corresponding Zoho Recruit fields and resolve the hiring manager via email match to Zoho Recruit Users.

Key Results represent measurable outcomes attached to Projects. We map Key Result title and metric type to Zoho Recruit custom fields on the Job Opening or Candidate module. Target values become number or percentage custom fields; current progress percentage migrates to a numeric custom field (e.g., KR_Progress__c). The Key Result owner maps to the Candidate's assigned recruiter via user email lookup. Progress values are validated as numeric and flagged if the source Cascade field contains non-numeric text.

Cascade Milestones are date-linked markers on Projects representing key delivery points. We map milestone names and target dates to Zoho Recruit Interview records (with Interview type set to the milestone name) or to Task records with a due date matching the milestone. Milestone ordering is preserved via a sequence number field. If the milestone maps to a hiring deadline, the Zoho Recruit Job Opening Application Deadline field receives the milestone date directly.

Cascade checklist items mark discrete sub-tasks within a Project. We map them to Zoho Recruit Task records linked to the corresponding Job Opening or Candidate. Completion status (boolean) migrates to Task Status (Completed/Pending). Checklist item order is preserved via a sequence field. Items with no completion flag default to Pending status in Zoho Recruit.

Cascade Teams group users for assignment and visibility. We map team names to Zoho Recruit Departments (Setup > Users & Control > Departments) where the department structure applies to the recruiting hierarchy. If Cascade teams do not map to a recruiting department (e.g., they represent an OKR ownership group), we create a custom picklist field (Cascade_Team__c) on the Job Opening and Candidate modules and populate team membership as picklist values.

Cascade Owners are individual users assigned to Plans, Projects, or Key Results. We export the user email address and display name and match by email against Zoho Recruit Users in the destination account. Owners without a matching Zoho Recruit User are held in a reconciliation queue for the customer's admin to provision before record import proceeds. Active and inactive status is preserved from Cascade where available.

Cascade entity template custom fields (text, number, date, dropdown, user picker) require pre-creation in Zoho Recruit before data import. We export the full field definition manifest including field name, type, and picklist options, and the Zoho Recruit admin creates matching custom fields. Custom fields are not available on the Zoho Recruit Free Edition; the Standard tier allows 50 custom fields per module and Enterprise allows 300. We confirm the destination edition supports the total custom field count before migration begins.

Cascade's core value is vertical alignment linking parent Plans to child Projects and Key Results via an alignment relationship with no standard foreign key. Zoho Recruit has no parent-child goal structure; this alignment concept has no native equivalent. We extract all alignment_source values and the full goal hierarchy tree, then deliver a written goal-mapping document listing the original Cascade parent-child relationships so the customer's admin can recreate the strategic context in a custom module or as linked Job Opening notes. We do not attempt to store alignment data in Zoho Recruit fields that lack the semantic meaning of Cascade's alignment model.

Cascade Engagement Page Snapshots are rendered read-only reports generated from live Plan and Project data. They have no structured underlying data model suitable for parsing and transfer. We flag Engagement Pages during discovery and advise treating them as reference screenshots to be manually re-created in the destination. The underlying data (Plans, Projects, Key Results) migrates normally to Zoho Recruit as Jobs, Candidates, and custom fields.

Cascade integration credentials and connector configurations (including any HRMS or calendar integrations) are external-service authentication data that does not transfer between platforms. We export a list of active integrations with their connection type and configuration parameters so the customer's admin can reconfigure equivalent integrations within Zoho Recruit's connector ecosystem post-migration.

Cascade goal progress percentages (on Key Results and Projects) migrate to numeric custom fields in Zoho Recruit. If the customer tracks organizational OKRs alongside recruiting data, we recommend a custom module (Goals__c) with fields for Goal Title, Parent Goal lookup, Metric Type, Target Value, Current Progress, and Owner. This captures the strategic context of Cascade's goal hierarchy without forcing it into Zoho Recruit's recruiting-native objects where it would lack functional meaning.