Migrate from Cascade to Crelate

Cascade Plans (top-level strategic containers) map to Crelate Opportunities with the Plan title stored as the Opportunity name and the Plan description as the Opportunity description. This is a semantic approximation since Crelate has no concept of a strategic Plan; the Plan context is captured as a note attachment. Multiple child Projects under a Plan become separate Opportunities linked back to the parent Plan Opportunity via a custom lookup field custom_plan_id__c that we create in Crelate before migration.

Cascade Projects map to Crelate Opportunities. Project name becomes Opportunity name; project status (Not Started, In Progress, Completed) maps to Opportunity stage values that we configure in Crelate before migration. Owner assignment transfers to the Opportunity owner_id by resolving the Cascade owner email against the Crelate user table. Custom fields on the Project export as Crelate custom fields on the Opportunity object.

Cascade Key Results are measurable outcomes attached to Projects. Key Result title and metric type (number, percentage, currency, milestone) map to Crelate custom fields on the parent Opportunity. The current progress value and target value are stored as numeric custom fields on the Opportunity. This is a significant semantic reduction: Crelate has no native Key Result concept and no OKR progress tracking, so the metrics are preserved as structured data in custom fields but without Cascade's progress visualization or alignment links.

Cascade Milestones (date-linked markers on Projects) map to Crelate Tasks with the milestone name as the Task subject and the milestone target date as the Task due date. We set Task status to Completed if the milestone is marked complete in Cascade, Open if pending. Milestone ordering is preserved via a custom sequence integer field. Milestone assignments transfer to the Task owner by email resolution.

Cascade Project checklist items map to Crelate Tasks with the checklist item text as Task subject, completion status mapped to Task status (Completed or Open), and a custom field checklist_project_ref__c linking back to the parent Crelate Opportunity representing the Cascade Project. We do not migrate checklist ordering because Crelate Tasks have no native sequence field beyond due date sorting.

Cascade Owners (individual users assigned to Plans, Projects, or Key Results) map to Crelate User records by email address lookup. We export the user ID, display name, and email from Cascade and attempt to match against existing Crelate users. Any Cascade Owner without a matching Crelate User is held in a reconciliation queue for the customer's Crelate admin to provision before record import.

Cascade Teams group users for assignment and visibility. Teams map to Crelate Companies with the team name as the Company name. Team membership is preserved by linking each member User record to the Company via Crelate's standard Contact-to-Company relationship, or by storing a custom multi-select picklist of member email addresses on the Company record. This is an imperfect mapping because Crelate Companies represent external organizations in a recruiting context, not internal team groupings.

Cascade entity template custom fields (text, number, date, dropdown, user picker) map to Crelate custom fields on the corresponding object (Opportunity for Plan/Project fields). Field types are matched as follows: Cascade text maps to Crelate short answer; Cascade number to Crelate numeric; Cascade date to Crelate date; Cascade dropdown to Crelate picklist with the same option values. User picker fields map to Crelate user lookup fields or store the selected user email as a text field if a user lookup is not available. We provide a custom-field manifest before migration listing field name, type, and picklist options so the Crelate admin can pre-create matching fields.

Cascade's cascading alignment model links parent Plans to child Projects and Key Results via directional alignment relationships. These relationships have no native equivalent in Crelate's ATS data model. We reconstruct one level of parent-child linkage as a custom lookup field custom_parent_opportunity__c on the Opportunity object. Customers with deeply nested goal trees (Plan contains Project contains Key Result) should be aware that multi-level hierarchy collapses to two levels (Plan-Project or Project-Key Result) in Crelate because Crelate does not support recursive lookup chains on Opportunity.

Cascade Engagement Page Snapshots are read-only rendered reports generated from live Plan and Project data. They contain 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 Crelate's reporting or shared via PDF. The underlying Plan, Project, and Key Result data migrates as described above.

Cascade integration credentials and connector configurations (such as Salesforce, HubSpot, or Jira sync settings) are external-service authentication data that does not transfer between platforms and has no equivalent in Crelate's integration model. We export a list of active integrations as a reference document so the customer's admin can reconfigure them in Crelate's integrations module post-migration.

Cascade Key Result progress percentages migrate to Crelate custom numeric fields on the parent Opportunity. Progress values are validated as integers between 0 and 100. Values stored as free-text or non-numeric in Cascade are flagged for manual review before migration and stored in a Crelate text field if numeric conversion is not possible.

Cascade Plan and Project start_date and end_date fields map to Crelate Opportunity date fields. If Crelate does not have a dedicated start date field on Opportunity, we map the Cascade start date to a custom date field custom_start_date__c and the end date to the Opportunity Close Date or a custom_end_date__c field, depending on which more accurately reflects the Cascade semantics.