Migrate from TalentWall to Zoho Recruit

Jobs originate in the connected ATS (Greenhouse, Lever, Jobvite, or another supported platform), not TalentWall itself. We extract the job record from the upstream ATS API, capturing Job Title, Department, Location, Job Description, Opening Date, and status. We then append any TalentWall-native job health ranking (Red/Yellow/Green) as a Zoho Recruit custom single-select picklist field tw_health_status__c. If the source ATS uses a custom job schema, we map its fields to Zoho Recruit Job Opening standard and custom fields during the import phase.

Candidate records come from the upstream ATS as the system of record. We export the full candidate profile including name, email, phone, current company, current title, source, and application date from the ATS API. We then append TalentWall-specific enrichment — candidate freshness score, any TalentWall-native tags or labels, and custom properties entered on the candidate card — as Zoho Recruit custom fields on the Candidate record. Resume files export from the ATS file storage and attach to the Zoho Recruit Candidate record via the Document module.

Stage names and order are defined per job in the ATS. We extract the stage definition from the ATS job configuration and create matching stage values in Zoho Recruit's Job Opening stage setup. Each TalentWall stage column on the Wall maps to a corresponding Zoho Recruit stage. If the ATS uses custom stage names not present in Zoho Recruit by default, we add them as new stage picklist values before migration begins.

TalentWall job-level custom fields map to Zoho Recruit custom fields on the Job Opening module. We extract these as key-value pairs from TalentWall's own database or direct storage access and write them to Zoho Recruit Job Opening custom fields. TalentWall's job-level vs offer-level scoping is validated during mapping — a job-level custom field must map to a Zoho Recruit Job Opening field, not an Offer field. Mixing scopes causes the widget to reference a non-existent field and fail silently.

TalentWall offer-level custom fields map to Zoho Recruit Candidate custom fields or Offer Letter custom fields depending on the customer's Zoho Recruit plan and configuration. We extract these from TalentWall and write them as key-value pairs to the appropriate Zoho Recruit module. If the customer's Zoho Recruit instance does not have Offer Letter customization enabled, we map to Candidate-level custom fields and flag the difference in the mapping document.

TalentWall's custom widget library maps widgets to specific job-level or offer-level custom fields by name or ID. We extract the widget-to-field mapping and recreate it in Zoho Recruit as a combination of custom fields and informational notes attached to the Job Opening or Candidate. Widgets without a clear field equivalent are documented as Zoho Recruit Custom Views or Notes for the customer's admin to finalize post-migration.

Job health status (Red/Yellow/Green) is a TalentWall-native annotation stored exclusively in TalentWall's own database — it is not written back to the connected ATS. We extract the health ranking for each job and write it to a Zoho Recruit custom single-select picklist field tw_health_status__c on the Job Opening record. The health ranking notes and any associated commentary migrate as a Zoho Recruit Note attached to the Job Opening. If the customer's instance does not expose a data export mechanism, we coordinate directly with TalentWall support to retrieve a full data snapshot before the import phase.

Candidate freshness is a TalentWall-computed or -entered metric reflecting last activity and pipeline position. This metric is TalentWall-native and does not exist in the ATS. We extract the freshness value for each candidate and write it to a Zoho Recruit custom number field tw_freshness_score__c on the Candidate record. If the freshness metric is a relative indicator (e.g., Fresh/Stale) rather than a numeric score, we map it to a custom picklist field tw_freshness_indicator__c. The field name and type are confirmed during the discovery phase based on the actual data observed.

Interview scheduling data shown in TalentWall's calendar view originates from the ATS calendar integration. We pull interview records — scheduled time, interviewer, interview type, duration, and location — from the ATS API and map them to Zoho Recruit Interview records. The Interview Feedback Form (available on Zoho Recruit Standard and Enterprise) is linked to the Interview record for evaluation capture. Interview notes and attachments migrate as Zoho Recruit Notes attached to the Interview.

Scorecard data may reside in TalentWall or the ATS depending on the customer's workflow — we audit both systems during the discovery phase to determine the authoritative source. If TalentWall holds scorecard data not present in the ATS, we extract it from TalentWall and map the evaluation ratings to Zoho Recruit's Interview Feedback Form fields. If the ATS is the source of truth, we pull from there. This dual-audit step prevents silent data loss on evaluations. Any scorecard submitted in TalentWall but not reproducible from the ATS is flagged in the mapping document for manual re-entry if the Zoho Recruit feedback form does not support the same structure.

Resumes and attachments live in the ATS as the system of record for candidate documents. We export them from the ATS file storage at migration time and deliver them as a structured file package alongside the record data. Files are linked to the corresponding Zoho Recruit Candidate record via the Document Library, preserving the original filename and file type. We do not rely on TalentWall for document storage since TalentWall does not hold canonical copies.

TalentWall may carry recruiter-applied tags and labels on candidate cards that are not mirrored back to the ATS. We extract any TalentWall-native tags and assess their cardinality and use case during discovery. Low-cardinality categorical tags (e.g., sourcing channel, tier rating) map to a Zoho Recruit custom multi-select picklist field. High-cardinality or freely-entered tags map to Zoho Recruit Tags on the Candidate record. The customer chooses the tag strategy during scoping, and we document the mapping decision in the migration mapping sheet.

TalentWall surfaces a candidate's current pipeline position as their card location on the Wall. We reconstruct this by mapping the candidate's ATS stage assignment to the corresponding Zoho Recruit Job Opening stage. If the customer uses TalentWall's custom stage orderings or per-job stage customizations not reflected in the ATS, we document these as Zoho Recruit stage customizations to be configured by the admin post-migration.