Migrating to Oracle Redwood: How to Effectively Support the Change

Redwood Migration: A Practical Guide

Oracle has initiated the transformation of the user experience across its cloud applications through Redwood, the codename given to its new generation of UX interfaces.

This evolution affects the entire Oracle Fusion Cloud Applications suite: ERP, HCM, SCM and more. It is notably built on Oracle Visual Builder Cloud Service (VBCS), the technical foundation enabling Oracle to progressively rebuild application screens with a more modern, role-based and mobile-first approach.

While this transformation promises improved usability and a more intuitive experience (and represents a strategic milestone for Oracle) it also raises several challenges for application managers and ERP project leaders:

• Helping users adapt to the new interfaces

• Avoiding disruptions to existing processes

• Maintaining data quality

• Limiting the volume of support requests

How can organisations effectively support the transition to Redwood without disrupting critical business processes?

In this article, we analyse the key changes introduced by the migration and how to facilitate their adoption.

On the agenda:

1. Redwood: A new UX for the entire Oracle Fusion Cloud suite
2. Purchase Requisition: The flagship process most exposed to migration impacts
3. Oracle HCM Cloud: Screens already migrated and deeply transformed user practices
4. Adoption, support and ticket management: The risks of a poorly managed transition
5. The Shortways Assistant: Your lever to secure the Redwood migration

1. Redwood: A New UX Across the Entire Oracle Fusion Cloud Suite

Redwood: What is it? Is not simply a “visual refresh”. It is a new unified design system designed to harmonise the user experience across all Oracle Cloud applications.

Several terms are commonly used in relation to this transformation:

• Redwood UX, referring to the new user experience
• VBCS (Oracle Visual Builder Cloud Service), which serves as the technical foundation
• More broadly, the modernisation of the user experience across Oracle Fusion Applications

The changes are clearly visible:

• Redesigned screens and detailed records
• Reorganised action buttons
• Simplified navigation
• Occasionally adjusted terminology
• A more analytical and concise presentation of information

This modernisation aims to improve efficiency, but it also disrupts established habits. Employees who previously mastered their Procurement or Finance processes must now relearn how to navigate the interface, identify the right actions, and interpret newly structured fields.

For application managers, this means managing a gradual coexistence between legacy screens and Redwood interfaces, module by module.

And while Oracle plans a progressive rollout of modules in Redwood, this transition can still create friction for business users, who often receive limited ERP training in their day-to-day roles.

💡 Tip: Map the modules that have already migrated and anticipate those that will follow in order to prioritise critical processes. Communicate early about upcoming changes and identify the key workflows that require reinforced support.

2. Purchase Requisition: The Flagship Process Most Exposed to the Impact of the Migration

In an ERP system, the purchase requisition process is often one of the most cross-functional workflows.

It does not only involve Procurement teams, but also a wide range of employees: managers, assistants, operational staff and support functions. It is also one of the processes with the highest number of users.

With Redwood, this type of process may experience several changes:

• A new organisation of fields

• A different presentation of approval steps

• Changes in the selection of categories or suppliers

• Modified visual cues and interface references

For occasional users who create a purchase requisition only a few times per month, these changes can lead to:

• Data entry errors

• Incorrect categorisation

• Delays in approvals

• Misunderstandings regarding request status

Yet the purchase requisition process directly impacts accounting, management control and supplier lead times.
A simple change in the interface can therefore create ripple effects across operational performance.

💡 Tip: Identify processes with a high number of occasional users, as these typically require the most support. Anticipate the necessary guidance even before the new screens go live.

3. Oracle HCM Cloud: Screens Already Migrated and Significantly Transformed User Practices

While Finance and Procurement ERP modules are significantly impacted by Redwood, Oracle HCM Cloud is one of the areas where the migration to the new UX is already the most advanced.

Unlike ERP modules, where the transition is gradual, several HCM screens have already been migrated to Redwood in many organisations.
Among the screens already transitioned:

• Talent Review

• Feedback

• Core HR: Employee Profile, Position Management

• Performance & Goals

• Learning

These changes affect:

• The layout of information

• The location of action buttons

• Field labels

• User journeys

