How Data Archiving Changes SAP S/4HANA Migration Economics

SAP customers moving to SAP S/4HANA are pricing the migration — the partner fees, the timeline, the change management — without pricing what they carry into it.

SAP HANA’s in-memory architecture means the data a company migrates determines the memory tier at cutover, and that single decision sets the RISE with SAP subscription level, the infrastructure footprint, and the cloud storage bill for the length of the contract.

The migration path matters. The data footprint matters just as much. TJC Group‘s pre-migration archiving program is built around that premise: the data an organization brings into SAP S/4HANA is as consequential to total cost as the migration path it chooses.

The Hidden Cost Driver Nobody Is Pricing

In most enterprise SAP environments, the majority of production database volume is historical data the business no longer uses day-to-day. That data slows system performance, stretches backup windows — in some cases past 14 hours — and puts month-end financial close at risk. The cost mechanics behind that problem are specific.

Primary SAP HANA storage runs roughly $3,000–$5,000 per terabyte per year at the storage layer, a figure that does not capture total infrastructure spend. Enterprise SAP data volumes grow 15–25% annually, and that growth compounds across a multi-year RISE with SAP contract. Every unnecessary record inside SAP HANA carries a recurring cost, and the tier a company lands in at go-live is the tier it pays for until renegotiation.

Most are signing contracts without a precise number for their data footprint. T-shirt sizing tiers — S, M, L, XL — translate directly into subscription cost and infrastructure spend for the life of the agreement. Organizations that size based on current volume without modeling growth, or without removing obsolete data, are locking in higher tiers unnecessarily.

That exposure is quantifiable before a contract is signed. Organizations that want to model their own data footprint can calculate their archiving ROI using TJC Group’s SAP Archiving Calculator.

The Migration Path Variable Few Are Optimizing

Brownfield, greenfield, and Selective Data Transition each carries a different leverage point. Where and when archiving matters depends on which path an organization takes.

In a brownfield conversion, archiving before cutover is the only way to prevent historical volume from converting intact into S/4HANA. In a greenfield implementation, the leverage point shifts post-migration — archiving determines how cleanly legacy systems can be decommissioned. In a Selective Data Transition, archiving the source system before transformation reduces scope, clarifies what data is in scope, and lowers mapping risk.

The sequencing error most organizations make is the same across all three: they begin thinking about data after selecting a migration partner.

Archiving at enterprise scale takes 12 to 18 months from assessment to completion, with results often emerging in months. Organizations that wait until migration planning is underway have already committed to a larger footprint than necessary, and the cost that comes with it.

What Pre-Migration Archiving Actually Delivers

Pre-migration archiving produces a 30–70% reduction in active data volume, depending on system age and industry. That reduction directly shrinks the required SAP HANA memory tier, shortens system conversion runtime, and cuts cutover downtime. Those are three cost centers that compound when they run long on a live migration.

TJC Group’s SAP data archiving program reduces the volume of data that needs to be migrated across. Once in SAP S/4HANA, automated data archiving keeps HANA memory growth under control and prevents costly upgrades to larger infrastructure tiers.

TJC Group’s archiving solutions automate the retention, extraction, and deletion workload that database teams otherwise manage manually. Without automation, that work is both time-intensive and error-prone at enterprise scale.

The company’s Archiving Sessions Cockpit configures once and runs continuously. This ensures archived data remains accessible through standard SAP transactions when Information Lifecycle Management is applied, addressing the most common internal objection to archiving: the fear of losing access to historical records required for audit, compliance, and financial reporting.

The organizations getting the best terms on their SAP S/4HANA contracts treat their data footprint as a negotiable variable before they sign. TJC Group works with enterprises at each stage of that decision, but the leverage is highest before the migration partner conversation begins.

What This Means for SAPinsiders

• Data footprint is a contract negotiation lever, not just a technical metric. Most RISE with SAP negotiations focus on user counts, modules, and support terms. Organizations that quantify and reduce their data volume before entering commercial discussions have a concrete basis for negotiating a lower infrastructure tier.
• The migration partner and the archiving partner serve different timelines. System integrators are engaged to execute a migration. Archiving specialists need to be engaged to prepare for one. Those two workstreams run on different clocks, and conflating them is how organizations arrive at cutover with more data than they planned for.
• Archiving is one investment that improves outcomes regardless of migration path. Most pre-migration decisions are path-dependent: a choice that helps a brownfield project may not apply to greenfield. Data archiving reduces cost, risk, and complexity across all three approaches. That makes it the only preparation activity with no downside regardless of how the migration strategy evolves.