At BLUEPRINT 4D 2026, the session “Cloud SCM Community Meetup: Change Management for Redwood in SCM – Ensuring Adoption and Zero Disruption” focused on a challenge nearly every Oracle Cloud SCM customer is now facing: how to successfully adopt Oracle Redwood without disrupting users, operations, or productivity. Presented by Aswanth Vaidiswaran and Srinivasan Narayanan, the discussion moved well beyond user interface modernization and into the operational realities of enterprise transformation.

The core message was clear: Redwood is no longer optional. Organizations that delay adoption risk compressing timelines later while also slowing their ability to take advantage of Oracle’s growing AI capabilities.

Redwood Is More Than a UI Refresh

One of the biggest misconceptions the presenters addressed is that Redwood is simply a visual redesign. In reality, Redwood represents a foundational platform shift for Oracle Cloud applications.

The session highlighted several functional improvements organizations are already seeing with Redwood, including:

• Guided transaction flows
• Elastic search-based filtering and navigation
• Mobile-native experiences
• Embedded AI capabilities
• Bulk edit and productivity enhancements
• Improved notification handling
• CI/CD-aligned customization deployment through Visual Builder Studio

The presenters used procurement as an example to show how Redwood changes the user experience. Instead of navigating traditional requisition screens with little guidance, Redwood walks users through transactions step by step, reducing confusion and improving accuracy.

More importantly, Redwood serves as the gateway for Oracle’s future AI investments. Features such as Ask Oracle and AI-driven agents increasingly depend on Redwood-enabled pages and workflows.

As Vaidiswaran explained, organizations pursuing AI transformation in Oracle Cloud SCM cannot treat Redwood as a separate initiative. The two are becoming tightly connected.

Oracle’s Timeline Is Moving — But Adoption Pressure Remains

The presenters discussed Oracle’s evolving timelines for mandatory Redwood adoption. While earlier guidance pointed toward aggressive migration deadlines, Oracle has since extended some timelines after recognizing that certain Redwood features still require maturity and parity with Classic UI functionality.

Even with those extensions, the recommendation from the session was straightforward: start now.

Waiting until Oracle enforces migration creates unnecessary risk. Customers that delay adoption may eventually face compressed testing windows, larger-scale retraining efforts, and more difficult customization remediation projects.

The presenters encouraged organizations to think immediately about small pilot opportunities rather than large-scale “big bang” migrations.

Change Management Is the Real Challenge

One of the strongest themes throughout the session was that Redwood projects succeed or fail based on change management, not technology.

Vaidiswaran emphasized that organizations often focus too heavily on technical enablement while underestimating the impact on people and processes. Different user groups experience Redwood differently, and successful adoption depends on tailoring training and rollout strategies accordingly.

For example:

• Buyers interact differently than requesters
• Shipping users have different priorities than inventory users
• Supervisors require different workflows than technicians

Because of this, generic Redwood training programs often fall short. Organizations need role-based training aligned to actual user behavior and pain points.

The presenters also stressed the importance of process evaluation. Even when the underlying business process technically remains the same, users may perceive major workflow changes because of navigation differences or feature placement within Redwood.

That gap between technical equivalence and user perception is where many adoption issues begin.

Parallel Rollouts vs. Forced Migration

A particularly valuable part of the discussion centered around rollout strategy.

Some organizations are allowing Redwood and Classic UI to coexist temporarily, enabling users to transition gradually. Others are deliberately removing Classic access during production rollout to accelerate adoption and reduce resistance.

The presenters made it clear there is no universal answer.

Organizations with strong change management teams and tech-savvy user bases may benefit from parallel operation models. Other organizations may achieve better results through structured cutovers with tightly managed enablement and support.

The important takeaway was that Redwood adoption should not be treated as a one-size-fits-all deployment.

Instead, organizations should evaluate:

• User readiness
• Feature maturity
• Business criticality
• Functional parity
• Upstream and downstream dependencies
• Organizational change tolerance

Functional Gaps Must Be Identified Early

The session repeatedly returned to the importance of upfront assessment and inventory work.

Customers need a clear understanding of:

• Existing customizations
• Personalizations
• Sandbox changes
• Missing Redwood functionality
• Integration dependencies
• Feature release timing

The presenters warned that discovering functionality gaps during user acceptance testing creates significant frustration and damages confidence in Redwood.

Instead, organizations should proactively document known limitations and communicate roadmap expectations to users before rollout.

The procurement change order example illustrated this point well. At one stage of Redwood adoption, requisition creation was available in Redwood while purchase order change functionality still required Classic UI. Organizations that failed to explain this transition state often faced user complaints and confusion.

The recommendation was to approach Redwood migration in sprint-style phases, enabling functionality incrementally as Oracle expands feature support.

AI Readiness Is Accelerating Redwood Priorities

Another major insight from the session was how aggressively AI initiatives are driving Redwood adoption inside organizations.

Narayanan shared that Milwaukee Tool is pushing hard toward Redwood migration specifically because AI enablement depends on it. Their organization is targeting more than 90% Redwood adoption across SCM modules by the end of the year to support future AI capabilities.

That work spans:

• Manufacturing
• Inventory
• Maintenance
• Supply chain planning
• Costing

The scale is significant, involving over 1,000 Oracle Fusion users across multiple operational areas.

The presenters explained that Oracle’s AI roadmap increasingly assumes Redwood as the delivery framework. As Oracle shifts development focus toward Redwood experiences, organizations staying on Classic UI risk falling behind on both innovation and support priorities.

Oracle’s Redwood Adoption Program Can Help

One of the most practical portions of the session focused on Oracle’s Redwood rapid adoption support programs. Many customers remain unaware these programs exist.

Narayanan explained how Milwaukee Tool works directly with Oracle product managers, support engineers, and Redwood platform teams through bi-weekly collaboration sessions.

This partnership provides several advantages:

• Early access to roadmap visibility
• Faster bug resolution
• Direct enhancement discussions
• Guidance on missing privileges and configurations
• Support for customization remediation planning

The session also revealed a practical reality many customers encounter: Oracle documentation alone is often not enough for successful Redwood enablement. Some organizations must work directly with Oracle support teams to identify required privileges, web services, and security adjustments necessary for Redwood pages to function properly.

That direct collaboration can significantly reduce deployment friction.

Start Small — But Start Now

The final recommendation from the session was simple but important: don’t wait for a perfect migration strategy before beginning Redwood adoption.

Organizations should identify low-risk opportunities first, such as:

• Inquiry-only pages
• Setup and configuration screens
• Small pilot groups
• Read-only use cases
• Limited transactional workflows

From there, teams can measure adoption, gather feedback, refine training, and expand rollout phases incrementally.

The presenters repeatedly emphasized that Redwood transformation is not purely technical. It is an organizational change initiative that requires planning, communication, phased execution, and continuous measurement.

For Oracle Cloud SCM customers, the message from BLUEPRINT 4D 2026 was unmistakable: Redwood adoption is coming, AI acceleration is increasing the urgency, and the organizations that begin preparing now will be in a far stronger position than those forced into rushed migrations later.

Want more?

Explore more content and resources to help you get the most from your Oracle investment:

• Visit the Quest Learn Library for blogs, how-to demos, and on-demand sessions.
• Connect with peers in one of our Quest Cloud Community User Groups to swap stories, ask questions, and share tips with other users facing the same challenges.

Not a Quest member yet? Join today and tap into the ultimate Oracle customer network.