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

Taleo Requisitions are the primary anchor object in this migration. We export Requisition records via TCC as structured XML/CSV, preserving fields including requisition title, department, location, hiring manager (as user reference), requisition status, and opening date. We map these to Recruit CRM Job records, setting the status field based on Taleo's reqstatus value. Hiring manager references resolve by email match against Recruit CRM User records during the User provisioning phase. Requisition data migrates first to establish the job_id keys that Submissions depend on.

Taleo Candidate records export cleanly via TCC with standard fields (name, email, phone, address, profile). We handle name normalization across regional variants, email deduplication (flagging duplicate email addresses with a candidate_merge_candidates__c flag for admin review), and phone formatting. We preserve the Taleo candidate_id in a custom field taleo_candidate_id__c for audit trail. Candidate records migrate second, after Requisitions but before Submissions.

Taleo Submissions are the join table between Candidates and Requisitions, carrying application status, submission date, scorecard data, and interview notes. We map Submissions to Recruit CRM Applications, linking candidate_id and job_id foreign keys that were established during the previous two phases. Submission status history migrates as a custom status log field. Scorecard format and interview evaluation data map to Recruit CRM's interview scorecard section if configured; unstructured notes migrate to the Application notes field.

Taleo Positions are head-count planning entities imported from an external HRMS, not created directly within Taleo. Position records cannot be created or edited by Taleo administrators. We export Position data as a standalone object but flag that the Position-to-Job relationship must be manually re-established in Recruit CRM as a custom field (e.g., head_count_plan__c or position_code__c) because the external HRMS reference no longer applies after migration. This requires the customer's HR team to re-enter or re-map the planning reference manually.

Taleo Requisition UDFs (Submission UDFs in the 17A+ release notes) carry entity-type availability scoping that does not have a direct Recruit CRM equivalent. We export UDF field labels, data types, and picklist values via the Taleo Learn Cloud REST API or TCC, then create equivalent custom fields in Recruit CRM via the Jobs API before Requisition migration begins. Picklist values on Taleo UDFs migrate as Recruit CRM picklist options; multi-select UDFs migrate to multi-select fields. UDF availability scoping (Taleo Recruiting vs. Career Section vs. both) does not translate and is documented for manual configuration in Recruit CRM.

Candidate-level UDFs from Taleo export via TCC and map to Recruit CRM Candidate custom fields. We preserve field labels, data types, and picklist values. Date-type UDFs normalize from Taleo's ISO date format to Recruit CRM's expected date format during the transform step. Boolean UDFs map to Recruit CRM checkbox fields. Any UDFs referencing Taleo-specific codes (legal entity codes, OLF structure identifiers) require manual value mapping or are flagged as requiring Recruit CRM admin to configure a picklist replacement.

Taleo Offer records include compensation components and approval history. We export Offer data in structured format, mapping compensation fields to Recruit CRM Offer compensation components. Approval history migrates as a custom approval_log__c text field, not as live approval records, since Recruit CRM's offer approval workflow is configured separately. Offer letter templates and e-signature bindings are system-specific and do not migrate; we deliver a written inventory of active offer templates for the customer's admin to recreate in Recruit CRM's offer builder.

Recruiter and hiring manager assignments stored as user references within Taleo Requisition and Submission records map to Recruit CRM Team Members. We extract Taleo user IDs, match by email against Recruit CRM User records during the User provisioning phase, and assign the appropriate role (Recruiter, Hiring Manager, Interviewer, Sourcer) per the Taleo assignment. Any Taleo user without a matching Recruit CRM User enters a reconciliation queue for admin provisioning before the Team Member phase runs.

TCC CSV exports cannot carry binary files directly. We export attachments as a separate file package using Oracle Integration, producing a mapping file that pairs each Taleo attachment with its source candidate_id or submission_id. During the Recruit CRM import, we re-upload each binary file to the corresponding Candidate record or Application record using the Recruit CRM file upload API. This requires a two-pass approach: structural data first, attachments second, with identifier key reconciliation between passes.

Taleo Requisition Templates encode approval chains and field defaults per requisition type. We export template structure (field defaults, approval routing rules, required fields) as a written configuration document. Recruit CRM does not have a native requisition template object; field defaults and stage structures are configured per Job Pipeline in Recruit CRM. We deliver a mapping from each Taleo template to a Recruit CRM Pipeline configuration and the customer's admin applies the stage defaults manually.

Performance review records export from Taleo via HDL or REST API, carrying ratings, goals, and review cycle metadata. Recruit CRM is a recruiting-focused ATS and does not have a performance management module. We do not migrate performance data as records. We export a written inventory of active review cycles, goal structures, and rating scales for the customer's HR team to evaluate alternatives (Workday, SAP SuccessFactors, or standalone performance tools) and manually re-enter current-cycle goals if needed.

Taleo Learn Cloud stores course enrollment and completion data. Recruit CRM does not support a learning or training records module. We do not migrate learning data. Completion status and curriculum completion rules do not have a destination equivalent in Recruit CRM. We export a written summary of active course enrollments and completion rates for the customer's L&D team to evaluate standalone learning platforms (Cornerstone, SAP SuccessFactors Learning, or Oracle Learning Cloud) if training tracking is required post-migration.