Migrate from Cascade to BambooHR

Cascade Owner records (individual users assigned accountability for Plans, Projects, and Key Results) map to BambooHR Employee records. We extract owner displayName, email, and any user-record metadata and create corresponding BambooHR employees. Cascade user records without email addresses (inactive or invited-only users) require admin validation before import because BambooHR requires a valid email for employee provisioning. The owner role type (Plan Owner, Project Owner, Key Result Owner) is preserved in a BambooHR custom text field cascade_owner_role__c for reference.

Cascade Teams map to BambooHR Departments. We export team names, descriptions, and membership lists. The membership list (which employees belong to which teams) maps to the BambooHR employee directory by matching on employee email. BambooHR does not support multi-department employee assignment natively, so employees in multiple Cascade Teams receive a primary department assignment from the team with the most recent membership date and secondary team memberships preserved in a custom multi-select field cascade_secondary_teams__c.

Cascade Plans are the top-level strategy containers with titles, descriptions, start/end dates, and owner assignments. BambooHR has no equivalent object for strategy or OKR management. We flag Plans during discovery and deliver a written inventory listing Plan title, owner, date range, and linked Projects and Key Results for the customer's strategy team to reconstruct outside BambooHR or in a dedicated OKR tool. The Plan owner (if a valid employee email) maps to a BambooHR Employee record but the Plan itself does not migrate as data.

Cascade Projects nest under Plans and contain operational work items, owners, teams, checklist items, milestones, and custom fields. BambooHR's object model covers employee data and HR workflows, not project or initiative management. We export all Project metadata, owner assignments, team memberships, milestone dates, and custom field values into a structured JSON manifest. The customer uses this manifest to rebuild Projects in their chosen project management or OKR platform. Project-linked employees (owners and team members) migrate as BambooHR Employees; the project structure does not.

Key Results are the measurable outcomes attached to Projects in Cascade's OKR model: result title, metric type, start and target values, current progress percentage, and owner. BambooHR's Pro plan supports performance review cycles and 360-degree feedback, but not individual Key Result tracking. We export Key Result metadata (title, owner, metric values, progress) into the migration manifest for the customer's strategy team. Progress percentage values do not map to any standard BambooHR field; if the customer requires retention, we map them to a custom number field cascade_key_result_progress__c on the Employee record with the understanding that this is a reference field, not a live OKR connection.

Cascade entity template custom fields (text, number, date, dropdown, user picker types) defined on Plans, Projects, and Key Results require schema recreation in BambooHR. We export the complete custom field manifest: field name, type, and picklist options. The BambooHR admin creates matching custom fields on the Employee object before import, as BambooHR enforces field creation before data import for custom attributes. Dropdown fields with enumerated values migrate as picklist fields; user picker fields migrate as text fields containing the referenced user's display name.

Cascade Milestones are date-linked markers on Projects representing key delivery points. We export milestone names, target dates, ownership, and ordering sequence into the migration manifest. BambooHR has no milestone object. If milestone dates correspond to employee work deadlines, we map the milestone date to a custom date field cascade_milestone_date__c on the related Employee record; otherwise milestones are flagged for reconstruction in the customer's project or strategy management tool.

Cascade Projects can contain checklist items marking discrete sub-tasks with completion status. BambooHR does not have a checklist or sub-task object. We export checklist item text and completion status into the project manifest. If checklist items correspond to onboarding steps or HR process tasks, the customer rebuilds them as BambooHR onboarding tasks or as rows in an HR process checklist tool post-migration.

Cascade Engagement Page Snapshots are rendered read-only reports generated from live Plan and Project data. They contain no structured underlying data model suitable for extraction. We flag Engagement Pages during discovery and treat them as reference screenshots to be manually re-created in the destination. The underlying Plan, Project, and Key Result data migrates normally per the mapping above; the snapshot renderings do not.

Cascade's cascading goals model links parent Plans to child Projects and Key Results via an alignment relationship stored as a directional alignment link with a source object reference. This structural hierarchy has no equivalent in BambooHR's relational model. We extract all alignment_source values and include them in the strategy manifest for reconstruction. BambooHR's reporting hierarchy (manager-employee relationships via the supervisor field on Employee) covers organizational structure, not goal alignment.