SAP ECC to S/4HANA Migration: The Finance Director's Survival Guide

SAP ECC mainstream maintenance ends December 31, 2027. It creates a hard arithmetic problem: a typical large-enterprise brownfield conversion takes 18-24 months. If your company has not started by Q2 2026, you are already running out of runway. But between that hard deadline and wherever your organisation sits today lies an enormous volume of vendor noise, consulting firm upsell pressure, and genuinely wrong advice — often delivered with the confidence of people who get paid regardless of outcome (unfortunatelty...). This guide cuts through it from a Finance Director's perspective.

The 2027 Deadline in Plain Terms

SAP ECC 6.0 mainstream maintenance ends December 31, 2027. After that date, SAP stops delivering standard support packages, legal and regulatory updates, and new functionality for ECC. Extended maintenance at a 2% annual surcharge was available through 2030, but SAP has confirmed it will not be renewed.

The deadline has shifted before — from 2020, to 2025, to 2027. Do not assume it will shift again. SAP has backed itself into a corner commercially: its cloud revenue model depends on S/4HANA adoption. Every major SAP event since 2022 has reaffirmed the 2027 date without qualification.

The arithmetic is unforgiving. A brownfield conversion for a mid-to-large enterprise takes 14-24 months in a well-run programme. A company starting in Q3 2026 will not finish before December 2027 unless it compresses its testing phases — which is precisely where migrations fail. Companies with more complex landscapes (multiple ECC systems, IFRS parallel ledgers, high custom code volume) should treat their effective deadline as mid-2025, not end-2027.

What Changes for Finance: Four Technical Landmines

Generic migration guides treat Finance as one department among many. They consistently underestimate Finance-specific complexity. These are the four changes that determine whether your SAP ECC to S/4HANA migration succeeds or produces a first month-end close in permanent crisis mode.

The Universal Journal Restructures Your Data Foundation

In ECC, Financial Accounting and Controlling are separate modules with separate underlying database tables. Reconciliation between FI and CO is a known, periodic pain. In S/4HANA, every financial posting goes into a single Universal Journal (table ACDOCA). The reconciliation pain disappears — but the transition creates a different problem.

Every custom ABAP report querying BSEG, BKPF, COEP, COSS, or COSP will break. These are the core FI and CO line item tables. In a typical large enterprise ECC system, there are 3,000-10,000 custom programmes. Finance departments are the heaviest users. Budget 3-6 months of Finance report remediation as a non-negotiable line item in your programme plan — not as contingency, as planned work.

Finance users accustomed to SAP GUI transactions also face mandatory Fiori adoption. F-53 (manual payment), F-32 (clear customer items), FB60 (vendor invoice) all have Fiori equivalents, but the navigation logic is different and the user experience requires retraining. This is a change management cost that Finance teams consistently underestimate, particularly in organisations where Finance users have operated the same SAP GUI screens for 10+ years.

New Asset Accounting is Mandatory, Not Optional

S/4HANA requires migration to New Asset Accounting. Companies running classic Asset Accounting in ECC must convert all asset master data, depreciation areas, and historical postings. For organisations with large asset portfolios — manufacturing, infrastructure, real estate, healthcare — this is months of data validation work.

Companies with IFRS parallel ledgers face additional complexity: depreciation recalculation across parallel ledger values affects statutory reporting balances. The Finance Controller must be involved in project scoping from day one, not introduced at the testing phase. Discovery of parallel ledger discrepancies during user acceptance testing, rather than during design, is one of the most expensive problems a Finance go-live can face.

Profit Center Becomes Mandatory on All Postings

In ECC, profit center assignment was optional or manual in many configurations. S/4HANA enforces it on every posting. Organisations that never properly maintained profit centers discover gaps at go-live — typically during the first month-end close, when segment reports fail and reconciling items appear with no clear owner.

If your organisation uses IFRS 8 segment reporting derived from profit centers through substitution rules, the entire derivation logic must be rebuilt in S/4HANA. This is not an IT problem. It is a Finance design decision that requires Finance Director sign-off before the project enters its configuration phase.

Custom Code Volume is Always Underestimated

The SAP Simplification List — the document detailing what breaks in S/4HANA — is long. SAP's Custom Code Migration Worklist helps identify affected programmes, but the initial inventory is consistently wrong in the same direction: companies discover roughly twice the custom code volume initially scoped. This is a pattern identified across hundreds of implementations, not a rounding error.

Finance-specific programmes that break predictably: FI line item reports, CO reporting against deprecated tables, bank statement processing via custom BAPIs, intercompany invoice matching programmes, and any integration that reads directly from standard FI tables. These need to be catalogued, assessed, and remediated before go-live. There is no shortcut through this work.

The Cutover Finance Directors Must Own

The most underestimated risk in any S/4HANA programme is not the technical migration itself. It is the Finance cutover weekend and the first period-end close.

Go-live timing is non-negotiable for Finance: S/4HANA Finance go-live must happen at a fiscal year boundary, or at minimum a period boundary. A mid-year go-live creates parallel ledger reconciliation problems that are extraordinarily difficult to resolve while operating a live system under the pressure of a statutory audit.

The cutover weekend runs 3-5 days. During those 72-120 hours, all open items migrate, asset accounting runs overnight, and parallel ledger opening balances must be validated line by line. The Finance Controller must be present throughout — signing off on each stage before the next begins. The Finance Controller's role in cutover is not a cameo. It is the most important 72-hour stretch of the entire programme.

Professional implementations run 3 trial migrations before actual cutover. Each rehearsal validates data completeness, identifies data quality issues, and confirms the cutover timeline is achievable. If a consulting firm proposes fewer than three trial migrations, treat that as a red flag — not an efficiency measure.

