Migrate from Talent Pathway to Crelate

Talent Pathway Candidate records (nurses, physicians, allied health, PRN staff) map to Crelate People records. The candidate's name, email, phone, address, and employment history fields map to standard Crelate People fields. Healthcare-specific properties like specialty area, shift preference, and travel willingness migrate as custom fields. Source system candidate IDs are preserved in a custom field for cross-system reconciliation.

Talent Pathway Credential records (RN licenses, BLS/ACLS, state certifications) map to Crelate People with credential data stored as linked Activity Forms or custom fields. Each credential type (License, Certification, Training) gets its own Crelate Activity Form definition. The license number, issuing state, issue date, and expiry date migrate as structured fields. We flag every credential with an expiry date within 90 days of migration date as requiring active follow-up at the destination so compliance gaps do not open silently after cutover.

Talent Pathway Job records (open healthcare positions) map directly to Crelate Job records. Job title, facility name, location, shift details, pay rate range, and job description migrate as standard Crelate Job fields. Healthcare-specific fields like required certifications and unit/department assignment migrate as custom fields. Active/inactive status is preserved so the destination system reflects which positions are currently open versus closed.

Talent Pathway Placement records (candidates assigned to jobs) map to Crelate Placement records with the Candidate-to-People and Job-to-Job lookups resolved at migration time. Placement start date, end date, pay rate, bill rate, and status (active, completed, terminated) migrate as standard fields. Placement-to-Credential associations are preserved by linking the same credential Activity Form records to both the Candidate's People record and the Placement record.

Talent Pathway Timesheet records (Performance-tier feature) map to Crelate Activity records or custom time-entry records tied to the Placement. Each timesheet row (date, hours worked, shift type) migrates as a separate Activity record with a custom field for hours and a reference to the parent Placement. Because timesheet formats vary by agency payroll cycle (weekly, biweekly, monthly), we map to the destination structure agreed during scoping. We do not replicate Talent Pathway's payroll integration logic.

Talent Pathway Invoice records (Performance-tier) migrate to Crelate as either a custom Invoice object (if the customer configures one during implementation) or as Activity records tagged with invoice metadata. Line items, billing amounts, and invoice status migrate as fields. Invoice-to-Placement associations are preserved via foreign key mapping to the migrated Placement records. Custom invoice templates and branding from Talent Pathway do not migrate.

Talent Pathway Commission records track payouts tied to Placements and Employee assignments. We export commission amounts, calculation bases, and payment status as custom fields on Crelate Placement records or as linked Activity records. The commission calculation rules (rate tables, multipliers, tiered structures) that produced the payout amounts do not migrate as logic; we preserve the resulting payout amounts and advise customers to document their commission rules separately for re-implementation in the destination payroll system.

Talent Pathway Skills Checklist Library records (Starter-tier) define question/answer pairs attached to candidates or job templates. These map to Crelate Custom Questionnaires or Activity Forms. The checklist definition (title, questions, answer options) migrates as an Activity Form template; the candidate's completed checklist responses migrate as Activity Form submissions linked to the corresponding People record. We map the checklist-attachment associations so each candidate retains a record of which checklists they completed.

Talent Pathway Employee records from the Hire/Employee Module (Performance-tier) map to Crelate People records with employment-specific custom fields. Personal details, assignment history, and employment status migrate as fields on the People record. The distinction between a Candidate (prospective) and an Employee (active placement) is maintained in Crelate through the People record status and a custom employee_type field.

Talent Pathway Scheduling Module records (Performance-tier) represent shift schedules tied to placed healthcare professionals. These map to Crelate Activity records with Event-type entries for scheduled shifts including start time, end time, facility location, and assigned employee. Shift assignments are linked to the corresponding Placement record. We preserve the schedule-to-placement association so that timesheet entries can be reconciled against scheduled shifts at the destination.

Talent Pathway Custom Workflows and Automation (Enterprise-tier) define triggers, conditions, and actions for recruitment automation. These do not migrate as executable code because Crelate's workflow model differs. We export the workflow schema (trigger type, conditions, action sequence) as a written configuration inventory that the customer's Crelate administrator uses to rebuild equivalent Recruiting Workflows in Crelate. The rebuild is out of migration scope.

Talent Pathway uploaded documents include resumes, signed e-signature documents, and company-branded files. These binary files export from Talent Pathway and re-associate by record ID in Crelate. File naming conventions and folder structures from Talent Pathway are documented but not replicated; Crelate's document attachment model attaches files directly to People, Job, or Placement records. We preserve the document-to-record associations so every candidate retains their uploaded resume and signed forms.

Recruiter and manager assignments on Candidates, Jobs, and Placements in Talent Pathway are stored as user IDs. We map these to corresponding user identities in Crelate by email match. Owners without a matching Crelate User go to a reconciliation queue for the customer's admin to provision before record import resumes. User-level permissions and role assignments do not migrate and must be reconfigured in Crelate's user management settings.

Talent Pathway VMS integration configurations (connection credentials, endpoint URLs, job synch settings, candidate submittal mappings) live in the platform's integration layer and are not accessible as exportable data. We document which VMS integrations were active in Talent Pathway and provide a configuration checklist for re-establishing those integrations in Crelate. The migration does not carry over integration credentials or mappings; the customer's admin rebuilds VMS connections in Crelate's integration settings post-migration.