Rise with SAP: SAP Archive—A Strategic Decision

With regular maintenance for SAP ECC 6.0 set to end on December 31, 2027, many companies are facing the transition to S/4. Rise is a frequently chosen transformation approach because it bundles infrastructure, hosting, and the operation of the SAP Basis system into a single subscription. However, the SAP Archive—including the ArchiveLink integration—is generally not included in this model. The archive remains a standalone component of the IT landscape with separate operations, its own software, and its own storage. In practice, this often leads to misunderstandings: companies assume that the archive is included in the Rise contract. In fact, this gap often only becomes apparent in the later phases of the project—for example, during the cutover.

Archive Architecture in the Rise Context

An SAP archive consists of several components: archive software, document storage, storage infrastructure, and the interface to the SAP system. In existing environments, this integration is primarily handled via ArchiveLink. In the Rise model, however, the archive is not operated within the SAP tenant but in a separate environment. The connection is established via defined networks and must be planned accordingly.

As part of this reorganization, the SAP Content Server is often considered as a potential target architecture. While it represents a solution closely integrated with SAP, it must be operated independently and only addresses modern cloud requirements to a limited extent. Furthermore, it does not support an open interface strategy. As a result, many projects face the need to fundamentally reassess their archiving solutions and integration approaches.

A common misconception is to view SAP’s own solutions as the only option for archiving. In fact, there are well-established alternatives on the market, such as those based on enterprise content management concepts. These differ significantly in terms of cloud capabilities, compliance support, and operating models. The choice of archiving architecture therefore directly influences flexibility, cost structure, and investment security.

ArchiveLink or CMIS?

A key issue concerns the interface strategy. ArchiveLink remains relevant as a proven interface and can also be used in the context of S/4 and Rise. At the same time, CMIS (Content Management Interoperability Services) is establishing itself as an open standard for the integration of content platforms. CMIS enables a decoupled architecture and reduces dependencies on individual vendors. In addition to technical considerations, regulatory requirements play an important role. Features such as SAP ILM support companies in implementing data protection requirements—for example, in the context of the GDPR—particularly when it comes to implementing retention and deletion rules.

Another key factor is cost-effectiveness. In the Rise model, data volume directly impacts the cost structure. Targeted archiving helps reduce database sizes, thereby optimizing both migration efforts and ongoing operating costs. In practice, many companies rely on a hybrid approach: Existing ArchiveLink integrations are retained, while new content is connected via CMIS going forward. This enables a phased transformation of the archiving landscape without disrupting ongoing operations.

„Rise takes over operation of the SAP system—but not automatically the archive. Projects regularly show that this point is underestimated. At the same time, SAP’s own solutions are not always the only option or the most cost-effective one. A deliberate decision regarding interfaces and architecture is therefore a key success factor in the transition to Rise,“ says Oliver Greiner, CEO of Entplexit, an IT consulting firm specializing in SAP security, SAP technology, and SAP archiving for data and documents.

Given the requirements described above, companies are increasingly turning to structured operational models for archiving. In addition to in-house operations, managed service approaches—which combine operation, maintenance, and further development—are gaining in importance.

These models range from fully cloud-based operating models to hybrid approaches that continue to utilize existing infrastructure. The goal: a clear structure of responsibilities and an archive architecture that is stable and scalable over the long term.

Conclusion

Rise addresses the operation of the SAP core system, but does not automatically address the SAP archive. The archive architecture remains a separate strategic consideration in the transformation process. Companies that take this aspect into account early on and deliberately design their interface strategy create resilient, flexible, and cost-effective structures for the long term. (Source: Entplexit)