Migrate from Cascade to Recruit CRM & ATS

Cascade Owners are individual users assigned to Plans, Projects, or Key Results. We export the user ID and display name from Cascade and map to Recruit CRM Contacts (the default for candidate-facing users) or Users (for licensed Recruit CRM seats). The choice is made during scoping based on whether the owner records represent internal team members or external candidate/contact records. Email address is the primary deduplication key. Owner assignments on migrated Plans and Projects are preserved in a custom field cascade_owner_ref__c on the target Contact or User record.

Cascade Teams group users for assignment and visibility purposes. We map team names and membership to Recruit CRM Tags on the Contact object. For organizations requiring structured team membership (rather than flat tagging), we create a multi-select custom field team_membership__c on the Contact object. The customer selects the strategy during scoping based on whether team structure is used for assignment routing or reporting segmentation in Recruit CRM.

Cascade entity templates define custom fields on Plans, Projects, and Key Results. Custom field types (text, number, date, dropdown, user picker) map to Recruit CRM custom field equivalents by type: text to Text, number to Number, date to Date, dropdown to Picklist, and user picker to Lookup (Contact or User reference). The destination custom field must be created in Recruit CRM before import or values land in the wrong column. We provide a custom-field manifest listing field name, type, and picklist options for the Recruit CRM admin to pre-create in the Admin Settings before data load.

Cascade Plans are the top-level container in the strategy hierarchy. Recruit CRM has no equivalent container for OKR-style goal tracking. Plans do not migrate as structured records. We extract the Plan title, description, owner assignment, and any custom field values into a CSV inventory that the customer can use to manually create a corresponding Job, Deal, or Contact record in Recruit CRM, or to document strategy goals externally.

Cascade Projects nest under Plans and contain the operational layer of work. Recruit CRM has no Project or task-management container equivalent. Projects do not migrate as structured records. We extract Project name, status, owner assignment, timeline dates, checklist items, milestones, and custom field values into a CSV inventory. The customer uses this as a reference to manually create corresponding records or to document project status externally.

Cascade Key Results are measurable outcomes attached to Projects with metric type, start and target values, current progress percentage, and owner. Recruit CRM has no Key Result or metric-tracking object. We extract Key Result title, metric type, progress percentage, owner, and any linked Project reference into a CSV inventory. The customer uses this as a reference for external documentation or for manual entry into a Recruit CRM custom field structure if one is designed.

Cascade Projects can contain checklist items marking discrete sub-tasks. We export all checklist items with their completion status flags and map to Recruit CRM Tasks. Each checklist item becomes a standalone Task with the original Project name embedded in the Task description for traceability. Completion status maps to Task Status (completed vs open). If the number of checklist items per Project exceeds 100, we chunk the import to comply with Recruit CRM's API batch limits.

Cascade Milestones are date-linked markers on Projects representing key delivery points. We migrate milestone names, target dates, and ownership to Recruit CRM Tasks with the milestone flag set in a custom field milestone__c. Date ordering is preserved via the Task due_date field. If the customer prefers milestone tracking without creating Tasks, we map milestone dates to a date custom field on the related Contact, Job, or Deal record instead.

Cascade Engagement Page Snapshots are read-only rendered reports generated from live Plan and Project data. They have no structured underlying data model that can be parsed and transferred. We flag Engagement Pages during discovery and advise customers to treat them as reference screenshots to be manually re-created in Recruit CRM's reporting module. The underlying Plan and Project data (if migratable) is handled per the Plan and Project mapping above.

Cascade's cascading goals model links parent Plans to child Projects and Key Results via an alignment relationship rather than a standard parent_id foreign key. We extract all alignment_source values and map them to a custom field cascade_parent_ref__c on the target record. Recruit CRM does not enforce a goal hierarchy, so the parent-child relationship is preserved as a reference field rather than a native hierarchy. Deeply nested goal trees may require flattening during scoping if the customer prefers a flat record structure.