Pre-built cornerstone ondemand data mapping for Users → HcmWorker, Learning Objects → Fusion Learning Items, Transcripts → Learning Records, Certifications → Fusion Certifications, Goals → Performance Goals. Signed-off workbook, HDL-ready, audit defensible.
Every HDL payload, every reconciliation rule and every regulator-audit answer for the next decade traces back to the cornerstone ondemand data mapping workbook. Skip the mapping discipline and every downstream activity runs against an undocumented baseline.
Cornerstone OnDemand and Oracle Fusion are built on fundamentally different data models. Cornerstone is a flat OU + Custom Field structure optimized for learning audience targeting and a per-user Transcript ledger of every completion event. Fusion HCM is a three-tier enterprise structure (Business Unit / Department / Location) with Worker as the core entity, Fusion Learn separates Learning Items from Learning Records, and Fusion Talent treats Performance Documents and Goals as distinct entities with explicit cycle alignment. Bridging those models requires explicit field-level decisions that cannot be deferred or improvised.
Syntra ETL's cornerstone ondemand data mapping workbook captures those decisions in a structured, version-controlled format: one tab per data domain, every Cornerstone source field, every Fusion target field, transformation rule, data-quality rule, reconciliation rule, sample values. The workbook is signed off by HR ops, learning ops, compliance and internal audit before any HDL load runs.
The discipline matters most for the Custom Field and certification-rule mappings. Mature Cornerstone tenants run 200–600 active Custom Fields driving learning audience eligibility, reporting splits and HR analytics. Importing them wholesale to Fusion as Worker DFFs creates an unmanageable HCM model. Classifying each one — hierarchy / segmentation / reporting / legacy — and routing accordingly is the single largest determinant of post-migration HCM cleanliness.
The pre-built mappings Syntra ETL ships. Customer-specific Custom Fields and certification rules are classified in week-2 workshops.
Cornerstone User ID → PersonNumber, Email → EmailAddress, OU → Department/Location/BU, Manager → ManagerAssignment, Hire/Term Date → HireDate/TerminationDate, Custom Fields → Worker DFFs.
Online Course → Learning Item, Curriculum → Specialization/Learning Path, Material → Resource, Test → Assessment, Event+Session → Class with offerings. Prerequisites and audiences preserved.
User ID + Learning Object ID + Completion Date + Status + Score + Attempts → Fusion HDL LearningRecord. Source-system audit hash preserved for every row.
Certification Name + Award Date + Expiry Date + Renewal Course → Fusion HDL Certification. OSHA/HIPAA/FDA/SOX regulator chain documented per certification.
Review Form → PerformanceDocument, Goal → Goal with parent alignment, Competency Assessment → Profile Item rating, 360 Feedback → ParticipantFeedback.
Succession Plan + Successors → Succession Plan, Talent Pool → Talent Pool, Nine-box → Profile Item, Requisition + Candidate + Application → Recruit HDL bundles.
A four-week workshop sequence that closes with sign-off from HR ops, learning ops, compliance and internal audit. Every HDL job downstream runs against the signed workbook.
Syntra ETL pulls the live field inventory from each Cornerstone domain (User, OU, Custom Field, Learning Object, Transcript, Certification, Performance, Goal, Succession, Recruit) via Cornerstone Edge REST/GraphQL and RDW SQL. Output: complete source-field catalog.
Syntra ETL pre-built mappings (User → HcmWorker, Learning Object → Learning Item, Transcript → LearningRecord, Certification → Certification, Goal → Goal) auto-populated into the workbook. Approximately 60–70% of fields covered without workshop time.
Workshop with HR ops and learning ops walks every Cornerstone Custom Field. Each classified: hierarchy (route to enterprise structure), segmentation (route to DFF/Audience), reporting-only (route to OTBI), legacy (route to archive). Decisions documented inline.
Workshop with compliance team walks every active Cornerstone certification rule. Governing regulation (OSHA/HIPAA/FDA/SOX), expiry cadence, renewal chain mapped to Fusion Certification target or to compliance archive. Audit chain preserved.
For every domain, reconciliation rule defined: row count, sum totals (training hours by BU, certifications by category, learning records by status), hash signature reconciliation. Output: signed reconciliation rule set.
Workbook walked end-to-end with HR ops, learning ops, compliance and internal audit. Final sign-off captured. Workbook moves to version control as the locked contract for every downstream HDL job.
The six mapping challenges that trip up consultant-led Cornerstone-to-Fusion projects most often.
200–600 Custom Fields per tenant. Syntra ETL classification engine routes each to enterprise structure / DFF / OTBI / archive — preventing the wholesale DFF import that breaks Fusion HCM cleanliness.
Each Cornerstone Learning Object type maps to a different Fusion Learn construct. Syntra ETL pre-built rules eliminate the multi-week back-and-forth on Curriculum vs Specialization vs Learning Path.
Regulator-visible certifications must trace back to supporting transcripts and original SCORM completion statements. Mapping preserves chain across Fusion + archive boundary.
Saba (2020), EdCast (2022), SumTotal (2022) acquisitions left overlapping User IDs and Course IDs. Dedup engine identifies golden records and flags duplicates for explicit reconciliation in the mapping.
Reporting-only Custom Fields and OU dimensions don't fit in Fusion HCM. Mapping routes them to OTBI dimension tables instead — preserving analytical context without bloating the Worker model.
OSHA/HIPAA/FDA/SOX retention requirements drive which records land in Fusion vs long-term compliance archive. Mapping captures the routing decision per regulation per record category.
Cornerstone ondemand data mapping is the field-by-field translation between Cornerstone OnDemand's data model — Users, OUs, Custom Fields, Learning Objects, Transcripts, Certifications, Learning Paths, Performance Reviews, Goals, Succession Plans, Requisitions and Compensation Cycles — and Oracle Fusion's HCM/Learn/Talent/Recruit/Compensation data model. Every Cornerstone source field gets an explicit Fusion target field (or an explicit 'no Fusion home, route to archive' decision). The cornerstone ondemand data mapping document is the contract between the migration team and the business: it dictates every HDL payload, every reconciliation rule and every regulator-audit answer for the next decade. Syntra ETL ships pre-built mappings for the standard Cornerstone-to-Fusion crosswalks and runs structured workshops to nail down the customer-specific Custom Field, OU and certification-rule translations.
The core Cornerstone User entity (User ID, First/Last Name, Email, Status, Manager, OU assignments, hire date, termination date, position, employment type) maps to Fusion HCM Worker (PersonNumber, PersonName, EmailAddress, AssignmentStatusType, ManagerAssignment, DepartmentName/LocationCode/BusinessUnit, HireDate, TerminationDate, JobName, EmploymentCategory) via HDL Worker.dat and WorkRelationship.dat. The cornerstone ondemand data mapping handles the structural differences: Cornerstone's flat OU model becomes Fusion's three-tier Department/Location/Business Unit; Cornerstone's User status flags (Active/Inactive/Terminated/Leave) map to Fusion's AssignmentStatusType lookup; Cornerstone Custom Fields driving worker context route to Fusion Worker DFFs. Where the customer is already on Oracle Fusion HCM with workers established, Cornerstone Users map by email or employee number and the worker context is preserved by reference rather than re-asserted.
Cornerstone OnDemand has six Learning Object types: Online Course (SCORM/xAPI/AICC/CMI5-driven self-paced), Curriculum (composite path of multiple courses), Material (downloadable PDF/video), Test (assessment-only), Session (specific scheduled instance of an event), Event (the parent ILT/VILT template). Each maps to Fusion Learn Item types via HDL: Online Course → Fusion Learning Item (self-paced), Curriculum → Fusion Specialization or Learning Path, Material → Fusion Learning Item (resource), Test → Fusion Assessment, Event + Session → Fusion Class with scheduled offerings. The cornerstone ondemand data mapping preserves prerequisite chains, completion-rule semantics (passing score, max attempts, time-in-course), certification linkages and audience eligibility rules through the HDL load. SCORM bundles repackaged and uploaded to the Fusion Learn content store separately.
The Cornerstone Transcript entity (per-user record of every completion event: User ID, Learning Object ID, Status, Completion Date, Score, Attempts, Instructor) maps to Fusion HDL LearningRecord with the equivalent fields (PersonNumber, LearningItemNumber, LearningRecordStatus, CompletionDate, Score, AttemptCount, AssignmentReason). Cornerstone Certifications (Certification Name, Award Date, Expiry Date, Renewal Course, Status, Original Transcript) map to Fusion HDL Certification with PersonNumber, CertificationCode, AwardDate, ExpirationDate, RenewalLearningItemNumber, Status. The cornerstone ondemand data mapping preserves the chain: a regulator-visible Fusion Certification can be traced back to its supporting Fusion Learning Record, which links to the original Cornerstone Transcript and the original SCORM/xAPI completion statement. Active records load to Fusion; expired/legacy records route to the long-term compliance archive.
Custom Fields in Cornerstone OnDemand drive most of the user-segmentation and reporting context in mature tenants — typical tenants run 200–600 Custom Fields. The cornerstone ondemand data mapping classifies each Custom Field into one of four routes: hierarchy-driving Custom Fields (Region, Cost Center, Legal Entity) map to Fusion enterprise-structure fields (BusinessUnit, Department, Location, LegalEmployer); segmentation Custom Fields (Job Family, Skill Tier, Compliance Group) map to Fusion Worker DFFs and Learning Audience criteria; reporting-only Custom Fields map to OTBI dimensions; legacy/inactive Custom Fields route to the long-term archive with no Fusion footprint. The classification is signed off by HR ops and learning ops before any HDL load runs — preventing the common failure mode of importing 600 Custom Fields wholesale into Fusion DFFs and creating an unmanageable Worker model.
Cornerstone Performance Review forms (review cycle, rating scale, competencies, manager and self-assessment sections, 360 feedback contributors) map to Fusion Performance Document via HDL PerformanceDocument bundles. Cornerstone Goals (goal title, description, weight, due date, status, alignment to manager goal, progress updates) map to Fusion Goals via HDL Goal bundles with parent/child alignment preserved. Cornerstone competency assessments (competency name, scale, assessment, evidence) map to Fusion Profile Item ratings on the Worker Talent Profile. The cornerstone ondemand data mapping handles cycle alignment carefully: historical review cycles route to closed Fusion review periods with read-only access; in-flight cycles are paused on Cornerstone, completed in Cornerstone or Fusion based on cutover timing, and reconciled with a documented chain.
Cornerstone Succession Management entities (Succession Plan, Successor candidates with readiness rating, nine-box assessment, retention risk, key positions) map to Fusion Talent Review and Succession via HDL Succession bundles. Each Cornerstone Succession Plan maps to a Fusion Succession Plan with key position, current incumbent, successor list, readiness ratings preserved. Cornerstone Talent Pools (defined groups of high-potential employees) map to Fusion Talent Pool entities with membership and pool-level criteria. Nine-box assessments and retention-risk flags map to Fusion Talent Profile attributes. The cornerstone ondemand data mapping preserves the link between succession plans and the underlying competency, performance and learning data — so that a Fusion talent review can drill from a successor's readiness rating back to the supporting performance reviews and completed development learning.
Every Cornerstone-to-Fusion mapping decision is documented in a structured cornerstone ondemand data mapping workbook with one tab per data domain: Users, OUs, Custom Fields, Learning Objects, Transcripts, Certifications, Learning Paths, Performance Documents, Goals, Succession Plans, Requisitions, Candidates, Compensation. Each row contains the Cornerstone source field, the Fusion target field (HDL bundle and column), the transformation rule (direct copy, lookup, derived, archive), the data-quality rule, the reconciliation rule, the sample source value and the sample target value. The workbook is version-controlled, sign-off-gated by HR ops and learning ops, and serves as the contract for every HDL job run. Updates after the migration completes are still applied to the workbook so that the audit chain remains intact for the regulatory retention period.
Book a 30-minute scoping call. We will walk through your Cornerstone tenant's Custom Field profile, Learning Object inventory, certification rules and Performance/Talent setup — and outline a four-week workshop sequence to deliver a signed-off field-level mapping workbook ready to drive HDL loads.