Migrate from Talent Pool Builder to BambooHR

Talent Pool Builder Candidate records map to BambooHR Applicant records. Name, contact info, application status, source attribution, and stage history migrate directly. Resume attachments migrate as documents linked to the Applicant. BambooHR attaches Applicants directly to Job Openings rather than maintaining a separate Application object, so we collapse the Talent Pool Builder Candidate-Application relationship into a single Applicant record per job.

Talent Pool Builder Job postings map to BambooHR Job Openings with title, department, location, and posting date preserved. BambooHR supports a limited number of active Job Openings by plan tier (5, 25, or 50), so we flag any migration scope that exceeds the customer's target BambooHR tier and recommend upgrading before cutover if necessary.

Talent Pool Builder Requisitions track hiring manager requests and approvals before a job opens. BambooHR does not have a first-class Requisition object separate from Job Opening, so we map requisition status and approver fields to custom fields on the destination Job Opening or to a separate internal tracking document for the customer's admin to configure post-migration.

Talent Pool Builder Talent Pools map to BambooHR Candidate Talent Pools, which were introduced in August 2021. Pool membership and tags migrate cleanly. BambooHR Talent Pools allow candidates to be moved in from previous applications or sourced separately, so we preserve pool names and segment criteria as Talent Pool metadata. Pool-specific custom fields require mapping to BambooHR custom fields on the Applicant record, which the customer's admin creates via the Custom Field Builder before migration.

Talent Pool Builder Application records (linking Candidates to Jobs with timestamps and stage transitions) collapse into BambooHR Applicant records attached to Job Openings. Stage history and transition timestamps migrate as activity entries on the Applicant record. BambooHR's Candidate Funnel report shows where candidates enter and move, which partially replaces Talent Pool Builder's stage pipeline view.

Interview scheduling data and structured scores from Talent Pool Builder map to Applicant activity entries in BambooHR. BambooHR supports interview scorecards linked to Applicants, but free-text interview notes may require truncation depending on field limits. We flag any interview data that exceeds BambooHR's field length constraints as manual-entry candidates for post-migration remediation.

Talent Pool Builder Offer records (template placeholders, status, digital signature state) map to BambooHR Offer Letter functionality. We export the offer data and preserve signature status as a custom field flag because BambooHR's e-signature integration may route through a different provider (DocuSign or HelloSign by default). Post-migration, the customer's admin configures offer letter templates in BambooHR that auto-populate candidate and role details.

Talent Pool Builder accounts frequently create custom fields for screening answers, rating scores, source tracking, and compliance data. We map these to BambooHR Custom Fields created via the Custom Field Builder before migration. BambooHR supports short answer, long answer, list (single answer), and list (multiple answer) types. Fields with incompatible types (e.g., Talent Pool Builder fields storing JSON or nested data) are logged as manual-entry candidates and flagged for the customer's admin to remediate post-migration.

Email, SMS, and call logs attached to Talent Pool Builder Candidate records migrate where the platform exposes them as discrete communication events. BambooHR stores communication history as Notes or Activity records on the Applicant. Thread continuity is not guaranteed — we export what is available, flag gaps in the validation report, and note that the customer should communicate this limitation to hiring managers who rely on inbox history for interview context.

Resume files and uploaded documents from Talent Pool Builder migrate as documents linked to the corresponding BambooHR Applicant. File naming conventions vary by account and are preserved as-is. BambooHR stores documents in its file repository linked to the Applicant record, making them accessible within the hiring workflow.

Talent Pool Builder's union compliance flags and seniority-based ranking are platform-specific features that do not map to standard BambooHR ATS objects. We export the raw seniority date and union membership fields as custom text or date fields so the data is preserved. Activation of equivalent compliance logic in BambooHR requires the customer's IT or legal team to configure a BambooHR Custom Field or an external compliance tool post-migration.