10-day validation

Prove it on your own SAP data, in a 10-day validation

In 10 business days, once security and access are ready, we connect to one S/4HANA landscape, refresh one QA or pre-production client with a masked, right-sized copy, and measure it against your current refresh. Fixed scope, a fixed fee, pass/fail criteria you set, and a decision meeting booked before access opens.

10 days
Business days, once access is ready
1 process
One SAP source, one target
Fixed
Scope, fee and decision date
Validation plan · S/4HANA QA clientExample
Scope and pass/fail criteria
Before day 1 · signed off by your sponsor
Agreed
Deploy in your environment and scan
Days 1–5 · standard and Z-tables
Done
Provision, validate and rerun
Days 6–10 · against your criteria
Running
Decision meeting
Day 10 · go or no-go
Next
Validation progressDay 7 of 10
Decision on day 10
Results measured in live deployments outside SAP
30%
faster testing and development cycles
Global bank · self-service test data
20bn
rows masked and subsetted in hours
Digital health platform · replaced a legacy TDM tool · Read the case study
28M
production rows protected, 100% referential integrity
Global specialty insurer · 40+ core applications · Read the case study
200×
more test data, from 100K to 20M entries
Telecom operator · masking and synthetic generation

On SAP, we measure results on your own data in a 10-day validation.

How it works

Ten business days, four steps

Scope is fixed before we start, so nobody is surprised by what the validation covers or what it costs.

Scope and security packSent before day 1
Agree criteriaScope, baseline, sponsor
Deploy and scanIn your environment, read-only
Close readinessSecurity, access, deployment
Provision and validateAgainst your criteria
SME checks resultsDaily 15-minute stand-up
Results and evidenceRun logs and reports
DecideGo or no-go meeting
Before day 1
Days 1–5
Days 6–10
Day 10
Synthesized
Your team
Who does what in the 10 business days. Green marks the results and the decision.
  1. 01
    Before day 1

    Agree scope and pass/fail criteria

    One SAP process, one source and one target, the company codes and dates in scope, and the criteria that decide go or no-go. We send the security pack first, so your review runs alongside the paperwork.

  2. 02
    Days 1–5

    Connect and run the first workflow

    Synthesized runs in your environment, connects to SAP through OData with the authorisations you approve, and scans standard and custom tables for personal data.

  3. 03
    Days 6–10

    Provision, validate and rerun

    The masked subset lands in the target client, checks run against your criteria, and your team reruns the workflow on demand.

  4. 04
    Day 10

    Decide

    Results against each criterion and effort against your baseline, in a decision meeting booked before access opened.

What you get

What you have on day 10

A masked test clientA right-sized QA or pre-production client with no real personal data in it.
A refresh your team ownsYour team reruns it on demand, with no custom code.
Masking rulesFor the standard tables and custom Z-tables in scope.
Measured resultsTime, size and effort compared with your current refresh.
A go or no-go readoutAgainst the criteria agreed on day one.

Pass/fail criteria

How the result is judged

A standard set, tuned to your decision question. You choose three to five and set each target before day 1.

CriterionPasses whenEvidence
ProvisionThe agreed scope lands in the target system within the target timeRun log
ProtectEvery named sensitive field is masked or synthesized to your rule setRule-set report
PreserveRelationships and business consistency hold for the agreed checksValidation report
UseTesters complete the selected SAP scenarios on the dataTest lead sign-off
RepeatThe workflow reruns on demand, by API or pipeline where neededSecond run log
EvidenceAudit records produced, and effort measured against your baselineEvidence pack

Fit check

Who the validation is for

The validation pays off when refreshes happen often enough for the time saved to add up.

Good fit

Validate if…

  • You're already on S/4HANA, or in the test phase of a migration
  • You refresh QA or pre-production at least once a quarter
  • Today you use client copies, an SAP add-on copy tool or scripts
  • Real personal data in test systems is a compliance problem, for example under DORA or GDPR
Not yet

Wait if…

  • You refresh once a year or less: scripts may be enough
  • Nobody owns test data refreshes yet
  • You need data from a system we don't connect to yet. Check the supported systems first.

Terms

Fixed scope, fixed fee, a decision on day 10

FeeA fixed feeAgreed up front for one SAP process, one source and one target, in 10 business days.
Before day 1Criteria you setPass/fail criteria and the decision date are agreed in a charter before access opens.
What we need from youA small teamOne process expert, one technical owner and one security or privacy owner, for the 10 days.

We've got you covered

Questions about the 10-day validation

Do you install anything in SAP?

No. Synthesized runs in your environment and connects to SAP through OData with the authorisations you approve, so nothing is installed in SAP.

Why isn't the validation free?

A fixed fee keeps both sides committed to the criteria and the decision date. The free first step is the 30-minute health check.

What happens to the data afterwards?

The masked data stays in your test client. Synthesized keeps no copy of it, and nothing is sent outside your environment.

Can our systems integrator run it with you?

Yes. We often run the validation with the partner already on your programme. See how partners work with us.

How long does an SAP test data validation take?

Ten business days in your environment, once security, access and deployment are ready. Readiness starts at the first workshop, so it runs alongside procurement instead of after it.

Next step

Start with a 30-minute health check

We build your baseline with you, then scope a validation only if it's worth it.

Runs in your environmentNothing installed in SAPRead-only access to SAPSecurity and deployment
Updated October 2026

SAP, S/4HANA, SAP HANA, SuccessFactors, Ariba, Concur and other SAP products and services mentioned herein, as well as their respective logos, are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.