Migrate from Talent Clue to BambooHR

Talent Clue job postings (title, description, department, location, publishing status) map to BambooHR Position records. The Job's published or archived status becomes the Position's open or closed status. We export all active and archived vacancies and map the Talent Clue job ID as a custom reference field for reconciliation. BambooHR's Position object does not support multi-step pipeline stages natively; if the customer used complex vacancy-specific stages, those labels are preserved in a custom text field on the Position record.

Talent Clue candidate profiles (contact details, source channel, stage, and scorecard data) map to BambooHR Employee records. The BambooHR Employee object is the primary record type in the HRIS; candidate contact information maps to the standard employee fields (firstName, lastName, workEmail, mobilePhone, address fields). Any Talent Clue custom fields on the candidate record are created as BambooHR custom employee fields before migration. Custom field definitions must be confirmed during discovery because the Talent Clue export does not expose the schema.

Talent Clue application records link a candidate to a specific job and record submission date and pipeline stage. In BambooHR, applicants are tracked within the hiring module linked to a Position. We map each Talent Clue application to a BambooHR Applicant record, preserving the candidate-to-position association and submission timestamp. If the candidate has been hired, the application status becomes the hire date anchor for the Employee record.

Talent Clue's talent pool is a persistent candidate database independent of any specific vacancy. We export all pool records and determine the best destination during scoping: pool members who have never applied map as BambooHR Employee records with a custom talent_pool_source flag set to true; pool members who already have application records are linked to their existing Employee record and do not create duplicates. The customer chooses whether pool membership is stored as a BambooHR custom multi-select field or as a tag.

Talent Clue evaluation forms capture interviewer ratings and free-text feedback against candidates. BambooHR does not have a native evaluation object, so structured scorecard ratings migrate as BambooHR custom fields on the Applicant record (for pre-hire evaluations) or Employee record (for post-hire performance data). Free-text evaluation notes migrate as Note records attached to the Applicant or Employee. We preserve the interviewer name and evaluation date as separate custom fields for audit trail.

Talent Clue interview records include scheduled time, interviewer name, and outcome flags. BambooHR's hiring module tracks interview status at the applicant level but does not store detailed interview schedules as discrete objects. We migrate interview scheduling data as Note records on the Applicant, with the interview date, interviewer name, and outcome stored in custom note fields. The customer may supplement this with BambooHR's built-in hiring stage notes.

Talent Clue's configurable pipeline stages per vacancy or globally map to BambooHR's hiring stage model. We extract the stage labels and sequence from the Talent Clue configuration (confirmed by the customer during discovery) and create corresponding hiring stages in BambooHR. Custom stage names that do not match BambooHR's default stage labels are created as custom stage values. If stages differ per vacancy in Talent Clue, we map the most-used global stage set and note per-vacancy deviations in the validation report.

Talent Clue recruiter accounts own vacancies and candidates. We map Talent Clue users to BambooHR users by email address. Role and permission structures differ significantly between an ATS and an HRIS; the customer's BambooHR admin assigns appropriate roles post-migration. If a Talent Clue user has left the company, their email address is flagged for the admin to either skip or provision as an inactive BambooHR user with historical ownership preserved.

Candidate-level notes from Talent Clue migrate as BambooHR Note records attached to the corresponding Employee or Applicant. The note body and creation timestamp preserve. If the note references a specific vacancy or stage, that context is embedded in the note text during migration. We do not attempt to reconstruct note threads or conversation histories as separate records.

File attachments on candidate records (CVs, cover letters, portfolio documents) are downloaded from Talent Clue and uploaded to the corresponding BambooHR Employee record as file attachments. Large attachment volumes may require chunking by candidate and manual verification. We preserve the original file name and MIME type. Files exceeding BambooHR's attachment size limits are flagged in the validation report for the admin to store externally.

Talent Clue custom fields on candidate and application objects require pre-migration schema work. We request the complete custom field definition list during the discovery call, create equivalent custom fields in BambooHR (with matching field types where possible), and then map values during migration. Fields with picklist values are created as BambooHR dropdown custom fields. Fields with no direct BambooHR equivalent are stored as text fields with a naming convention that preserves the original field label for reference. All unmapped custom fields appear in the validation report.