Migrate from Cascade to Bullhorn ATS & CRM

Cascade Plans map to Bullhorn JobOrder records if the Plan represents a job requisition or staffing need, or to a Bullhorn Custom Object (e.g., customObject1s) if the Plan represents a strategic initiative with no direct staffing workflow. We determine the mapping during scoping based on whether the Plan has associated recruiting activity (job postings, candidate submissions) or exists purely as an OKR container. The Plan title becomes the JobOrder title or Custom Object name field; Plan description maps to the JobOrder description or Custom Object text field. Start and end dates map to the JobOrder date fields or Custom Object date fields.

Cascade Projects map to Bullhorn JobOrder records or to a second tier of Custom Objects linked to the Plan-level Custom Object via a lookup field. We use Bullhorn's Custom Object lookup capability (customObjectX.pickerField) to reconstruct the Project-to-Plan parent-child relationship. Project status (not started, in progress, completed, on hold) maps to JobOrder status or to a Custom Object picklist field that the customer configures. Owner assignment maps to the Bullhorn User via email match.

Cascade Key Results are measurable outcomes attached to Projects. We map Key Result title to a Custom Object text field, metric type to a picklist, and start/target/current values to Custom Object number fields. Progress percentage maps to a numeric field with validation to ensure it lands as a number rather than free text. For Key Results that represent hiring milestones (e.g., 'Fill 3 positions by Q3'), we offer a mapping to Bullhorn Placement records with target end dates and status tracking.

Cascade checklist items on Projects map to Bullhorn Task records or to a sub-section within the Project Custom Object. Task Subject carries the checklist item title; Task Status carries the completion flag (completed maps to Completed, open maps to Not Started). ActivityDate carries the due date if one is set. If the Project Custom Object is the destination, checklist items map to a repeating group of fields within the Custom Object.

Cascade milestones on Projects map to Bullhorn Task records with a due date and no assignee (or the Project owner), or to dedicated Custom Object date fields if the customer prefers milestones as structured date fields rather than activity records. Milestone ordering is preserved via a sequence number stored in a Custom Object integer field. We validate that milestone dates transfer as ISO date strings rather than free-text dates to avoid format issues in Bullhorn.

Cascade Owners are individual users assigned to Plans, Projects, or Key Results. We extract the Cascade user ID and display name and match by email against the Bullhorn User table. Any Cascade Owner without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes. Migration cannot proceed past owner resolution because Bullhorn requires valid OwnerId references on most standard and custom records.

Cascade Teams group users for assignment and visibility. Bullhorn has a native Teams concept for user grouping and permissions. We map Cascade Team names and memberships to Bullhorn Teams where the feature is available in the customer's Bullhorn edition, or to a Custom Object text field holding the team name. Team membership is reconstructed by linking the relevant Bullhorn Users to the Bullhorn Team or by populating a multi-select picklist on the record.

Cascade entity templates let teams define custom fields on Plans, Projects, and Key Results. Custom field types include text, number, date, dropdown, and user picker. Bullhorn does not support freeform custom fields on standard objects; custom data lives in Custom Objects attached to the standard entity. We pre-create the Bullhorn Custom Object schema in partnership with Bullhorn Support using the Custom Object Setup Spreadsheet, then populate the fields during migration. The customer must file the setup ticket with Bullhorn Support before we can create Custom Object instances via the API.

Cascade's core value is vertical goal alignment: parent Plans link to child Projects and Key Results via directional alignment_source references rather than a standard parent_id foreign key. We extract all alignment_source values from Cascade and reconstruct the hierarchy in Bullhorn using Custom Object lookup fields (customObjectX.pickerField targeting the parent Custom Object or JobOrder). Mis-alignment occurs when the Cascade goal tree exceeds three levels and Bullhorn's lookup chain becomes difficult for admins to navigate. We document the full goal tree as a separate deliverable for the customer's Bullhorn admin to validate post-migration.

Cascade Engagement Page Snapshots are read-only rendered reports generated from live Plan and Project data. They contain no structured underlying data model suitable for extraction. We flag these during discovery and advise the customer to treat them as reference screenshots to be manually re-created in Bullhorn. The underlying data (Plans, Projects, Key Results) migrates normally. This is documented in the FlitStack AI Cascade source page as a platform-level limitation.

Cascade integration credentials and connector configurations (Salesforce sync, Jira sync, or other third-party connections) are external-service authentication data that does not transfer between platforms. We export a written inventory of active integrations for the customer's IT team to reconfigure manually in the destination system. Bullhorn integrations are set up separately via Bullhorn Marketplace or API credentials in the Bullhorn admin settings.

If Cascade data includes user engagement records such as comments, activity timestamps, or document attachments on Plans or Projects, we map these to Bullhorn Task records and Note records (stored as ContentDocument via ContentDocumentLink). Bullhorn's engagement model is oriented around recruiting activity (calls, emails, submissions) rather than strategy collaboration, so the migration preserves the timestamp and content but may not preserve the full conversational context. We flag any engagement records that cannot be cleanly mapped for the customer to review.