Migrate from TalentRecruit to Recruit CRM & ATS

TalentRecruit candidate profiles (contact information, work history, education, skills, resume file references) map directly to Recruit CRM Candidate records. We extract the complete profile including any parsed resume data and re-apply it as structured fields. Raw resume files migrate as attachments to the candidate record. Skills and competency tags from TalentRecruit's tag vocabulary re-apply as Recruit CRM's custom label fields or native candidate tags.

TalentRecruit job records (title, description, department, location, hiring manager, opening count) map to Recruit CRM Job records. Stage configuration and approval chain settings require mapping to Recruit CRM's pipeline stage definitions, which are configured at the system level. We capture the customer's full stage sequence during discovery and apply it to the destination pipeline before candidate migration begins.

Each TalentRecruit application links a candidate to a job with a current stage and stage-transition timestamps. We map the stage name and transition history to Recruit CRM's application record, preserving the application date and current status. Stage timestamps migrate as structured date fields for pipeline reporting at the destination.

Interview records include scheduled datetime, interviewer panel, calendar references, and scorecard feedback. Scorecard templates vary per TalentRecruit tenant, so we flatten the structured scorecard data into Recruit CRM's interview record with custom fields for each评分维度. Free-text feedback migrates as a note or description field. Calendar integration references do not transfer and require re-configuration in Recruit CRM's calendar settings.

Posting records track which job boards and career pages a requisition was published to, along with posting date and status per channel. We export the posting manifest as a structured list and re-apply it as Recruit CRM job publishing records. Channel-specific posting credentials and authentication tokens do not transfer and must be re-configured in Recruit CRM's integrations settings.

Assessment scores and test results stored as linked records against an application migrate to Recruit CRM's Assessment records linked to the candidate job application. We export the score, assessment type, and completion timestamp. Proprietary third-party assessment vendor formats are not transformed; we flag these records for manual re-entry or re-assessment at the destination.

Offer records include salary, benefits summary, start date, and approval status. We export structured offer fields and flag whether a signed document attachment exists. Document files migrate as attachments to the offer record in Recruit CRM. Approval chain status resets to pending at the destination unless the customer specifically requests re-approval workflows to be pre-configured.

Onboarding documents, task checklists, and completion status linked to the hired application migrate as Recruit CRM onboarding checklist items. We export the checklist structure and completion state; completed state resets at the destination as is standard across ATS migrations. New hire documentation files migrate as attachments.

TalentRecruit user accounts, role assignments, and team membership are exportable. We map roles to equivalent Recruit CRM permission groups. Users must be re-provisioned at the destination with fresh login credentials; we export the permission matrix and role definitions as a configuration document for the customer's admin to rebuild. Active versus inactive status is preserved in the documentation for provisioning decisions.

Candidate and application tags stored as flat label arrays in TalentRecruit export as structured tag lists. We re-apply them as Recruit CRM custom label fields or native candidate tags, preserving the full tag vocabulary. Tag metadata (tag creation date, associated user) does not transfer; only the tag labels are migrated.