{"id":1013000000505,"date":"2026-10-01T08:08:53","date_gmt":"2026-10-01T08:08:53","guid":{"rendered":"https:\/\/www.version1.com\/en-us\/?p=1013000000505"},"modified":"2026-10-01T08:08:54","modified_gmt":"2026-10-01T08:08:54","slug":"the-countdown-to-27b-what-you-need-to-know-about-oracle-redwood","status":"publish","type":"post","link":"https:\/\/www.version1.com\/en-us\/blog\/the-countdown-to-27b-what-you-need-to-know-about-oracle-redwood\/","title":{"rendered":"Oracle Redwood explained: Migration strategy, AI capabilities and the 27B deadline"},"content":{"rendered":"\n
\n \n
\n
\n \n
\n

By the end of 27A (February to April 2027), all SCM pages must be running on Redwood. After that, Oracle stops supporting Classic. It’s not a suggestion; it\u2019s the date.<\/strong><\/p>\n

For guidance on planning your Redwood migration, watch our on-demand webinar or contact us today.<\/p>\n <\/div>\n \n

\n \n \n \n \n <\/g>\n <\/g>\n<\/svg><\/span>Watch our on-demand webinar<\/span><\/a> <\/div>\n <\/div>\n <\/div>\n<\/section>\n\n\n\n
\n \n
\n
\n
\n \n
\n
\n \n \n

I don’t want to indulge in unnecessary scaremongering but I do want to be clear about what this means practically.<\/p>\n

When we asked SCM leaders what’s driving their move to Redwood, 58% gave the same answer: the mandatory deadline and what happens after. <\/p>\n

Here’s what matters: this isn’t a visual refresh, Oracle has made a clear choice. Every innovation the company is creating now goes into Redwood only. <\/p>\n<\/div>\n <\/div>\n\n <\/div>\n <\/div>\n \n

\n
\n \n
\n
\n \n \n \n <\/path>\n <\/path>\n <\/path>\n <\/path>\n <\/path>\n <\/path>\n <\/g>\n <\/g>\n<\/svg> <\/div>\n \n

Every AI agent<\/h3>\n \n \n <\/div>\n <\/div>\n
\n \n
\n
\n \n \n \n <\/path>\n <\/path>\n <\/path>\n <\/circle>\n <\/circle>\n <\/circle>\n <\/g>\n <\/g>\n<\/svg> <\/div>\n \n

Every new feature<\/h3>\n \n \n <\/div>\n <\/div>\n
\n \n
\n
\n \n \n \n <\/path>\n <\/path>\n <\/path>\n <\/path>\n <\/path>\n <\/g>\n <\/g>\n<\/svg> <\/div>\n \n

Every performance improvement<\/h3>\n \n \n <\/div>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n<\/section>\n\n\n\n
\n \n
\n
\n \n
\n

Classic gets none of it. No updates. No new capability. It simply stops.<\/p>\n

That gap between what Redwood can do and what Classic can do gets wider every quarter. So, the cost of moving early is considerably less than the cost of moving late. Moving late means you’re not just updating your interface, you\u2019re catching up on six, nine, maybe twelve months of capability you’ve missed.<\/p>\n

The timeline: What you’re working with<\/strong><\/h4>\n

\"Timeline<\/p>\n

We’re currently in 26C, so you have roughly three release cycles until 27A hits in February to April 2027. If that sounds like a lot of time, trust me, it isn\u2019t.<\/p>\n

26C (now):<\/strong> This is where you are. If you haven’t started Redwood testing, you need to start now.<\/p>\n

26D (October-December 2026):<\/strong> Oracle is shipping new AI agents. Requisition creation assistants. Planning exception assistants. Supplier qualification agents. If you’re still in testing mode here, you’re behind.<\/p>\n

27A (February-April 2027):<\/strong> This is the deadline. All pages must be in Redwood. All your key processes must have been tested end-to-end. Your users must be trained and working in Redwood. Your customisations must be sorted. Your legacy navigation must be closed off. There’s no partial credit here.<\/p>\n

27B onwards:<\/strong> Support for Classic ends. That’s it.<\/p>\n

People often assume they can stack everything into that final quarter. Testing, training, configuration changes, adoption \u2014 all together. The problem is obvious when you say it out loud: you’ve got maximum pressure and zero time to fix things if they break.<\/p>\n

The organisations that start now<\/u> won’t be under pressure in 27A. The organisations that procrastinate or choose to wait will be.<\/p>\n <\/div>\n \n <\/div>\n <\/div>\n<\/section>\n\n\n\n

\n \n
\n
\n

What you need to do<\/h2>\n \n
\n

The work isn’t just about enabling pages. Here’s where most projects get it wrong: they treat this as a technical project. It’s not – it’s an operational change.<\/p>\n