Vigilant Technologies

The-Quadrilateral-Orange
The-Quadrilateral-Orange

Oracle Redwood Transition
Summary and Readiness Overview

Oracle Redwood Transition Summary and Readiness Overview

This document summarizes Oracle’s Redwood design system transition, key release timing, customer readiness actions, and references to authoritative sources. Redwood is Oracle’s next-gen UX for all Fusion Cloud Applications. It introduces a unified design system, modern navigation, accessibility improvements, and embedded AI capabilities. The transition affects all Oracle Cloud customers, with full rollout targeted by 2026. 

Key References and Sources 

  1. Opkey – Prerequisites for Oracle Redwood Design Systems: https://www.opkey.com/blog/prerequisites-for-oracle-redwood-design-systems
  2. Kovaion – All You Need to Know About Oracle Redwood: https://www.kovaion.com/blog/all-you-need-to-know-about-oracle-redwood/
  3. Opkey – Oracle Redwood Migration Timeline and Testing Guide: https://www.opkey.com/blog/oracle-redwood-migration-timeline-and-testing-guide
  4. Oracle Newsroom – Redwood UX Updates for Supply Chain: https://www.oracle.com/news/announcement/oracle-elevates-supply-chain-efficiency-with-user-experience-enhancements-2024-08-13/
  5. USDM – Redwood Rollout Timeline for Life Sciences: https://usdm.com/resources/blogs/oracle-fusion-to-redwood-migration
  6. Maverick Solutions – Oracle Redwood Soon to Be Mandatory: https://mavericksolutions.com/2024/05/14/oracle-redwood-soon-mandatory/
  7. UC Merced – Redwood UI Update Communication: https://dfa.ucmerced.edu/news/2024/oracle-redwood-ui-update 
  1. Overview of Oracle Redwood

Oracle Redwood is a comprehensive redesign initiative to unify the user experience across all Fusion Cloud Applications. Beyond aesthetics, it redefines workflow simplicity, introduces AI-driven insights, and ensures accessibility compliance. Oracle’s goal is to migrate all applications to Redwood by 2026, beginning with HCM and EPM, and expanding across ERP, SCM, Procurement, and CX modules.

  1. Rollout Timing and Transition Milestones

  • 2024 Q3–Q4: Early adoption for HCM and EPM modules. New Oracle Cloud implementations default to Redwood UX.
  • 2025 Q1–Q3: Procurement and SCM transitions begin (Releases 25A–25C).
  • 2025 Q4–2026 Q2: Mandatory rollout for ERP, SCM, and CX modules.
  • End of 2026: Target for complete Redwood coverage across all Fusion Cloud applications. (Brandon told me that Oracle may need to extend this because people aren’t ready)
  1. Module-Specific Impacts

  • HCM: Employee and Manager Self-Service modules will shift fully to Redwood in 2025. Includes new AI assistants.
  • ERP / Financials: General ledger, expenses, and procurement workflows redesigned; mandatory by 2026.
  • SCM: Inventory and order management adopting Redwood UX with embedded AI.
  • Procurement / SSP: Redwood becomes default mid-2025 (Release 25C).
  • EPM: Transition largely complete since July 2024; non-Redwood themes retired.
  • CX: To follow in 2025–2026, with AI recommendations and Redwood-based dashboards.
  1. Actions for Existing Oracle Customers

  • **Audit customizations:** Identify Page Composer, Visual Builder, and theme overrides incompatible with Redwood.
  • **Test quarterly updates:** Redwood updates roll out via quarterly releases; use sandbox testing before each.
  • **Develop a change management plan:** Update internal training, documentation, and user onboarding.
  • **Align branding:** Update company themes and ensure compliance with Redwood’s accessibility standards.
  • **Create a readiness roadmap:** Prioritize modules by impact and timing, with IT ownership defined. 
  1. Risks of Not Preparing

  • Broken or outdated custom pages when legacy themes retire.
  • Confusion among end users as navigation and workflows change.
  • Potential noncompliance with accessibility requirements (WCAG 2.2).
  • Delayed feature adoption and loss of AI-enhanced user experience.  
  1. Strategic Guidance

Redwood is not a cosmetic refresh—it’s a UX and platform overhaul. Treat it as part of your broader digital transformation. Organizations should form a Redwood task force, monitor Oracle’s quarterly readiness documentation, and coordinate with Oracle or system integrators to manage timelines. Testing and communication are key to avoiding disruption. 

  1. Conclusion

Oracle Redwood represents the next evolution of Oracle Cloud UX—modern, intelligent, and standardized across applications. Customers who prepare proactively will experience a smoother transition, lower support overhead, and faster adoption of new AI capabilities. Delaying readiness could lead to service disruptions and user friction once Redwood becomes mandatory. 

Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.