Migrating Oracle Classic Help Desk to Redwood: What You Need to Know
Oracle Fusion Help Desk: Classic to Redwood migration is mandatory. All organisations must migrate prior to their Fusion 27A update.
The migration is not just about running automated jobs. It involves manual configuration tasks and planning — especially if you are using Help Desk across HR, Employee Relations, Sensitive Cases, Finance and Procurement.
What This Session Covers:
- Why migrate now — Oracle’s mandatory deadline
- The four migration jobs — what they do and what they don’t do
- Cases and Employee Relations, Finance and other Help Desk use cases — not covered by migration jobs, how to plan separately
- What to assess before you start — custom fields, page layouts, Groovy scripts, integrations and reports
- The manual configuration tasks — VBS setup, Groovy rewriting, queue rules and milestones
- Live demo — VBS configuration for Help Desk pages and how it differs from HCM pages
- Testing and timing — how to plan three migration cycles and go-live safely
Who Should Attend?
- Oracle Fusion Cloud HCM, ERP and Service Leads
- HR, Finance Technology and IT Teams managing the migration
- System Administrators responsible for Classic Help Desk configuration
- Project Managers planning the migration timeline and resources
Speaker
Nizam Mogal
Director | Oracle Cloud Applications Architect | Oracle ACE Pro
Nizam brings 20+ years in Oracle Applications, specialising in Fusion Cloud HCM, ERP and Service with deep expertise in Core HR, Finance, Redwood, Visual Builder, Help Desk and Case Management. Oracle certified in Fusion Cloud and Redwood Applications, he has led multiple global Oracle Fusion Cloud implementations, delivering HR, Payroll, and Finance solutions. He is also recognised as an Oracle ACE Pro, reflecting his thought leadership and active technical contributions to the global Oracle community.
