What should you test before going live with SAP S/4HANA?

Before going live with SAP S/4HANA, you need to complete four types of testing: unit testing, integration testing, user acceptance testing (UAT), and a cutover rehearsal. Each phase validates a different layer of your system, from individual configuration settings to the readiness of your entire organisation. Skipping or rushing any of these phases is one of the most common reasons SAP go-lives run into serious trouble. The sections below walk through each testing type, how to structure it, and how to know when you have done enough.

Which types of testing are mandatory before an SAP S/4HANA go-live?

Four testing phases are considered mandatory before an SAP S/4HANA go-live: unit testing, integration testing, user acceptance testing (UAT), and a cutover rehearsal. Each phase serves a distinct purpose and builds on the previous one. Completing all four gives you a defensible basis for the decision to go live.

Unit testing happens early in the project, typically during the build phase. Individual configuration objects, custom developments, and process steps are tested in isolation to confirm they behave as designed. This is largely a technical exercise carried out by the implementation team.

Integration testing comes next. Here you test end-to-end business processes across modules and system interfaces, checking whether data flows correctly from one step to the next. This is where many hidden issues surface, particularly around interfaces with third-party systems.

UAT follows integration testing and puts the system in front of actual business users. Their job is to validate that the configured processes match real operational needs, not just technical specifications.

The cutover rehearsal sits outside the main test cycles but is equally important. It simulates the actual go-live weekend to validate your cutover plan, timelines, and rollback options before you are under real pressure. Structured test management across all four phases helps you track progress, manage defects, and build the evidence base you need to make a confident go-live decision.

What is the difference between integration testing and UAT in SAP projects?

Integration testing checks whether the system works correctly end-to-end across modules and interfaces. UAT checks whether the system works correctly for the business. Integration testing is led by the project team; UAT is led by business users. Both are necessary, and neither replaces the other.

In integration testing, the focus is on data flow and system behaviour. You run scenarios like procure-to-pay or order-to-cash across the full chain, from the triggering transaction through every downstream step, including any interfaces with external systems such as logistics platforms, payment providers, or reporting tools. The goal is to find technical defects before business users ever touch the system.

UAT shifts the perspective entirely. Business users execute realistic scenarios based on their actual day-to-day work, not scripted test cases designed to catch technical errors. They are assessing whether the system supports their processes, whether the screens make sense, and whether they can complete their tasks without assistance. UAT often surfaces usability issues, missing functionality, and process gaps that integration testing never would have caught because the test team did not know to look for them.

A common mistake is treating UAT as a formality after integration testing. In practice, UAT findings frequently require configuration changes, which means you need to plan time and resources for a remediation cycle before UAT sign-off.

How do you structure a UAT cycle for SAP S/4HANA?

A well-structured UAT cycle for SAP S/4HANA runs in three stages: preparation, execution, and sign-off. Each stage has clear outputs, and the cycle should be time-boxed with a defined remediation window built in before the sign-off deadline.

During preparation, you define the scope of UAT based on the business processes in scope for go-live. You write test scripts from the user’s perspective, not the system’s. You identify and train the business users who will execute the tests, and you confirm the test environment is stable and loaded with representative data. This last point matters more than most teams expect. UAT with poor or incomplete test data produces unreliable results.

During execution, business users run their assigned scenarios and log defects with enough detail for the project team to reproduce and fix them. You track completion rates and defect volumes daily. A defect triage process should be in place from day one so that critical issues get immediate attention and lower-priority items are assessed against the go-live risk threshold.

Sign-off is a formal decision, not just the end of the test period. It should be based on agreed exit criteria: for example, all critical defects resolved, a defined percentage of high-priority defects resolved, and all in-scope scenarios executed. Vague sign-off criteria are a risk you want to eliminate early in the project.

What should be tested during a cutover rehearsal?

A cutover rehearsal should test the complete sequence of activities required to move from your legacy system to SAP S/4HANA, including system shutdowns, data migration runs, technical configuration steps, validation checks, and the conditions under which you would trigger a rollback. The rehearsal validates your plan, your timings, and your team’s ability to execute under pressure.

Specifically, a cutover rehearsal should cover:

Data migration execution — running the full migration sequence and validating data completeness and accuracy in the target system
System configuration and transport steps — applying final transports and confirming the system is in the correct state for go-live
Interface activation — switching on connections to third-party systems and confirming they are exchanging data correctly
Validation and reconciliation checks — confirming that key business data such as open orders, stock balances, and financial positions match expected values
Timing against the cutover schedule — checking whether each task completes within its allocated window and identifying where you are at risk of overrunning
Rollback decision point — confirming the team understands the criteria and process for triggering a rollback if the go-live cannot proceed

Most projects benefit from running at least two rehearsals. The first one will surface gaps in the plan and timing issues. The second gives the team the confidence and muscle memory to execute the real thing under pressure. Structured cutover management is what separates teams that go live smoothly from those that spend the first week firefighting.

How do you know when testing is complete enough to go live?

Testing is complete enough to go live when you have met your pre-agreed exit criteria across all test phases, your critical and high-priority defects are resolved or have accepted workarounds, and your business stakeholders have formally signed off on UAT. The decision should be based on evidence, not optimism.

Exit criteria vary by organisation, but a solid baseline includes:

100% of planned test scenarios executed
Zero open critical defects
A defined threshold for high-priority defects, typically resolved or formally accepted with a workaround
Cutover rehearsal completed with timing validated
Data migration validated and reconciliation checks passed
Business sign-off from process owners in each functional area

One thing worth being honest about: there is no such thing as zero risk at go-live. Every SAP S/4HANA implementation reaches a point where the remaining open items are manageable post-go-live and the business risk of delaying outweighs the risk of proceeding. That judgement call belongs to the business, not the project team, which is why formal sign-off from business stakeholders is so important. It puts the decision in the right hands and creates shared accountability for what comes next.

Hypercare planning matters here too. Knowing that you have experienced support available in the first weeks after go-live makes it easier to make a confident decision to proceed when some lower-priority items are still open. Check out our full range of services to see how end-to-end support from test management through to post-go-live hypercare fits together.

How Optinus helps with SAP S/4HANA test management

We support SAP S/4HANA projects across the full testing lifecycle, from planning your test strategy at the start of the project to managing defects during UAT and running cutover rehearsals. Our consultants have hands-on experience from real ERP migrations at leading multinationals, so we know where the risks are and how to manage them before they become go-live blockers.

Here is what working with us on test management looks like in practice:

Building a test strategy and plan that covers unit testing, integration testing, UAT, and cutover rehearsals
Setting up defect management processes and exit criteria that give you a clear, evidence-based basis for the go-live decision
Preparing and coaching business users for UAT so that sign-off reflects genuine readiness, not just a completed checklist
Running cutover rehearsals and stress-testing your timelines before the real thing
Providing hypercare and aftercare support after go-live so your team has expert backup when it matters most
Working on-site or remotely, across the Netherlands, Belgium, and internationally

If you are preparing for an SAP S/4HANA go-live and want to make sure your testing approach is solid, get in touch with our team or learn more about what we do.

home|

blog|