Key Points:
- SAP S/4HANA selective data transition (SDT) allows you to migrate only business-critical data from SAP ECC to SAP S/4HANA instead of moving everything.
- Migrating all historical data increases HANA costs, extends cutover timelines, and adds long-term system complexity.
- Non-migrated legacy data should be archived in a governed, searchable environment rather than keeping ECC in read-only mode solely for historical access.
- Archon ArchiveLink facilitates SAP archiving and helps preserve access to historical SAP data and documents after legacy SAP environments are retired, while Archon Data Store supports governed, long-term retention and access.
- A clear data strategy, retention alignment, and ongoing archiving approach help keep S/4HANA lean while maintaining access to historical data for business, audit, and compliance needs.
SAP S/4HANA migration conversations often center on what to move, without giving equal clarity to what can remain outside the new system, and that gap is costing enterprises more than they realize.
Teams spend months migrating historical purchase orders from deactivated company codes, transferring years of inactive records into an environment that may not require the entire legacy backlog.
The result?
- Bloated HANA databases
- Inflated storage costs
- Extended cutover windows
- A new system that already feels heavy from day one
A more strategic approach is to focus not on moving everything, but on moving only what truly matters, while keeping the rest accessible, compliant, and operationally separate. That is precisely what SAP S/4HANA selective data transition enables.
What Is Selective Data Transition in SAP?
When organizations plan a move from SAP ECC to SAP S/4HANA, they typically weigh two well-known paths:
- Greenfield implementation: A new implementation of SAP S/4HANA where business processes are redesigned from scratch using SAP best practices. Legacy configurations and custom developments are not carried forward unless intentionally rebuilt. Historical data is typically not migrated in full but may be archived or selectively transferred.
- Brownfield migration: A system conversion approach where the existing SAP ERP system is technically converted to SAP S/4HANA. Existing configurations, custom code, and historical data are retained, subject to compatibility checks and remediation. While this approach preserves continuity, it can also carry forward legacy complexity and unused data—challenges that are also common during an Oracle to SAP S/4HANA migration.
SAP S/4HANA selective data transition, often called SDT, sits squarely between these two. It is a hybrid migration approach that lets organizations retain valuable configurations and custom developments from SAP ECC, while choosing exactly which data to bring into S/4HANA and which to leave behind.
Think of it as a curated migration. You are not abandoning the past, and you are not dragging it all into the future unchanged. You are making deliberate, strategic decisions about what belongs in your new system and what belongs somewhere else. The same principle applies to a carve-out strategy, where organizations separate specific business units, data sets, or operations while preserving continuity and compliance.
That decision, however, raises an important follow-up question: Once you decide what stays out of S/4HANA, where exactly does it go?
Read more: Choosing between Greenfield, Brownfield, and Bluefield S/4HANA migration strategies
What Happens to the Data That Does Not Get Migrated?
This is where most organizations hit a wall. You have committed to selective data transition; you know what moves into S/4HANA. But what do you do with the years of legacy data still sitting in your ECC system?
Some organizations keep the old ECC system running in read-only mode. It sounds safe until you realize it means paying to maintain an aging system for ten or more years purely for the occasional audit query.
The costs add up quickly:
- Infrastructure and licensing fees do not go away
- Accessing data is slow and cumbersome
- The team supporting a dead system grows frustrated
- Security risk on an unsupported platform keeps climbing
So where should that data live?
Legacy data archiving is the cleaner answer. Instead of keeping a full system alive for the occasional tax audit or compliance check, organizations extract the data from their ECC environment, store it in a governed and accessible archive, and decommission the legacy system entirely.
The data is not deleted. It is preserved in a structured, searchable format: accessible when needed, compliant with retention regulations, and can be purged securely once retention policies are met, ensuring the archive remains lean and manageable.
Now that we know where the non-migrated data needs to go, the next question is:
The Role of Archiving in SAP S/4HANA Selective Data Transition
In an SDT project, your SAP archiving strategy is not a cleanup task. It is one of the most consequential decisions you make before the cloud migration begins, directly shaping how lean your system is and how much you spend on infrastructure for years ahead.
Pre-Migration: Making the Scope Manageable
Before anything moves, your team needs a clear picture of what is actually in your ECC system:
- How old is the data?
- Which records are still operationally relevant?
- Which ones exist purely to meet retention obligations?
- Which ones are redundant or no longer tied to active business processes?
A strong pre-migration archiving phase answers these questions and identifies data that can be excluded from the migration entirely, shrinking your cutover window, reducing HANA storage requirements, and simplifying testing validation.
During Migration: Keeping the Scope Controlled
During migration, archiving ensures only the data you genuinely need in S/4HANA gets there. Historical records tied to closed entities, completed transactions, or past fiscal periods go straight to the archive rather than through the migration pipeline. This is particularly important for high-volume financial data stored in the ACDOCA table, where controlling historical data scope can significantly reduce migration complexity.
This matters because one of SDT’s defining strengths is the ability to time-slice your historical data, bringing only the most recent years of transactional records into S/4 HANA and archiving everything older.
Post Go-Live: Sustaining a Lean, Compliant Environment
After go-live, your S/4 HANA system will keep generating data. Without an ongoing archiving discipline, you will find yourself back in the same situation within a few years: a growing database, rising storage costs, and a system carrying more weight than it needs to. Post-go-live archiving keeps the environment lean and enforces retention policies. It also supports the secure purging of archived data once it reaches the end of its retention period, completing the data lifecycle efficiently.
SDT Migration Readiness Scorecard
Use this scorecard before your next planning session. Score your organization honestly across five dimensions. The results will tell you not just whether you are ready to begin your SAP S/4HANA selective data transition, but where the gaps are most likely to surface during execution.
| Readiness Dimension | What to Assess | Score 1 / 2 / 3 |
|---|---|---|
| Data Landscape Visibility | Do you have a current, documented view of what is in your ECC system (volume, age, ownership, and sensitivity), or are you working from assumptions? | ___ / 3 |
| Retention Policy Alignment | Are your legal, finance, and IT teams aligned on what data must be kept, for how long, and under which regulatory framework (SOX, GDPR, sector mandates)? | ___ / 3 |
| Archive-to-Decommission Plan | Is there a defined plan to decommission the ECC system after go-live, with archiving as the path to get there rather than read-only mode? | ___ / 3 |
| Business Access to Archived Data | Can business users (finance, legal, operations) retrieve historical records from your archive without raising an IT ticket? | ___ / 3 |
| Post Go-Live Archiving Discipline | Does your S/4HANA environment have an ongoing archiving policy in place to keep the new system lean as it continues generating data? | ___ / 3 |
| Total Score: | ___ / 15 | |
How to Read Your Score
13 to 15 – Strong foundation. You have the visibility, alignment, and planning discipline to execute SDT with confidence. Focus your energy on tooling and execution.
9 to 12 – Proceed with caution. There are gaps that will surface during migration if not addressed upfront. Identify the lowest-scoring dimension and resolve it before go-live planning begins.
Below 9 – Address the fundamentals first. Moving forward without closing these gaps will create downstream problems, particularly around compliance and ECC decommissioning. A data assessment and archiving strategy workshop is the right next step.
Wherever your organization scores today, the practices in the next section are what move the needle, and they are exactly what a well-executed legacy data archiving approach is built on.
Read more: How to reduce SAP SOFFCONT1 table size as part of SAP data archiving and migration planning.
Best Practices for Retaining Legacy Data Without Migrating It
A solid legacy data archiving approach in the context of SAP S/4HANA selective data transition comes down to five principles:
1. Start with a data assessment
Know your data landscape: age, volume, connections, and regulatory obligations. Without this clarity, migration and archiving decisions become guesswork.
2. Align archiving to retention policies from day one
Map your archiving strategy to retention regulations (SOX, GDPR, sector mandates) so data is retained exactly as long as required and disposed of properly.
3. Make archived data accessible without IT involvement
Enable business users to retrieve archived records independently, searchable by document type, date, or org unit, without IT involvement.
4. Preserve data integrity throughout
Archived records must match source data exactly. Document and audit all transformations during legacy archiving for compliance and legal readiness.
5. Plan for decommissioning from the beginning
Plan for ECC decommissioning from day one. Archiving is what enables you to shut down the legacy system confidently, not just reduce storage costs.
Following these principles is one thing. Having the right platform to execute them across discovery, extraction, and long-term retention is another. That is where Archon comes in.
Read More: A Complete Guide about SAP System Decommissioning
How Archon Helps You Retain Legacy Data During SAP S/4HANA Selective Data Transition
Archon is an enterprise data archiving platform designed to help organizations manage historical data as part of a structured SAP S/4HANA selective data transition strategy.
Archon ArchiveLink: Archive SAP Data Without Carrying It Into S/4HANA
Archon ArchiveLink facilitates SAP archiving, helping organizations archive historical SAP data and documents while maintaining secure access to those records after legacy SAP environments are retired.
This is particularly relevant when a selective data transition leaves historical records outside the new S/4HANA environment. Instead of keeping a legacy SAP system operational solely to access older records, organizations can archive historical data and maintain governed access to it separately.
Archon ArchiveLink supports organizations that want to:
- Archive historical SAP data and documentsthat do not need to remain in the operational S/4HANA environment
- Reduce reliance on legacy SAP systems while preserving access to historical records
- Maintain access to historical SAP information for business reference, audits, and compliance requirements
- Support SAP system decommissioningwithout losing access to required historical records
- Support retention and compliance requirementsthrough SAP archiving and related governance capabilities
Archon Data Store: Secure, Searchable, Long-Term Retention Without the Legacy System
Archon Data Store (ADS) provides the long-term archival environment for historical data after it is removed from operational systems. It provides a governed, searchable archive that keeps historical information accessible without requiring the original system to remain available.
What ADS delivers:
- Tiered storage (hot, warm, cold) with compression and lifecycle automation built in
- Metadata-driven search that enables users to retrieve historical records without relying on IT support
- Role-based access controls to keep sensitive data accessible only to authorized users
- Legal holdsto protect records from disposition when they are subject to preservation requirements
- Retention-based disposition to support controlled removal of archived data once applicable obligations are fulfilled
- Analytics support that allows historical data to remain available for reporting and analysis after go-live
- SAP ILM integration and support for cloud, hybrid, and on-premise deployment
Conclusion
SAP S/4HANA selective data transition is a sound strategy for organizations that want to modernize without starting from scratch and without carrying unnecessary data into their new environment. But it only delivers its full value when the question of legacy data is handled deliberately rather than deferred.
The data that does not migrate into S/4HANA is not data you can ignore. It may have compliance obligations, operational value, and audit implications that persist long after go-live. The right answer is a structured, governed archiving approach that preserves what you need, supports controlled disposition when retention obligations are fulfilled, and gives your teams access to historical data without the burden of maintaining a legacy system solely for that purpose.
With Archon, organizations can address that challenge through Archon ArchiveLink for SAP archivingand Archon Data Store for governed, long-term retention and access. Together, these capabilities support a cleaner approach to managing historical SAP data around S/4HANA transition and legacy system retirement. Contact us!
