For many years, SAP Financial Consolidation (SAP BFC), SAP Business Planning and Consolidation (SAP BPC) and Oracle Hyperion Financial Management (HFM) have formed the foundation of financial reporting, planning and consolidation for many groups.
These platforms often remain at the heart of critical processes. However, their maintenance roadmaps now differ significantly. Some deadlines are approaching, while other solutions continue to benefit from long-term vendor support.
It is therefore essential to distinguish between these situations and prepare a roadmap suited to each environment.
SAP Financial Consolidation: maintenance is now scheduled to end in 2030
SAP Financial Consolidation, also known as SAP BFC, is still widely used for statutory consolidation, group reporting and the preparation of financial statements.
SAP now indicates that standard maintenance for SAP Financial Consolidation 10.1 will end on 31 December 2030. This deadline gives companies additional time, but it should not be interpreted as a reason to wait.
Replacing a consolidation solution involves far more than a technical migration. It requires organisations to address:
- consolidation scopes and methods;
- charts of accounts, flows and intercompany partners;
- currency translation and elimination rules;
- interfaces with ERPs and reporting systems;
- controls, reports and disclosures;
- the historical data required for comparative information;
- close procedures and related documentation.
The proximity of the deadline should therefore encourage companies to assess their BFC environment now and identify possible transformation scenarios.
SAP BPC: different timelines depending on the version
The situation for SAP BPC is more nuanced because maintenance dates depend on the platform and version in use.
For SAP BPC 10.1 for Microsoft, standard maintenance ends on 30 June 2026. SAP states that no further general extension is planned after that date and that support will become customer-specific.
For SAP BPC 10.1 on SAP NetWeaver and BW 7.5, standard maintenance is planned until 31 December 2027, with an extended maintenance option through the end of 2030.
BPC versions based on SAP BW/4HANA follow a different roadmap. SAP BPC 2021 is supported until the end of 2030 when combined with the corresponding BW/4HANA versions. BPC deployments embedded in SAP S/4HANA follow the lifecycle of the relevant S/4HANA release, with a horizon that may extend to at least 2040.
There is therefore no single “end date for SAP BPC”. Each company must first identify precisely:
- the BPC version in use;
- the underlying platform;
- the SAP BW or SAP BW/4HANA version;
- the level of support actually purchased;
- the functions covered: planning, consolidation, reporting or a combination of these uses.
This assessment will determine the appropriate strategy: upgrade, controlled temporary maintenance, progressive transformation or complete replacement.
Oracle HFM: no imminent end of maintenance for version 11.2
Oracle HFM must be considered differently. Contrary to a common misconception, Oracle has not announced the imminent discontinuation of the solution.
Oracle Hyperion EPM 11.2 benefits from the Continuous Innovation model. Oracle currently commits to continuing Premier Support for on-premise Hyperion applications until at least 2037, with an annual review that may extend this commitment further.
Companies using an older HFM version must nevertheless assess their position. Long-term support mainly applies to the 11.2 branch. A technical upgrade to a recent version may therefore be required to remain in an officially supported environment.
For HFM users, the question is not limited to the end of support. It also concerns:
- the cost of maintaining the infrastructure;
- the availability of technical expertise;
- the frequency and complexity of upgrades;
- integration with the information system;
- changing expectations regarding automation and user experience;
- the opportunity to move to a cloud solution.
Why should companies not wait until the final year?
An EPM migration is both a business project and a technology project. Waiting until a maintenance deadline is imminent reduces the available options and increases risk.
Planning ahead makes it possible to:
- compare several solutions without excessive time pressure;
- challenge historical processes instead of reproducing them unchanged;
- clean up obsolete master data and rules;
- rationalise interfaces and manual files;
- secure the migration of historical data;
- run several parallel closes;
- train administrators and users progressively;
- control the budget and the workload of finance teams.
The objective should not be a simple technical migration. Replacing a legacy platform can provide an opportunity to redesign the consolidation model, improve controls and bring statutory consolidation, management reporting and forecasting closer together.
What approach should be adopted?
1. Assess the current environment
Identify the installed versions, technical architecture, applications in use, interfaces, volumes, customisations and manual processes that depend on the solution.
2. Clarify future requirements
Requirements should go beyond simply reproducing the existing system: statutory consolidation, management reporting, budgeting, forecasting, simulations, disclosure management, ESG or integration with BI tools.
3. Consider several scenarios
Depending on the situation, the company may consider an upgrade, a controlled maintenance period, a progressive migration or complete platform replacement.
4. Secure data and business rules
The migration of historical data, consolidation entries, controls and calculation rules requires a precise strategy. It is also essential to define which information will remain accessible in the former system.
5. Plan a parallel-running phase
Several parallel closes make it possible to compare results, validate processes and secure go-live before the former solution is permanently retired.
Turning a constraint into an opportunity
Maintenance deadlines are not the same for SAP BFC, SAP BPC and Oracle HFM. SAP BFC now benefits from standard maintenance until the end of 2030. SAP BPC follows several timelines depending on its version and technical platform. Oracle HFM 11.2, meanwhile, continues to receive long-term support from Oracle.
In every case, the first step is to understand the exact position of the current environment. A roadmap prepared sufficiently early limits risk while transforming a technology requirement into a genuine finance transformation project.
Calisto Consulting supports finance departments from the assessment of their current platform through the selection, integration and deployment of their future EPM solution, including data migration, training and team support.
Sources: official SAP and Oracle maintenance schedules and documentation, consulted in August 2026.