Migrate from Oracle Talent Management Cloud (formerly Taleo) to BambooHR

Taleo Requisitions map to BambooHR Jobs with most structured fields translating directly: job title, department, location, employment status, and description. We map Requisition status (Open, On Hold, Filled, Cancelled) to BambooHR Job status. Note that BambooHR Jobs do not have a formal requisition number field; the Taleo requisition ID migrates as a custom field requisition_id__c for audit traceability. Approval routing configured on Taleo Requisition Templates does not migrate because BambooHR Workflows operate on a different model; we document the approval chain structure in a separate inventory for the customer's admin to rebuild.

Taleo Candidate records map to BambooHR Job Applications with contact information (name, email, phone, address) translated to BambooHR's applicant fields. We normalize regional phone formats, deduplicate by email across multiple applications, and preserve the Taleo candidate_id as a custom field candidate_id__c on the BambooHR application. Historical candidate records (rehires, previous applicants) map as new applications with a note field referencing the prior Taleo candidate ID.

Taleo Submissions are the join table between Candidates and Requisitions carrying status, scorecard data, interview notes, and submission-specific custom fields. BambooHR does not have a separate Submission object; submission status maps to the Application status field (Applied, Interview, Offer, Hired, Rejected), and scorecard data and interview notes merge into the Application Notes section. We flatten the nested submission chain so that each candidate-requisition pairing produces one BambooHR Application with a consolidated notes history ordered by original submission timestamp.

Taleo Positions are head-count planning entities typically imported from an external HRMS and cannot be created or edited within Taleo. BambooHR does not have a Position or head-count planning module. We export Position data as a standalone reference file during migration but flag that the Position-to-Job relationship must be manually re-established in BambooHR by the customer's HR team using BambooHR's headcount planning approach if applicable.

Taleo Employee records (typically synchronized from Oracle HCM on-premises via middleware) map to BambooHR Employee records. Standard fields including name, employment status, department, job title, manager, start date, and location translate directly. Custom employee fields migrate to BambooHR Custom Fields with equivalent data types. We resolve manager relationships by matching manager employee IDs to BambooHR Employee records during import.

Taleo custom fields on Candidates, Requisitions, Submissions, and Employees are exported via TCC or the Taleo Learn Cloud REST API. We preserve field labels, data types, and picklist values during extraction and map them to BambooHR Custom Fields on the equivalent records (Employee custom fields on Employee, applicant custom fields on Job Application). Picklist values migrate as-is; conditional logic on Taleo custom fields is documented for manual rebuild in BambooHR Workflows.

TCC CSV exports do not carry binary attachments. We export candidate resumes and supporting documents as a separate file package via Oracle Integration or manually downloaded archives, using the Taleo-generated filename and candidate ID as the linking key. We re-associate each file to the corresponding BambooHR Job Application using the candidate email as the dedupe anchor. Resumes migrate as applicant attachments; offer letters and signed documents migrate as Employee Files on the newly created employee record. Files without a resolvable match go to a reconciliation queue for the customer admin to resolve.

Taleo Requisition Templates encode approval chains and field defaults per requisition type. BambooHR does not have a requisition template object. We export template structure (default field values, required fields, approval routing configuration) as a written configuration inventory. The customer's BambooHR admin recreates default job posting templates by configuring Job Templates and Workflows in BambooHR directly.

Taleo Career Sites export as zipped configuration files containing field mappings, template assets, and look-and-feel settings. BambooHR includes a built-in BambooHR Career Site that is configured within the BambooHR platform itself, not imported from external files. We extract job board posting field configurations and re-create them as BambooHR Job field configurations manually. Branded CSS and Taleo-specific template tokens require manual review before they function correctly in BambooHR's career site builder.

Taleo performance review records include ratings, goals, and review cycle metadata. BambooHR's Performance Management add-on covers review cycles, 360 feedback, goal tracking, and 1:1 management but does not ingest historical Taleo performance data as native records. We export Taleo review history as a structured reference file and a PDF summary package per employee, which the customer stores in BambooHR Employee Files. Individual goal records can be re-created as BambooHR Goals manually.

Taleo Learn Cloud stores course enrollment, completion data, and certification records. BambooHR has no native learning management module. Compliance training is available through BambooHR's Compliance add-on (15 courses on Core+, 300+ courses on Elite) and third-party integrations. We export Taleo learning history as a structured reference file per employee for the customer to manage outside BambooHR or through a dedicated LMS integration.

Recruiter and hiring manager assignments stored as user references within Taleo Requisitions and Submissions map to BambooHR by resolving the Taleo user email against BambooHR User accounts. We assign the primary recruiter to the Job Application record and the hiring manager to a manager_notes__c field or to the manager assignment on the resulting Employee record. Taleo's formal Hiring Team construct with role-specific permissions does not exist in BambooHR; the assignment model is flattened to a single recruiter assignment per job.