Migrate from Talent finder to Crelate

Talent finder Job records carry title, department, location, description, and status. We map these to Crelate's Job object fields including jobtitle, department, location, and description. Crelate stores job taxonomy via customizable fields per Job record type, so we align Talent finder's job categories to Crelate's job type and discipline picklists during the field mapping pass. Active and archived status flags map directly to Crelate's isactive boolean.

Talent finder Candidate profiles map to Crelate Person records (the candidate-facing contact type). Contact information, work history, skills, and source attribution migrate with email used as the primary dedupe key. We deduplicate against existing Crelate Person records before inserting and flag any email collisions for customer review. Skills stored as comma-separated or multi-value fields in Talent finder map to Crelate's skills multi-select or tag fields depending on how the destination is configured.

Applications link a Candidate to a Job and track stage progression in Talent finder. We preserve the full stage history including timestamps so that the Crelate pipeline reflects the original hiring journey. The application-to-job relationship resolves via Crelate's linking table between Person and Job, which we populate after both parent records exist. Stage names are mapped to Crelate pipeline stage values during the transform pass.

Talent finder uses configurable stages per job or across the org. Crelate uses pipelines with stage names scoped per Job type. We create Crelate pipeline records matching Talent finder's stage ordering and labels, map probabilities where present, and flag any Talent finder stage with no direct Crelate equivalent in the mapping review document. The customer selects stage equivalence during scoping.

Talent finder user accounts with recruiter, hiring manager, or admin roles migrate to Crelate Users with corresponding role flags. We resolve users by email match and hold any Talent finder owner without a matching Crelate User in a reconciliation queue for the customer to provision before record import proceeds. Role names are mapped to Crelate's user permission set equivalents.

Scorecard data stored as structured evaluations tied to a candidate and interviewer in Talent finder extracts as field values that we map to Crelate's custom evaluation fields on the Person or Application record. Since Crelate supports customizable fields per record type, we pre-create the destination field schema before migration and populate it during the candidate and application load phases.

Resume files and uploaded documents are extracted from the Talent finder export, renamed to follow candidate-referenced filename conventions, and loaded as Crelate Attachment records linked to the corresponding Person record. We validate that each attachment's parent Person record exists in Crelate before attaching. Binary file integrity is verified with MD5 checksums against the source export.

Outreach emails, notes, and event timestamps migrate as activity records against the Candidate or Application in Crelate. We strip HTML from email bodies to ensure clean display in Crelate's activity timeline. Timestamps preserve the original activity date so the timeline ordering reflects the original Talent finder record. Note-type activities map to Crelate Notes linked to the Person record via ContentDocumentLink.

Any custom properties added to Candidates or Applications in Talent finder require explicit field mapping. We extract the custom field schema from the export during discovery, display it for customer review, and create matching custom fields in Crelate (via Settings | Core Records | Customize Fields) before the data load begins. Custom field type mapping follows Crelate's supported types: text, number, date, picklist, multi-select picklist, boolean, and currency.

Talent finder may store employer or client records alongside candidate records. These map to Crelate's Company object with the company name, website, industry, and address fields populated from the source export. Company records are loaded before Person records so that any Person-to-Company relationship is satisfied at insert time.

Candidate source attribution (job board, referral, direct) stored in Talent finder migrates to Crelate's source and medium fields on the Person record. We map Talent finder's source values to Crelate's canonical source picklist and flag any source with no direct equivalent for customer review.

Candidate records contain PII subject to GDPR and regional privacy laws. We flag every PII field during scoping and offer to strip or hash values (email addresses, phone numbers, home addresses) before loading into Crelate. The customer chooses the PII handling strategy during discovery. If GDPR compliance requires a Data Processing Agreement, we ensure the DPA is in place before any candidate PII is processed.