Migrating to SAP S/4HANA With 15 Months Left: What a Good Partner Asks Before Quoting

Migrating to SAP S4HANA With 15 Months Left

Fifteen months can seem like enough time for an SAP S/4HANA migration, until the questions behind the timeline are examined. With SAP Business Suite 7 core applications, including SAP ERP 6.0, approaching the end of mainstream maintenance in 2027, organizations need to understand what the remaining window actually allows.

That makes the questions asked before the quotation critical. A credible SAP partner should assess the business landscape, operational constraints, data, custom code and technical readiness before committing to cost or timelines. Without that assessment, estimates can quickly turn into change requests and delays.

This blog explores what partners should ask when migrating to sap s 4hana, from plant shutdowns and master data to testing, custom code and migration approach.

15 Months Is Not a Comfortable Timeline

The first question should not simply be, “When do you want to go live?” It should be, “What makes that date non-negotiable?” A board commitment, audit requirement, regulatory deadline, cloud contract or decision to move away from ECC can create different levels of urgency.

For SAP ERP 6.0 enhancement packages 6–8, mainstream maintenance ends on December 31, 2027. SAP also offers eligible customers optional extended maintenance through the end of 2030 at an additional cost. That additional window should not replace a clear assessment of what migrating to sap s 4hana will require.

A realistic plan works backward from go-live, covering design, custom code remediation, data migration, testing, training, cutover and stabilization. The sap project implementation life cycle is therefore critical. A timeline focused only on technical conversion will not reflect the full effort involved in migrating to s 4hana.

Decision-making speed, resource availability and ownership also matter. Unavailable process owners, unclear data ownership and delayed approvals can affect both timeline and cost. With only 15 months available, these dependencies should be understood before the quotation is finalized.

When Can the Business Actually Stop?

What Are Your Plant Shutdown Windows?

For a manufacturer, distributor or asset-intensive organization, downtime is an operating decision, not simply a technical detail. A partner should understand when plants, warehouses, shared services and sales operations can realistically go offline and which business processes depend on SAP during that window.

The discussion should cover production, procurement, invoicing, dispatch, payroll and quality, along with:

  • Plants, warehouses, company codes and legal entities in scope
  • Planned shutdowns, maintenance periods and fiscal closures
  • Production peaks and operational constraints
  • How long the business can operate without SAP
  • Whether a big-bang or phased deployment is practical
  • Manual fallback if cutover takes longer than planned

A 24/7 manufacturing operation requires cutover rehearsals, contingency planning and business continuity to be built into the estimate. If a suitable shutdown window is unavailable until later in the project, that constraint should be identified before the quotation is finalized. Otherwise, technical readiness may not translate into a practical go-live.

How Much Custom Code Are You Carrying?

Years of SAP ERP use often leave behind Z-transactions, reports, enhancements, interfaces, forms, workflows and ABAP developments. The key question is not how many custom objects exist, but which are still used, which support critical processes and which genuinely need to move forward.

A proper assessment should consider:

  • Usage data and business-critical custom objects
  • Critical plant and business processes
  • Statutory reporting, tax and pricing requirements
  • Batch management, quality, maintenance and production planning
  • Developments that can be retired, replaced with standard SAP functionality, remediated or extended through SAP BTP

This becomes particularly important when migrating to sap s 4hana, because assumptions about the custom-code footprint can materially affect the timeline and cost. A fixed remediation estimate without understanding the existing landscape is based on assumptions rather than evidence. The quotation should clearly define what is included in analysis, remediation, retirement, replacement and testing.

For organizations moving from sap erp to sap s 4hana, late discoveries can quickly create rework. A custom report supporting a critical production process can affect testing, user acceptance, training and cutover planning, making early assessment essential.

Is Your Master Data Ready for SAP S/4HANA?

Data migration is often treated as a technical workstream. In reality, it is a business-readiness exercise.

Material masters may contain duplicates. Business partners may have inconsistent records. Units of measure may not be standardized. Supplier information may be incomplete. Customer hierarchies, tax information and open transactions may also require significant cleansing before they can support the target system.

The partner should therefore understand the quality of the source data before estimating migration effort. For organizations migrating to sap s 4hana, data quality can directly influence the amount of preparation, validation and reconciliation required.

How Much Data Needs to Move?

The s 4hana implementation steps need to connect closely with the data migration strategy. A partner should establish what data is actually required and what can be retired rather than assuming everything in the legacy system needs to be transferred.

Key questions include:

  • Which master and transactional data is moving?
  • What historical data is actually required?
  • Which records need cleansing or deduplication?
  • How will source fields map to the target system?
  • What data needs to be retained for statutory, operational or reporting purposes?

The answers determine the effort required for extraction, transformation, mapping, validation and reconciliation. They also influence the wider sap project implementation life cycle, because data preparation and validation need to align with testing and cutover activities.

Who Owns Data Readiness?

SAP Activate provides a structured approach to learning, validating requirements and preparing the migration. Fit-to-standard workshops can help teams understand the target solution using preconfigured processes and sample data.

However, sample data is only a learning aid. The business must ultimately provide accurate data and take ownership of validation.

The SAP S/4HANA migration cockpit can support migration activities, but it does not replace decisions around data ownership, cleansing, mapping and validation. Those decisions remain business responsibilities and need named owners.

How Many Migration Cycles Will Be Required?

