The Real Cost of a Failed EPM Migration

A failed Oracle EPM migration rarely fails in week one. It fails quietly — in mapping tables nobody owns, in eliminations that "mostly" work, and in a close calendar that still ends on day twelve.

The sticker price vs. the ledger

Procurement compares license and SI day rates. Controllers live with:

• Parallel close for two (or four) quarters
• Manual bridges between legacy HFM/Essbase and Cloud
• Restatements when ownership or FX rules were underspecified

type MigrationCost = {
  licenses: number;
  integrator: number;
  parallelCloseMonths: number;
  opportunityCostPerMonth: number;
};
 
export function trueCost(c: MigrationCost) {
  return (
    c.licenses +
    c.integrator +
    c.parallelCloseMonths * c.opportunityCostPerMonth
  );
}

What “done” should mean

Done is not go-live. Done is three consecutive closes with:

1. Zero unexplained IC out-of-balances above materiality
2. FX CTA that reconciles to the treasury pack
3. A documented ownership chain finance will defend in audit

If your SOW does not define those exits, you are buying a go-live party — not a system of record.