Redwood Adoption Blog Series Part 1: Introduction to Redwood – Oracle’s Next-Gen UI

Welcome to a three-part series exploring the transition to Oracle’s Redwood Experience, presented from the house of MIPRO’s Center of Excellence on Oracle Technologies. This series is designed to help Oracle Cloud customers understand Redwood, what changes during migration, and how to prepare for the shift successfully. Whether you are part of an implementation team, a system administrator, or a business user impacted by the change, these posts provide clarity and actionable insights.

Navigating the Shift to Redwood: What to Expect When Upgrading

As Oracle continues its rollout of the Redwood Experience across Oracle Cloud Applications, organizations must prepare for more than a visual upgrade. Redwood represents a complete redesign of how applications are structured, customized, and experienced.

This first post introduces Redwood, highlights how it differs from the older Responsive UI, and explains the strategic importance of planning for migration.

What is Oracle’s Redwood UI?

Key features include:

• Modern Look and Feel – Streamlined layouts, simplified navigation, and cohesive branding
• Responsive Design – Optimized for desktop, tablet, and mobile
• Role-Aware UI – Adjusts content based on user roles
• Visual Builder Studio Integration – Supports low-code customization
• Enhanced Accessibility – Designed to meet global standards

Unlike the previous Responsive UI, which was built using Oracle’s Application Development Framework (ADF), Redwood is built entirely on Visual Builder Studio and Oracle JET components. This brings new customization capabilities — but also requires thoughtful migration of legacy configurations.

Why Redwood Matters

For users:

• Faster performance
• Intuitive navigation
• Customized data visibility

For organizations:

• Improved compliance and data governance
• Lower long-term customization overhead
• Better mobile and accessibility support

Migration isn’t automatic. Every personalization, rule, and layout may need review and refinement.

Key Areas to Watch During Your Redwood Migration

Although Redwood brings a sleek interface and performance upgrades, some behind-the-scenes components require closer inspection to ensure functionality is preserved. Two of the most critical categories during the transition are:

Personalization – These include all UI-level customizations that affect user interaction, such as field visibility, read-only status, required fields, and embedded content. These do not carry over automatically and need to be migrated manually using Visual Builder Studio (VBS) or assisted tools like the Redwood Personalization Helper Tool.

Auto-Complete Rules – These enforce validation or set default values to ensure accurate data input. While Redwood supports these rules, each one should be thoroughly retested to prevent logic issues across environments.

Overlooking either of these areas can lead to broken workflows, data integrity issues, and end-user frustration. Identifying where these configurations live today and planning their transition is essential for a smooth go-live.

MIPRO Consulting provides hands-on support to help teams audit, reconfigure, and validate these elements as part of a structured migration approach. We ensure your business rules, compliance logic, and personalization investments are preserved — and optimized — in Redwood.

Getting Started with Confidence

As Redwood adoption continues across Oracle’s ecosystem, teams that prepare early will experience smoother transitions, reduced post-launch disruptions, and faster time-to-value. The shift from Responsive UI to Redwood isn’t just visual — it reshapes how applications are configured, secured, and customized. Areas such as personalizations, auto-complete rules, and page layouts must be carefully reviewed and realigned.

MIPRO Consulting helps clients approach this shift strategically. From auditing current personalizations and revalidating logic rules to rebuilding layouts and preparing your security framework, we provide tailored support at every step. Our goal is to ensure your transition is not only compliant and technically sound — but also aligned with your business workflows.

---

Part 1 has laid the foundation: Redwood is modern, powerful, and flexible — but migration requires careful planning and collaboration.

In the next post, we’ll dive into three major technical areas affected by this transition: Feature Changes, Personalization Challenges, and Page Layout Redesigns. Understanding these will help you avoid common pitfalls and make informed decisions about your upgrade strategy.

If you would like more information on Redwood, visit https://redwood.oracle.com/

Please contact MIPRO for more information on Oracle Cloud. You can also visit Redwood.Oracle.com for additional information on Redwood.