Migrate from TalentNest to Recruit CRM & ATS

TalentNest Jobs (top-level recruitment containers with title, description, and workflow stages) map 1:1 to Recruit CRM Jobs. The stage configuration from TalentNest maps to Recruit CRM pipeline stages, though stage names and counts are re-created manually during Recruit CRM setup because pipeline stages are a configuration in Recruit CRM rather than a stored export value. Job status, location, and salary fields map directly.

TalentNest Candidate profiles (contact details, resume, demographics, notes) map 1:1 to Recruit CRM Candidates. We preserve the original application submission date from the application audit trail as a separate field because TalentNest resets the application_date field on record touch. All profile fields map by label-matched custom fields in Recruit CRM.

TalentNest Applications (junction records linking Candidate to Job with status, rating, and stage history) map 1:1 to Recruit CRM Applications. Stage history and transition timestamps migrate as an activity log attached to the Application. We use the audit trail timestamp as the canonical application date rather than the potentially-reset application_date field.

TalentNest screening results are stored as job-specific custom fields on Applications with no standardized schema across roles. We export all numeric and text fields from the screening section as key-value pairs and enumerate them in the migration manifest. You map these to Recruit CRM custom fields during the field-mapping phase; the mapping is manual because the source schemas vary by job profile configuration.

TalentNest workflow stages (e.g., Review Candidate, Interview, Offer) with associated email and SMS triggers are exported as structured stage definitions. Recruit CRM pipeline stages are re-created manually as part of pipeline setup; we deliver a written stage map documenting the original stage order, names, and automation triggers so your admin can re-configure them in Recruit CRM pipelines.

TalentNest User accounts (names, emails, roles, and assignment history) map to Recruit CRM Users by email match. We resolve each TalentNest owner referenced on a record to the corresponding Recruit CRM User; any unmatched owners go to a reconciliation queue for admin provisioning before the main record import.

Recruiter notes attached to candidate profiles in TalentNest migrate to Recruit CRM Note records or Activity entries depending on whether they represent structured notes or timestamped interactions. Author, timestamp, and full note body are preserved.

TalentNest Referral tracking (available on Business and Enterprise tiers) stores referral source as a property on the Application record. We export this value and map it to a Recruit CRM custom field for referral source. Accounts on Starter or Growth tier will have null or absent referral data because the feature is tier-gated.

TalentNest Talent CRM (candidate profiles stored outside active applications, available on Growth and above) migrates to Recruit CRM's candidate database or talent pool feature. We flag all CRM-only records not linked to an active Application so you can validate whether they should migrate as active candidates or archived talent pool entries.

TalentNest email and SMS templates tied to workflow stages export as template body and metadata. Template IDs are proprietary and cannot be imported into Recruit CRM. We deliver the full template inventory (subject, body, conditional logic, stage trigger) in a written document for manual re-creation in Recruit CRM's template editor.

TalentNest job board distribution (30+ aggregators, gated to Business and Enterprise) exports as a per-job property listing which boards were active. Recruit CRM handles job distribution through integrations rather than native board connections. We surface the distribution list so your admin can re-configure job postings in Recruit CRM's partner ecosystem.

Pre-screen and demographic question custom fields on TalentNest Applications (field types, labels, answer options) export with full schema metadata. We map them to equivalent custom field definitions in Recruit CRM. Field types are matched to Recruit CRM's supported types (text, number, date, picklist, multi-select); any unsupported types are flagged for manual handling.