Migrate from Oracle Talent Management Cloud (formerly Taleo) to Zoho Recruit

Taleo Job Requisitions export via TCC in structured CSV or XML with fields for requisition ID, title, department, location, hiring manager, status, description, and creation date. We map these directly to Zoho Recruit Job records, using Taleo's requisition ID as the external ID for deduplication. Requisition status values (Open, On Hold, Filled, Cancelled) map to Zoho's Job Status picklist. We flag Requisition Templates (approval chains and field defaults per type) as non-migratable automation and document them in a separate handoff artifact for the customer's admin to rebuild in Zoho Recruit's Workflow Rules and Blueprints.

Taleo Candidate records export cleanly via TCC with standard fields: name, email, phone, address, social profiles, source channel, and creation timestamp. We handle name normalization (handling suffixes, prefixes, and dual-first-name formats common in global candidate pools), email deduplication (using external ID to flag duplicates rather than reject), and phone formatting for regional variants. Binary resumes are exported separately and re-associated to the Zoho Candidate record using the Taleo candidate ID as the Zoho external ID.

Submissions are the join table between Candidates and Requisitions in Taleo, carrying submission status, scorecard data, interview notes, and submission date. We export Submissions after both Requisitions and Candidates are loaded, using Taleo requisition ID and candidate ID as foreign keys resolved against the imported Zoho Job and Candidate external IDs. Submission status history migrates as a Zoho note attached to the submission record. Scorecard format differences mean we preserve raw scorecard data as a custom text field rather than attempting format translation.

Taleo Positions are head-count planning entities typically imported from an external HRMS, not created directly within Taleo. We export Position data as a standalone object with its associated job requisition reference. The Position-to-Job relationship cannot be mechanically re-established in Zoho Recruit because Zoho does not have a native Position object; we document the original HRMS Position ID alongside the mapped Job record for manual review by the customer's admin, who re-establishes the relationship in their HRIS of record post-migration.

Taleo UDFs on Candidates, Requisitions, and Submissions export via the Taleo Learn Cloud REST API or TCC, preserving field labels, data types, and picklist values. We map them to Zoho Recruit's corresponding custom field structures (text, number, date, picklist, multi-select, and lookup types). Taleo Submission UDF availability rules (which Oracle describes as configurable per Recruiting and Career Section) do not have a direct Zoho equivalent; we set all imported UDFs as active and document the availability matrix for the admin to configure post-load. Large picklist valuesets may require Zoho custom field re-creation by the admin.

Taleo Offer records include compensation components and approval history. We extract Offer records in structured CSV format and migrate them as Zoho Note attachments to the corresponding Candidate or Job record. Offer letter templates and e-signature bindings are Taleo-specific and do not migrate; we deliver the structured Offer data (salary, bonus, equity, start date, approval chain) as a custom field set on the Zoho Candidate or Job record and document the original e-signature status for the admin to re-establish in Zoho's document workflow.

Recruiter and hiring manager assignments in Taleo are stored as user references within Requisition and Submission records. We map Taleo user IDs to Zoho Recruit users by email match. Any Taleo user without a matching Zoho Recruit user account goes to a reconciliation queue; the customer's admin provisions the missing Zoho users before record import resumes. Hiring manager assignments attach to the Zoho Job record as a custom field or note since Zoho Recruit's native hiring team model uses role assignments within the Jobs module.

TCC CSV exports cannot carry binary files directly. We export attachments as a separate file package using Oracle Integration or a file-level extraction pass, preserving the original Taleo candidate ID as filename metadata. We then re-associate the files to the correct Zoho Candidate record using the external ID mapping (Taleo candidate ID -> Zoho Candidate external ID). Resume parsing in Zoho Recruit (which uses its own parsing engine) is triggered after attachment import so that structured resume fields are available immediately post-migration.

Taleo Career Sites export as zipped configuration files containing template assets, CSS, and field mappings rather than structured records. We unpack these archives, parse the field mapping and look-and-feel settings, and document them as a configuration specification for Zoho's Career Page builder. Branded CSS and Taleo-specific tokens do not carry forward; the customer's admin uses the documented field mappings to reconfigure Zoho's career pages. This is a manual rebuild step, not an automated migration.

Taleo Requisition Templates encode approval chains and field defaults per requisition type. We export template structure (field defaults, required fields, routing rules) as a written specification. Approval workflow logic is destination-system-specific and cannot be mechanically migrated. We deliver a Zoho Recruit Blueprint or Workflow Rule specification document for each Taleo Template, listing the trigger conditions, approval sequence, and field actions, which the customer's admin configures in Zoho Recruit's native automation builder post-migration.

Taleo performance management records (goals, ratings, review cycles) do not map to Zoho Recruit, which is an ATS without a native performance module. We export performance data as a structured CSV for the customer's HRIS of record. If the customer uses Zoho People alongside Zoho Recruit, we note that performance records could be imported as custom Zoho People records; otherwise they are out of scope for the ATS migration and should be handled in a separate HRIS engagement.

Taleo Learn Cloud stores course enrollment and completion data. Zoho Recruit has no learning management module. We export learner progress and certification records as a structured CSV for the customer's LMS of record. If the customer migrates to Zoho People, learning records could be imported as custom modules; otherwise they are out of scope for the ATS migration.