Oracle SCM has entered its mandatory Redwood transition, with full adoption required by release 26D in Q4 2026. Classic HR Help Desk must also move before 26D. Release 26C alone carries around 915 feature changes, with roughly 60% flagged for Redwood. This is a UI and interaction-model change, not a re-implementation — your configuration, data and integrations stay where they are. The work is in personalisations, saved searches, user training and testing.
For three years Redwood was something you could look at, trial in a sandbox, and then postpone. That period is over. Oracle Supply Chain Management has moved into its mandatory Redwood transition phase, with full adoption required by release 26D in Q4 2026, and Classic HR Help Desk must be migrated to the Redwood experience before the same release. If your organisation has been treating Redwood as optional, the calendar has now made the decision for you.
This post is the practical version: what actually changes, what does not, which teams feel it first, and what a sensible preparation plan looks like from where you are standing today.
What Redwood Actually Is (And What It Is Not)
Redwood is Oracle's design system and front-end architecture for Fusion Applications. It replaces the older Oracle Applications Cloud (OJET/ADF-era) interface with a new visual language, new page patterns, and a different interaction model built around guided, task-focused workspaces rather than dense form-and-tab screens.
The single most important thing to understand — and the thing that calms most anxious project sponsors — is what Redwood is not. It is not a re-implementation. Your chart of accounts does not move. Your business units, ledgers, item masters and approval hierarchies stay exactly where they are. Your transactional data is untouched. Your integrations continue to call the same REST and SOAP services. What changes is the layer your users touch.
That distinction matters commercially too. Anyone quoting you a Redwood transition as though it were a fresh Fusion implementation is either misunderstanding the change or overselling it.
The Deadlines That Actually Bind
- Oracle SCM is in its mandatory Redwood transition phase now, with full adoption required by 26D in Q4 2026.
- Classic HR Help Desk must be migrated to the Redwood experience before release 26D.
- Release 26C is Oracle's largest 2026 quarterly update so far — around 915 feature changes, with close to 60% flagged as Redwood UI work and roughly 139 involving AI capabilities.
- Oracle Fusion updates quarterly (26A, 26B, 26C, 26D), so there is no option to skip a release and catch up later — you move with the calendar.
The practical read: if you are on SCM, the runway is measured in months rather than years, and the 26C release already contains the bulk of the change surface. Teams that start testing in 26C are working with the real thing. Teams that wait until 26D are testing and cutting over simultaneously, which is where projects get painful.
What Genuinely Changes for Users
1. Navigation and task flow
Redwood favours workspaces and guided flows over the classic springboard-and-tabs pattern. A task that used to be 'navigate to the work area, filter the table, open the record, switch tab, edit' is often restructured into a single focused page with progressive disclosure. Faster once learned — but it is genuinely new muscle memory, and experienced power users often feel the disruption more sharply than casual users, because their speed came from knowing exactly where everything was.
2. Saved searches, personalisations and layouts
This is where most of the real project work sits. Personalisations made against classic pages do not automatically carry across to their Redwood equivalents, and heavily personalised environments carry the most migration effort. Inventory what you actually have before you estimate anything — most organisations discover they are carrying personalisations nobody has used in two years, which is the cheapest possible thing to find early.
3. Reports and analytics embedding
OTBI and BI Publisher continue to work, but where analytics are embedded into pages, the surrounding page has changed. Expect to re-verify that embedded content still lands where users expect it and still renders at a usable size within the new layouts.
4. Training material and documentation
Every screenshot in every internal SOP, training deck and user guide is now out of date. This is unglamorous and consistently underestimated. For an organisation with mature documentation, refreshing it is frequently the single largest line item in the transition — larger than the technical work.
What Does Not Change
- Configuration and setup data — ledgers, business units, item masters, approval rules.
- Transactional data and history.
- REST and SOAP integration endpoints, and the FBDI/HDL loaders your interfaces rely on.
- Security model — roles, data access sets and privileges carry across.
- Underlying business logic. Invoice matching still matches invoices; the screen around it looks different.
Reading that list is the fastest way to right-size the effort. The system of record is not being replaced. The window onto it is.
A Preparation Plan That Works
Step 1 — Inventory before you estimate
List every personalisation, saved search, sandbox and embedded report currently in use, and mark which are genuinely used versus historically created. You cannot size the work without this, and the exercise usually removes a meaningful chunk of it.
Step 2 — Enable Redwood in a test environment now
Do not wait for 26D. Turn Redwood on in test during 26C and walk your highest-volume transactions through it end to end. Volume, not complexity, is the right filter here — the process a hundred people run daily matters far more than the quarterly close routine two people run.
Step 3 — Pick your loudest users first
Counter-intuitive but reliable: give early access to the power users most likely to complain. They find the genuine friction fastest, and bringing them in early converts them from critics into advocates. Discovering their objections during cutover week is considerably more expensive.
Step 4 — Rebuild training on the new screens
Budget real time for this and start it while you still have a working classic environment to compare against. Side-by-side screenshots are far easier to produce before the old UI disappears than after.
Step 5 — Test integrations even though they should be fine
Integrations should be unaffected because they run below the UI layer. Verify that assumption anyway. 'Should be fine' is not a test result, and a quarterly release carrying 915 feature changes deserves a regression pass regardless.
What This Means If You Are Learning Oracle Fusion Now
If you are training on Fusion today, learn Redwood as the default and treat classic as the legacy you should recognise but not specialise in. Every new implementation will be Redwood, and the migration wave means the market specifically values people who can work in both and explain the difference to nervous users.
There is a real, time-boxed opportunity here. Consultants who can run a Redwood readiness assessment, inventory personalisations, rebuild training material and steer user adoption are in demand precisely because the deadline is fixed and the installed base is large. That demand window is open now and narrows once the bulk of the base has transitioned — which is exactly the shape of opportunity that rewards moving early.
Frequently Asked Questions
Is Redwood mandatory for all Oracle Fusion modules?
Not simultaneously. Oracle is phasing mandatory adoption by module. Supply Chain Management is in its mandatory transition phase with full adoption required by 26D in Q4 2026, and Classic HR Help Desk must migrate before 26D. Other areas follow their own timelines, so check the release readiness material for the specific modules you run rather than assuming one universal date.
Will the Redwood migration affect my data or configuration?
No. Redwood changes the user interface and interaction model, not the underlying data model, configuration or business logic. Your ledgers, business units, item masters, transactional history, security roles and integration endpoints all carry across unchanged. The migration work sits in personalisations, saved searches, embedded analytics placement, user training and testing.
How long does a Redwood transition typically take?
It depends almost entirely on how heavily personalised your environment is and how mature your training documentation is, rather than on how many modules you run. A lightly personalised environment with modest documentation can move in weeks. An environment with years of accumulated personalisations, saved searches and detailed SOPs should plan for months — and most of that time goes on documentation and user enablement rather than technical work.
Do my integrations need to be rebuilt for Redwood?
No. Integrations operate against REST and SOAP services beneath the UI layer, so they are unaffected by the interface change. You should still run a regression pass over them, because Redwood arrives inside large quarterly releases — 26C alone carries around 915 feature changes — and something else in that payload may touch your interfaces.
Should I still learn the classic Oracle Fusion interface?
Learn to recognise it, not to specialise in it. Many organisations are still running classic today and will be mid-transition through 2026, so you will encounter it on live projects and should be able to navigate it. But every new implementation is Redwood, so build your depth there and treat classic as context.
The Short Version
Redwood stopped being optional for SCM, the deadline is 26D in Q4 2026, and 26C already carries most of the change. It is a user-interface transition rather than a re-implementation, so the risk is concentrated in adoption, personalisations and training rather than in data or integrations. Organisations that start testing during 26C will find it manageable. Organisations that wait until 26D will be testing and cutting over at the same time, which is the version of this project nobody enjoys.
At LearnwithCR our Oracle Fusion training is delivered on current releases by consultants working on live implementations, so you learn the interface you will actually be handed on a project — not a version that was current three years ago.
Ready to become an Oracle Fusion expert?
Join LearnwithCR for live, hands-on Oracle Fusion training with certification guidance and placement assistance.