Old SAP data fills the HANA memory you pay for and slows your S/4HANA conversion. It also keeps a read-only ECC alive just for auditors. Archon’s SAP archiving solution moves it out, keeps it searchable, and lets you switch old systems off.
Explore our trusted SAP solution for secure data archiving, historical access, and SAP system decommissioning.
37 TB
Cut from an SAP ECC and BW landscape before S/4HANA
40 %
Smaller SAP database for a global apparel enterprise
$1.3M
Saved in storage costs in the same program
Zero
Records lost across 27 TB of migrated SAP content
Every terabyte of old FI, SD, MM, and HR data adds conversion runtime, downtime, and HANA sizing.
GOS files and scans pile up in SOFFCONT1. In one landscape, they were 27 TB of the 37 TB removed.
ADK files only open through SAP, so many teams keep ECC running for occasional lookups.
With Archon’s SAP archiving solution, your teams search SAP data, documents, and ADK archives in one place. None of it depends on SAP still running.
Keep HANA lean after go-live, with custom retention policies and lower-cost storage tiers.
Move less into S/4HANA, then retire ECC. Users keep familiar transaction screens.
Inactive data leaves running systems automatically, based on compliance need and actual usage.
Clear out logs, old configuration data, and legacy files, and keep them ready for audits.
Three moves take you from a heavy SAP estate to one you can switch off.
Most SAP archiving projects stall in planning. Archon Analyzer™ gives you a fact-based scope first: what to archive, what to keep, and where sensitive data sits.
Years of SARA runs have left much of your history in ADK files that only open through SAP. Archon moves that content out. You can access ADK files after decommissioning and stop paying to keep SAP alive.
PO PDFs, scanned invoices, and signed HR forms pile up in SOFFCONT1. Reducing SAP SOFFCONT1 table size gives you a smaller HANA footprint, shorter backups, and faster system copies. Users still open every attachment from the same GOS screens.
Platform Capabilities
Archived records appear in screens that mirror familiar SAP transactions. No SAP GUI needed.
Query Visualizer gives metadata search, dashboards, and reports across every archived system.
Z-tables come out through a connector and mapping layer. No ABAP archiving objects to build.
Pseudonymization at ingestion, plus masking, tokenization, and role-based access.
Move that data, its documents, and its ADK files into one archive your auditors can search. Then drop the server, the license, and the Basis effort.
| What you need | SAP native (ADK, SARA, ILM) | Archon |
|---|---|---|
| Archive inside a live SAP system | ✓ Yes | ✓ Yes, on SAP's standard process |
| Reach archived data after SAP is switched off | ✕ No | ✓ Yes |
| Read archives without SAP GUI or a license | ✕ No | ✓ Yes |
| Bring existing ADK files along | Not applicable | ✓ Yes |
| Search across archiving objects and systems at once | ◐ Partial: within one SAP system | ✓ Yes |
| Archive SOFFCONT1 and GOS content | ◐ Partial: needs a certified content server | ✓ Yes, with Archon ArchiveLink |
| Tamper-proof (WORM) storage built in | ◐ Partial: needs a certified third-party store | ✓ Yes |
| Retention and legal hold that outlive the source system | ✕ No: configured in the live system | ✓ Yes |
| Archive custom Z-tables | ◐ Partial: needs custom objects and ABAP work | ✓ Yes, no ABAP project |
| Keep non-SAP systems in the same archive | ✕ No | ✓ Yes |
| Pseudonymize archived personal data | ✕ No | ✓ Yes |
| Profile data before archiving | ◐ Partial: table-level analysis (for example, TAANA) | ✓ Yes, with Archon Analyzer™ |
Proof
Data archiving handles structured records, such as financial documents, sales orders, and purchase orders. Document archiving handles unstructured content, such as scanned invoices, PDFs, and GOS attachments, usually through SAP ArchiveLink. Both grow the SAP footprint, and most landscapes need both. Archon covers structured data, ADK files, and SOFFCONT1 content in one archive, so a record and its attachments stay linked.
interfaces, because ADK files are read back through the SAP system that wrote them. Once that system is switched off, the archive is effectively locked. The fix is to migrate ADK content before retirement. With Archon, ADK data becomes structured records you can search through prebuilt views, with no SAP license or SAP GUI.
Yes, in most cases. Archiving before conversion reduces the data volume you migrate, which shortens conversion runtime and downtime and lowers HANA sizing. It also forces clear decisions on how much history the new system needs. In one Archon program, archiving removed about 37 TB from an ECC and BW landscape and made the S/4HANA move practical.
SOFFCONT1 is the SAP table that stores the binary content of documents and attachments, such as GOS files. It often grows into one of the largest tables in an SAP database. You reduce it by moving existing content to an external repository and routing new attachments there through ArchiveLink. Archon does both, so users still open attachments from the same GOS screens.
Start with an analysis of your SAP data. You’ll see what to archive, what to keep, and what it takes to switch old systems off.
Read the latest from Archon Data Store's team to learn more about the world of data management.
SOFFCONT1 often becomes one of the largest SAP tables because every attachment, workflow document, and GOS file gets stored directly …
SAP ADK files are proprietary archive files that store historical SAP business data and typically require SAP runtime environments or …
SAP modernization is incomplete until legacy systems are fully retired, not just migrated. Legacy SAP systems continue running mainly …
Legacy SAP ECC systems hold decades of data, increasing costs, migration complexity, and compliance risk. With ECC support ending in …
Products
Solutions
Guides
Resources
Company
Follow us on
Archon © 2026, All rights reserved.