Migrate your Cascade data

Plans are the top-level container in Cascade's hierarchy. We preserve all plan metadata including title, description, start/end dates, and the plan-level owner assignment during migration. Plans can be exported via CSV or API and map cleanly to any destination's equivalent initiative or program object.

Projects nest under Plans and contain the operational layer of work. We map project name, status, assigned owner, team associations, custom fields, and timeline dates. Project-to-plan parent linkage is preserved via a foreign-key mapping field in the destination.

Key Results are the measurable outcomes attached to Projects. We migrate the result title, metric type, start and target values, current progress percentage, and owner. Progress values are validated as numeric fields to prevent type-mismatch errors in the destination.

Projects can contain checklist items marking discrete sub-tasks. We export all checklist items with their completion status flags and map them to subtasks or checklist fields in the destination. Checklist ordering is preserved where the destination supports ordered lists.

Cascade Teams group users for assignment and visibility purposes. We map team names and membership to the destination's org groups or team objects. Where the destination lacks a dedicated Teams object, we merge team membership into employee records as a custom property.

Entity templates in Cascade allow custom fields on Plans, Projects, and Key Results. Custom field types include text, number, date, dropdown, and user picker. We perform field-type mapping and create matching custom fields in the destination, handling dropdown option lists explicitly to avoid silent value-loss on picklist fields.

Milestones are date-linked markers on Projects that represent key delivery points. We migrate milestone names, target dates, and ownership. Milestone ordering is preserved via a sequence field. Date-based reporting downstream requires explicit validation that target dates transfer as date fields, not datetime or text.

Owners are individual users assigned to Plans, Projects, or Key Results. We export the user ID and display name and map these to the corresponding user records in the destination system. Owner reassignment requires that destination user accounts exist or are created during the migration.

Engagement Page Snapshots are snapshot reports generated within Cascade's UI for sharing strategy status externally. These are read-only rendered reports and have no structured data model suitable for migration. We exclude them from the data export and flag them for manual re-creation in the destination.

Integration credentials and connector configurations (such as Salesforce, HubSpot, or Jira sync settings) are external-service authentication data that does not transfer between platforms. We export a manifest of active integrations for manual re-configuration in the destination.

Cascade's core value proposition is vertical alignment: parent goals link to child goals across the hierarchy. We capture the parent_id and alignment_source for each goal to preserve the cascade linkage. Where the destination uses a flat list or different alignment model, we reconstruct the hierarchy as parent-child relationships on the target object.