The first period-end close in S/4HANA will take 2-3 times the normal close duration. Finance teams are simultaneously re-learning processes, navigating Fiori apps for the first time under production pressure, and running unfamiliar report paths. Build this explicitly into your programme plan. Do not accept external reporting commitments that fall within the first month post-go-live.

Greenfield vs Brownfield vs Selective: The Finance Decision Framework

Brownfield — The Right Default for Most Finance Departments

Brownfield converts your existing ECC system technically to S/4HANA. Historical financial data, configurations, and most customisations are retained. The chart of accounts is preserved.

For Finance, this is the correct default. Historical data stays in the system — critical for audit, statutory reporting, and tax. Finance processes change minimally. Go-live happens faster than alternatives. Typical timeline: 14-24 months for mid-to-large enterprise. Typical cost: EUR 3M-25M depending on landscape complexity.

The tradeoff: you carry all existing data quality issues into S/4HANA. Custom ABAP remediation is still required. Chart of accounts complexity does not improve automatically.

Greenfield — Highest Risk, Rarely the Right Choice

Greenfield builds S/4HANA from scratch using SAP Best Practices. Transactional history is not migrated — you maintain an ECC read-only system for 7-10 years for compliance access. All Finance users must be fully retrained, all reports rebuilt from scratch, every integration redesigned.

The clean-slate pitch has genuine merit in specific circumstances: when the ECC landscape is not technically convertible, when a company is consolidating multiple ECC systems and needs to rationalise the chart of accounts simultaneously, or when regulatory constraints require a defined accounting start date. These are demonstrable technical conditions, not strategic preferences.

A realistic greenfield for a large enterprise runs 24-42 months and EUR 15M-100M+. Finance Director rule: ask for the specific technical justification for greenfield on your landscape, not the strategic pitch about clean slates and future-proofing.

Vendor Tactics to Recognise and Counter

The RISE with SAP or Nothing Push

SAP's commercial priority is RISE with SAP. Sales reps may present it as the only viable path, downplaying Private Cloud Edition or on-premise options. The technical migration process is identical regardless of deployment model. The commercial model is a separate decision. Watch for TCO comparisons that omit hyperscaler hosting costs or exclude change management costs that RISE pricing does not cover.

Overscoped Projects

Large system integrators have financial incentive to broaden project scope. A brownfield conversion executable in 18 months frequently gets expanded into a 36-month transformation programme with parallel workstreams, Centre of Excellence setup, and process redesign that could happen incrementally after go-live — at a fraction of the programme-phase rate.

Counter-tactic: define the minimum viable migration. Phase 1 is the technical migration with minimal process change. Business transformation happens in subsequent phases, after the system is stable and the Finance team has recovered.

Compressed Timelines Under 2027 Urgency

With the deadline creating pressure, some vendors will propose 12-month programmes for landscapes that realistically require 20 months. This compression always targets testing phases. Compressed testing is where data migration errors, unremediated custom code, and undertrained Finance teams converge at go-live. The result is a first period-end close under permanent crisis.

Pre-Go-Live: What Finance Must Sign Off Before Any Go-Live Date

Financial data and balances: Trial balance in S/4HANA matches ECC to the cent after the final dress-rehearsal migration. All parallel ledger opening balances validated by the Finance Controller. Open AP/AR items migrated and reconciled with no unexplained differences. Asset accounting NBV per asset matches ECC values. Intercompany balances agreed across all legal entities.

Finance process readiness: Full period-end close simulation completed and signed off — not just a partial run, but an end-to-end close including all statutory reports: P&L, Balance Sheet, Cash Flow Statement. Tax reporting validated including VAT returns and withholding tax. Payment runs tested end-to-end including bank file formats. All critical custom Finance reports tested and signed off by Finance business owners, not IT.

People readiness: Finance team trained on Fiori apps for all key processes (AP, AR, GL, Asset Accounting, Controlling). Finance super-users identified and trained — at least one per department. Hypercare support plan in place for the first three months post-go-live. Rollback plan documented and rehearsed by the Finance team before cutover weekend.

If any of these cannot be confirmed, the go-live should not proceed. The cost of a delayed go-live is measurable and bounded. The cost of a failed go-live — a statutory deadline missed, an audit finding triggered by data migration errors, a Finance team that cannot close the first month — is not.

What Industry Benchmarks Show

Total implementation cost ranges by scope:

• Small to mid-market (1-3 ECC systems, under 500 Finance users): EUR 2M-8M
• Large enterprise (4-10 systems, 500-2,000 Finance users): EUR 10M-40M
• Global enterprise (10+ systems, multi-continent): EUR 40M-200M+

Services typically run 3-5x annual SAP license cost for brownfield, 5-8x for greenfield. Proposals that fall significantly below these ranges are almost certainly under-scoped for your landscape complexity. For context on how to justify these numbers to your board, see The Real Cost of Delaying Your SAP S/4HANA Migration.

From real programmes: a mid-market manufacturer at EUR 500M revenue completed a brownfield in 16 months for EUR 4.5M. The key overrun was Finance report remediation — three months longer than planned because the custom code inventory missed 40% of affected programmes. A large international group consolidating 12 ECC systems ran 36 months and EUR 45M; the critical path issue was intercompany reconciliation across 8 currencies during cutover. Both programmes succeeded, but both exceeded their original budgets in the same places that almost all programmes overrun: custom code and Finance data quality.

The five failure modes that account for the majority of troubled SAP ECC to S/4HANA migrations: Finance treated as a stakeholder rather than a programme team member; data quality underestimated at every phase; custom code volume discovered to be double the initial inventory; period-end close never simulated end-to-end before go-live; change management budget cut first when programmes run over budget — the cost that multiplies catastrophically when Finance users cannot operate the new system in the months after go-live.