Migrate from Talent Clue to Recruit CRM & ATS

Talent Clue candidate records (contact details, source channel, current pipeline stage, and scorecard data) map directly to Recruit CRM Candidate records. The mapping preserves the full candidate profile including any embedded notes and ratings. Custom properties on the candidate object require field-level mapping during discovery because Talent Clue's dashboard export does not include custom field definitions by default. We request the full custom field list during the scoping call and store unmapped fields as Recruit CRM custom properties.

Talent Clue job postings (title, description, department, location, and publishing status) map to Recruit CRM Job records. The job status from Talent Clue (published, draft, archived) maps to Recruit CRM's publish or draft state. Department and location transfer to Recruit CRM's department and location fields. Active and archived vacancies export separately and import as active or archived in Recruit CRM according to the original status.

Each Talent Clue application links a candidate to a specific job and records the submission date and current pipeline stage. We preserve the candidate-to-job association and the stage history as a structured log or custom field in Recruit CRM. The original application submission timestamp transfers as a custom date field to preserve sourcing attribution. We flag any application records where the associated candidate or job is missing from the export and report them in the validation report.

Talent Clue's talent pool is a persistent candidate database independent of any specific vacancy. We export all pool records and map them to Recruit CRM's talent pool feature (if available in the customer's edition) or to candidate records tagged with a talent-pool source flag. We apply the same custom field mapping rules to pool candidates as to direct applicants. We confirm the destination talent pool configuration during discovery because not all Recruit CRM plans expose a separate talent pool object.

Talent Clue defines configurable pipeline stages per job or globally. We extract the stage labels and sequence from the customer's configuration and translate them to Recruit CRM's stage model. Custom stage names (for example, pre-screening rounds or technical interview stages) may not have direct equivalents in Recruit CRM's default pipeline, so we create custom stage values or map to the nearest standard stage and note the deviation. Stage order is preserved. Stage probability values transfer where the destination supports custom probability mapping.

Talent Clue evaluation forms capture interviewer ratings and free-text feedback against candidates. We export structured scorecard data (rating fields, overall score, interviewer name, date) and map them to Recruit CRM's scorecard fields if available, or to a structured set of custom fields on the candidate record. Free-text comments transfer as notes attached to the candidate. If Recruit CRM uses a different evaluation schema, we store evaluation data as custom fields in a consistent field order and document the original evaluation structure for the customer's admin.

Talent Clue interview records include scheduled time, interviewer, and outcome. We export scheduling data and outcome flags. Recruit CRM tracks interviews as activities on the candidate record. We map the interview date, time, interviewer (mapped to a Recruit CRM user by email), location or meeting link, and outcome (selected, rejected, pending) as structured fields. Interview notes from Talent Clue transfer as activity notes. Note: Recruit CRM's Google Calendar sync does not reflect deleted meetings bi-directionally; we document this limitation and recommend the admin verify calendar state post-migration.

Candidate-level notes export as raw text from Talent Clue. We import them as Note records attached to the corresponding Recruit CRM Candidate record. The original note author and timestamp transfer as metadata on the note. Large note volumes (over 5,000 notes) may require batched import to avoid timeout. We verify note attachment after each batch and report any failed attachments in the validation report.

File attachments on candidate records download from Talent Clue and re-upload to Recruit CRM as files attached to the candidate profile. CV and resume files transfer as the candidate's primary document where Recruit CRM supports a primary document field. We handle file type validation (PDF, DOCX, RTF) and flag any unsupported file formats before upload. Large attachment volumes (over 2,000 files) require chunked download and upload cycles. We report any corrupt or inaccessible attachments in the discovery audit.

Talent Clue recruiter accounts own vacancies and candidates. We map Talent Clue users to Recruit CRM users by email address match. Role and permission structures differ between the two platforms, so we flag permission discrepancies during discovery. Any Talent Clue user without a matching Recruit CRM account goes to a reconciliation queue for the customer's admin to provision before the candidate migration phase begins.

Talent Clue supports custom fields on candidate and application objects. We identify all active custom field definitions during the discovery call (customer provides a screenshot or manual list because these are not included in dashboard exports by default). Each custom field maps to a Recruit CRM custom property of the matching data type (text, number, date, picklist, checkbox). Picklist values require explicit mapping where the value sets differ between platforms. We store unmapped custom fields in a catch-all custom property and flag them in the validation report.