Beyond Go-Live: How CFOs Drive ERP Transformations That Last

ERP transformation has officially moved beyond the IT bucket and into the CFO’s job description.

In 2026, that shift is easy to see. Half of enterprise CFOs say using digital tools to transform finance is their top priority for the year, and 87% say AI will be extremely or very important to finance operations. At the same time, Deloitte says 43% of organizations are now investing in ERP, up from 35% in 2024. Finance leaders are being asked to modernize fast, cut costs, improve decision-making, and build a stronger foundation for AI, all at once.

It all sounds exciting until exciting until the project calendar starts slipping, the business case gets fuzzy, and the transformation slowly turns into a very expensive exercise in status meetings.

You can see that shift in the broader conversation around ERP modernization. The focus has moved well beyond software selection and into harder questions around scope creep, tax exposure, integration choices, outages, and cybersecurity. That alone says a lot. ERP transformation is no longer being treated like a system upgrade. It’s being treated like a business risk issue.

The hard truth is that ERP transformations rarely stall because the technology is inherently flawed. They stall because companies try to modernize the system without fully redesigning the way work, data, decisions, and accountability move around it.

Stop treating ERP like a software project

A surprising number of ERP programs start with the wrong question.

Teams ask which platform has the right modules, the right roadmap, or the right AI story. Those questions matter, but they come too early. The better question is simpler: what business problems are we trying to fix, and what has to change in daily operations for this investment to pay off?

When that answer isn’t clear, the project starts absorbing every unresolved issue in the business. Old process exceptions get carried forward. Reporting disputes get buried under migration work. Approval bottlenecks are labeled “phase two.” Data cleanup gets delayed because the team is already overwhelmed. Before long, the ERP program becomes a holding pen for problems nobody really owns.

Gartner’s view is blunt: more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals, and as many as 25% will fail catastrophically. Gartner also says 75% of ERP strategies are not strongly aligned with overall business strategy. That’s not a software problem. That’s a leadership and design problem.

The stall starts before go-live

Most ERP trouble doesn’t begin with some dramatic outage. It starts quietly.

It starts when finance and operations use different definitions for the same metric, when IT thinks a workflow is “covered” because the field exists in the system, and when data conversion gets treated like a technical task instead of a business accountability exercise.

Recent reporting on fragmented finance environments points to the same problem. Teams may invest heavily in reporting and automation yet still fall back on offline spreadsheets and manual reconciliations to validate key metrics. In those situations, executives spend time proving the numbers are right instead of using them to make decisions. It’s the kind of drag that makes ERP projects look successful on paper and frustrating in real life.

This is why so many finance teams feel disappointed after “progress.” The new platform may be live, but the old habits are still everywhere.

Real-world ERP problems have very little to do with screens

One of the clearest examples comes from McKinsey’s 2025 interview on getting an ERP transformation back on track. In the case of METRO AG, the program had been running for almost five years, the budget had already been spent, and only a single pilot entity had launched. The executive who stepped in to help fix it said the turnaround depended on addressing issues that had nothing to do with technology.

The example resonates because it feels familiar.

ERP projects get framed as platform decisions, but the real breakdowns show up somewhere else:

• Ownership is unclear across finance, IT, tax, procurement, and operations.
• Business rules were never standardized in the first place.
• Approval paths still run through inboxes and tribal knowledge.
• Data definitions shift by team, entity, or geography.
• Reporting logic goes unchallenged because quarter-end is coming.

By the time those issues surface in testing, the project is already carrying too much weight.

People problems are transformation problems

There’s another reason these initiatives slow down: the people doing the work are already stretched.

Recent research shows that more than 60% of finance leaders now see talent acquisition and retention as their top priority, ahead of both regulatory compliance and technology investment. At the same time, demand for finance professionals with “fusion skills,” or the ability to combine core finance knowledge with data and technology skills, has jumped 80%, while CPA exam candidate volumes have fallen by nearly 20% since 2019. Finance teams are being asked to modernize in a market where qualified talent is harder to find and the work keeps getting more complex.

