Migrate from TalentNest to Crelate

TalentNest Jobs (the top-level recruitment containers with title, description, and stage configuration) map directly to Crelate Job records. We preserve the job status, posting dates, and the job description body. Crelate does not replicate TalentNest's stage-based workflow triggers as automation; the stage names and order are preserved as a written stage map for your admin to configure in Crelate's Business Development Workflows or as a custom pipeline if your Crelate tier supports it.

TalentNest Candidate profiles (contact details, resume, demographics, notes) map to Crelate Contact records. The Crelate Contact is the canonical record; we resolve all contact fields including name, email, phone, address, and resume attachment. Source attribution from TalentNest (where the candidate originated) maps to Crelate's Candidate Source Tracking field.

TalentNest Applications (the junction records linking Candidates to Jobs with status, rating, and stage history) map to Crelate Activity records attached to the Job. We preserve the full application timeline including stage transitions, timestamps, and reviewer assignments. The original submission timestamp is pulled from the TalentNest application audit trail (not the auto-reset application date field) to ensure reporting accuracy.

TalentNest's proprietary screening scores are stored as job-specific custom fields on Applications with no standardized schema across roles. We export all screening-related numeric and text fields as key-value pairs and configure Crelate custom fields to match. The mapping is documented field-by-field, and Crelate's field-mapping feature on Activity Forms allows the screening response to write directly to the Contact record field (for example, desired_salary__c) if desired. This is the highest-scope configuration step in the migration.

TalentNest's Talent CRM (candidate pool outside active applications, available on Growth and above) maps to Crelate Contact records that are not linked to an active Job Application. We export all CRM candidate profiles and flag those not currently attached to any Application so they land as standalone Contacts in the Crelate talent database. Records that do have an active Application are linked via the Job Application Activity record.

TalentNest User accounts with roles and access permissions map to Crelate User records by email match. We export name, email, role, and assignment history. Users without a matching Crelate account at migration time are held in a reconciliation queue for your admin to provision before record import resumes. OwnerId references on Contacts, Jobs, and Activities are resolved via this User mapping.

Recruiter notes attached to candidate profiles in TalentNest migrate as Crelate Note records linked to the Contact. We preserve the author, timestamp, and full note body. Crelate's Note object supports rich text, and notes are linked via ContentDocumentLink to the parent Contact record for timeline visibility.

Referral source data from TalentNest (available on Business and Enterprise tiers) maps to Crelate's Candidate Source Tracking field on the Contact. Referral attribution (referrer name, referral date, referral program) is preserved as a custom field if the native Crelate source tracking fields do not capture the full referral context. Starter and Growth tier accounts without referral tracking export will have null values here.

TalentNest workflow stage definitions (e.g., Review Candidate, Interview, Offer) with associated trigger actions and email templates are exported as a structured configuration document, not as migratable automation. Crelate's pipeline stages are configured manually in Settings | Workflows. We deliver a stage-by-stage map showing which TalentNest stages correspond to which Crelate pipeline statuses, including any stage probability or disposition values.

TalentNest customizable email and SMS templates tied to workflow stages are exported as template bodies and metadata. Since template IDs are proprietary to TalentNest, we deliver the full template content with variable placeholders identified so your admin can recreate them in Crelate's Email Templates section. This is a manual re-creation task; templates are not imported as functional automation.

TalentNest job board distribution configuration (30+ aggregators on Business and Enterprise tiers) is exported per Job as a distribution list. We flag which boards were active at time of posting and deliver this as a written configuration guide. Crelate's free job board distribution (50 postings on Business tier) and its native integrations with Indeed, Dice, CareerBuilder, and Monster serve as the replacement posting infrastructure.

TalentNest pre-screen and demographic custom fields on Applications are exported with field types, labels, and answer options. We configure equivalent Crelate custom fields on the Contact or Activity record before migration. Field types are mapped: TalentNest text fields map to Crelate text fields, dropdowns map to picklists, and multi-select arrays map to Crelate multi-select fields where the data type supports it. Custom field mapping is validated in a Crelate Sandbox before production import.