The first migration timeline is often the least reliable document in an ECC program. It is usually created before anyone has measured the parts of the current landscape that will decide the route, scope, and sequence.
That is why SAP ECC to S/4HANA migration discovery belongs before detailed migration planning.
Discovery is often reduced to an inventory of interfaces, custom objects, database size, and business functions. Those facts matter, but the stronger outcome is decision evidence. A good assessment should show which findings can change the migration path, reduce scope, move the critical path, or require stronger business controls.
SAP’s own tooling supports this kind of evidence. SAP Readiness Check can identify relevant simplification items, provide high-level custom code analysis, assess add-on compatibility, and support sizing for a system conversion. SAP ERP Usage and Data Profiling adds a functional view of an ERP 6.0 system, covering configuration, active usage, master and transactional data, and application-relevant KPIs. SAP says its detailed profile runs 190 data collectors and can help assess transition complexity and the best-fitting transition approach.
The real value of ECC to S/4HANA discovery is the planning assumptions it can replace with evidence.
Which Discovery Findings Can Change the Migration Path?
An SAP migration assessment should challenge the preferred migration path before the organization invests in a detailed plan.
A company may begin with brownfield because continuity appears attractive. Discovery may show that the current organizational structure remains useful, most processes should continue, historical data needs to stay operational, and the custom estate is manageable. That strengthens the system-conversion case.
Different evidence can point elsewhere. Several ECC instances may need consolidation. Large portions of historical data may no longer need to move. The business may want to restructure company codes or redesign processes embedded in the current system.
SAP currently supports System Conversion, New Implementation, and Selective Data Transition as distinct transition paths. Lean Selective Data Transition can scope migration using company codes and time slices, allowing selected historical data to move instead of the entire source footprint.
This is why ECC to S/4HANA discovery should happen before teams lock the answer. Its first job is to determine whether the proposed path still fits the evidence.
What Does Custom Code Reveal About Scope?
Custom code is frequently used to estimate technical effort. Discovery should first use it to challenge scope.
SAP’s Custom Code Migration capabilities can identify code affected by S/4HANA changes and use collected usage data to identify unused ABAP code. SAP supports scoping based on that usage information and can create deletion transports for unused source code during system conversion.
That changes the question from “How much code must we remediate?” to “How much of this code still deserves remediation?”
A raw object count tells leadership very little. Some objects may be inactive. Others may support processes the business plans to retire. A smaller set may sit inside pricing, production, finance, or integrations and carry far greater business impact.
ECC to S/4HANA discovery should separate unused code, technically affected code, and business-critical code before those objects enter the delivery estimate. Otherwise, the migration plan prices the current estate before deciding what belongs in the future one.
What Should Data Discovery Establish Before the Timeline Is Set?
Data volume affects sizing, migration effort, downtime, reconciliation, and testing. Data relevance can affect the migration model itself.
This is where an S/4HANA readiness check needs to go beyond database size.
SAP ERP Usage and Data Profiling examines master and transactional data, important customizing settings, active components, and usage patterns. For selective transition scenarios, SAP Business Transformation Center can use that analysis as input to a Digital Blueprint that helps define data scope.
The planning question is direct: which data must remain operational in S/4HANA, which data only needs to remain accessible, and which data has no reason to enter the target environment?
These distinctions influence scope. Selected company codes may need migration while inactive entities remain behind. Poor master data may require remediation before it can be trusted in the target.
A useful SAP migration assessment turns those answers into scope and sequencing decisions before the timeline is presented as committed.
Why Do Integrations Change the Critical Path?
Interface counts are another weak planning measure.
An estate with many low-risk batch interfaces can be easier to move than one with fewer tightly coupled connections to manufacturing, warehouse, tax, banking, ecommerce, or logistics systems.
Discovery should identify business criticality, owner, technology, frequency, data exchanged, downtime tolerance, and the target-state requirement for each material integration.
The critical issue is often external dependency. An SAP development may take days while the connected application’s release cycle takes months. A third-party vendor may have a fixed testing window. A warehouse interface may only be validated during a specific operational period.
ECC to S/4HANA discovery should surface these constraints before the SAP timeline assumes integration remediation can happen whenever the project reaches that workstream.
This is where ERP transformation planning becomes more realistic. The critical path is shaped by the slowest dependency required for a safe move, as well as the SAP work itself.
How Does Process Readiness Affect Migration Risk?
Technical readiness can confirm that a system is convertible. It cannot decide which process variants should survive.
An S/4HANA readiness check should therefore be paired with business process review where active processes, local variations, custom dependencies, and mandatory S/4HANA changes need interpretation.
The assessment does not need to redesign every process before migration. It needs to expose decisions that could change configuration, custom code, testing, or change effort.
If six purchase approval variants exist across business units, the migration plan should know whether all six remain required. Standardizing some of them can change workflows, roles, test scope, and custom logic. A legally required variation needs to remain visible in the target design.
Process uncertainty becomes schedule uncertainty when those decisions are postponed.
How Should Discovery Findings Be Converted Into a Plan?
The most useful way to organize findings is by the decision they can change.
| Finding type | Planning question |
| Path-changing | Could this evidence make another transition approach more suitable? |
| Scope-changing | Can code, data, processes, systems, or interfaces leave migration scope? |
| Sequence-changing | Does this need earlier resolution because other work depends on it? |
| Control-changing | Does the issue require extra reconciliation, testing, governance, or business validation? |
This classification creates a cleaner bridge between ECC to S/4HANA discovery and delivery planning.
A simplification finding may be technically manageable while requiring an early Finance decision. An unused custom object may remove remediation and regression work. A data-quality issue may become an entry criterion for the first conversion rehearsal. An external integration may force testing earlier than expected.
Discovery findings become useful when they alter the plan.
When Is the Enterprise Ready to Start Migration Planning?
Detailed ERP transformation planning should begin when the major assumptions have evidence behind them.
Leadership should know which transition paths remain credible, which custom-code scope is real, which data must move, which integrations create external dependencies, and which process decisions still need owners. The program should also know which findings can affect cutover, reconciliation, or business continuity.
At that point, estimates have a defensible basis.
ECC to S/4HANA discovery makes the important uncertainty visible early enough to manage it. The stronger migration plan starts after the organization has established what it is moving, why it is moving it, and which conditions must be true before the move can proceed.
