SAP Migration · 5 min read · December 2025
Dark data in SAP, and why you should not migrate it
By Thinklytics Partners, SAP S/4HANA Practice
Dark data is the unused historical data clogging your SAP system. Migrating it inflates cost, volume, and conversion time for zero value.
Dark data is the historical SAP data nobody uses and nobody will miss: obsolete customers, dead materials, stale records. Migrating it inflates cost, volume, and conversion time for zero value.
What counts as dark data
Inactive customers and vendors, obsolete and non-moving materials, orphaned records, and years of transactional history nobody references. It accumulates quietly over a decade on ECC and becomes a large share of the database.
Why not to move it
Every record you migrate costs time to map, convert, validate, and reconcile. Dark data adds all of that cost and risk for data that delivers no value in the new system. It also slows conversion and inflates your S/4HANA footprint.
- 40% of the migration timeline is discovery and data cleansing. Pre-move cleansing with validation rules cuts post-migration defects by about 60% and post-go-live performance issues by about 25%. The work you skip up front returns as production incidents.
What to do instead
Identify dark data during readiness, decide what to archive versus retire, and migrate only what the business actually needs. A smaller, cleaner migration is faster, cheaper, and lower-risk. The goal is a lean digital core, not a copy of the old mess.
What to do with dark data instead of migrating it
Every record migrated costs time to map, convert, validate, and reconcile. Move only what earns its place.
| Record type | Example | Action |
|---|---|---|
| Compliance-relevant history | Closed financial periods you must retain | Archive |
| Obsolete master data | Inactive customers, dead materials | Retire |
| Active, in-use data | Open orders, current customers and materials | Migrate |
Source: Thinklytics SAP data readiness practice, 2026.
A readiness assessment profiles usage and flags the dark data before you pay to move it.
Frequently asked questions
What is dark data in SAP?
Historical data nobody uses and nobody will miss: obsolete customers, dead materials, orphaned records, and stale transactional history that accumulates over years on ECC.
Why should we not migrate dark data?
Every record costs time to map, convert, validate, and reconcile. Dark data adds that cost and risk for zero value, and it inflates your S/4HANA footprint.
How much of the database is usually dark?
It varies, but after a decade on ECC it is often a large share. Identifying it is part of a proper readiness assessment.
What do we do with dark data instead of migrating it?
Decide what to archive for compliance and what to retire, then migrate only what the business actually needs.
Does removing dark data speed up the migration?
Yes. A smaller, cleaner data set is faster to convert, cheaper to migrate, and lower-risk at cutover.
How do we find dark data?
Through data profiling during a readiness assessment, which measures usage and flags obsolete and non-moving records for archive or retirement.
Topics covered
- Dark Data
- Data Archiving
- S/4HANA
- Migration
Frequently asked questions
What is dark data in SAP?
Historical data nobody uses and nobody will miss: obsolete customers, dead materials, orphaned records, and stale transactional history that accumulates over years on ECC.
Why should we not migrate dark data?
Every record costs time to map, convert, validate, and reconcile. Dark data adds that cost and risk for zero value, and it inflates your S/4HANA footprint.
How much of the database is usually dark?
It varies, but after a decade on ECC it is often a large share. Identifying it is part of a proper readiness assessment.
What do we do with dark data instead of migrating it?
Decide what to archive for compliance and what to retire, then migrate only what the business actually needs.
Does removing dark data speed up the migration?
Yes. A smaller, cleaner data set is faster to convert, cheaper to migrate, and lower-risk at cutover.
How do we find dark data?
Through data profiling during a readiness assessment, which measures usage and flags obsolete and non-moving records for archive or retirement.