S/4HANA migration
A mock load fails, a test cycle slips, UAT waits for data. When your programme is in its test phase, Synthesized refreshes each cycle with a masked, right-sized dataset, without another full copy of production.
Already live on S/4HANA? See upgrade testing
Mainstream maintenance for SAP ECC 6.0 (enhancement packages 6 to 8) ends. Extended maintenance runs to 2030 at extra cost.
Each stage needs a different dataset, and most need it more than once.
Fit-to-standard workshops on a sandbox with masked data the business recognizes.
Integration and regression cycles, with data refreshed at the start of each cycle.
Rehearse the conversion on masked copies of ECC and compare results run after run.
User acceptance testing and cutover rehearsal with business-realistic scenarios.
Regression testing for every release and feature pack after go-live.
The approach you take decides where test data comes from.
Brownfield
Test the converted system with masked copies of ECC data, and compare results before and after conversion.
Greenfield
Load migrated master data plus synthetic transactions, so tests can run before any real history exists in S/4HANA.
Selective
Move and test subsets by company code or date range, with the same masking on the source and the target.
To prove S/4HANA gives the same answers as ECC, both systems must run on the same data. Synthesized masks both consistently, so a customer, an order and its invoice carry the same masked values on each side and reconciliation reports match line by line.
Read: how better test data de-risks parallel testing and cutover
Example values: the same masked record on both sides of a parallel test.
Tricentis Tosca and UiPath test cases request the data they need when they run, so automated regression keeps working through every cycle of the programme.
In the Explore phase, alongside the test strategy. Settling scope, masking rules and refresh cadence early avoids a scramble before the first mock conversion.
GDPR asks for a lawful basis and data minimisation for any use of personal data, testing included. Masking personal data before it reaches test systems is the usual way to meet both.
Yes. Synthesized connects through SAP's OData services, so it needs neither OS nor database access, and nothing is installed in SAP. See RISE with SAP test data.
It moves data once. Test data needs subsetting, masking and a refresh for every cycle, so each cycle would become a migration project of its own.
Big enough to hold complete business processes for the scenarios you test, and rarely all of production. Compare a full copy with a subset in the calculator.
Bring your test plan to a 30-minute health check. We'll map which cycles need which data, and how often it needs refreshing.
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.