Migrate your Talent Pathway data

Candidates are the core object in Talent Pathway, representing healthcare professionals (nurses, physicians, allied health, PRN staff). We map all standard candidate fields including contact details, skills checklists, and credential references. Resume files are exported separately as binary attachments and linked by candidate ID during import into the destination system.

Credential tracking is a first-class feature storing license numbers, expiration dates, and verification status for certifications like RN licenses and BLS/ACLS. The schema varies by credential type, so we apply type-specific field mapping and flag any expired or expiring credentials that may require re-verification at the destination.

Jobs represent open healthcare positions; Placements are the records of candidates placed into those jobs. We migrate both objects with their association preserved so the destination system maintains the link between placed candidate and the original job requisition.

Timesheet records exist on the Performance tier and higher. We export timesheet entries tied to each Placement. Because timesheet formats vary by agency payroll cycle, we map to the destination's time-entry structure and flag any unsynced pay periods.

Invoicing is a Performance-tier feature. We export invoice records including line items, billing amounts, and status. Invoice-to-placement associations are preserved via foreign key mapping, but custom invoice templates or branding are not migratable as they are display-level, not data-level.

Skills Checklist Library is a Starter-tier feature. Checklists are structured as question/answer pairs attached to candidates or job templates. We map the checklist definitions and their candidate-level completions, noting that branching logic or conditional requirements may not translate directly to all destination systems.

Custom Workflows and Automation are Enterprise-tier features. Workflow definitions include triggers, conditions, and actions that define automation behavior. We export the workflow schema as structured metadata and map step outcomes to the destination's automation model where equivalence exists.

The Hire/Employee Module is a Performance-tier feature. Employee records include personal details, assignment history, and commission tracking. We migrate the employee profile and assignment associations, but commission calculation logic (how rates are applied) is application-level and not migratable as data.

Commission records track payouts tied to Placements and Employee assignments. We export commission amounts, calculation bases, and payment status. Historical commission totals are preserved, but the platform's commission calculation engine does not migrate—only the resulting figures.

Scheduling Module is a Performance-tier feature. Shift schedules tied to placed healthcare professionals are exported as event-like records with start/end times, location, and assigned employee. We map these to the destination's scheduling or calendar structure.

Talent Pathway connects to VMS, job boards, communication tools, and payroll systems. Integration configurations (credentials, endpoint URLs, sync settings) are not migratable. We document which integrations were active so they can be reconfigured in the destination environment.

Custom branding (logo, color scheme, document templates) is an Enterprise-tier feature stored as display assets, not data records. These assets are not accessible via standard export and are not migratable as part of the data migration.

AI features branded as Theo are Enterprise-exclusive and operate as an application layer on top of existing data rather than a data object itself. AI-generated recommendations, candidate scoring, or automation triggers built by Theo do not have a migratable data schema.

Recruiter and manager assignments on Candidates, Jobs, and Placements are stored as user IDs. We map these to the corresponding user identities in the destination system, flagging any users that do not yet exist in the target environment.

Documents include uploaded resumes, signed eSignature workflows, and company-branded documents. These are binary files we export and re-associate by ID. File naming conventions and folder structures are not standardized and may require cleanup at the destination.