Migrate from Oracle Talent Management Cloud (formerly Taleo) to Bullhorn ATS & CRM

Taleo Requisitions map to Bullhorn Job Orders via TCC CSV or XML export. We map req_title to JobOrder.title, req_department to JobOrder.department (custom field if Bullhorn standard department is not available), req_location to JobOrder.address, req_hiringManager to JobOrder.owner (User lookup), and req_status to JobOrder.status. Approval chain configuration encoded in Taleo Requisition Templates is not mechanically migratable; we document each template's routing logic as a written handoff for the customer's Bullhorn admin to rebuild in Bullhorn placement workflow settings.

Taleo Candidate records map to Bullhorn Candidate directly. We normalize name fields (firstName, lastName), email address for dedupe, phone and alternate phone, and address components. Taleo user custom fields on Candidate migrate as Bullhorn custom fields (customText1, customDate1, etc.) of matching data type. Binary resumes are exported as a separate file package via Oracle Integration adapter and re-associated to Bullhorn Candidate records using exported candidate identifier keys after the Candidate insert phase completes.

Taleo Submission records—the join table between Candidate and Requisition carrying status, submission date, scorecard data, and interview notes—map to Bullhorn Candidate records with a placement or submission status flag. We preserve submissionDate as a custom date field on Bullhorn Candidate, submission status as a custom picklist (submitted, screening, interview, offer, hired, rejected), and interview notes as a Bullhorn Note attached to the Candidate record. The Candidate-to-JobOrder linkage is resolved at migration time by cross-referencing Taleo req_id against the migrated Job Order ID.

Taleo Position data originates from an external HRMS and cannot be created within Taleo. Positions do not map as standalone Bullhorn records; instead, we extract position-level data (headcount, job level, job family, qualifications) from Taleo as a separate export and attach it as Bullhorn custom fields on the corresponding Job Order. The Position-to-Job relationship must be manually re-established in Bullhorn against the customer's new HRMS or workforce planning system, as the original external HRMS reference no longer applies post-migration.

Taleo Offer records carry compensation components and approval history. We extract offer data in structured format and write it to Bullhorn Candidate custom fields (customText for compensation details, customDate for offer date, customPicklist for offer status). E-signature bindings on offer letter templates are Taleo-specific and do not transfer; we document the offer letter field mapping and recommend Bullhorn's DocuSign integration or Bullhorn Einstein 1 for Staffing as the replacement configuration path.

Taleo Requisition Templates encode approval chains and field defaults per requisition type. We export the template structure (approval routing levels, required fields, default values, OLF organization scope) and deliver it as a written template inventory document. Bullhorn placement workflows, user permissions, and Job Order settings replace the functional role of templates, but the mapping is configuration-based rather than mechanical. Customer's Bullhorn admin rebuilds approval logic using Bullhorn's user permission model and workflow settings.

Taleo Career Sites export as zipped configuration archives containing CSS, templates, field mappings, and job board posting configurations. We unpack the archive and document the site structure, branded CSS, and field configurations. Bullhorn Career Portal is built from within the Bullhorn UI; Taleo CSS assets that reference Taleo-specific tokens require manual rewrite. We deliver a written career site inventory with a field-to-field mapping table and a note that branded template assets require Bullhorn admin review before activation.

Recruiter and hiring manager assignments stored as user references within Taleo Requisition and Submission records are resolved by email match against Bullhorn User records. We extract every distinct Taleo user referenced on Requisition, Candidate, and Submission, match by email against Bullhorn Users, and flag any Taleo user without a matching Bullhorn User in a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes.

Taleo custom fields on Candidates, Requisitions, and Submissions are exported via Taleo Learn Cloud REST API or TCC. We preserve field labels, data types, and picklist values, then map them to Bullhorn custom fields on the equivalent Bullhorn object. Custom field naming follows Bullhorn's customText, customLongText, customDate, customNumber, and customPicklist conventions. Multi-select picklists from Taleo map to Bullhorn multi-select custom fields.

TCC CSV exports cannot carry binary attachments directly. We export attachments as a separate file package via Oracle Integration adapter, generating a manifest that maps each file to its parent Taleo record (Candidate or Submission) using the exported identifier key. After Bullhorn Candidate records are inserted and validated, we re-associate the attachment files using the Bullhorn Candidate ID resolved from the manifest. Resume files attach to the Candidate record; supporting documents (offer letters, compliance files) attach as Bullhorn Note attachments to the relevant record.

Taleo Performance Review records export via HDL or REST API carrying ratings, goals, and review cycle metadata. Bullhorn is a recruiting and staffing ATS, not a performance management platform. We map review data to Bullhorn Candidate custom fields or as Note records attached to the Candidate, preserving rating values, goal text, and review date. Full performance management lifecycle data (goal structures, competency frameworks) is out of scope for Bullhorn and is documented as a separate system requirement if needed.

Taleo Learn Cloud stores course enrollment and completion data. We export learner progress and certification records and map them to Bullhorn Candidate custom fields or Note records. Bullhorn does not have a native learning management module. Certification and training data migrates as candidate credentialing information rather than a structured LMS equivalent.