Migrate from Talent finder to BambooHR

Talent Finder Job records (title, department, location, description, status) map to BambooHR Job Opening records via the BambooHR ATS API endpoint. The job department maps to BambooHR's Department field; location maps to BambooHR Location. Active and closed status is preserved. We flag any Talent Finder job with a department value that does not have a matching BambooHR department during scoping so the customer's admin can create it before import.

Talent Finder Candidates map to BambooHR in two phases. Active candidates with no hire date map to BambooHR Applicant records linked to the corresponding Job Opening. Candidates with a hire date or an offer status in Talent Finder map to BambooHR Employee records with the hire date carried over. We preserve the original Talent Finder candidate ID in a custom BambooHR field candidate_source_id__c for audit and deduplication. Email serves as the dedupe key; duplicate candidates within BambooHR are flagged before insert.

Talent Finder Application records link a Candidate to a Job and track stage progression. We map each Talent Finder pipeline stage to a BambooHR applicant status value (Applied, Phone Screen, Interview, Offer, Hired, Rejected). The stage history timestamps migrate as application notes on the BambooHR Applicant record. We flag any stage with no direct BambooHR equivalent for the customer to configure as a custom status during scoping.

Talent Finder uses configurable pipeline stages per job or across the organization. BambooHR ATS uses a fixed applicant status flow. We design a mapping table during scoping that assigns each Talent Finder stage name to the closest BambooHR status, and we flag stages with no equivalent (such as technical assessments, take-home projects, or panel rounds) as note fields that the customer can configure as custom BambooHR applicant statuses post-migration.

Talent Finder Users with recruiter, hiring manager, or admin roles map to BambooHR Employee records with the corresponding access level set in BambooHR. We resolve users by email match. Any Talent Finder User without a matching BambooHR employee record is held in a reconciliation queue for the customer's admin to provision before application migration begins, because BambooHR requires an Employee record to exist before assigning an ATS role.

Talent Finder Interview Scorecards store structured evaluations with ratings tied to a candidate and interviewer. BambooHR does not have a native scorecard object, so we migrate scorecard data as structured Note records with a header line identifying the interview type, interviewer, and date, followed by the rating fields and free-text feedback. The notes are linked to the corresponding BambooHR Applicant record via the Employee Note API.

Talent Finder resume files and uploaded documents extract from the CSV export as file references or base64-encoded content. We extract, rename following candidate-referenced naming conventions, and load to BambooHR as Employee Files via the BambooHR Employee Files API. Attachments associated with Applications (cover letters, work samples) load against the corresponding BambooHR Applicant record. File type and original upload date are preserved in the file metadata.

Talent Finder outreach emails, notes, and event timestamps migrate as Note records against the BambooHR Applicant. We strip HTML from email bodies to ensure clean display in BambooHR's note format. Meeting and event timestamps migrate as Note records with event type, date, and location preserved. BambooHR's native activity history is limited to time-off requests and document events, so the Talent Finder engagement timeline is reconstructed as a chronological Note feed on each Applicant record.

Talent Finder custom properties on Candidates require explicit field mapping. We extract the custom field schema from the CSV export, display it for review during scoping, and configure equivalent custom fields in BambooHR before migration. Multi-select, date, number, and text field types map to corresponding BambooHR custom field types. Any custom field with a value set that does not match a BambooHR picklist is flagged for manual review or pre-migration configuration.

Talent Finder custom fields attached to Applications migrate to BambooHR Applicant custom fields. BambooHR ATS supports custom fields on applicants, but the field configuration must be created per job opening in the BambooHR admin UI. We extract all application-level custom field schemas from Talent Finder, consolidate them into a deduplicated list, and configure the BambooHR applicant custom fields during setup so they are available for import across all job openings.