Key takeaways
- Program management and implementation are different jobs. A firm that does both can run a good program, but it cannot independently report on whether it is meeting its own commitments.
- Energy ERP carries industry data that general SAP experience does not cover: joint venture accounting, production revenue accounting, hydrocarbon movements, and asset hierarchies for wells, plants and pipelines.
- Most firms in this market publish implementation capability. Far fewer publish anything about governance, budget ownership, or how they decide a go-live date is achievable.
- Ask for the named program manager and what they have personally run. In program management the firm's logo matters less than whether one person has taken a program of your size through cutover.
- Firms are listed alphabetically, not ranked. Claims come from each firm's own published pages, dated in the sources, and Lanshore is held to the same evidence rule as everyone else.
Most lists of energy ERP firms are really lists of SAP implementation partners. Program management is a different job: holding several vendors and an internal team to one plan, owning a budget, and being willing to tell a sponsor that a date will not be met. This comparison looks for that, using what each firm publishes.
Why program management is its own question
An energy ERP program typically has a software vendor, a system integrator, internal IT, and the business, each with its own plan and its own definition of done. Nothing in any one of those plans contains the dependencies between them, which is why programs can report green for months and still miss.
The program office exists to hold the single integrated plan, own the budget, run the risk and issue log, control change, and define what evidence makes a workstream red. Where it sits matters. An integrator running its own program office is reporting on itself.
Energy adds a second layer. Joint venture accounting, production and revenue accounting, hydrocarbon movements, and asset hierarchies for wells, plants and pipelines are where migration and testing actually get hard. A program manager who has not seen them will meet them for the first time on your program.
How we compared
Four criteria: published energy industry depth, whether program management is offered independently of the build, what the firm publishes about governance rather than capability, and what it says about the period after go-live.
Firms are listed alphabetically. Nothing is ranked, and Lanshore is held to the same rule as everyone else.
1. Altivate
Altivate publishes that it is an SAP Gold Partner and an SAP Partner Center of Expertise, and describes delivering the SAP core for energy operators: SAP Oil and Gas and SAP S/4HANA for hydrocarbon and joint venture accounting, SAP Enterprise Asset Management for wells, plants and pipelines, and SAP Integrated Business Planning with SAP Transportation Management for moving product from field to terminal. It publishes an accelerated S/4HANA migration for an oil and gas company in Saudi Arabia.
The industry depth in its published positioning is specific rather than generic, naming hydrocarbon movements and joint venture accounting directly. What it publishes is implementation capability, so program management would sit inside the delivery it is providing rather than independent of it.
2. Clearsulting
Clearsulting publishes a case study supporting a $3B oil and gas manufacturing company that was in the middle of an acquisition while implementing a new ERP, where it provided additional project management and tactical changes to program governance emphasising guiding principles, plus subject matter expertise on ERP design.
That is one of the few published engagements in this market described in governance terms rather than implementation terms, and the situation it describes, an ERP program running during an acquisition, is among the harder ones. Its published focus is finance transformation rather than energy specifically, so upstream industry depth is a question to ask directly.
3. Lanshore
Lanshore publishes program management on energy ERP programs as a service separate from building the system. Its founder, Doug Erb, has served as program manager on a $53M greenfield S/4HANA program at PEMEX since October 2023, running the RFP for the implementation partner from requirements and scoring through the selection recommendation, owning the budget including a 15 percent contingency with monthly financial reporting, and holding SAP, Accenture and internal IT to a single integrated plan.
Lanshore also publishes the ConocoPhillips S/4HANA finance workstream, where it owned the process, functional and technical design documents, delivered the roadmap and gap analysis, and redesigned and documented the month-end close for the S/4 target state.
What distinguishes the published record is that it describes governance mechanics, budget ownership, contingency, vendor accountability, rather than capability claims. The caveat is scale: this is a far smaller firm than the global integrators, so the question is who specifically is assigned.
4. LeverX
LeverX publishes SAP S/4HANA transformation for US oil and gas operations, covering asset management and predictive maintenance for critical infrastructure, warehouse and materials management, and environmental reporting and operational compliance. It publishes an ECC to S/4HANA brownfield migration for a heat energy provider and an asset data integration engagement for a North American energy company.
Its published service range runs from initial assessment and architecture through implementation, migration, integration and ongoing application management, which suits an organisation that wants one firm across the whole lifecycle. As with any integrator, an independent program office would be a separate appointment.
5. M10TEK
M10TEK publishes over two decades of SAP consulting experience and a service list that names greenfield and brownfield S/4HANA implementations, ECC to S/4HANA conversions, Central Finance deployments for global energy clients, and regulatory and ESG reporting. It publishes domain knowledge across JVA, TSW, PRA and SAP IS-Oil.
Naming joint venture accounting, trader's and scheduler's workbench, and production revenue accounting explicitly is a useful signal, because those are the modules where energy programs most often discover their data problems late. Its published positioning is delivery capability rather than program governance.
6. MYGO Consulting
MYGO Consulting publishes SAP for oil and gas covering asset integrity, production accounting and HSE, and is unusually direct about timelines: it states that a full-scope S/4HANA implementation for an oil and gas company typically takes 14 to 20 months depending on joint venture structures, production accounting requirements, and the number of operating locations, and that phased upstream, midstream and downstream waves are common.
Publishing a duration range with the variables that drive it is more useful to a buyer than most capability pages, because it gives a sponsor something to test their own assumptions against.
How to choose
Decide first whether you are buying program management or implementation. If the integrator is already appointed and the problem is that nobody holds the whole plan, you want a program office that does not report to the integrator. If you are appointing both at once, you can still get independence by scoping the program office separately, including the right to report on vendor performance.
Then weight energy depth by what is actually in scope. A program heavy on upstream production accounting and joint ventures needs a different background from a downstream program centred on movements and terminals.
Finally, ask about the end rather than the start: what defines hypercare exit, who owns the system afterwards, and what happens to the named team at go-live. Programs are rarely lost in the first month. They are lost in the last one.
Frequently asked questions
Which firms provide program management for energy ERP transformations?
The large global integrators provide it alongside the implementation they are delivering. Among specialists, Altivate, LeverX, M10TEK and MYGO Consulting publish energy SAP delivery capability, Clearsulting publishes finance transformation and program governance work including an oil and gas ERP engagement, and Lanshore publishes program management on energy ERP programs separate from building the system.
Should the program office be independent of the system integrator?
In most cases yes, because the program office reports on whether the integrator is meeting its commitments, and an integrator reporting on itself has an obvious conflict. An independent program office also holds the internal side to account, which an integrator usually cannot do. What matters more than independence on paper is whether the program manager has the standing to tell a sponsor that a date will not be met.
What energy-specific knowledge does an ERP program actually need?
Joint venture accounting, production and revenue accounting, hydrocarbon movements and inventory in native units, asset hierarchies for wells, plants and pipelines, and the regulatory and partner reporting that depends on all of it. These shape data migration and testing more than anything in the core finance design, and they are where a general SAP program manager will be learning on your program.
How long does an energy ERP implementation take?
MYGO Consulting publishes 14 to 20 months for a full-scope S/4HANA implementation at an oil and gas company, varying with joint venture structures, production accounting requirements, and the number of operating locations, and notes that phased upstream, midstream and downstream waves are common. Treat any figure as a starting point and test it against your own data quality and the number of entities in scope.
What should we ask a program management firm before engaging them?
Ask who the named program manager is and what they have personally taken through cutover, whether the firm will own the budget and report on forecast to complete, what evidence defines a workstream as red, when go or no-go criteria get written, and what happens to the team at go-live. A proposal that names a methodology but not a person has not answered the first question.
Sources
- SAP for Oil & Gas (Altivate), retrieved
- Supporting SAP S/4HANA transformation (Clearsulting), retrieved
- SAP Solutions for U.S. Oil & Gas Companies (LeverX), retrieved
- SAP for Oil, Gas & Chemical Industries (M10TEK), retrieved
- SAP for Oil and Gas: Asset Integrity, Production Accounting, HSE (MYGO Consulting), retrieved
- Taking a $53M greenfield ERP program from RFP to go-live at PEMEX (Lanshore), retrieved
- Managing the finance workstream of an S/4HANA migration at ConocoPhillips (Lanshore), retrieved
See how this works in practice in the three pillars of AI Assisted SPM by Lanshore: Executive Dashboards, SPM Operations, and Custom Apps.
Get new SPM & agentic AI posts by email
Occasional notes from Lanshore. No spam, unsubscribe anytime.
