Phase 2: Extending the Core

Oracle Cloud / By /

Phase 2: Extending the Core

Oracle Cloud Migration Series, Part 3 of 7

If Phase 1 is where you pour the foundation, Phase 2 is where you build the structure above it. The modules in this phase are not afterthoughts or nice to haves. They represent core business functions that matter deeply to employee experience, financial accuracy, and operational performance. But they have one thing in common: they depend on Phase 1 being solid before they can deliver their full value.

This is the walk phase. Your organization has found its footing on Oracle Fusion Cloud. Your finance team knows the new month end process. Your HR team understands the Core HR data model. Your users have built base level confidence in the platform. Now you extend the investment and accelerate the return.

Expense Reimbursement

Oracle Expenses is a natural extension of the AP and Procurement foundation built in Phase 1. Travel and expense reports flow through an approval workflow and ultimately result in employee payments, which run through the same disbursement framework established for supplier payments in Payables.

The dependency here is deliberate. Expenses sit on top of the accounting structure in GL, the payment infrastructure in AP and Cash Management, and the organizational hierarchy in Core HR. All three are live after Phase 1, which means Expenses can be configured cleanly without workarounds.

From an employee experience standpoint, Oracle Expenses with mobile receipt capture, AI driven workflows, and automated policy enforcement is a significant upgrade from the systems most PeopleSoft and EBS organizations are running today. The ROI is visible quickly because the user experience improvement is immediate.

Fixed Assets

Fixed Assets has a close relationship with both GL for asset accounting entries and Projects for asset capitalization from project costs. Implementing Fixed Assets in Phase 2 rather than Phase 1 is the right call because asset capitalization workflows, especially for organizations with significant capital projects, require Projects to be in scope first.

The other consideration is data migration complexity. Asset registers accumulated over many years in legacy systems are often among the messiest data sets in any migration. Prorate calculations, accumulated depreciation balances, partially disposed assets, assets modified in ways the system never formally recorded, all of this requires careful data remediation work. Build in adequate time and do not assume a lift and shift will work cleanly.

Project Portfolio Management

Oracle Project Portfolio Management, covering Project Costing, Project Billing, and Project Management, is a powerful and complex module set. It has dependencies on GL for project accounting, AP for supplier costs that hit projects, Procurement for project related purchase orders, and HR for project resource assignments.

This is why PPM belongs in Phase 2 and not Phase 1. The interdependencies are real and broad – I call PPM the ‘Octopus of Oracle’ because all of its tentacles touch so many other modules. Trying to implement PPM before those upstream systems are stable creates significant integration risk and typically results in workarounds that turn into technical debt.

For project driven organizations, professional services firms, government contractors, construction companies, organizations with significant capital programs, PPM is often one of the highest value modules in the entire implementation. Getting it right matters enormously.

Time and Labor

Time and Labor integrates with Core HR for worker data and assignment records, with Projects for labor costing, and with GL for cost accounting. Its Phase 2 placement exists specifically because Core HR must be live and stable before Time and Labor can function correctly.

Many organizations migrating from PeopleSoft have sophisticated Time and Labor configurations, complex work schedules, union rules, overtime calculations, shift differentials. Resist the temptation to recreate all of that complexity without first asking whether it still reflects how your business actually operates. Cloud migrations are a forcing function for process rationalization, and Time and Labor is a module where that rationalization often pays significant dividends.

Recruiting

Oracle Recruiting connects to Core HR for position management and onboarding, and to Talent Management for internal mobility. Its Phase 2 placement reflects those dependencies on Core HR structures being firmly established.

The business case for modernizing recruiting is often compelling for legacy Oracle customers. Modern candidate experience, mobile apply, AI driven candidate matching, and integration with external job boards are capabilities that EBS and PeopleSoft recruiting tools simply cannot match. The talent acquisition function is frequently one of the most eager constituencies for cloud migration.

Talent and Performance Management

Goal management, performance reviews, succession planning, and career development live in Oracle Talent Management. This module requires worker records in Core HR, compensation data, and it provides opportunity to pass certain data collected during recruiting and onboarding into employee talent profiles.

Organizations often under resource Talent Management implementation because it feels less operational than financials or payroll. But it sits at the center of how you develop and retain your workforce, which makes it strategically critical even if it is not a transactional engine in the same way Payables or Receivables is.

Enterprise Data Management

Oracle Enterprise Data Management deserves special mention because it cuts across the entire Phase 2 scope and frankly the entire program. EDM is Oracle’s platform for governing shared reference data: chart of accounts, cost centers, organizational hierarchies, project structures, and more.

As Phase 2 modules go live and the data model grows more complex, having EDM in place ensures that changes to master data are controlled, versioned, and distributed consistently across the application landscape. Organizations that skip EDM or defer it too long inevitably face data governance challenges that become increasingly expensive to remediate.

Think of EDM as the control tower for your enterprise data. Phase 2 is the right time to get it live and operational.

The Compounding Value of Phase 2

By the end of Phase 2, your organization is running a comprehensive modern ERP: full financials, procurement, core HR, talent functions, expense management, fixed assets, and projects, all integrated, all on a single platform, all feeding a unified data model. The AI capabilities embedded in these modules have been active since go live. Your users have six to twelve months of experience on the platform.

That is the walk phase complete. Next comes running.

Next in the series: Phase 3: Operational Depth and HCM as Full Source of Truth

Written by

Zubin Shah is a technology and transformation leader specializing in Oracle implementations, with a track record of delivering complex ERP programs across industries. As an Oracle ACE, he is recognized for his expertise, thought leadership, and contributions to the Oracle community. Zubin focuses on bridging the gap between business strategy and system execution—helping organizations modernize operations, scale efficiently, and unlock value from their technology investments. When he’s not leading implementations, he shares insights on ERP strategy, delivery best practices, and the evolving role of enterprise technology.

He holds a dual degree in Finance and Spanish from the McCombs School of Business at the University of Texas at Austin. Zubin began his career in consulting, working across several leading system integrators where he built deep experience spanning both sales and delivery—giving him a rare end-to-end perspective on how Oracle programs are positioned, sold, and successfully executed. Today, he serves as a Practice Director at Alithya, where he leads Oracle-focused initiatives and helps organizations navigate complex transformation efforts from strategy through execution.

This blog is a personal platform where Zubin shares perspectives on Oracle technology, ERP strategy, and the rapidly evolving role of AI in the enterprise software landscape. Drawing from real-world delivery experience, his writing focuses on practical insights—what works, what doesn’t, and where organizations should be investing as platforms continue to evolve. Topics span Oracle Cloud, implementation strategy, and how emerging technologies like AI are reshaping how enterprises operate, make decisions, and extract value from their systems.