Industrial pipeline valves at sunset
All case studies
Case StudyChange Management

From Six Platforms to One

How a publicly traded midstream energy operator consolidated six legacy ERP platforms into a unified Oracle Cloud environment — and delivered every phased go-live on time through a global pandemic.

ClientPublicly traded midstream energy operator
FocusOracle Cloud ERP & EPM finance transformation
Timeline22-month engagement, 5 phased go-lives

Growth by acquisition is a strategy. It is rarely a system architecture. For one large midstream energy company — a publicly traded operator with billions in revenue, hundreds of legal entities, and accounting hubs in two states — every deal closed had added another ERP, another sub-ledger, another spreadsheet, and another version of the truth.

By the time the executive team engaged Taligens, the back office was running six platforms in parallel: Oracle E-Business Suite, Microsoft Dynamics AX, Hyperion HFM, a standalone planning tool, a legacy invoice imaging system, and a homegrown BI environment. Month-end was a logistical exercise. Real-time visibility into cash, payables, and operating performance was effectively impossible.

Twenty-two months later, the company was operating on a single Oracle Cloud platform spanning fourteen-plus modules, one rationalized chart of accounts, a unified master-data governance model, and a procure-to-pay workflow powered by automated OCR. We delivered it through a global pandemic and a parallel internal reorganization — without missing a phased go-live.

01

The Starting Point

The symptoms read like a textbook of legacy ERP debt: a month-end close that spanned multiple consolidation tools and depended on offline extracts; no automated segregation-of-duties controls; reconciliations performed manually in spreadsheets; no formal source-to-pay process; fixed-asset tracking unable to proactively manage capital authorizations; and budgeting locked inside Excel templates with no driver-based modeling capability.

Thirty-plus legal entities. Multiple chart-of-account variants inherited from each acquisition. Duplicate vendor and customer records across business units. SOX documentation that consumed entire weeks per cycle.

The next acquisition was already being negotiated. The company needed a platform that could absorb new entities into existing structures — rather than reshape itself around each deal. The brief was clear: consolidate, rationalize, and build for the future.

6 → 1Platforms consolidated
14+Oracle Cloud modules delivered
22 mo.Kickoff to final go-live
0Days slipped from plan
02

The Approach

We structured the transformation across four phases — core financials, consolidation and reconciliation, and capital projects and planning — with explicit quality gates between each. The methodology held three principles without exception: configure, don't customize; review, fix, build, repeat; and show, don't tell. Every storyboard, every control point, every training session walked through a live system — never a static deck.

Each phase ran through three instrumented control points — at 30%, 70%, and 99% build completion — tied to documented test scenarios. By Phase 1 alone, approximately 160 accounts-payable test cases had been executed across supplier setup, invoice entry, OCR scanning, intercompany flows, bank interfaces, and payment processing, each mapped to a requirements traceability identifier.

When the pandemic struck one week before the first control-point launch, we compressed an eight-week pilot into four, redistributed scope across the next gate and UAT, re-issued every invitation within 48 hours, and moved the program to a hybrid model. The Master Test Plan, Issue Tracker, and daily summary cadence ran exactly as planned across both geographies. The pilot hit its objectives. The broader program did not slip.

03

Three Workstreams That Carried the Change

Stakeholder Engagement

A 216-Name Register, Actively Managed

A power-and-influence stakeholder map tracked 216 names from advocate to blocker. High-influence leaders had documented engagement plans, named escalation paths, and individual one-on-one cadences. Identified blockers had targeted mitigation plans built on proof and inclusion. Several became the program's strongest internal advocates by go-live.

Change Communication

A Brand, a Newsletter, and a Persistent Training Library

The program ran under its own brand identity from kickoff through hypercare — a monthly newsletter, a dedicated employee inbox, daily summary decks during control-point windows, and a full go-live communications package. Fourteen-plus quick guides, instructor-led decks, and recorded walkthroughs lived in a central repository, accessible to every employee, indefinitely.

Design Discipline

Chart-of-Accounts Rationalization as a Strategic Investment

Multi-month workshops collapsed several legacy chart-of-account variants into a single forward-compatible structure, with an alternate hierarchy preserved for regulatory reporting. Enterprise Data Management was configured to auto-synchronize changes across general ledger, consolidation, and planning — a design that has paid for itself across every subsequent acquisition.

Two operating hubs. A parallel corporate merger. Thirty-plus legal entities. A team learning to work remotely in the same month the project launched. None of it was theoretical. All of it shipped.
Taligens Field Report
04

Four Phases to a Single Platform

The program was structured for resilience — each phase self-contained, each control point a formal decision gate, and the overall design built to absorb disruption without losing the structural discipline that made the work succeed.

  1. Phase 0 — Business Process Design

    Three months of current-state discovery and future-state workshops across every in-scope process. Storyboard sign-off as the formal user-requirements baseline. Every requirement validated against a live prototype before build began.

  2. Phase 1 — Core Financials & Procurement

    Ten months covering General Ledger, Accounts Payable and Receivable, Cash Management, Fixed Assets, Procurement, and automated invoice processing with OCR. Two iterations of unit testing followed by user acceptance testing, each test case mapped to a requirements traceability identifier.

  3. Phase 1.1 — Consolidation, Reconciliation & Master Data

    Five and a half months delivering Financial Consolidation and Close, Account Reconciliation with Transaction Matching, and Enterprise Data Management — the governance platform that automatically synchronizes the rationalized chart of accounts across GL, consolidation, and planning.

  4. Phase 2 — Capital Projects, Full Procurement & Planning

    Eight months delivering driver-based enterprise planning, Project Costing tied to capital authorizations, and the expanded procurement footprint. The second master-data release completed the unified data governance model.

05

What the Platform Delivered

By the end of the program, the company was operating on a fundamentally different foundation — one system, one chart of accounts, one source of financial truth across every operating segment.

Consolidation

Six platforms replaced by one unified source of truth

A single Oracle Cloud platform spanning every operating segment replaced six legacy systems, with a rationalized chart of accounts and real-time drill-through from balances to source transactions replacing the offline-extract dependency.

Governance

Automated controls and an audit-ready close

Embedded segregation-of-duties controls, integrated reconciliations with end-to-end preparer-and-reviewer signatures, and configuration monitoring replaced manual SOX reconstruction — and a faster, more auditable month-end replaced the multi-tool close.

Planning

Driver-based forecasting connected to actuals

Rolling forecasts with scenario modeling replaced static spreadsheet planning. Enterprise Data Management keeps chart-of-accounts hierarchies synchronized across GL, consolidation, and planning automatically — and adapts to new acquisitions without manual intervention.

M&A Ready

A platform engineered to absorb acquisitions

The architecture was designed to bring new entities into existing structures rather than reshape the platform around each deal — a design validated by every acquisition the company has completed since go-live.

Is this kind of engagement right for your organization?

This work is built for organizations facing the following conditions:

  • You have grown by acquisition and are operating multiple ERPs or sub-ledgers in parallel.
  • Month-end close depends on offline extracts, spreadsheets, or manual consolidation across systems.
  • Your chart of accounts and master data are inconsistent across business units or acquired entities.
  • You are planning a major platform migration and need the change management to match the technical ambition.
  • You need your workforce prepared and capable on day one — not surprised by the system they find.
Next step

Ready to turn a fragmented estate into a single source of truth?

Let's talk about how to structure a transformation that sticks — technically and organizationally.