For HR teams and managers, these screens are used on a daily basis.
A simple interface change can therefore lead to:

• Confusion when updating data

• Errors in request approvals

• Increased requests to HRIS teams

• Reduced efficiency in managerial processes

The HCM migration clearly illustrates an important reality: Redwood transforms user practices even before it transforms the underlying technology.

💡 Tip: In HCM environments, prioritise the screens used by managers and employees in self-service, as these typically generate the highest volume of support requests after migration.

🎯 Customer case: Major French banking institution

Several HCM screens have already migrated to the new Redwood experience: Performance & Goals, Feedback, and Learning.

The challenge was not only technical, but organisational: supporting 65,000 HR users and managers in adopting redesigned screens while ensuring operational continuity.

In this context, Shortways’ contextual guidance made it possible to:

• Explain the new interfaces as soon as users opened the screens
• Guide managers through their approval workflows
• Limit the increase in tickets related to user onboarding
• Safeguard the quality of HR data

4. Adoption, Support and Ticket Management: The Risks of a Poorly Managed Transition

During a Redwood migration, the first warning sign is often a surge in support tickets.
Users report issues such as:

• “I can’t find my button anymore.”
• “The field is no longer in the same place.”
• “The status has changed.”
• “The screen looks different.”

These tickets are not technical. They are related to user adoption.

Without appropriate support:

• The volume of tickets increases
• Resolution times become longer
• User frustration grows
• Support teams become overwhelmed

Ticket management therefore becomes a strategic issue.
The less prepared the transition is, the more costly the post-migration phase becomes.

A Redwood migration is therefore not just a UX project.
It is an operational change management project.

The transition to Redwood does not happen overnight. Oracle rolls it out module by module, update after update. IT departments and application managers therefore have to operate within hybrid environments: some screens have already changed, while others have not. Users navigate within a two-speed system, increasing the risk of errors, confusion or process interruptions.

This coexistence between legacy and new interfaces requires increased vigilance when supporting change.

Existing training materials quickly become outdated, screenshots no longer match the current screens, and process documentation must be rewritten, all while end users typically have only a few minutes per day to dedicate to training.

💡 Tip: Avoid long, top-down training sessions. Anticipate the post–go-live phase by implementing support directly integrated into the tool. In 2026, it is essential to prioritise embedded guidance available at the moment of need, enabling learning within the flow of work.

5. The Shortways Assistant: Your Lever to Secure the Transition to Redwood

To effectively support the transition to Redwood, the key challenge is to assist users directly within the screen, at the exact moment they execute their process.

In response to this challenge, the Shortways Assistant acts as a true adoption catalyst.
Integrated directly into Oracle Fusion Cloud, the Shortways Assistant enables organisations to:

• Introduce new features through notification bubbles when a migrated screen is opened

• Guide users through critical processes (purchase requisitions, invoice approvals, time entry, etc.) with interactive step-by-step instructions updated according to the new interface

• Explain new field labels, terminology or interface-specific rules through integrated contextual help

• Reduce ticket volume by providing immediate answers to frequently asked questions through dynamic FAQs

• Support HCM, Finance and Procurement teams during the progressive coexistence of environments

Results:

✅ Users become more autonomous
✅ Data entry errors decrease
✅ Support teams can focus on higher-value requests

Redwood adoption becomes smooth and controlled, without jeopardising operational continuity.

✅

Faster adoption of the new screens

Shortways is available on the Oracle Marketplace and already supports several large organisations in their Oracle Cloud transformations, including Orange and a major French banking institution.

Conclusion

Redwood marks a major milestone in the evolution of Oracle Fusion Cloud Applications.

While this modernisation improves the user experience in the long term, it represents a significant short-term challenge for application managers.

The success of this migration depends less on the technology itself than on users’ ability to adopt the new interfaces without disrupting critical business processes such as purchase requisitions.

By integrating a contextual guidance solution such as the Shortways Assistant, you can transform a UX evolution into a lever for operational performance.

👉 Are you preparing for the Redwood migration and looking to secure user adoption? Contact us, our teams are here to help.

During the deployment of Oracle Fusion ERP in 2017, Orange engaged Shortways to improve day-to-day support, training and communication, particularly around its purchase requisition process.