Migrate from TalentWall to Recruit CRM & ATS

Jobs originate in the upstream ATS (Greenhouse, Lever, Jobvite, etc.) connected to TalentWall. We extract the canonical job record directly from the ATS API, preserving job title, department, location, job description, and job status. The TalentWall job health ranking (Red/Yellow/Green) and any associated notes are TalentWall-native; we extract these separately and write them as a custom Job field in Recruit CRM (e.g., tw_health_status__c with values Red, Yellow, Green) to preserve the visibility signal. Stage names and order are pulled from the ATS job configuration and mapped to Recruit CRM pipeline stages.

Candidate records are exported from the upstream ATS, which is the system of record for application data and status history. We pull all candidate profiles, contact information, work history, education, skills, and current stage status. The TalentWall candidate freshness metric (last activity date and pipeline position) migrates as a custom Candidate property (e.g., tw_freshness_score__c or tw_last_activity_date__c) if it exists in TalentWall's storage. Any TalentWall-native tags or labels applied by recruiters that are not mirrored back to the ATS are extracted and written as Candidate tags in Recruit CRM.

Stage names and ordering are defined per job in the upstream ATS. TalentWall reflects these as Kanban columns on the Wall. We pull stage definitions from the ATS job configuration and map them to Recruit CRM pipeline stages. The customer configures the stage pipeline in Recruit CRM before migration so that stage names align; stage order is preserved by setting the sequence value during import.

TalentWall job-level custom fields are TalentWall-native and not stored in the upstream ATS. We extract them as key-value pairs from TalentWall storage and map them to custom fields on the Job object in Recruit CRM. The field type in Recruit CRM is chosen based on the data format (text, number, date, picklist). We validate that every TalentWall job-level custom field has a corresponding Recruit CRM custom field created before import to avoid silent mapping failures.

TalentWall offer-level custom fields are scoped to the offer stage within a job pipeline. These do not map directly to a Recruit CRM Offer object (Recruit CRM uses Placement records for hired candidates). We extract offer-level fields as key-value pairs and map them either to a custom field on the Candidate record (if the offer context is a candidate-level annotation) or to a custom field on the Placement object (if the offer context is tied to the placement outcome). The customer chooses the target during scoping.

TalentWall's custom widget library maps visual widgets to specific job-level or offer-level custom fields by name or ID. We extract the widget-to-field mapping configuration and recreate the equivalent functionality in Recruit CRM using standard custom fields. The widget reference is a UI convenience that does not have a structural analog in Recruit CRM; the underlying data (the custom field values) migrates, and the widget presentation is replaced by Recruit CRM's native field display.

Interview scheduling data shown in TalentWall's calendar view originates from the upstream ATS calendar integration. We export interview records (scheduled time, interviewer, interview type, candidate, job) from the ATS and import them into Recruit CRM as Interview records or Activity records linked to the Candidate and Job. Interview type and interviewer assignment migrate directly; any TalentWall-specific interview notes or scorecards entered in TalentWall rather than the ATS require separate TalentWall extraction (see scorecard gotcha).

Interview scorecards may exist in TalentWall, the upstream ATS, or both depending on the team's workflow. We audit both systems during discovery. If TalentWall holds scorecard data not present in the ATS, we extract it from TalentWall storage and import it as an Evaluation or custom object record in Recruit CRM linked to the Candidate. Scorecard fields (rating, strengths, concerns, recommendation) map to corresponding Recruit CRM evaluation fields or custom fields if the standard evaluation template is not in use.

Resumes and attachments are stored in the upstream ATS as the system of record. We export them from the ATS file storage at migration time and deliver them as a structured file package alongside the record data, then import them into Recruit CRM's candidate record as Resume or Attachment files. File names are preserved and linked to the corresponding candidate record by email or candidate ID matching.

Recruiters may apply tags or labels directly on TalentWall cards that are not mirrored back to the ATS. These TalentWall-native tags are extracted and written as Candidate tags in Recruit CRM or as a multi-select custom property if the tag set is structured. We deduplicate any tags that already exist in the ATS export to avoid double-tagging the same candidate.