Migrate from TalentWall to Bullhorn ATS & CRM

Jobs originate in the upstream ATS (Greenhouse, Lever, or Jobvite) and sync to TalentWall. We extract the canonical job record from the ATS API — not TalentWall — preserving title, department, location, employment type, and the job description. Bullhorn JobOrder fields map directly: title to title, department to jobBoardCategory or a custom department field, and the ATS job ID preserved as an external reference field. If multiple ATS instances are connected to TalentWall, we run separate ATS API extracts per instance and merge by external ID before Bullhorn ingestion.

Candidate records come from the upstream ATS as the system of record. We export all application data, contact information, work history, education, and resume from the ATS. Bullhorn's Candidate entity is the direct equivalent. Resume files export from the ATS file storage and attach to Bullhorn Candidate records via ContentDocumentLink. We preserve the TalentWall card position (pipeline stage at time of extraction) as a custom Candidate field if the customer requires historical position tracking.

TalentWall reflects ATS pipeline stages as visual columns on the Wall. We extract stage names and ordering from the ATS job configuration. Each distinct ATS pipeline maps to a Bullhorn JobOrder Record Type with its own Sales Process that defines the allowed Status values. Stage probability percentages from the ATS migrate to Bullhorn's JobOrder probability field.

Job health status is a TalentWall-native annotation not stored in the ATS. We extract it from TalentWall's storage (via support-coordinated export or direct access if available) and write it as a custom picklist field job_health_status__c on the Bullhorn JobOrder. We also extract any health annotation notes and write them to a custom text area field job_health_notes__c. If the customer's Bullhorn edition is ATS Growth (which has no Custom Objects), we use standard Bullhorn custom fields instead.

Candidate freshness is TalentWall-computed or -entered metadata indicating last activity and pipeline position. We extract it as a numeric or categorical value and write it to a Bullhorn Candidate custom field candidate_freshness_score__c. If the freshness score is a composite value not exposed in the ATS, we coordinate with TalentWall support to retrieve the full freshness dataset. Bullhorn ATS edition customers with limited custom fields use a single custom field to store the score as a text value for filtering.

TalentWall's custom widget library maps widgets to specific ATS custom fields scoped at the job level. We extract the widget-to-field mapping table from TalentWall, identify the corresponding ATS custom field, and recreate the display logic as Bullhorn JobOrder custom fields and section headers in the Page Layout. Widget visual placement does not migrate; the customer configures the Bullhorn Page Layout post-migration based on the inventory we deliver.

Offer-level custom widgets in TalentWall reference offer-level custom fields in the ATS. These map to Bullhorn Placement custom fields (Placement being Bullhorn's record for a placed candidate). We extract the widget configuration and write key-value pairs as Placement custom fields. If the customer does not use Bullhorn Placements (only tracking candidates through the pipeline), we map to Candidate custom fields instead.

Interview scorecards entered directly into TalentWall (rather than the ATS) exist only in TalentWall storage. We audit both TalentWall and the upstream ATS during discovery. If TalentWall holds scorecard data not present in the ATS, we extract it and write it to Bullhorn Custom Objects if the edition supports them (Front Office Growth/Enterprise: 10, Bullhorn ATS: 2, ATS Growth: none), or to Candidate custom fields. Bullhorn ATS Growth customers receive scorecard data as text-area fields on the Candidate record.

Interview scheduling data shown in TalentWall originates from the ATS calendar integration. We pull interview records (scheduled time, interviewer, interview type, meeting link) from the ATS calendar export and write them to Bullhorn PlacementSchedule (if the customer's Bullhorn edition supports it) or to Event records linked to the Candidate. Bullhorn's Event object stores StartDateTime, EndDateTime, Location, and interviewer as EventRelation records.

Recruiters may apply tags or labels on TalentWall cards that are not mirrored back to the ATS. We extract any TalentWall-native tags per candidate or job and write them as Bullhorn Candidate tags (if Bullhorn's tag feature is enabled) or as a multi-select picklist custom field candidate_tags__c. Tags used for candidate classification migrate to TopicAssignment records if the customer uses Bullhorn's Topic feature.

Client companies are not managed in TalentWall (it is candidate- and job-focused). We export ClientCorporation records from the upstream ATS if they exist there (Lever and Greenhouse store client or organization data). Bullhorn ClientCorporation maps directly to ATS organization records, with the ATS organization ID preserved as an external reference field. If the upstream ATS does not store client data, we extract it from any CRM connected to TalentWall or coordinate a separate export.

Resumes and attachments live in the ATS as the system of record. We export from the ATS file storage at migration time and deliver them as a structured file package alongside the record data, then attach to Bullhorn Candidate records via ContentDocumentLink. File naming follows the convention CandidateID_Filename to maintain association during ingestion. Bullhorn parses resumes through its built-in resume parsing on Candidate insert if the Bullhorn parsing feature is enabled.