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 platform rather than keeping ECC in read-only mode.
- Archon supports secure extraction, validation, and long-term access to legacy SAP data while enabling full ECC decommissioning.
- A clear data assessment, retention alignment, and ongoing archiving strategy keep S/4HANA lean and compliant after go-live.
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.
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.
That decision, however, raises an important follow-up question: Once you decide what stays out of S/4HANA, where exactly does it go?
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 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 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.
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.
How Archon Helps You Retain Legacy Data During SAP S/4HANA Selective Data Transition
Archon is an enterprise data archiving platform designed to manage legacy data as part of a structured SAP S/4HANA selective data transition strategy. Its three core products work together across the full data lifecycle.
Archon Analyzer: Know What You Have Before You Decide What to Move
Archon Analyzer scans your legacy SAP ECC environment, profiles the data it finds, and surfaces what is active, redundant, and sensitive. Specifically, it:
- Auto-tags records with metadata and visualizes relationships between data objects
- Identifies ROT content (Redundant, Obsolete, and Trivial records) that can be excluded from migration or disposed of under retention policies
- Assigns confidence scores to datasets based on completeness, accuracy, and consistency
- Uses AI-driven classification to identify personally identifiable information and other sensitive records that need careful governance throughout the transition
Every decision is informed, documented, and defensible before a single byte moves.
Archon ETL: Move Legacy Data with Integrity and Zero Data Loss
Archon ETL handles the extraction, transformation, and loading of data from your SAP ECC system into the Archon Data Store, bridging your legacy environment and your long-term archive with full integrity.
Key capabilities:
- Supports complex SAP schemas and handles schema drift, preserving referential integrity between tables automatically via Smart ETL
- Every load is validated through checksum and count matching, confirming what arrived in the archive matches exactly what left the source
- AES-256 encryption in transit and at rest, with full audit logs for every operation
- Runs workflows in parallel with dynamic resource allocation, reducing archiving time significantly, with native connectors to SAP ECC and enterprise systems, so no custom integration is required
Archon Data Store: Secure, Searchable, Long-Term Retention Without the Legacy System
Archon Data Store (ADS) is where your legacy SAP data lives after ECC is decommissioned. It is a fully searchable, intelligent archive that makes historical data accessible on demand without the original system.
What ADS delivers:
- Tiered storage (hot, warm, cold) with compression and lifecycle automation built in
- Metadata-driven search that enables users to retrieve any record on demand without relying on IT support
- Role-based access controls to keep sensitive data accessible only to authorized users
- Legal holds applied instantly, with retention policies enforced automatically
- Secure purging of archived data once retention obligations are met, keeping the archive lean, compliant, and manageable
- Analytics support that allows historical data to remain available for reporting and analysis even after go-live
- Integrates with SAP ILM and supports 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 weight into their new environment. But it only delivers its full value when the question of legacy data is handled deliberately and not deferred.
The data that does not migrate into S/4 HANA is not data you can ignore. It has compliance obligations, operational value, and audit implications that persist long after go-live. The right answer is a structured, governed archiving approach that preserves everything you need, eliminates what you do not, allows secure purging of data once retention obligations are fulfilled, and gives your teams access to historical data without the burden of a legacy system.
With Archon, organizations can approach that challenge with confidence. From the first data assessment through to full ECC decommissioning, the platform handles every step of the legacy data lifecycle so your SAP S/4HANA migration can be exactly what it was designed to be: lean, focused, and built for the future. Contact us!