ERP transformations place those demands on the same people already closing the books, answering audit questions, supporting the business, and managing exceptions no system has cleaned up yet.

So when a project stalls, the issue isn’t always resistance. In many cases, the team is already stretched thin, carrying too much change at once, and trying to figure out how to keep the business moving while the work gets rebuilt.

What CFOs can do differently

Stalled ERP transformations leave clues early. CFOs who know what to look for can change course before the project becomes a cautionary tale.

Anchor the business case in operating pain

Don’t let the value story stay vague.

“Modernization,” “efficiency,” and “better data” sound good in steering committee decks, but they don’t help teams make tradeoff decisions when scope gets messy. Tie the business case to a small set of operational outcomes that matter in plain language: faster close, fewer manual reconciliations, better working capital visibility, cleaner approvals, lower exception volumes, less time spent validating reports.

It creates a sharper filter for what belongs in scope now and what can wait.

Shrink the first win on purpose

Big-bang thinking still causes a lot of unnecessary pain.

The smartest ERP programs don’t try to prove everything at once. They choose a domain where the pain is visible, measurable, and worth fixing. That might be reporting, procurement, document-heavy approvals, or finance workflows with too much email and spreadsheet dependency.

The same lesson applies here: start with one domain where the problem is both visible and impactful, then build trust through measurable results. That’s far more effective than trying to tackle everything at once and hoping adoption catches up later.

Put controls and workflow on the critical path

This is where many CFOs can change the outcome.

Projects often spend months on architecture, configuration, and migration while workflow, control readiness, and exception handling get pushed down the list. Then the team reaches go-live and discovers that the system may support the intended workflow, but real life still runs on side channels.

Finance leaders are waking up to a broader risk picture, from hidden tax exposure after go-live to the balance-sheet impact of outages and cyber incidents. Risk doesn’t wait politely until implementation is finished. It shows up anywhere governance and workflow design fall short.

For finance, that means approval logic, document access, audit trails, exception handling, and payment-related controls should be treated as core design decisions, not cleanup items.

Run finance and IT as one decision team

ERP programs stall when finance and IT are aligned in theory but separated in practice.

CFOs don’t need to micromanage configuration, but they do need to make sure business decisions are being made in the same room as technical ones. Finance has to be present when teams define data ownership, workflow rules, reporting logic, approval thresholds, and integration priorities. Otherwise, the project ends up technically complete and operationally frustrating.

Current ERP thinking is shifting toward modularity and orchestration for the same reason. Deloitte argues that modern ERP needs a leaner, more agile approach that protects the core while allowing flexibility around it. McKinsey makes a similar point: fragmentation often happens when new capabilities are layered on without connecting end-to-end processes, data, people, and technology.

Measure adoption, not just milestones

A project plan can look healthy while the business is quietly struggling.

Go-live dates, completed sprints, and migrated records still matter, but CFOs also need a clearer view into how work is actually happening after launch. How many exceptions still require manual intervention? How many approvals still happen outside the intended path? How often do teams export data just to get answers they trust? How many reconciliations still depend on tribal knowledge?

Those signals show whether transformation is truly taking hold or whether old workarounds are still running the show.

The bigger lesson

ERP transformations stall when companies mistake the system for the strategy. The technology matters, but the real transformation happens in the workflows, controls, and decisions surrounding it. That’s why smart CFOs look beyond the ERP itself and focus on the process gaps that keep slowing finance down.

onPhase helps finance teams bring more structure and visibility to those workflows without waiting for every phase of ERP change to be perfect. For a closer look at one of the most common disconnects ERP alone doesn’t fix, read Why Your ERP Isn’t Solving Your Accounts Payable Problems.

Because the real test isn’t what changed in the system. It’s what changed for finance.