Migrate from Talent Pathway to Recruit CRM & ATS

Talent Pathway Candidates map directly to Recruit CRM Candidates. Standard fields (name, email, phone, address, employment type, availability, specialty) migrate 1:1. Healthcare-specific fields like employment_type (PRN, full-time, part-time), unit_specialty, and bill_rate require custom fields in Recruit CRM since its standard Candidate schema does not include healthcare staffing-specific properties. User/owner assignments on Candidates are resolved by email match against Recruit CRM users; unresolved owners go to a reconciliation queue for the agency's admin to provision.

Talent Pathway Credentials (RN licenses, BLS/ACLS, certifications, state licenses) are stored as first-class objects with license type, license number, issuing state, expiry date, and verification status. Recruit CRM has no native credentialing module, so we create custom fields on Candidate: credential_type__c (picklist), license_number__c (text), issuing_state__c (text), expiry_date__c (date), and verification_status__c (picklist). For candidates with multiple credentials, we create one custom field group per credential type or store as a delimited text field. Any credential with expiry_date within 90 days of migration is flagged in a separate reconciliation report for active follow-up at the destination.

Talent Pathway Jobs map to Recruit CRM Job Orders. Standard fields (title, location, department, employment_type, description, requirements) migrate 1:1. Healthcare-specific fields like unit, shift_type, and pay_rate require custom fields. The Job's active/closed status maps to Recruit CRM's job status field. We preserve job_owner assignments by email reconciliation against Recruit CRM users.

Talent Pathway Placements map to Recruit CRM Placements as a linked object under the Job and Candidate. The Candidate-to-Job association is preserved via Recruit CRM's placement linkage. Placement fields including start_date, end_date, placement_status, and bill_rate map directly. Commission amounts from Talent Pathway's commission module migrate as read-only historical values to a custom field placement_commission__c; the calculation rules that produced them do not migrate (see Commission gotcha).

Talent Pathway Timesheet records (Performance-tier) store shift hours, dates, and status tied to a Placement and Employee. Recruit CRM has no native timesheet module. We export timesheet entries as custom fields on the Placement or as a standalone time-entry object that the agency creates. Agencies relying on Talent Pathway's automated timesheet feature for payroll integration need to evaluate Recruit CRM alongside a separate payroll tool (RecruitBPM, built-in payroll, or a Zapier-connected payroll system). We document the timesheet schema and data for the agency's admin to design the target structure.

Talent Pathway Invoices (Performance-tier) store line items, billing amounts, and status tied to Placements. Recruit CRM has no native invoicing module. We export invoice records as a structured data file and either store them as a custom invoice object the agency creates or attach them as documents to the Placement record. Invoice-to-placement associations are preserved via record linkage. Custom invoice templates and branding do not migrate.

Talent Pathway Skills Checklists are structured as question/answer pairs attached to Candidates or Job templates. We export checklist definitions and candidate-level answers as a flat data file. Recruit CRM's standard schema does not include a skills checklist object, so we map each checklist to a set of custom fields on Candidate or as structured notes attached to the record. The agency decides during scoping whether to use individual checkbox fields per skill or a consolidated notes section.

Talent Pathway Employee records from the Hire/Employee Module (Performance-tier) store personal details, assignment history, and commission tracking. We map Employee to Candidate in Recruit CRM since the candidate is the primary person record in a recruitment ATS. Assignment history is preserved as a linked notes section or custom employment history field group. Commission history migrates as a custom field group (see Commission gotcha).

Talent Pathway Commission records store payout amounts tied to Placements and Employees. We export commission amounts, calculation bases, and payment status as custom fields on the Placement: commission_amount__c, commission_basis__c, commission_status__c. The commission calculation rules (rate tables, multipliers, tiered structures) are application logic, not data records, and do not migrate. We advise the agency to document their commission logic separately for re-implementation in Recruit CRM's configuration or in a connected payroll system.

Talent Pathway Scheduling Module records (Performance-tier) store shift schedules with start/end times, location, and assigned Employee. We export scheduling records as structured data tied to the Placement. Recruit CRM has no native scheduling module, so we store schedule data as a custom field group on the Placement or advise the agency to manage scheduling through a connected calendar tool or Zapier integration. The migration does not include active shift automation or schedule-triggered alerts.

Recruiter and manager assignments on Candidates, Jobs, and Placements in Talent Pathway are stored as user IDs. We resolve Talent Pathway owner records by email match against Recruit CRM users. Any Talent Pathway owner without a matching Recruit CRM user is held in a reconciliation queue. The agency's admin provisions missing users in Recruit CRM before production migration begins. OwnerId references on standard objects require resolved users, making this a dependency gate for subsequent object imports.

Talent Pathway documents include uploaded resumes, signed eSignature workflows, and company-branded files. We export binary files and re-associate them to the corresponding Candidate, Job, or Placement record in Recruit CRM by ID. File naming conventions and folder structures from Talent Pathway do not map directly; we attach files to the most relevant parent record and note the original file path in a custom field. Company-branded documents created with Talent Pathway's custom branding features (Enterprise-tier) are not migratable as branded templates; only the underlying content migrates.