Graveyard for SAP
Retire the workload. Keep access to the history.
Graveyard for SAP keeps a legacy SAP system reachable after you have stopped using it for day-to-day work, for as long as you still need to produce the data it holds. We reduce the system to read-only access, run it on infrastructure sized for that one job, and replace an open-ended maintenance contract with a fixed, predictable cost.
- 99.9% SAP application uptime SLA
- 1,000+ SAP databases
- Since 1999
Is this for you?
- 01
You are retiring an SAP system, but people still need its historical data.
- 02
You want read-only access for the right users, right-sized for occasional use.
- 03
You need a documented path to decommissioning when the data is no longer needed.
Why keep the system at all?
Many organisations are required, by internal policy, by an auditor or by regulation, to keep historical accounting and transaction data accessible for years after the system that created it goes out of active use. That data usually still lives inside SAP, so someone has to keep SAP reachable for it, even once nobody is posting new transactions.
The usual alternatives both carry real cost. An Information Lifecycle Management or archiving project can run for months and still miss tables an auditor later asks for. Exporting everything to flat files loses the reporting and drill-down your finance team is used to. Graveyard for SAP is the alternative to both: keep the SAP system itself, but resize everything around it, including cost, for a system whose only remaining job is answering lookups.
Access after the transition
We define exactly who still needs to get into the system and for what, so the environment is scoped to actual use rather than a guess carried over from production.
- Define the required users and read-only access
- Document data-retention and retrieval requirements
- Map dependencies that must remain available
- Bring adjacent systems into the same graveyard if they hold data you still need, for example an SAP Content Server or an OpenText archive tied to the SAP landscape
A smaller operational footprint
Once the scope is agreed, we rebuild the operating model around it: less infrastructure, less patching and less monitoring, matched to a system that no longer runs daily operations.
- Right-size the environment for occasional access
- Confirm software licensing and support constraints
- Define decommissioning criteria and data disposition
Choose how you connect
Connectivity is one of the choices in the package, not something we assume for you. Pick whichever fits your existing network policy.
IPsec VPN
A site-to-site VPN tunnel into the basis.no data centre, set up and managed like any other connection to a hosted environment your organisation already runs.
Another method
If your organisation standardises on a different connection type, we match it, agreed case by case during setup.
basis Remote Access
Our own remote desktop, self-hosted and licence-free. No VPN, no site-to-site tunnel and no inbound firewall rules: nothing to configure or maintain on your side.
- Single sign-on through your own identity provider, e.g. Microsoft Entra ID
- A self-service dashboard where you manage who on your side has access, without opening a ticket with basis.no
Choose how the SAP application is supported
Hosting and the resized operating model are always part of the package. On top of that, you choose the support level. A system used only for read-only lookups rarely needs the same tier it had in production.
No support contractRun without a formal software support agreement. basis.no still operates the hosting and infrastructure, but no vendor patches or fixes the SAP application layer itself. The lowest-cost option.Best for: stable, unchanging systems used purely for read-only lookup
Third-party supportbasis.no can arrange third-party SAP support as part of the package, so hosting and support are handled together. It covers the underlying stack once you no longer need mainstream SAP support, typically at a lower cost than staying on SAP's own support.Best for: stable systems that still need a patched, supported stack underneath
Continued SAP supportKeep your existing SAP support agreement running on the retained system. This fits organisations that must keep vendor support for compliance or contract reasons, or that may reactivate parts of the system later.Best for: contractual or regulatory obligations to keep vendor support
One package, agreed once
Graveyard for SAP is quoted as a single package covering hosting and the right-sized operating model, plus the connectivity and support level you choose above. One agreement, one fixed monthly fee and one exit plan for when the system can finally be switched off.
| Part of the package | What it covers |
|---|---|
| Always included | Right-sized SAP hosting for read-only access, and an agreed data-retention scope and decommissioning plan |
| You choose: connectivity | IPsec VPN, another method agreed case by case, or basis Remote Access (licence-free, with single sign-on and self-service user administration) |
| You choose: support | No support contract, third-party support or continued SAP support |
Let's look at your legacy system.
Tell us which system you want to retire and how long its data must stay available. We come back with a package and a fixed monthly price.