SAP ECC to S/4HANA Migration: A Complete Guide for Finance Teams

1The Three Migration Approaches: Greenfield, Brownfield, and Bluefield

The first strategic decision in any S/4HANA migration is the approach. Each has different implications for timeline, cost, risk, and business disruption.

A Greenfield implementation starts from scratch: a new S/4HANA system is built with a clean configuration, and only required data (master data and open items) is migrated. This is the cleanest approach technically — it eliminates years of accumulated customizations and workarounds — but it also requires re-implementing all business processes, retraining users, and managing a much longer project timeline.

A Brownfield conversion (also called a System Conversion) upgrades the existing ECC system in-place to S/4HANA. Historical data, configurations, and customizations are preserved. The technical risk is lower and the timeline is shorter, but legacy technical debt is carried forward, and the Finance team still needs to adapt to significant changes in GL structure and processes.

Bluefield (or selective data transition) is a hybrid: certain parts of the business or legal entities migrate to a new S/4HANA system while others remain temporarily on legacy systems. This is complex to manage but allows a phased approach for large multinational organizations.

• Greenfield: clean start, longer timeline, best for organizations wanting to modernize processes
• Brownfield: faster, lower risk, preserves history — but carries legacy customizations
• Bluefield: phased migration by entity or business unit — most complex to manage

2What Changes in Finance: The Universal Journal

The most fundamental change in S/4HANA Finance is the Universal Journal (table ACDOCA). In SAP ECC, financial data was stored in multiple separate tables: FI line items in BSEG, CO line items in COEP, Profit Center Accounting in GLPCA, and so on. Reconciliation between these tables was a constant operational burden.

In S/4HANA, every financial posting — FI, CO, ML (Material Ledger), AA (Asset Accounting) — writes a single line to ACDOCA. There is one version of the truth. Reconciliation between FI and CO is eliminated because they share the same document.

For Finance teams, this means real-time reporting across all dimensions (cost center, profit center, segment, project) from a single source, without batch jobs or reconciliation runs. Period-end closing is significantly faster.

3Changes to General Ledger and Chart of Accounts

The New GL in ECC introduced parallel ledgers and document splitting, but adoption was inconsistent. In S/4HANA, these are mandatory architectural components — there is no 'classic GL.'

During migration, the chart of accounts must be reviewed and rationalized. S/4HANA requires that all balance sheet accounts are managed as open items or via the new reconciliation logic. Accounts used for CO posting must be defined as cost elements (now part of the GL account master in S/4HANA, replacing the separate cost element master in ECC).

The migration tool (SUM — Software Update Manager) handles the technical conversion of GL tables, but the Finance team must pre-work the chart of accounts cleanup, define the ledger strategy, and configure document splitting rules before the technical migration begins.

4Asset Accounting: The Biggest Technical Change

Asset Accounting in S/4HANA (called 'new Asset Accounting') is a complete redesign. In ECC, the asset subledger (tables ANLA, ANLZ, ANLC) was separate from the GL and required periodic reconciliation. In S/4HANA, asset postings write directly to ACDOCA in real time — there is no separate asset subledger reconciliation.

The depreciation areas work differently: in ECC, only area 01 posted to the GL in real time; others posted periodically. In S/4HANA, all areas that are relevant to accounting post in real time to the corresponding ledger.

Migration impact: any open depreciation differences between the asset subledger and GL in ECC must be resolved before migration. The migration cockpit will not proceed with unreconciled asset accounting.

• All APC and depreciation values are migrated to ACDOCA
• Depreciation keys and methods must be reviewed for S/4HANA compatibility
• T-code AW01N (Asset Explorer) remains, but internal tables have changed
• AJRW (fiscal year change) and AJAB (year-end close) logic is updated

5Data Migration: What Must Be Cleaned Up Before Go-Live

Data quality is the most common cause of S/4HANA migration delays. SAP provides pre-checks (via transaction SPRO and the Readiness Check tool) that identify blockers, but many data issues require manual resolution by the Finance team.

Open item management: In S/4HANA, certain accounts that were not managed as open items in ECC must be converted. This conversion process (using program FAGL_ACTIVATE_OP) must be run before migration and requires that the affected accounts have zero balance or that all line items can be cleared.

Business Partners: S/4HANA replaces separate customer and vendor master records with the Business Partner (BP) concept. Every customer and vendor must be converted to a BP before migration. The FLCU01 and FLVN01 programs handle the conversion, but duplicate BP records and incomplete master data must be cleaned up first.

Obsolete customizations: ECC allowed workarounds that are no longer valid in S/4HANA (e.g., posting to reconciliation accounts directly, certain substitution rules). These must be identified and removed before migration.

6How Finance Teams Should Prepare

Finance teams are not passive participants in an S/4HANA migration — they are critical stakeholders with specific pre-migration responsibilities.

Start with the SAP Readiness Check: this free tool analyzes your current ECC system and produces a report identifying custom code that needs adaptation, add-ons that need updating, and simplification items (deprecated features) that must be addressed.

Run the Finance-specific pre-checks: transaction FINS_RECON_BALNC checks for FI-AA reconciliation issues; FAGL_FC_TRANS checks foreign currency valuation data; FAGL_ACCOUNT_ITEM_CHECK validates open item accounts.

Upskill your team: the Finance team that manages the post-go-live S/4HANA system needs to understand the Universal Journal, the new closing cockpit (SAP Central Finance Closing), and the changed behavior of period-end programs. Training before go-live, not after, is what determines whether the Finance department can run independently from day one.

• Run SAP Readiness Check 2.0 to identify blockers early
• Clean up open items and resolve FI-AA reconciliation differences
• Convert customer/vendor masters to Business Partners
• Train Finance team on Universal Journal, new Asset Accounting, and S/4HANA closing process
• Review and rationalize the chart of accounts before technical migration