Migrate from TalentWall to Crelate

Jobs originate in the connected ATS (Greenhouse, Lever, or Jobvite) and sync to TalentWall as the pipeline visualization frame. We extract Jobs directly from the upstream ATS API using the ATS's native endpoints rather than TalentWall, since the ATS holds the canonical job record. We pull job title, department, location, open date, close date, hiring manager, and job description. In Crelate, the Job maps to the Crelate Job object with status, assigned recruiter, and custom properties populated from the ATS export. If TalentWall carries job health rankings (Red/Yellow/Green) for an open role, we extract those from TalentWall's storage and write them as custom fields on the corresponding Crelate Job record.

Candidates are surfaced on TalentWall as interactive pipeline cards but their canonical record lives in the upstream ATS. We extract all candidate data from the ATS API — name, email, phone, current company, current title, application date, source, and pipeline stage — and map it to the Crelate Person object. Crelate unifies candidate and contact records under the Person model, which eliminates the separate company-and-candidate object split that some ATS platforms require. Historical stage assignments and movement timestamps transfer to Crelate's activity timeline as StageHistory entries.

Stage names and ordering are defined per job in the upstream ATS and reflected as columns on TalentWall's visual wall. We pull stage definitions from the ATS job configuration, not from TalentWall's visual layout. Crelate uses a pipeline-and-stage model that maps directly: each upstream ATS pipeline becomes a Crelate Pipeline, and each stage within it becomes a Crelate Stage with its sequence order preserved. If the customer used TalentWall's custom widget library to display additional stage metadata (e.g., stage-specific notes or target days-in-stage), we capture that as stage-level custom fields in Crelate.

TalentWall allows custom widgets bound to job-level custom fields. These are TalentWall-native and not stored in the upstream ATS. We extract the job-level custom field definitions and values from TalentWall's storage (coordinating with TalentWall support for a full data export if no self-service mechanism exists) and map them to Crelate Job-level custom properties. We validate field scope at extraction time: a job-level TalentWall custom field must map to a job-level Crelate custom field, not an offer-level or candidate-level one, or the widget reference breaks silently in the destination.

Offer-level custom fields in TalentWall track compensation details, start date contingencies, and offer letter metadata specific to an individual offer on a job. We extract these as key-value pairs from TalentWall's storage and map them to Crelate Offer-level custom properties. If Crelate does not have a dedicated Offer object in the customer's tier, offer-level custom fields map to the Candidate custom properties or as linked records. We flag this scope constraint during discovery so the mapping decision is made before data transformation begins.

TalentWall's custom widget library maps visual widgets (kanban cards, summary tiles, pipeline metrics) to underlying custom fields. The widget-to-field binding lives in TalentWall. We extract the widget configuration and the field it references, then recreate the equivalent in Crelate: custom field for the data, and stage layout configuration for the visual representation. TalentWall's widget layout state (card positioning, column width, collapsed sections) has no Crelate equivalent and is not migrated — we document the widget inventory for the customer's admin to rebuild in Crelate's pipeline configuration UI.

Job health (Red/Yellow/Green status with associated notes) is a TalentWall-computed or recruiter-entered annotation that lives exclusively in TalentWall's database and is not written back to the ATS. We extract this data during the TalentWall-specific extraction phase, pairing each ranking with the corresponding job ID from the ATS. We write the health status as a custom picklist field on the Crelate Job record and the health notes as a custom text area field. If no job health annotation exists in TalentWall for a given role, no value is written.

Candidate freshness — a TalentWall-computed or recruiter-entered metric reflecting last activity and pipeline position — is TalentWall-specific and not stored in the upstream ATS. We extract freshness scores and associated timestamps from TalentWall's storage and write them as custom numeric or picklist fields on the Crelate Person record. Freshness is used by recruiters for prioritization; Crelate's Activity Last Touched date and custom date fields provide an equivalent signal once the migration is complete, but the original TalentWall freshness value is preserved for historical continuity during the transition period.

Interview scheduling data shown in TalentWall's calendar view originates from the ATS calendar integration. We extract interview records (scheduled time, interviewer, interview type, location or meeting link, candidate reference, and job reference) from the upstream ATS API, which is the authoritative source. We map these to Crelate Activity records of type Interview with the scheduled date, assigned recruiter, and candidate link preserved. Interview scorecards that live in TalentWall rather than the ATS require the separate TalentWall extraction audit step; if found in TalentWall, they migrate as evaluation custom fields on the Crelate Activity record.

Interview scorecards may be entered directly into TalentWall by some teams rather than into the ATS, depending on workflow. We audit both TalentWall and the connected ATS during discovery to determine where the authoritative evaluation record lives. If scorecards are in TalentWall, we extract them from TalentWall's storage and write them to Crelate as custom fields on the Activity record (for interviewer-specific evaluations) or as Candidate-level custom properties (for aggregate scoring). If scorecards are in the ATS, we pull from the ATS export. This dual-audit step prevents silent data loss on evaluations that recruiters rely on for hiring decisions.

Resumes and attachments are stored in the ATS as the system of record. We export all file attachments from the ATS file storage — typically via the ATS's document download endpoints or bulk export — and deliver them as a structured file package indexed by candidate ID and file type. Files are ingested into Crelate's document storage and linked to the corresponding Person record. File naming conventions from the ATS are preserved to simplify reconciliation.

Recruiters may apply tags or pipeline labels directly on TalentWall cards that are not mirrored back to the ATS. We extract TalentWall-native tags and map them to Crelate Tags on the corresponding Person record. Tags used for candidate segmentation in TalentWall map to Crelate Tags which support filtering and bulk operations. If a tag in TalentWall represents a pipeline-stage-specific flag rather than a global candidate label, we document it for the customer to either create as a stage-level custom field in Crelate or fold into the existing Tags model.

TalentWall surfaces owner assignments from the upstream ATS. We extract distinct owner records from the ATS export and match by email against the Crelate destination's User table. Any TalentWall owner without a matching Crelate User is held in a reconciliation queue, and the customer's admin provisions the missing user before the production migration phase begins. Owner assignments on Jobs, Candidates, and Activities resolve via the User ID once provisioning is complete.