Since mainstream maintenance for SAP ECC is scheduled to end, many organisations are planning their move to S/4HANA. One of the first questions finance and IT teams ask is what will happen to years of posted invoices, payments, goods movements and journal entries. Companies reviewing their ERP software in Singapore and elsewhere often find that the answer depends on the migration approach, the data model changes in S/4HANA and how long records must be kept for audit and tax purposes. Understanding these factors early helps avoid surprises during the project.
The Migration Approach Shapes the Outcome
How much history moves into S/4HANA depends largely on the path an organisation chooses. The main approaches usually handle historical data in ways like these:
- A system conversion, often called brownfield, converts the existing ECC system and generally keeps historical transactions.
- A new implementation, often called greenfield, usually loads master data, open items and balances, leaving older history behind.
- A selective data transition moves chosen company codes, years or business units while leaving the rest in the old system.
- Some organisations combine approaches, converting one entity while starting fresh in another.
Customer and Vendor Records Become Business Partners
S/4HANA replaces separate customer and vendor master records with a single Business Partner model. This affects historical transactions in ways such as the following:
- Every customer and vendor linked to past documents must be converted to a business partner before the system conversion.
- Duplicate or incomplete master records often surface during this step and need cleansing.
- Old documents stay linked to the converted records, so history remains traceable.
- Inactive records may be archived or blocked rather than converted.
Financial Data Moves Into the Universal Journal
Amidst most SAP S/4HANA vs ECC comparisons, the finance data model is one of the largest changes. During a conversion, historical financial data is restructured in several ways, including these:
- Separate ECC tables for general ledger, controlling, asset accounting and material ledger postings are merged into a single Universal Journal table.
- Reconciliation between finance and controlling is checked before conversion, as inconsistencies can stop the migration.
- Asset accounting history is converted to the new asset accounting model.
- Customer-specific fields and reports that read old tables may need to be adjusted.
Inventory Documents Are Restructured
Material movements are also stored differently in S/4HANA. When historical inventory data is converted, teams may encounter changes like these:
- Material documents are moved into a simplified data structure.
- Stock values are recalculated and compared before and after conversion.
- The material ledger becomes mandatory for inventory valuation.
- Long-running conversion steps may require planned system downtime.
Older Data May Be Archived First
Large volumes of historical data increase conversion time and database size. Before migrating, organisations often reduce the load through steps such as these:
- Archiving closed financial years and completed business documents.
- Deleting temporary data, logs and obsolete records.
- Setting clear rules for which years must remain directly accessible.
- Testing archive retrieval so auditors can still view archived documents.
Keeping Access to History Outside S/4HANA
When history is not carried forward, it still needs to remain available for reporting, audits and legal retention. In Singapore, businesses are generally required to keep records for at least five years, and organisations commonly preserve access through options like these:
- Keeping the old ECC system running in read-only mode for a set period.
- Moving historical data into a data warehouse or reporting platform.
- Using archive management or legacy retention tools.
Planning for the Records You Still Need
Historical data is often treated as a technical detail, but decisions about it affect auditors, finance teams and day-to-day reporting. Agreeing early on which records to convert, archive or retain elsewhere can reduce delays during the migration and keep the history you need within reach.
Contact Vanguard to discuss how your historical data can be handled during your S/4HANA migration.
