Thinklytics

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.

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.

Related reading

Thinklytics

Data and AI consulting for Fortune 500s, health systems, and growth-stage companies. Clean data, governed metrics, analytics ready for AI.

Austin, TX · United States

[email protected]