Taleo to ORC migration is schema translation, not a lift-and-shift. TCC's 500K/day limit and HDL's validation rules are the primary bottlenecks — plan for hybrid API + file-based extraction.
A CTO-level guide to migrating from Taleo to Oracle Recruiting Cloud, covering TCC export limits, HCM Data Loader constraints, object mapping, and real API trade-offs.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Oracle does not provide a native migration path from Taleo to ORC
Oracle Consulting explicitly tells customers not to think of Taleo-to-ORC as a lift-and-shift. Conversion of candidate data must be done by customers themselves or by a partner. (static.rainfocus.com)
Why flat Taleo exports mislead teams
In Oracle's own documentation, a candidate with two work experiences and three education elements produces six rows in XML/CSV-report mode because n-ary relations multiply rows. CSV-entity mode avoids row multiplication but serializes multivalue relations into single columns and does not support joining or grouping. (docs.oracle.com)
Migrate operating history; archive reporting history
Oracle's own HDL guidance says not to load historic job applications just for reporting, and Oracle Consulting's Taleo-to-ORC material explicitly lists "all data needs to move" as a misconception. Move what recruiters must work with in ORC. Archive the long tail elsewhere. (docs.oracle.com)
Keep two immutable source keys
one for the person and one for the candidacy. Use SourceSystemOwner and SourceSystemId wherever the business object supports them. This is what lets you rerun failed batches without duplicating records or breaking relationships. (docs.oracle.com)
If you load Job Applications before their parent Job Requisition exists in ORC, every
If you load Job Applications before their parent Job Requisition exists in ORC, every application record will fail validation and the entire batch will be rejected. HDL does not do partial loads of logical objects — it is all or nothing per record.
This is a structural outline, not production-ready code
Real implementations need retry logic with exponential backoff, TCC session management, HDL job status polling, comprehensive error logging per record, and source-key idempotency so reruns do not duplicate data.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Scope candidates, pipelines and the compliance obligations that come with them.
Objective Agreed scope across candidates, applications, jobs and interview history, with legal signed up on retention.
Keep these open
-
Inventory every object in Oracle Taleo
Count candidates, applications (a candidate can have many), jobs and requisitions, interviews, scorecards, offers, and resume files. Applications and scorecards usually outnumber candidates several times over, and resume files dominate storage.
Data Profiler Get real record counts instead of estimating from memory -
Settle retention and consent with legal
Candidate data is heavily regulated: GDPR right-to-erasure, EEOC/OFCCP record-keeping, and per-region retention windows that conflict with each other. Decide what may be migrated at all before you scope anything else — this frequently shrinks scope substantially.
Migrating candidate records whose consent has lapsed or whose retention window has expired creates a new compliance breach in the target system.
-
Map the hiring pipeline and agree the target stages
Document every job's pipeline, stage, and rejection reason, then agree the Oracle Recruiting Cloud model with talent leadership. Stage definitions drive every funnel metric you report, so changing them silently rewrites your hiring analytics.
-
Catalogue integrations and the job-board estate
List job boards, careers-site integration, HRIS, background check, assessment platforms, calendar and email. The careers site and job boards are customer-facing, so their cutover needs its own plan and its own testing.
-
Build the business case and choose the window
Model licence delta, effort and recruiter productivity dip. Time the window against your hiring cycle: a migration during peak graduate recruitment or a hiring surge will fail on people, not technology.
Vendor Evaluator Score Oracle Recruiting Cloud against alternatives on weighted criteria
Oracle Taleo → Oracle Recruiting Cloud specifics
- Commercial pressure
- Oracle's February 1, 2026 Taleo price list shows Taleo Enterprise and Taleo Midsize are no longer available to new customers. Multiple Oracle partners report that existing Taleo renewals are becoming increasingly difficult to secure, with Oracle steering customers toward ORC. (oracle.com)
- Component sunsetting
- Oracle already retired Taleo Performance (December 2020, due to Flash dependency) and the legacy Taleo Career Website (May 2024). The pattern is unmistakable.
- Integration tax
- Taleo requires dedicated integrations for foundational data — organizations, locations, job functions, requisition templates, position details, and new hires. ORC eliminates most of these because it natively shares HCM Core structures. Baker Tilly notes that "the number of integrations needed to maintain the system decreases dramatically" when moving to ORC. (bakertilly.com)
Don't move on until
- Counts confirmed for candidates, applications, jobs and offers
- Retention and consent obligations confirmed with legal
- Hiring-stage model agreed with talent leadership
02 Data Audit Audit candidate data with compliance sitting next to you.
Objective Profiled exports with duplicates, expired records and resume files all quantified and triaged.
Keep these open
-
Export and profile candidates, applications and jobs
Profile each object separately and reconcile against API counts. Watch the candidate-to-application ratio: a mismatch usually means applications have been silently truncated by pagination.
Data Profiler Profile the Oracle Taleo export for nulls, outliers and type drift -
Quantify duplicate candidates and agree survivorship
The same person applies repeatedly over years with different emails and name spellings. Measure the duplicate rate and agree survivorship rules — which record wins and what happens to the application history attached to the losers.
Merging candidates without agreed survivorship rules destroys application and interview history that you may be legally required to retain.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Identify records outside their retention window
Flag candidates whose consent has expired, who have exercised erasure, or who fall outside regional retention. Exclude them from scope and document the exclusion — you need to show the decision was deliberate.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Inventory resume files and attachments
Count files, total volume and MIME types, and check every attachment still resolves to a live URL. Expiring signed download URLs are the classic reason a resume migration completes with a large fraction of empty files.
Resume download URLs are often short-lived signed links. Fetch files close to load time or they will 404 mid-migration.
-
Verify relationship integrity
Confirm every application links to a live candidate and a live job, and every scorecard to a real interview. Orphaned applications produce a funnel report that does not tie to anything.
-
Clean, normalise and produce masked test data
Normalise emails, phone formats and locations, standardise timestamps to UTC, and generate a masked dataset for the sandbox. Real candidate data in a sandbox is a compliance breach in most jurisdictions.
PII Masker Generate a safe copy for sandbox and vendor testing
Don't move on until
- Duplicate candidate rate quantified with a merge policy agreed
- Records outside retention identified and excluded
- Resume and attachment inventory complete with total volume
03 Field Mapping Map the candidate-application-job triangle before anything else.
Objective A signed mapping covering objects, stages, rejection reasons, scorecards and EEO fields.
Keep these open
-
Map the candidate, application and job model
ATS platforms differ on whether a person or an application is the primary record. Establish this first: getting it wrong means one candidate becomes five, or five applications collapse into one, and the entire field map has to be redone.
Candidate-centric and application-centric models are not interchangeable. Confirm which Oracle Recruiting Cloud uses before mapping any field.
Schema Mapper Match Oracle Taleo fields to Oracle Recruiting Cloud by uploading both schemas -
Map pipeline stages and rejection reasons exhaustively
Enumerate every stage and rejection reason across all jobs, including retired values on historical applications, and map each explicitly. Unmapped rejection reasons are both a reporting gap and, in regulated hiring, a compliance one.
-
Decide EEO and diversity data handling
These fields are separately regulated and often legally required to be stored apart from the candidate record. Confirm with legal whether they migrate at all, and how Oracle Recruiting Cloud isolates them.
EEO data usually cannot be migrated into ordinary custom fields without breaching the segregation rules that govern it.
-
Map interviews, scorecards and feedback
Structured scorecards rarely have a native equivalent. Decide whether to reconstruct them, flatten them into notes, or keep them only in the archive — and be explicit that flattening loses the ability to report on them.
JSON to CSV Converter Flatten nested API responses into a reviewable sheet -
Plan resume and file migration
Confirm size limits, MIME support and whether Oracle Recruiting Cloud re-parses resumes on upload. Re-parsing can overwrite carefully curated candidate fields with worse machine-extracted values, so test it deliberately.
-
Set load order and freeze the spec
Users, then jobs, then candidates, then applications, then interviews and scorecards, then files. Keep source IDs in custom fields, then version and sign off the spec.
-
Deduplicate candidates
Taleo's duplicate detection is optional; many instances have significant duplicate populations
-
Build lookup tables
Translate Taleo org IDs, location IDs, and job field codes to HCM Core equivalents
-
Normalize data types
Date formats, phone number formats, email validation (ORC enforces RFC-compliant email addresses), Unicode normalization
Data Format Converter Reshape the export into the format Oracle Recruiting Cloud's importer expects
Oracle Taleo → Oracle Recruiting Cloud specifics
- Restructure CSW states
- Map Taleo's custom workflow steps to ORC's standardized selection phases
- Decode attachments
- Taleo compresses and Base64-encodes attachments; you must decode, decompress, and re-package for HDL or REST upload
Don't move on until
- Candidate/application/job model mapped and reviewed
- Every stage and rejection reason explicitly mapped
- EEO and diversity field handling agreed with legal
04 Test Migration Pilot whole candidate journeys, not isolated records.
Objective A sandbox pilot where candidate journeys, funnel metrics and resume files all verify.
Keep these open
-
Configure the Oracle Recruiting Cloud sandbox with the agreed pipelines
Create jobs, pipeline stages, scorecard templates, user roles and custom fields first. Loading applications before the stages exist puts every candidate in a default stage and invalidates the pilot.
-
Select complete candidate journeys as the pilot slice
Take 100-200 candidates with all their applications, interviews, scorecards and files — including repeat applicants, hires, rejections at every stage, and candidates on multiple jobs. Repeat applicants are where the model mapping actually gets tested.
-
Run the load in dependency order with logging
Jobs, candidates, applications, interviews, then files, logging each request against its source ID. Track file uploads separately: they fail for different reasons and at different rates than record writes.
-
Verify journeys and funnel metrics
Confirm each candidate sits at the right stage on the right job with their history intact, and that per-stage funnel counts match Oracle Taleo for the pilot jobs. Funnel mismatches point straight back to stage mapping.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Open every pilot resume and check re-parsing
Actually open the files rather than trusting the upload count, and check whether re-parsing has overwritten any candidate fields. A resume that uploaded as a zero-byte file still counts as a success in most logs.
-
Put recruiters in front of the pilot data
Have recruiters work their own pilot requisitions end to end. They immediately spot missing feedback, wrong stages and unreadable history that reconciliation cannot see.
Don't move on until
- Candidate-application-job relationships intact for the pilot
- Funnel counts per stage match source for pilot jobs
- Resume files open correctly for every pilot candidate
05 Cutover Switch recruiting without dropping a live candidate.
Objective All in-scope recruiting data live in Oracle Recruiting Cloud, careers site and boards repointed, recruiters working.
Keep these open
-
Pre-load historical candidates and closed jobs
Load closed requisitions, rejected candidates and archived applications while Oracle Taleo stays live. Only active pipeline and the final delta need to move in the window.
-
Publish the runbook including the careers-site switch
A timed sequence with owners and abort criteria, treating the careers site and job boards as first-class steps. They are candidate-facing, so a failure there is publicly visible in a way a data defect is not.
-
Freeze Oracle Taleo and take the final delta
Stop new applications and let recruiters finish in-flight actions, then export everything changed since the pre-load. Coordinate with anyone actively interviewing so feedback is not entered into the old system mid-freeze.
Interview feedback entered in the old ATS during the freeze is lost, and it is the data recruiters most immediately notice missing.
-
Load active pipeline and reconcile stages
Load active candidates and applications, then verify every active candidate is at the correct stage on the correct job before repointing anything. Active-stage accuracy is what recruiters check first on day one.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint careers site, job boards and integrations
Switch the careers-site integration, repost or migrate live job ads, and repoint HRIS, background check, assessment and calendar integrations. Then submit a real test application through the careers site and every major board.
Job ads left posted against the old ATS keep collecting applications that never reach the new system.
-
Go/no-go and switch recruiters over
Call the decision against the exit criteria, then move recruiters with support on hand for the first day. Keep Oracle Taleo read-only — candidate records have retention obligations that outlast the migration.
Oracle Taleo → Oracle Recruiting Cloud specifics
- Feature freeze
- New feature development for Taleo has stopped. Updates are limited to security patches and critical bug fixes. All product innovation is going into ORC.
Don't move on until
- Historical load complete and reconciled before the freeze
- Careers site and job boards posting into Oracle Recruiting Cloud and verified
- Active candidates confirmed at the correct stage
06 Validation Prove the funnel, the files and the compliance position.
Objective Reconciled recruiting data, funnel parity with baseline, and a defensible compliance record.
Keep these open
-
Reconcile every object including files
Compare counts for candidates, applications, jobs, interviews, scorecards and files, with field-level spot checks on a sample. Count files separately — they are the object most likely to be quietly short.
Migration Validation Tool Reconcile Oracle Taleo and Oracle Recruiting Cloud record-for-record -
Tie funnel and time-to-hire reporting to baseline
Rebuild funnel conversion, time-to-hire, source effectiveness and offer-acceptance reporting and compare to pre-migration figures. Variances trace back to stage mapping and to how application timestamps were handled.
Time-to-hire depends on stage-transition timestamps. If those were approximated, the metric will differ even with identical records.
-
Verify file integrity at scale
Sample-open resumes across the whole load and compare file sizes against source. Zero-byte and truncated files are common and never surface in an upload success count.
-
Confirm retention, consent and EEO configuration
Verify retention rules, consent state and EEO segregation are correctly configured in Oracle Recruiting Cloud, and that excluded records genuinely did not migrate. File this as your compliance evidence.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Test workflow, notifications and candidate-facing paths
Fire every stage automation, interview scheduling flow, rejection template and offer approval, and submit a live application through the careers site. Candidate-facing emails going out wrong is a brand problem, not just a bug.
-
Sign off and schedule decommission
Get written acceptance against the Discovery criteria, retain Oracle Taleo read-only for the period your retention policy requires, take a final archive export, and diarise cancellation.
-
Rebuild selection processes
Taleo CSW workflows do not migrate. Redesign them in ORC's selection process configuration.
-
Run Maintain Candidates and Job Requisitions for Search
This scheduled process must execute after bulk data loads for candidates to appear in ORC's search index.
-
Rebuild integrations
Any downstream systems that consumed Taleo data — background check providers, HRIS feeds, BI tools, agency workflows — need new integration points against ORC's REST API or HCM Extracts.
Oracle Taleo → Oracle Recruiting Cloud specifics
- Reconfigure career sites
- Taleo career sites are separate from ORC career sites. All branding, application flows, and questionnaire configurations must be recreated.
- User training
- The ORC interface is fundamentally different from Taleo's Recruiting Center. Budget time for recruiter, hiring manager, and admin training.
Don't move on until
- Reconciliation complete across candidates, applications and files
- Funnel and time-to-hire reporting tie to baseline
- Retention and EEO configuration verified, acceptance signed
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
Taleo Object ORC / HCM Equivalent
| Oracle Taleo field | Oracle Recruiting Cloud field | Notes |
|---|---|---|
| Requisition | Job Requisition | Must link to HCM Job, Position, Organization, Location. Taleo's standalone org/location data must be pre-mapped. |
| Candidate (external) | Recruiting Candidate | External candidates load through Candidate.dat. ORC candidate is a Person in HCM — can convert to Worker on hire. |
| Candidate (internal) | Worker | Oracle only supports internal candidates through worker data, not Candidate.dat. |
| Submission | CandidateJobApplication | The join between Candidate and Job Requisition. User key is RequisitionNumber + CandidateNumber. Workflow state mapping is manual. |
| Offer | Offer (within Job Application) / Pending Worker | HDL does not support loading job applications with offers in the same load. Accepted offers should become pending workers or new hires. |
| Candidate Profile (Education, Experience, Skills) | Candidate child objects | Mapped to subcategories under recruitingCandidates resource. |
| Attachments (Resume, Cover Letter) | Candidate Attachments | Taleo stores as Base64-encoded, gzip-compressed SOAP blobs; must decode before import. Some job-site attachment endpoints are partner-restricted. |
| User Defined Fields (UDFs) | Extensible Flexfields (EFF) | EFF contexts are only available on specific entities and must be registered and deployed before data loads. Not every Taleo UDF will have a home. |
| Candidate Selection Workflow (CSW) | Selection Process Phases | No direct mapping. ORC uses a standardized phase model; Taleo's custom CSW steps must be redesigned. |
| Source/Medium tracking | Recruiting Source | Different taxonomy; requires value mapping. |
| OLF (Org, Location, Job Field) | HCM Foundation Data (Departments, Locations, Job Families/Profiles) | Must exist in HCM Core before any recruiting records reference them. |
| Approval history / Audit trail | No direct HDL target | HDL does not support loading historical approval chains or audit log entries. Plan for archival in a separate system if required for regulatory compliance. |
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Does Oracle provide a native Taleo to ORC migration tool?
No. Oracle does not provide a native migration path from Taleo to ORC. Oracle Consulting explicitly frames the move as not a lift-and-shift. The transition must be handled by customers themselves using TCC for extraction and HDL/REST API for loading, or through a partner or managed migration service.
What are the Taleo Connect Client (TCC) export limits?
TCC's basic offering imposes a maximum of 500,000 extracted records per day, 100,000 records per extraction transaction, and 50,000 imported records per day. These are hard limits documented by Oracle. For multi-million-record databases, extraction must be spread across multiple days using date-range filtering.
Is Oracle sunsetting Taleo?
Oracle has not published a formal end-of-life date for Taleo Enterprise Edition. However, new feature development has stopped, updates are limited to security patches, Taleo Enterprise is no longer available to new customers as of the February 2026 price list, and components like Taleo Performance (2020) and the legacy Career Website (2024) have already been retired.
Can I migrate all historical Taleo applications into ORC?
Not cleanly as-is. ORC HDL creates job applications only in the first CSP phase/state, and loading job applications with offers is not supported in the same load. Oracle's own guidance says not to load historic job applications just for reporting. Most teams migrate operating history and archive the long tail elsewhere.
How do I migrate Taleo attachments to Oracle Recruiting Cloud?
Taleo stores recruiting attachments as Base64-encoded, gzip-compressed blobs within SOAP XML. Standard TCC cannot export these — you need the TCC Custom Steps library (ExtractAttachedFilePostStep) to decode and extract the files. Once extracted, attachments can be loaded into ORC via the REST API attachment endpoints or packaged for HDL.