Migrate your TalentWall data
Visual ATS overlay that converts candidate pipelines into interactive card walls for recruiting teams who want kanban-style visibility on top of Greenhouse, Lever, or Jobvite.
In its favor
Why people choose TalentWall
The signal that keeps TalentWall on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Real-time interactive card-wall view layered on top of Greenhouse, Lever or Jobvite gives recruiters a kanban-style pipeline view their underlying ATS does not provide natively.
Customised analytics dashboard surfaces time-to-hire, offer-acceptance rate, pipeline health and interview statistics in one place — operational reporting most ATSs only offer at higher tiers.
Sits on top of the customer's existing ATS rather than replacing it, so adoption risk is low — no data migration required at install, only API connectivity to the ATS.
Job-health Red/Yellow/Green annotations and candidate-freshness scores add a layer of pipeline hygiene visibility that drives recruiter prioritisation.
Custom widgets and job/offer-level custom fields let recruiting ops teams enrich pipeline data without changing fields in the upstream ATS.
Public pricing is not surfaced — quote-only model complicates budget evaluation.
Coverage is limited to a handful of supported ATSs (Greenhouse, Lever, Jobvite primarily) — teams on other ATSs can't use TalentWall at all.
All ATS-side data lives in the upstream system — when TalentWall is removed, custom widgets, job-health rankings and freshness scores are lost unless explicitly exported.
AS a thin visualisation layer, TalentWall doesn't replace any core ATS functionality, so customers paying for both eventually evaluate whether their ATS's native dashboards have caught up.
Brand confusion with similarly named recruiting/HR tools; ensure the customer is on TalentWall.io specifically before scoping.
Reasons to switch
Why people leave TalentWall
The recurring reasons buyers give for replacing TalentWall. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where TalentWall fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
TalentWall pricing overview
TalentWall publishes pricing by per-user model with rates available by contacting the vendor directly; no public pricing tiers are listed. The platform is positioned for small businesses through enterprise organizations based on Capterra deployment information.
TalentWall (sales-led)
Tier 1 of 1
Custom (sales-led — not publicly listed)
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on TalentWall's schedule — see our quote-based pricing →
What gets migrated
TalentWall object support
Object-by-object support for TalentWall migrations. Per-pair details surface during scoping.
Jobs
Fully supportedJobs are synced from the connected ATS (Greenhouse, Lever, Jobvite, etc.) via TalentWall's integration layer. We extract the job object directly from the upstream ATS API, preserving title, department, hiring manager, and open date.
Candidates
Fully supportedCandidates are pulled from the ATS and surfaced on the Wall as interactive cards. We export from the upstream ATS, which is the system of record, ensuring all application data and status history is preserved.
Pipeline Stages
Fully supportedStage names and order are defined per job in the ATS. TalentWall reflects them visually as columns on the Wall. We pull stage definitions from the ATS job configuration and map them to the destination ATS or ATS-agnostic schema.
Custom Fields (Job-level)
Mapping requiredTalentWall allows custom fields scoped to individual jobs or offers. These are TalentWall-native and not stored in the ATS. We extract them via the TalentWall interface or direct storage access and map them to equivalent custom fields in the destination system.
Custom Fields (Offer-level)
Mapping requiredOffer-level custom fields are similarly TalentWall-specific. We extract these as key-value pairs and map them to offer custom fields or candidate custom properties in the destination ATS.
Custom Widgets
Mapping requiredTalentWall's custom widget library maps widgets to specific job-level or offer-level custom fields. Widgets reference the custom field by name or ID. We extract the widget-to-field mapping and recreate the equivalent widget or custom field configuration at the destination.
Job Health Rankings
Mapping requiredJob health (Red/Yellow/Green status) and associated notes are TalentWall-native annotations stored in TalentWall's own database. These are not in the ATS. We extract them and write them as custom fields or status annotations in the destination system.
Candidate Freshness Data
Mapping requiredCandidate freshness is a TalentWall-computed or -entered metric reflecting last activity and pipeline position. This data lives in TalentWall. We extract it as a candidate-level custom property and map it to an equivalent field at the destination.
Interviews
Fully supportedInterview scheduling data shown in TalentWall's calendar view originates from the ATS calendar integration. We pull interview records (scheduled time, interviewer, type) from the ATS to preserve them at migration.
Scorecards and Evaluations
Mapping requiredIf scorecards are entered directly into TalentWall rather than the ATS, they may not be accessible via the upstream ATS export. We attempt extraction from TalentWall's storage; if the ATS is the sole system of record for evaluations, we pull from there instead.
Attachments and Resumes
Fully supportedResumes and attachments live in the 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.
Tags and Labels
Mapping requiredTalentWall may carry tags or labels applied by recruiters on the Wall that are not mirrored back to the ATS. We extract any TalentWall-native tags and write them as candidate tags or custom properties in the destination.
| Object | Support | Notes |
|---|---|---|
| Jobs | Fully supported | Jobs are synced from the connected ATS (Greenhouse, Lever, Jobvite, etc.) via TalentWall's integration layer. We extract the job object directly from the upstream ATS API, preserving title, department, hiring manager, and open date. |
| Candidates | Fully supported | Candidates are pulled from the ATS and surfaced on the Wall as interactive cards. We export from the upstream ATS, which is the system of record, ensuring all application data and status history is preserved. |
| Pipeline Stages | Fully supported | Stage names and order are defined per job in the ATS. TalentWall reflects them visually as columns on the Wall. We pull stage definitions from the ATS job configuration and map them to the destination ATS or ATS-agnostic schema. |
| Custom Fields (Job-level) | Mapping required | TalentWall allows custom fields scoped to individual jobs or offers. These are TalentWall-native and not stored in the ATS. We extract them via the TalentWall interface or direct storage access and map them to equivalent custom fields in the destination system. |
| Custom Fields (Offer-level) | Mapping required | Offer-level custom fields are similarly TalentWall-specific. We extract these as key-value pairs and map them to offer custom fields or candidate custom properties in the destination ATS. |
| Custom Widgets | Mapping required | TalentWall's custom widget library maps widgets to specific job-level or offer-level custom fields. Widgets reference the custom field by name or ID. We extract the widget-to-field mapping and recreate the equivalent widget or custom field configuration at the destination. |
| Job Health Rankings | Mapping required | Job health (Red/Yellow/Green status) and associated notes are TalentWall-native annotations stored in TalentWall's own database. These are not in the ATS. We extract them and write them as custom fields or status annotations in the destination system. |
| Candidate Freshness Data | Mapping required | Candidate freshness is a TalentWall-computed or -entered metric reflecting last activity and pipeline position. This data lives in TalentWall. We extract it as a candidate-level custom property and map it to an equivalent field at the destination. |
| Interviews | Fully supported | Interview scheduling data shown in TalentWall's calendar view originates from the ATS calendar integration. We pull interview records (scheduled time, interviewer, type) from the ATS to preserve them at migration. |
| Scorecards and Evaluations | Mapping required | If scorecards are entered directly into TalentWall rather than the ATS, they may not be accessible via the upstream ATS export. We attempt extraction from TalentWall's storage; if the ATS is the sole system of record for evaluations, we pull from there instead. |
| Attachments and Resumes | Fully supported | Resumes and attachments live in the 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. |
| Tags and Labels | Mapping required | TalentWall may carry tags or labels applied by recruiters on the Wall that are not mirrored back to the ATS. We extract any TalentWall-native tags and write them as candidate tags or custom properties in the destination. |
Gotchas
What to watch for in TalentWall migrations
Issues we've hit on past TalentWall migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
TalentWall-native annotations are not in the ATS
Scorecard data may reside in TalentWall or the ATS
Custom fields have job-level vs. offer-level scoping
No publicly documented API for programmatic migration
| Severity | Issue |
|---|---|
| High | TalentWall-native annotations are not in the ATS |
| Medium | Scorecard data may reside in TalentWall or the ATS |
| Medium | Custom fields have job-level vs. offer-level scoping |
| High | No publicly documented API for programmatic migration |
Leaving TalentWall?
Where TalentWall customers move next
5 destinations TalentWall can migrate to.
How a TalentWall migration works
Four steps, TalentWall-specific
Connect
Not publicly documented — TalentWall connects to upstream ATSs (Greenhouse, Lever, Jobvite) using vendor-specific API tokens provisioned by the customer's ATS admin into TalentWall. Scopes limited to read-only on the data we move.
Map
We translate TalentWall-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate TalentWall quirks before production.
Migrate
Full migration with TalentWall rate-limit handling. Rollback available throughout.
FAQ
TalentWall migration FAQ
Answers to the questions buyers ask most during TalentWall migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your TalentWall migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther HR systems we support
Ready when you are
Migrate TalentWall.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your TalentWall setup and destination — written quote back within a business day.