The buyer may not need SAP, but they still need the history. When a divested business moves to Oracle, Microsoft Dynamics, or another ERP, historical records from the seller’s SAP environment can remain relevant for audit, legal, financial, regulatory, and ongoing business purposes. 

If you’re managing the divestiture, this leaves a practical question: How do you preserve access without keeping SAP running solely for historical inquiries? The new cloud version of Kyano Datafridge lets you extract the relevant history into a cloud archive and access it through a web application, independent of the original SAP system. 

Key takeaways 

• If you acquire a business that runs SAP but use a different ERP, you still need a plan for accessing its historical SAP data. 

• A cloud archive can preserve access without retaining SAP solely for historical inquiries. 

• Records need meaningful business context and supporting documents to remain usable. 
• Kyano Datafridge Cloud provides web access, with SaaS and hybrid deployment options. 

Keep the history without keeping the SAP system 

Retaining SAP solely for historical reference means paying for infrastructure, maintenance, and specialist support for a system that is no longer part of daily operations. It also adds IT complexity and can create security risks if it isn’t kept patched and maintained. 

An archive provides historical information in a separate home from the buyer’s operational data. Your team can plan retention and access around the records people need, while the buyer develops their chosen ERP without taking on SAP simply to preserve that history. 

Start by agreeing on what belongs in the archive: 

• Records: Which historical information falls within the carve-out scope? 

• Documents: Which attachments and supporting files need to remain accessible? 

• Access: Who needs the information, and which business inquiries must it support? 

Defining these requirements early helps you plan historical access alongside the operational migration. 

How Kyano Datafridge Cloud delivers historical access 

With Kyano Datafridge Cloud on the Kyano platform, relevant data is extracted from the legacy SAP environment and preserved in a cloud archive. Users then access the archived information through a web application, without needing the original SAP system. 

The process follows this sequence: 

Legacy SAP → Data extraction → Cloud archive → Kyano Datafridge Cloud → User access 

The archive’s scope should reflect the historical inquiries you’ve identified. That gives your team a practical basis for checking whether the retained information meets the buyer’s requirements. 

For one large utility company, this meant giving a newly spun-off business access to its SAP history without bringing that history into its new ERP. The new entity chose a non-SAP system and needed only selected open items from the existing SAP S/4HANA system for ongoing operations. Kyano Move supported the carve-out, while Kyano Datafridge Cloud held the historical data separately. This kept the operational transfer focused on what the new business needed to run, with past records accessible through the archive. 

Preserve business context, not just tables 

Retaining historical data is only the starting point. A business user investigating an old transaction may also need its associated invoice and related records to explain what happened. Without that context, finding a record can still leave the inquiry unanswered. 

Kyano Datafridge Cloud supports searchable historical information, reporting, and access to retained documents and attachments. Business object views help users work with the information in context, rather than having to interpret disconnected database tables. 

That matters when the buyer’s users have little or no SAP experience: The information needs to be understandable and usable without relying on their knowledge of the source system. 

Choose between SaaS and hybrid deployment 

For SNP-managed deployments, two models are available:

The choice depends on how your team wants to manage the environment and data storage. Snowflake and AWS Redshift are supported today, with support for Google BigQuery and Azure SQL planned for a future release. 

Build historical access into your separation plan 

Historical access can become a reason to extend transitional arrangements if the buyer still relies on the seller’s SAP system to retrieve records. Planning an independent archive gives you a way to address that dependency before it delays the legacy IT exit. 

Before retiring the relevant environment, check that: 

• The agreed records and supporting documents have been preserved. 

• Authorized users can retrieve the information they need. 

• Representative audit and business inquiries can be answered using the archive. 

Once historical access is established, your team has a clearer basis for reducing reliance on seller-managed SAP infrastructure and planning decommissioning. Any remaining operational or contractual dependencies still need to be resolved. 

The buyer should be able to retain the history without inheriting the system. By planning archive access as part of the carve-out, you can preserve the information the business needs, reduce reliance on the seller’s SAP environment, and establish a clearer path to decommissioning.