Selective, not comprehensive – Why companies shouldn’t take everything with them to S/4HANA

When companies discuss migrating to SAP S/4HANA, one assumption tends to dominate: the idea that the existing system must be transferred in its entirety. Processes, data, structures, and history –  everything should move over.
What sounds logical at first is, in practice, one of the most common mistakes in modern ERP transformations. Migration does not mean copying data. It means making conscious decisions.

The central question therefore is: What truly belongs in the new system – and what intentionally does not?

The Blind Data Transfer: A Costly Myth

Many ERP systems have grown over decades. As a result, data volumes have become enormous – from transactional data to technical leftovers.

Typical examples include:

• millions of transactions
• documents from many years of operations
• technical logs
• inactive business events
• outdated master data
• archival material that was never properly outsourced

Transferring all of this data into S/4HANA without evaluation introduces several risks:

1. Rising Costs

S/4HANA is based on in-memory technology – powerful, but expensive. Unnecessary data directly increases licensing and operating costs.

2. Increased Complexity

Large data volumes slow down testing, extend downtimes, and raise the risk of technical issues during migration.

3. No Real Fresh Start

If historical complexity is simply carried over, the new system will feel like the old one – just running on new technology. In short: Data volume is a critical factor for the cost, stability, and quality of any migration.

Not All Data Belongs in an Operational System

An ERP system is not an archive – it is the foundation for current business processes. Yet over time, data accumulates that no longer plays any operational role, such as:

• old purchase orders
• long-completed projects
• expired business transactions
• unused material numbers
• data from discontinued business units

The key question is not whether this data is important, but where it belongs.
In most cases, the answer is: in an external, compliant archive – not in the operational S/4HANA system.

This separation enables a system that supports processes instead of slowing them down.

Migration as an Opportunity – Not a Copying Task

A system transition offers a rare chance: to fundamentally question the existing data landscape.

Key questions include:

• Which data do we still use today?
• What remains in the system purely out of habit?
• What must be kept for compliance purposes – yet is no longer operational?

This shift in perspective changes everything.
The goal is no longer to migrate as much as possible – but to migrate the right things.

Selective Migration: The Pragmatic Middle Ground Between Greenfield and Brownfield

Migration is often presented as a binary decision:

• Greenfield = start from scratch
• Brownfield = fully adopt the existing system

But the most sensible path lies between the extremes: selective migration.

Its principles are straightforward:

• Operationally relevant data is migrated
• Historical or inactive data is archived
• Processes with modernization potential are redesigned
• Outdated logic is critically evaluated

The result: a system that is leaner, more stable, and future-proof – without losing business‑critical processes.

Selective Migration as a Key to a Clean Core

Many S/4HANA transformation strategies aim for a clean core: a system with clear structures, standard‑aligned processes, and minimal complexity.

But this is only possible through deliberate reduction.
A clean core primarily means:

• fewer data
• fewer custom implementations
• fewer dependencies

Selective migration is therefore an essential prerequisite for achieving a truly clean core. Only by leaving unnecessary legacy behind can a system remain lean in the long term.

A Lean System Is a Future-Proof System

The fewer unnecessary elements an S/4HANA system contains, the greater the benefits:

• higher system performance
• simpler operations
• more stable updates
• reduced testing effort
• increased innovation capability

Organizations that migrate selectively often report:

• shorter go‑live phases
• significantly lower costs
• fewer operational issues
• improved data quality
• stronger acceptance among business users

The real question, then, is not whether data should be reduced – but why it wasn’t done earlier.

The Crucial Shift in Perspective

A successful migration is not about completeness – it is about selection.

Selective migration is not a technical detail but a strategic decision. It determines whether S/4HANA becomes a truly modern ERP system – or merely an old system in new clothing.

Conclusion: Less Is More

The greatest opportunity in an S/4HANA migration lies in the willingness to let go. What is no longer needed does not belong in the new system:

• unused data
• outdated processes
• historically grown structures

Organizations that select before they migrate gain:

• speed
• clarity
• stability
• cost control

This is how a system becomes genuinely future‑ready – lean, understandable, and built for innovation.