Table of contents
At a glance
What drives the effort and cost of SAP validation?
Start with the implementation path, business processes, configuration and custom developments. Add access controls, interfaces, data migration, test environments, deviations and handover to operations. Separate the implementation partner's technical work, external validation effort and internal QA and process-owner time. Apply agreed rates once those work packages have been scoped.
- A module name alone does not provide a reliable basis for a validation estimate.
- Conversion, new implementation and selective data transition each put the emphasis on different tasks.
- Include custom developments, roles and historical data explicitly in the estimate.
- Project work and recurring change assessments need separate budget lines.
Which SAP decisions drive validation effort?
SAP describes several transition paths for S/4HANA Cloud Private Edition. A new implementation, a conversion of an existing ERP system and a selective data transition each have a different starting point. For CSV, decide which existing processes and evidence remain suitable and which configuration or transfer activities require fresh evidence.
Describe the edition, operating model, sites and intended use. An SAP validation project can range from a limited change to a system replacement. Define the data and process boundaries before estimating person-days. Use the comparison to identify the work your implementation requires.
Sources: [1]
What drives effort across custom developments, roles and data flows?
Use the matrix to turn technical and business details into work packages. For each row, record what you already know, the open question and who will contribute. Give a reason for excluding a row and record any unknown as a planning assumption.
One SAP module can involve several of these factors. Equally, suitable shared evidence can cover several process variants. Check the work involved before assigning an amount to each module or site.
| Effort driver | Question to ask | Possible work |
|---|---|---|
| Implementation path | What will you configure from scratch, convert or transfer selectively? | Define the scope of new evidence, regression tests and data transfer |
| Process variants | Which sites and workflows differ? | Assess the common baseline and site-specific additions |
| Configuration | Which settings influence quality decisions? | Link the expected rules and configuration version to suitable tests |
| Custom developments | Which custom logic will change? | Investigate affected functions and dependencies |
| Authorisations | Who can change relevant data or status values? | Check the role design and access restrictions |
| SAP transports | How will the tested version reach the target environment? | Link the change and its environment to the version actually deployed |
| Interfaces | Which data and error scenarios matter? | Check mappings, messages and the expected business outcome in the target system |
| Migration | Which datasets and transformations does the migration cover? | Plan data transfer, reconciliation and exception handling |
| Historical data | Where can users access information that will not be migrated into active use? | Plan archiving and decommissioning tasks |
| Tools and environments | Which tests and reference data are suitable for use? | Assess suitability, data preparation and differences between environments |
| Findings and retests | Who will fix the technical issue and who will retest it? | Assign responsibility for resolving findings and repeating tests |
| Operation | Who evaluates releases, roles, and subsequent changes? | Plan the handover and recurring work separately |
When can we confirm the effort?
We confirm the estimate after scoping, once we understand the project's scope and objective.
Budget separately for validation, implementation and internal contributions
The implementation partner describes configuration and technical changes. The validation team assesses the resulting requirements and the evidence needed. Process owners supply the expected business rules, reference data and decisions. However your organisation assigns these roles, each task should be visible in the budget.
Sections 7.14–7.15 of EU GMP Chapter 7 address the allocation of responsibilities for outsourced GMP activities. The budgeting method here is our own. Check whether the quotation covers defect correction, data cleansing and retesting. Assessing the business impact of a finding and changing the software are different services.
Sources: [2]
Check what existing global evidence covers
Suitable existing evidence can support local activities. Check the system version, configuration, environment and processes covered. Annex 11 section 3.3 addresses the assessment of documentation supplied with commercial off-the-shelf software against user requirements. Section 4.1 links the extent of documentation to the risk assessment.
Estimate the assessment and any additional evidence separately. A centrally executed test might establish that a shared workflow works while leaving a local role restriction untested. Whoever assesses coverage needs access to the execution record. Use the linked guide to assess the SAP partner, then identify the tasks that partner will perform.
Sources: [3]
Worked example of external and internal person-days
Assume that a system conversion affects one site with three identified quality-relevant workflows, one LIMS interface and a group of custom developments.
Multiply 24 external days by the agreed day rate. Estimate internal capacity separately. Licences, technical implementation and separately contracted supplier services are additional where applicable. Check whether a partner already covers a task before counting it again.
In this example, an additional SAP transport changes the status logic under test. Assume two more external days and one more internal day for impact assessment and the affected retests. The totals become 26 external and 21 internal days. The status change explains the additional work. Your own project needs a separate estimate.
| Work package in the example | External CSV days | Internal days |
|---|---|---|
| Define which processes and evidence are in scope | 3 | 2 |
| Assess affected custom developments and roles | 5 | 4 |
| Address LIMS mapping and data transfer questions | 4 | 3 |
| Run suitable tests and reconcile the results of the run | 7 | 6 |
| Evaluate findings and results | 3 | 2 |
| Hand over operations and evidence | 2 | 3 |
| Total | 24 | 20 |
Plan how to retain historical data and budget for it
Decide which historical information users need in the live target system and which can remain accessible in a suitable archive. Migrating all historical records creates different tasks from migrating a limited active set and archiving the rest. The chosen approach must meet users' actual information needs.
Consider data mapping, reconciliation of relationships, search functions and the cost of keeping the legacy environment running after the initial export. Annex 11 section 4.8 addresses the value and/or meaning of migrated data. Sections 7 and 17 cover data availability and archiving. The SAP ECC guide explains how to demonstrate continued access after shutdown.
Sources: [3]
Budget for recurring SAP work after go-live
Assess relevant changes in operation, including transports of custom logic, changes to roles, platform moves and releases. Annex 11 section 10 addresses change control and section 11 addresses periodic evaluation. The impact of the change determines the scope and evidence needed.
Separate planned, recurring activities from work triggered by individual changes. For a cloud service, consider the supplier information available and the tests you can run yourself. Managing your own system landscape may require different work. The operating model alone does not establish a general premium or a fixed saving.
Sources: [3]
When the basis for the estimate changes
Keep a short assumptions register. For each open business question, record the planned approach and what would trigger a new estimate. A flat contingency allowance gives little information about these dependencies.
Distinguish additional work from waiting time. If a test environment is unavailable, the schedule may slip without adding the same number of person-days. Agree the pricing model, customer contributions and scope-change rules in the contract. The fixed-price guide explores these commercial decisions.
| Assumption | What the estimate assumes | When to reassess |
|---|---|---|
| One site follows the central workflow | The identified local additions | An additional site-specific rule is needed |
| Historical data remain accessible in a suitable archive | Only a limited set of data moves into active use | The archive does not provide the required context |
| The configuration is stable for testing | The planned scope of testing | A new transport affects status logic that has already been tested |
| Test data and reviewers are available | Planned sequence | An input or decision is delayed |
Estimate SAP validation work by work package
A useful estimate connects the process questions and data with the implementation work and the contribution your team can make. We discuss which assumptions already hold and which parts of the assignment still need to be defined.
Start with our computer system validation guide →
We discuss why you are getting in touch, where your system stands and which decision comes next.
Project experience and collaboration
Break SAP validation costs down by work package
We review the SAP plan with process owners, QA, IT and the implementation team. We link validation work to the actual changes and record which assumptions still affect the budget. Existing evidence can make planning easier. Unclear interfaces or historical data may need attention first. The estimate separates external services from your team’s contribution so the same task is counted once.
FAQ on SAP validation costs
Can we use a standard validation estimate per SAP module?
A module name tells you little about intended use, roles, customisations or data flows. Several modules can support one business process. Define the deliverables and effort drivers before assigning a price or a number of days.
Why can the effort differ between conversion and a new implementation?
It depends on the existing evidence you can use, processes you retain or configure from scratch, technical changes and the data strategy. A conversion does not automatically mean less CSV work. Ask the partner to substantiate that assumption using the actual functions and evidence.
Sources: [1]
How do custom developments affect the budget?
Consider their effect on the process, planned changes, dependencies and existing evidence. Even a small code change can affect a critical status. Counting custom objects alone gives an unreliable estimate.
Does this budget cover ECC decommissioning?
That depends on the agreed scope. Implementing the new system and retaining access to the historical information people need are related decisions. Assign archiving and decommissioning work explicitly, even if you commission a separate work package.
Sources: [3]
Which recurring costs should we consider for a cloud project?
Allow for internal assessment of releases and changes, suitable testing, maintenance of roles and configuration, and reviews. The service and contract determine what the supplier provides and what remains with your team. Check which activities the licence fee covers.
Sources: [3]
Which figures from the example can we reuse?
Use the calculation structure as a template and substitute your own estimate for every number of days. Apply the agreed rates to the services in scope. Plan for internal contributions, technical supplier work and ongoing operation separately.
Sources and review date
Primary sources were checked on 17 October 2026. SAP describes the transition paths. Their relationship to CSV effort is our planning assessment. The regulatory sources give no consulting rates. All person-days in the example are assumptions. Pricing and scope are agreed for each engagement.
- SAP Learning: Customer Transition Paths to SAP S/4HANA Cloud Private EditionSAP describes transition paths for Private Edition. The article's assessment of CSV implications and work packages is our own.
- European Commission: EU GMP Chapter 7, Outsourced ActivitiesOutsourced GMP activities, suitability, responsibilities, agreements and oversight.
- European Commission: EU GMP Annex 11, Computerised Systems, January 2011 revisionGMP for human medicinal products. The relevant provisions include sections 1–4, 7, 10–13 and 16–17, as identified in the article.
Sources checked: .
Compare the SAP project scope with your current estimate
Bring your implementation path, processes in scope, data strategy and existing quotations. Use the matrix to see which line items you can already compare and which assumptions you need to clarify before relying on the estimate.
- SAP S/4HANA validation →
Support an SAP go-live with evidence your team can defend at audit while keeping validation on schedule. We take a risk-based approach from the template to the interface for greenfield or brownfield projects and existing ECC systems.