A good partner should establish:

  • Who owns data validation and approval
  • How many mock migration cycles are required
  • How migrated data will be reconciled and validated
  • Which data issues must be resolved before each migration cycle

These answers affect the estimate directly. Extensive cleansing or multiple mock migrations can add significant effort. With 15 months available, data readiness needs to be understood early enough to influence the migration plan rather than becoming a final-stage problem.

What Does the Testing Burden Look Like?

A technically successful conversion can still fail the business if critical processes are not tested properly. This becomes especially important when migrating to SAP S/4HANA Solutions involves multiple plants, business units, countries or integrations.

Testing should cover core processes such as order-to-cash, procure-to-pay, record-to-report, plan-to-produce, maintenance, quality, warehouse operations and intercompany transactions, along with integrations across MES, WMS, TMS, CRM, banking, tax, payroll, EDI and reporting.

Fit-to-standard workshops help define the business scenarios, data, integrations and test cases required. Before quoting, a partner should confirm whether test scripts and realistic test data exist, whether business SMEs are available, and what the entry and exit criteria are for integration testing, UAT, performance, security and cutover.

Testing effort depends on processes, integrations, business availability and migration cycles. It should therefore be included in the quotation, not treated as a later-stage activity.

Which Migration Path Fits the Business?

Not every organization should approach migrating to sap s 4hana in the same way. Before quoting, a partner should understand the current landscape, business objectives and target state to recommend the right approach.

  • System conversion: Retaining the existing SAP ERP environment, data and configuration while adapting it to SAP S/4HANA requirements.
  • New implementation: Building a fresh SAP S/4HANA environment focused on process redesign, standardization and harmonization.
  • Selective data transition: Moving selected data and processes where restructuring, consolidation, carve-outs or selective historical data are required.
  • rise with sap migration: Moving toward SAP S/4HANA Cloud Solutions, private edition using the RISE model and its cloud transformation services.

The choice should be based on business requirements, not simply on which option appears fastest. For organizations moving from sap erp to sap s 4hana, the existing landscape, data quality, customization and business objectives should shape the recommendation.

RISE with SAP does not remove the need to assess processes, custom code, integrations, data, testing, security and change management. A rise with sap migration still requires clarity on the starting point and desired outcome.

The migration approach also affects the quotation. A credible partner should explain how the recommended path affects scope, effort, dependencies, cost and timeline.

What Should Be Clear Before the Quote?

Before a proposal is finalized, the partner should understand the business and technical landscape, including organizational scope, plants, warehouses, countries, company codes, modules, integrations, data volumes, custom developments and third-party systems. Internal capacity matters too. The partner should know who owns each process, who makes decisions, how much time SMEs can commit and what SAP resources are available.

SAPinsider’s 2025 research found that 55% of organizations identified project duration as a major concern, compared with 37% in 2024. Duration becomes harder to manage when scope, dependencies and business readiness are unclear. These questions directly affect the sap project implementation life cycle, from planning through testing, cutover and stabilization.

A sound quotation should make assumptions, scope, risks, dependencies, data, testing, cutover, training and hypercare requirements clear. It should also identify exclusions and change-control conditions so the business understands where uncertainty remains. The lowest initial quote is not always the lowest project cost. Untested assumptions can lead to change requests, rework and delays.

A Good Quote Starts With Better Questions

With 15 months left, speed matters. But rushing into a quotation without understanding the business creates uncertainty that can appear as rework, additional cost or missed timelines. A good SAP partner should first ask: When can plants stop? How much custom code is critical? Is the master data reliable?

Testing, integrations, data and operational dependencies also need clear answers before a number is committed. These questions are not delays. They are part of the project. Migrating to sap s 4hana affects processes, people, data and operations, so organizations need to understand what they are committing to before implementation begins.

At Geschäft Formulae, we believe every SAP proposal should begin with understanding the business. We Deliver Trust by bringing clarity to scope, readiness, risk and execution before implementation begins. Connect Today.

FAQs

1. What should a partner assess before migrating to SAP S/4HANA?

Before migrating to sap s 4hana, a partner should assess the existing SAP landscape, custom code, master data, integrations, testing requirements, plant shutdown windows, business resources and target-state objectives. These factors help establish a realistic scope, timeline and implementation cost.

2. How long does migrating to S/4HANA typically take?

The timeline for migrating to s 4hana depends on the starting landscape, number of plants and business units, data quality, customizations, integrations, testing cycles and migration approach. A credible estimate should be based on these factors rather than a standard project duration.

3. What are the key S/4HANA implementation steps?

The s 4hana implementation steps typically involve planning, solution design, custom code assessment, data preparation, configuration or conversion, testing, training, cutover and stabilization. The exact sequence and effort depend on whether the organization chooses system conversion, a new implementation or selective data transition.

4. Should organizations choose system conversion or a new implementation?

The right approach depends on the existing SAP environment, business objectives, data quality, customizations and desired target state. Organizations moving from sap erp to sap s 4hana should assess these factors before deciding between system conversion, new implementation, selective data transition or a rise with sap migration.

5. What should be included in an SAP S/4HANA migration quotation?

A quotation should clearly define scope, assumptions, dependencies, custom code remediation, data migration, testing, integrations, cutover, training, hypercare, risks and exclusions. These elements form part of the sap project implementation life cycle and help prevent unexpected change requests, rework and cost increases.

Apply to attend

Give us a call or fill in the form below and we'll contact you. We endeavor to answer all inquiries within 24 hours on business days.