Migrate from Talent Clue to Crelate

Talent Clue job postings (title, description, department, location, publishing status) map to Crelate Job records. We export all active and archived vacancies per job export batch and map the Talent Clue status field to Crelate's job active or archived state. Department and location from Talent Clue map to Crelate's standard job classification fields or custom properties if the destination uses a structured department taxonomy.

Talent Clue candidate records map to Crelate Contact. Contact details (name, email, phone, address), source channel, and any scorecard data migrate as structured fields. Custom properties on the candidate record require field-level mapping: we identify all custom field definitions during discovery, match them to Crelate's built-in contact fields or create custom fields on the Business Plus plan, and flag any Talent Clue custom fields with no Crelate equivalent for the customer to decide whether to store as free-text custom properties or drop.

Each Talent Clue application links a candidate to a specific job and records submission date and pipeline stage. We preserve the candidate-to-job association by resolving the Talent Clue candidate ID to the migrated Crelate Contact and the Talent Clue job ID to the migrated Crelate Job. Stage history migrates as a log entry or custom activity on the Crelate application record, since Crelate's application form and activity form field mappings can copy stage answers directly to a contact column.

Talent Clue's persistent talent pool is a candidate database independent of any specific vacancy. We export all pool records and map them to Crelate Contacts tagged with the original pool name as a label or topic. Crelate's Tag and Topic model allows multiple pool memberships per candidate, which maps cleanly to candidates who appear in multiple Talent Clue talent pools.

Talent Clue evaluation forms capture interviewer ratings and free-text feedback. We export structured scorecard data as field values and map them to Crelate Activity Form questions created as part of the migration schema. Crelate's field mappings allow question answers to copy directly to Contact columns (e.g., overall rating, recommendation score) so that scorecard data is visible in the candidate record without navigating to the activity form.

Interview records include scheduled time, interviewer, and outcome. We export scheduling data as Crelate Activity records with the scheduled date, time, and interviewer name. Outcome flags (hired, rejected, pending) map to Crelate's application status or a custom activity field. Where Talent Clue tracks interview type or round number, we store these as custom properties on the activity record.

Talent Clue recruiter accounts owning vacancies and candidates map to Crelate Users by email match. Role and permission structures differ significantly between the two platforms and are not migrated as configuration; we provide a mapping table of Talent Clue roles to Crelate role equivalents for the customer's admin to configure post-migration.

Talent Clue's configurable pipeline stages per vacancy or globally map to Crelate application statuses and, on Business Plus, to Crelate's recruitment workflow stages. We extract the stage labels and sequence from Talent Clue during discovery, present the customer with a Crelate stage configuration plan, and implement it in the destination before application import begins. Custom stage names are preserved as labels; the sequence order is enforced by Crelate's status ordering.

Candidate-level notes migrate to Crelate Note records or Activity records with note type, linked to the parent Contact. Note body migrates as plain text with timestamps preserved. Notes are linked to the contact record via Crelate's content linkage model so they appear in the candidate's timeline.

File attachments (resumes, cover letters, portfolio items) are downloaded from Talent Clue and re-uploaded to the corresponding Crelate Contact record. Large attachment volumes may require batched upload with pause-and-resume capability. We flag any file types not supported by Crelate's attachment model during discovery.

Talent Clue custom fields on the candidate object are identified during discovery via the customer's manual field list. We create matching Crelate custom fields on the Contact object (Business plan supports standard custom fields; Business Plus supports Advanced Custom Fields). Field types are mapped: text to text, number to number, date to date, picklist to picklist. Any field type mismatches are flagged in the mapping spec.

Career page branding assets and job ad templates export as file downloads. Crelate's Branded Job Portal feature supports logo, colors, and portal styling but does not consume Talent Clue's asset files directly. We deliver the asset files and metadata as a downloadable package with a naming convention matching the original Talent Clue structure, so the customer's admin can re-apply branding manually in Crelate's portal settings.