Migrate from Talent finder to Recruit CRM & ATS

Talent finder Candidate records map directly to Recruit CRM Candidate profiles. We extract contact fields (name, email, phone, location), work history, skills, source attribution, and any custom properties. Email address serves as the dedupe key. We flag records with missing or malformed email before loading and hold them in a reconciliation queue. GDPR-sensitive fields (full name, email, phone) are stripped or hashed on request before the CSV is processed into the Recruit CRM import format.

Talent finder Job postings carry title, department, location, description, and status. We map these to Recruit CRM Job records, preserving the original job status (open, closed, on hold). Recruit CRM supports unlimited open jobs on all paid tiers, so no reconfiguration of job limits is required. We flag any job with a status value that has no direct Recruit CRM equivalent for manual review before import.

Applications link a Candidate to a Job in both systems. We preserve the full application stage history including timestamps so the Recruit CRM hiring pipeline reflects the original candidate journey. Stage ordering migrates from Talent finder's configurable pipeline to Recruit CRM's Kanban pipeline view, with stage names mapped one-to-one where possible and reconciled against the destination stage schema.

Talent finder uses configurable stages per job or across the org. We map each stage by name and ordering to Recruit CRM's pipeline stages, creating a custom pipeline in Recruit CRM if the destination already has an existing pipeline. Stage probability and stage color metadata from Talent finder carry over as custom fields in Recruit CRM if they are present in the export. Any stage without a direct equivalent is flagged in the scoping report for the customer to assign before migration.

Talent finder user accounts with recruiter, hiring manager, or admin roles are migrated with role flags preserved. We map role names to the closest Recruit CRM user role (Admin, Recruiter, Hiring Manager). User provisioning in Recruit CRM is validated by email match; any Talent finder owner without a matching Recruit CRM user account is held in a reconciliation queue until the customer admin provisions the account.

Talent finder stores structured evaluations tied to a candidate and an interviewer. Scorecard field values extract from the CSV export and map to Recruit CRM candidate summary and evaluation fields. We preserve the rating values, interviewer name, and evaluation timestamp. Where the source scorecard uses a rating scale not supported by Recruit CRM's default fields, we create a matching custom evaluation field during schema setup.

Resume files and uploaded documents are extracted from Talent finder's export, renamed to follow candidate-referenced conventions (candidate name and job reference in the filename), and loaded to Recruit CRM with the same attachment relationship preserved against the candidate record. File size limits are checked against Recruit CRM's attachment constraints. Any file exceeding the limit is flagged for the customer to decide whether to upload manually post-migration or exclude from the migration scope.

Talent finder outreach emails, notes, and event timestamps migrate as activity records against the candidate or application. We strip HTML from email bodies to ensure clean display in Recruit CRM's activity timeline. Call and meeting activities preserve their original timestamps and are linked to the candidate record. We handle both standalone notes and timestamped communication events, routing each to the appropriate Recruit CRM activity type.

Any custom properties added to Candidates, Jobs, or Applications in Talent finder require explicit field mapping during discovery. We extract the Talent finder custom field schema from the export, present it for review, and create matching custom fields in Recruit CRM before any data import. Custom field types (text, number, date, picklist, multi-select) are mapped to their Recruit CRM equivalents. Multi-select fields require special handling if the source stores values as delimited strings.

Talent finder tracks candidate availability status as a field on the candidate record. We map this directly to Recruit CRM's Candidate Unavailable toggle, preserving the original status and the date of the last status update. If the source uses a custom availability scale (available, open to offers, not looking), we create a matching custom picklist field in Recruit CRM rather than forcing a boolean fit.