Oracle has been systematically declaring end of support for Hyperion products since 2018, announcing EPM System 11.1.x end of Sustaining Engineering dates and steering every customer conversation toward Oracle EPM Cloud. The migration pitch is compelling in Oracle's telling: modern architecture, automatic updates, no on-premise infrastructure. What Oracle omits is the cost — typically £2M–£9M in professional services, 18–36 months of business disruption, and the near-certain loss of every calculation, form, and workflow your finance team has built over the past decade.
Third-party support (TPS) for Oracle Hyperion and EPM is the mechanism that breaks this coercion. Your Hyperion estate continues running — Hyperion Planning, HFM, Essbase, FDMEE, DRM, Disclosure Management — under fully supported cover at 62–65% less than Oracle's Software Update Licence & Support (SULS) fees. No re-implementation. No migration project. No EPM Cloud subscription.
Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
Oracle EPM Cloud is not an upgrade of Hyperion — it is a complete re-implementation. Customers who have attempted migration report 100% of custom Hyperion Planning business rules require rewriting in Groovy, HFM consolidation rules require manual reconstruction in FCCS, and Essbase outline structures must be rebuilt from scratch. Average professional services engagement: £2M–£9M over 18–36 months.
What Oracle Won't Tell You About EPM EOS
Oracle's Hyperion lifecycle communications are technically accurate and strategically selective. The headline dates — EPM System 11.1.2.4 Premier Support ended January 2021, Sustaining Engineering ends December 2026 for most components — are real. What Oracle does not explain is the legal distinction between end of vendor support and end of software operation.
Your Hyperion 11.1.2.4 Planning application will not stop working on December 31, 2026. The software is licensed in perpetuity. Oracle's obligation to provide patches, updates, and tax/regulatory content ends; your right to use the software does not. Third-party support fills precisely this gap — providing proactive monitoring, incident resolution, security patch analysis, and tax/regulatory updates (where applicable) for Hyperion environments that Oracle has abandoned commercially but which remain technically sound.
The same analysis that applies to Oracle Database TPS and Oracle E-Business Suite TPS applies equally to EPM: perpetual licence rights are durable, Hyperion on-premise remains operationally viable for a further 7–10 years with proper maintenance, and the EPM Cloud migration economics do not stack up for the majority of mid-market and enterprise EPM estates.
Hyperion & EPM Version Matrix — TPS Eligibility
| Product / Version | Oracle Premier Support | Oracle Status | TPS Available |
|---|---|---|---|
| EPM System 11.1.2.4 (Planning, HFM, Essbase, FDMEE, DRM) | Ended Jan 2021 | Sustaining Engineering (ends Dec 2026) | ✓ Full TPS |
| EPM System 11.1.2.3 | Ended Jan 2019 | End of Support | ✓ Full TPS |
| Hyperion System 9 (9.3.x) | Ended 2014 | End of Support | ✓ Full TPS |
| Essbase 21c / 19c (on-premise) | Active | Supported | ✓ TPS available |
| Hyperion Planning 11.x (standalone) | Ended Jan 2021 | Sustaining Engineering | ✓ Full TPS |
| HFM (Hyperion Financial Management) 11.x | Ended Jan 2021 | Sustaining Engineering | ✓ Full TPS |
| Hyperion DRM (Data Relationship Management) | Ended Jan 2021 | Sustaining Engineering | ✓ Full TPS |
| FDMEE / Oracle Financial Data Quality Management | Ended Jan 2021 | Sustaining Engineering | ✓ Full TPS |
| Oracle Hyperion Disclosure Management | Ended 2019 | End of Support | ✓ Full TPS |
What Third-Party Support Covers for Hyperion
Hyperion TPS provides a comprehensive support envelope across the full EPM stack. The scope is governed by what your estate actually contains, not a generic product matrix:
Hyperion Planning & Budgeting
- Business rule troubleshooting and defect resolution (Calculation Manager and legacy RTP rules)
- Web form rendering, data form hierarchy issues, approval unit workflow
- Planning application server performance, Java heap analysis, patching
- Workforce Planning, Capital Asset Planning, and Project Financial Planning modules
- Smart View integration — Excel add-in compatibility across Microsoft 365 release cycles
Hyperion Financial Management (HFM)
- Consolidation rule debugging (VBScript and custom logic)
- Entity, account, and custom dimension hierarchy support
- Intercompany elimination and equity pickup workflow
- Journal entry, phased submission, and sign-off workflow
- Financial Reporting Studio and Web Analysis integration
Oracle Essbase
- Outline structure maintenance, dimension build, data load rules
- Calculation script optimisation and parallel calculation configuration
- Aggregate storage option (ASO) vs. block storage option (BSO) guidance
- MaxL scripting, EAS (Essbase Administration Services), and Smart View
- Performance analysis — spool files, cache sizing, data fragmentation
FDMEE / Financial Data Quality Management
- Import format, location, and mapping maintenance
- Custom scripting (Jython) and event scripts
- Source system connectivity (EBS GL, SAP BW, flat file)
- Process flow debugging and data audit trail maintenance
Hyperion DRM (Data Relationship Management)
- Node property and derivation logic support
- Version and export maintenance for downstream targets
- Governance workflow and blend/compare functionality
EPM Cloud Migration: The Real Cost Oracle Doesn't Publish
Oracle's EPM Cloud pitch rarely includes a line-item for professional services, because doing so would make the migration economics transparent. Independent analysis of EPM Cloud migrations completed between 2021 and 2025 yields the following cost structure:
| Cost Component | Small EPM Estate (≤3 apps) | Mid-Size (4–8 apps) | Large (9+ apps / complex consolidation) |
|---|---|---|---|
| Oracle EPM Cloud subscription (annual, per user) | £180K–£320K | £380K–£750K | £850K–£2.2M |
| System integrator migration fees | £350K–£750K | £900K–£2.5M | £2.5M–£6M |
| Business rule / calc rewrite (Groovy) | £80K–£180K | £220K–£600K | £600K–£1.8M |
| HFM → FCCS consolidation rebuild | N/A | £200K–£500K | £500K–£1.5M |
| Data migration and reconciliation | £50K–£120K | £120K–£280K | £280K–£650K |
| User training and change management | £30K–£60K | £60K–£140K | £140K–£350K |
| Total 3-Year Cost | £1.2M–£2.2M | £3.2M–£7.5M | £8M–£19M |
| TPS Cost (3 years) | £185K–£340K | £320K–£620K | £620K–£1.35M |
The EPM Cloud migration economics are particularly poor for organisations with large Essbase BSO cubes (which require BSO-to-ASO migration or application redesign), HFM consolidation models with complex intercompany elimination logic, or bespoke FDMEE integrations to ERP systems. These are precisely the customers Oracle most aggressively targets with Sustaining Engineering pressure.
Sector-Specific Considerations
Pharma & Life Sciences — Financial Consolidation
Pharmaceutical groups with SAP ECC or Oracle EBS as their ERP backbone have typically built Hyperion Planning and HFM as the financial consolidation layer, often with currency translation rules and statutory reporting formats validated under internal controls frameworks (SOX, ICFR). Migrating to EPM Cloud triggers a full revalidation of the financial reporting process — typically treated as a material change to internal controls and requiring board-level sign-off. For pharma groups under GxP compliance requirements, any change to finance system infrastructure carries audit risk. TPS eliminates this trigger entirely.
Financial Services — Regulatory Reporting
Banks and insurers using HFM for IFRS 17 or Solvency II reporting have invested substantially in entity hierarchies, consolidation rules, and inter-company elimination logic. The FSA/PRA does not require migration to a specific platform — it requires that the platform produces accurate, auditable outputs. TPS satisfies this requirement. The financial services TPS analysis covers HFM regulatory reporting continuity in detail.
Manufacturing — Enterprise Planning
Discrete manufacturers using Hyperion Planning for multi-division budgeting and Essbase for product-line margin analysis face a classic EPM Cloud problem: Essbase BSO cube architectures with millions of cells cannot be lifted into cloud ASO without application redesign. The manufacturing sector TPS page covers the cross-system planning integration considerations.
Four-Profile Cost Model — Hyperion TPS Saving
The following model is based on typical EPM estate configurations. Oracle SnS is calculated at 22% of current licence value; TPS at 8% of licence value.
Moving to Hyperion TPS: The 5-Step Transition
The mechanics of moving an Oracle Hyperion estate to third-party support follow the same structure as any Oracle TPS engagement. The critical path item is the 30-day contractual notice requirement under Oracle's standard licence terms:
- Estate inventory — Identify all Hyperion products, versions, and licence types (NUP vs. Processor vs. Named Application User). Confirm perpetual licence ownership.
- TPS provider briefing — Share estate details for TPS provider technical assessment. Confirm coverage scope for all products including middleware dependencies (WebLogic, Oracle Database for repository).
- Oracle cancellation notice — Provide 30 days' written notice of support contract cancellation. Oracle will attempt retention; the decision is contractually yours.
- TPS onboarding — TPS provider installs monitoring agents, ingests support history, establishes SLA parameters. Typical onboarding: 15–20 working days for a full EPM estate.
- Perpetual licence verification — Confirm LMS (Oracle Licence Management Services) cannot raise a compliance claim post-cancellation. TPS provider assists with licence position documentation.
See the Oracle Support Cost Reduction white paper for a complete TPS transition planning guide, including the perpetual licence rights analysis and Oracle retention tactics to expect during the cancellation process.
Frequently Asked Questions
Will Hyperion stop working when Oracle Sustaining Engineering ends?
No. Your Hyperion licence is perpetual. Oracle's obligation to provide patches ends; your right to use and operate the software continues indefinitely. Third-party support ensures you have proactive monitoring, incident response, and security advisory without Oracle.
Can TPS cover Essbase BSO cubes with custom calculation scripts?
Yes. Custom Essbase calculation scripts, MaxL automation, and outline maintenance are all within TPS scope. TPS providers maintain engineers with deep Essbase experience covering BSO, ASO, and hybrid modes across all active versions.
What happens to Smart View integration with Microsoft 365?
Smart View compatibility with evolving Microsoft 365 release cycles is a live support issue for Oracle customers — including those on active Oracle support. TPS providers maintain Smart View compatibility analysis and workaround documentation as a standard deliverable.
Does TPS cover the HFM repository database (Oracle Database)?
TPS can be extended to cover the Oracle Database instances supporting the Hyperion repository. This is frequently included in EPM TPS engagements, providing a unified support envelope across the full EPM stack. See the Oracle Database TPS page for more detail.
How does EPM TPS work with SOX compliance requirements?
Third-party support does not affect SOX compliance. The Sarbanes-Oxley Act requires adequate internal controls over financial reporting, not specific vendor support arrangements. TPS providers document their support processes and maintain audit trails equivalent to Oracle's support activities.