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

Taleo Requisitions map directly to Crelate Jobs via TCC CSV export. We extract fields including requisition title, department, location, hiring manager, status, open and close dates, and job description. The Taleo requisition identifier is preserved in a custom field for reconciliation and as a cross-reference key. Active and on-hold statuses map to Crelate Job status values; cancelled requisitions are migrated as closed jobs for historical completeness. Approval chain status (pending, approved, rejected) does not migrate as a workflow state — we record the final approval outcome as a note on the Job record.

Taleo Candidate records export cleanly via TCC with standard fields (name, email, phone, address, application date, source). We normalize name components (first, middle, last), standardize phone formats across regional variants, apply email deduplication across the candidate pool, and map the candidate source value (employee referral, job board, agency) to Crelate's Candidate Source field. Resume binary files migrate separately via Oracle Integration and are re-associated to the Candidate record using the Taleo candidate identifier key exported alongside the record.

Taleo Submissions are the join table between Candidate and Requisition, carrying pipeline stage, status history, submission date, and scorecard data. In Crelate, a Candidate can be associated to a Job through multiple application records, but each association carries its own status and activity log. We create one Crelate association per Taleo Submission, preserving the submission date, current status, and a structured history of stage transitions as activity log entries. Scorecard data migrates as formatted notes attached to the association rather than as a structured Crelate scorecard object.

Taleo Positions originate from an external HRMS and cannot be created or edited within Taleo. Positions are exported as a standalone object but do not map to a native Crelate object because Crelate's Jobs are created directly by recruiters rather than imported from headcount planning. We flag the Position-to-Job relationship as requiring manual re-establishment in Crelate: the Position's organizational unit, job family, and headcount justification map to Crelate Job custom fields for your admin to configure against the original HRMS data. We deliver a Position mapping sheet as part of the handoff documentation.

Taleo Offers with compensation components, approval history, and status (pending, accepted, declined, retracted) map to Crelate Placements. Offer amount, currency, start date, and offer status migrate to the corresponding Crelate Placement fields. E-signature binding and offer letter template formatting are Taleo-specific and do not transfer — the offer letter document itself migrates as an attachment to the Placement record, and your team rebuilds the letter template in Crelate's offer tool. Approval history migrates as a structured note on the Placement.

Recruiter, sourcer, and hiring manager assignments stored as user references within Taleo Requisition and Submission records map to Crelate User records by email match. We resolve Taleo user identifiers to Crelate User IDs at migration time. Any Taleo user without a matching Crelate User account is held in a reconciliation queue for your admin to provision before the Job migration phase begins. If the recruiter or hiring manager is inactive in Crelate but was active in Taleo, we flag it for your admin to activate or reassign.

Taleo Requisition Templates encode approval chains, field defaults, and required fields per requisition type (full-time, contract, executive, campus). Template structure is exported as a data artifact, but approval workflow logic does not mechanically migrate to Crelate because Crelate uses a different workflow rule model. We deliver a written template inventory listing every Taleo Requisition Template with its field defaults, approval chain configuration, and a recommended Crelate Job Template configuration for your admin to rebuild under Settings > Jobs > Templates.

Custom fields on Taleo Candidates, Requisitions, and Submissions are exported via the Taleo Learn Cloud REST API or TCC. We preserve field labels, data types, and picklist values as a configuration inventory. Crelate supports custom fields on Jobs, Candidates, and Placements. We create the Crelate custom field schema (field name, type, picklist values) as a pre-migration step under Settings > Fields before any record data is loaded, so that incoming Taleo data populates the correct fields during import rather than landing in generic notes.

TCC CSV exports cannot carry binary files. We export all attachments (resumes, offer letters, supporting documents, background check results) as a separate file package using Oracle Integration, organizing files by the Taleo record identifier (candidate ID, submission ID, offer ID). After the Candidate and Submission records land in Crelate, we re-associate each binary file to the correct Crelate record by cross-referencing the Taleo identifier stored in the Crelate custom field created during the initial migration phase. Resume files map to the Candidate record; offer letter documents map to the Placement record.

Taleo Career Sites export as zip files containing configuration assets, field mappings, and template tokens rather than structured records. We unpack these archives, parse the field configuration and look-and-feel settings, and produce a Crelate Career Portal configuration guide. Branded CSS, logo assets, and template tokens that reference Taleo-specific identifiers require manual review and re-import. Crelate's career portal settings are rebuilt under Settings > Career Site by your admin using the configuration guide we deliver.

Taleo Performance Review records (ratings, goals, review cycle metadata, manager comments) export via HDL or REST API but Crelate does not store performance management data as a native or custom object. We export the performance review data as a structured CSV and PDF archive for your records, flagging that this data is outside Crelate's scope as a recruiting-focused ATS. If performance data must be accessible post-migration, we recommend a separate HRIS or performance management system and can provide a data export in a format compatible with common import tools.

Taleo Learn Cloud stores course enrollment, completion records, certifications, and curriculum progress. Crelate is a recruiting ATS and does not have a learning management module. We export Taleo Learn records as a structured CSV archive, including learner name, course title, completion date, and certification status. Goal structures, curriculum completion rules, and compliance training flags do not map to Crelate's schema and are flagged as requiring manual re-entry in your LMS or HRIS of record.

Taleo Submission scorecards contain structured evaluation criteria, rating values, and evaluator comments for each interview round. Crelate does not have a native scorecard object, so we merge scorecard records into activity notes attached to the Candidate-to-Job association. Each scorecard maps to a formatted note entry with the evaluator name, evaluation date, criteria label, and rating value. We preserve the full evaluation history as a chronological note log so that hiring managers can review the interview evaluation trail in Crelate without needing to reference the Taleo archive.

Taleo Candidate notes export via TCC as structured text with timestamps and author attribution. We map these to Crelate Activity Log entries and Notes on the Candidate record, preserving the original author name, creation date, and full note body. Notes are imported in chronological order so that the candidate's activity timeline in Crelate reflects the historical progression from the Taleo record.