Migrate from Talent Pathway to Bullhorn ATS & CRM

Talent Pathway Candidate records map directly to Bullhorn Candidate. We preserve all standard contact fields (name, phone, email, address), professional summary, specialty, license type, and the assigned recruiter owner ID. The mapping resolves the owner by email against Bullhorn User records. Any Candidate without a resolved owner is placed in a reconciliation queue for the customer's admin to assign before placement records are imported.

Credential records (RN license, BLS, ACLS, state-specific healthcare certifications) map to Bullhorn Custom Object instances on the Candidate entity. The license number, issuing state, issue date, and expiry date migrate as custom fields. Bullhorn Support must provision the Custom Object schema before migration; we coordinate this via a setup ticket during the scoping phase. Credentials with expiry dates within 90 days of migration are flagged in the handoff report for active follow-up at the destination because expiry alert logic is not migratable.

Talent Pathway Job records map to Bullhorn JobOrder. The job title, description, facility/location, specialty requirement, shift details, and job status migrate. Job-to-Candidate associations migrate as separate Placement records rather than embedded in the JobOrder, preserving the independent relationship so that one job can have multiple placements over time.

Talent Pathway Placement records map to Bullhorn Placement with the Candidate and JobOrder lookups resolved at migration time. Placement pay rate, bill rate, start date, end date, and status transfer. The Placement-to-Timesheet association is preserved by resolving the timesheet records against the migrated Placement ID so that Bullhorn Onboarding or Bullhorn Timecards can access the linked history.

Timesheet records (Performance-tier feature) map to Bullhorn Timecard or custom time entry records depending on whether the customer licenses Bullhorn Onboarding. Each timesheet entry is linked to the migrated Placement ID via the WhatId relationship. Hours worked, pay rate applied, overtime hours, and approval status migrate. Agency payroll cycles (weekly, bi-weekly, monthly) are mapped to the destination time period configuration during schema setup.

Invoice records (Performance-tier feature) map to Bullhorn Invoice with line items, billing amounts, status (draft, sent, paid), and invoice date preserved. Invoice-to-placement associations are preserved via the Placement lookup so that billing history traces back to the original placement record. Custom invoice templates and branding assets do not migrate because they are Enterprise-tier display assets stored in Talent Pathway's presentation layer.

Talent Pathway Employee records (Performance-tier feature) represent placed healthcare professionals with personal details, assignment history, and commission tracking. These map to Bullhorn ClientContact for the contact profile and to User records for system access if the employee also has recruiter or admin access. Commission payout amounts migrate as financial fields on the ClientContact; the commission calculation rules (rate tables, multipliers, tiered structures) do not migrate and are documented for re-implementation in Bullhorn Billing or a third-party payroll system.

Commission records track payouts tied to Placements and Employee assignments. We export commission amounts, calculation bases, and payment status as historical values. The payout amounts migrate to Bullhorn as Placement financial fields or a commission Custom Object. The calculation logic (how the payout was derived from bill rate, pay rate, or tier) does not migrate because it lives as configuration in Talent Pathway's commission engine. We deliver a written commission logic document for the customer to re-implement in Bullhorn Billing or their payroll system.

Talent Pathway Skills Checklist Library records (Starter-tier feature) define checklist templates with question/answer pairs attached to candidates or job templates. We export the checklist definitions and their candidate-level results as Bullhorn Custom Object instances on the Candidate entity. The Bullhorn Custom Object schema must be provisioned by Bullhorn Support before migration; we coordinate this during scoping. If the number of checklist fields exceeds the Custom Object 55-field limit per object, we split into multiple Custom Objects (ChecklistSectionA, ChecklistSectionB) per Bullhorn's multi-object guidance.

Scheduling Module records (Performance-tier feature) represent shift assignments for placed healthcare professionals with start/end times, facility location, and assigned employee. These map to Bullhorn Event records with StartDateTime, EndDateTime, Location, and the assigned ClientContact as the WhoId. If the customer licenses Bullhorn Onboarding, scheduling migrates to the Onboarding shift module for healthcare-specific compliance tracking.

Talent Pathway Custom Workflows and Automation (Enterprise-tier feature) are workflow definitions including triggers, conditions, and actions. We export the workflow schema as a structured JSON document describing the automation logic. Bullhorn Automation is a separate add-on module with a different trigger-condition-action model. We do not migrate workflows as code. We deliver a written inventory of every Talent Pathway workflow with its trigger, conditions, actions, and recommended Bullhorn Automation equivalent for the customer's admin or a Bullhorn partner to rebuild post-migration.

Talent Pathway uploaded documents including resumes, signed eSignature files, and credential scans migrate as Bullhorn ContentDocument records. Each document is linked via ContentDocumentLink to the parent record (Candidate, JobOrder, Placement, or ClientContact). File naming conventions and folder structures from Talent Pathway are not preserved; we use a standardized naming convention (CandidateID_DocumentType_Date) to maintain traceability. eSignature workflow status (signed/pending/expired) migrates as a custom field on the ContentDocument rather than as a separate workflow.

VMS integration configurations (connection credentials, endpoint URLs, job sync settings, candidate submittal mappings) in Talent Pathway are stored in the platform's integration layer and are not accessible as exportable data. We audit which VMS integrations were active (Apex, SimpleMSI, Shiftwise, or other) by reviewing the integration log during discovery. Bullhorn VMS connectors are configured separately post-migration using Bullhorn's VMS integration framework. We deliver a VMS integration inventory document listing every active connection and its configuration parameters for the customer's admin to re-enter.

Talent Pathway recruiter and manager assignments on Candidates, Jobs, and Placements are stored as user IDs. We map these to Bullhorn User records by resolving the user email address. Any Talent Pathway user without a matching Bullhorn User goes to a reconciliation queue. The customer's Bullhorn admin provisions any missing users before record migration begins. Inactive Talent Pathway users are migrated as inactive Bullhorn users to preserve historical assignment data.