Moving from Oracle E-Business Suite to Fusion Cloud is one of the most consequential decisions a company makes about its technology stack and its Oracle relationship. Done right, the move resets Oracle spend and modernizes the platform. Done wrong, the company inherits an unfavorable contract and a security model that was never actually redesigned for Fusion.
Craig Guarente of Palisade Compliance covers the contractual and financial dimension: how legacy Oracle agreements constrain or empower a negotiating position, how OCI decisions create leverage, and how new SaaS agreements should be structured to reduce spend rather than inflate it.
Jeff Hare of ERP Risk Advisors covers the technical dimension most negotiations do not touch. Teams that treat the EBS security model as a template for Fusion, rather than redesigning it, end up with seeded roles that are significantly overprovisioned through custom role design. Audit logging in Fusion is mostly configurable rather than automatic, and certain controls that existed in EBS cannot be replicated the same way. Mass assignment access and workflow management permissions are often left broader than they should be, creating exposure that surfaces well after go-live.
Attendees leave with a complete view of the migration decision: the financial leverage available before signing, and the specific role and logging gaps to close before go-live.
Learning Objectives:
The Oracle Applications & Technology Users Group (OATUG), formerly the Oracle Applications Users Group (OAUG), is the world’s largest education, networking and advocacy forum for Oracle Applications & Technology users.
HomeLearnEngageJoin