Get the whitepaper!
The Test Data Imperative: Towards SAP Autonomous Enterprise

Carve-outs and divestitures

Test data for SAP carve-outs and divestitures

A carve-out splits one company's SAP data in two, on a deadline the deal sets. Every mock run needs realistic data for the divested entity, and none of the seller's retained business can reach the buyer's systems. Synthesized subsets by company code and masks what stays private.

Book a health checkHow it works
Available on SAP Store
Carve-out scope · mock run 2Example
Company codes 3000 and 3100
The divested entity
In scope
Plants and sales organisations
Linked to the divested codes
In scope
Shared customers and vendors
Used by both businesses
Masked
Company codes 1000 and 2000
Retained by the seller
Excluded
Same scope every mock run
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.

Why carve-outs are hard

Four reasons carve-out testing runs short of data

01
Shared master dataCustomers, vendors and materials both businesses use must be split, kept or masked, record by record.
02
Fixed deadlinesTransition service agreements set the date the buyer must run alone, so mock runs can't slip.
03
Data the buyer mustn't seeThe seller's retained customers, prices and employees can't appear in any system the buyer touches.
04
Many rehearsalsEach mock conversion and integration test round needs a fresh, consistent copy of the divested entity.

How it works

Copy only the entity being carved out

Seller's SAP productionRetained and divested company codes
SynthesizedSubsets by company code and masks what stays private
Carve-out test systemDivested entity only, for mock runs
Buyer's integration testingDivested entity only, masked
Retained business dataNever copied into carve-out systems
excluded by scope
Each test copy holds only the entity being carved out. The seller's retained business never reaches the buyer's systems.
  1. 01

    Define the entity

    The company codes, plants, sales organisations and date range that make up the divested business.

  2. 02

    Decide shared records

    For customers, vendors and materials both sides use: copy, mask or leave out, by rule.

  3. 03

    Refresh for each mock run

    Write a masked subset of the divested entity into the carve-out test system before every rehearsal.

  4. 04

    Give the buyer test data

    The buyer's team gets masked data for integration testing, with nothing from the retained business.

Copy and delete, or subset

What changes when test copies hold only the divested entity

Full copy, then delete

Copy everything and clean it up

  • The whole client, retained business included
  • Deletion scripts rerun for every mock run
  • A risk that retained data slips through to the buyer
  • Test systems the same size as production
With Synthesized

Copy only the divested entity

  • Subsets by company code, plant and sales organisation
  • Shared records masked or left out, by rule
  • The same scope for every mock run
  • Smaller test systems and faster rehearsals

We've got you covered

Questions about carve-out test data

What is an SAP carve-out?

Separating part of a company's SAP data, usually by company code, into a new system or client for a divested business or a new entity. Selective data transition services and tools move the data; test systems need their own copies for every rehearsal.

How is this different from SAP's selective data transition?

Selective data transition moves the divested entity into its target system. Synthesized prepares the test copies around it: masked subsets for each mock run and for the buyer's integration testing.

How do we handle customers both businesses share?

Set a rule per object: copy it into the divested entity, mask it, or leave it out. The same rules run for every mock, so results can be compared.

Can the buyer test before the legal split?

Yes, on masked data scoped to the divested entity, so the buyer's team sees neither the seller's retained business nor real personal data.

Does this work for acquisitions and mergers too?

Yes. The same scoping and masking prepare test data when an acquired business moves into your SAP landscape.

Next step

Plan test data for your carve-out

Tell us the company codes and the mock-run calendar. We'll show a masked subset of the divested entity on your system.

Runs in your environmentNothing installed in SAPRead-only access to SAPSecurity and deployment
Book a health checkFor SI partners

Related SAP pages

ProjectTest data for S/4HANA migrationMigration test dataCapabilitySAP data masking and scramblingData maskingPartnersFor SAP systems integratorsPartner with us
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.