🔍 Read the full analysis: How The 2027 SAP Deadline Makes HANA Memory A Hosting Challenge on Rymvard

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get office and shipping supplies delivered free — and shop member deals

• Fast, free delivery on millions of items
• Access to Prime Big Deal Days deals on October 6–7
• Prime Video, Amazon Music and more included

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

TL;DR

SAP’s 2027 end-of-mainstream-maintenance date for core Business Suite 7 applications is increasing pressure on customers to move to S/4HANA. Rymvard, now in early access, has added tools to track HANA host memory, replica needs and probability-weighted go-lives; its Frankfurt scenario is illustrative, not a customer case.

Rymvard added SAP and HANA capacity-planning support on 4 October 2026, targeting a hosting challenge expected to grow as SAP Business Suite 7 customers prepare to move to S/4HANA before mainstream maintenance ends at the close of 2027. The company’s tool tracks memory available on individual hosts, including capacity reserved for operating systems and replicas, and compares it with planned customer go-lives.

During a migration, a company may keep its existing SAP environment running while the replacement system is built, tested and brought into service. Rymvard says the two environments can operate side by side for months, temporarily increasing the customer’s demand for HANA memory. For hosting providers, the planning problem is not just total capacity across a fleet: it is having suitable memory on a particular host and site when a customer is ready to go live.

Rymvard’s capacity ledger divides physical memory on each HANA host into several categories. These include an operating-system reserve, memory in use by HANA systems based on their 30-day peak, memory allocated but unused, and capacity held for replicas at other sites. It also identifies memory that is actually free. The default operating-system reserve is 10 percent of the first 64 GiB and 3 percent of the remainder, unless a host specifies a different reserve.

The system displays allocations that exceed physical memory as overbooking rather than disguising them as negative free capacity. Planned go-lives are weighted by probability and compared quarter by quarter with genuinely free memory. Rymvard says a new system is assigned a host with room and a partner host for its replica. The company’s example uses a hypothetical SAP hosting provider in Frankfurt; it is not presented as a real customer deployment or measured outcome.

Why HANA Capacity Must Match Migration Timing

The announcement addresses a practical constraint for service providers: migration demand can arrive in concentrated waves, while usable memory is tied to the capacity and location of specific infrastructure. A provider may have sufficient memory across its data centers in aggregate but still lack room at the site needed for a planned go-live. Replica requirements add another placement constraint, because capacity must be available at a partner host as well.

That makes the timing of overlapping systems relevant to infrastructure planning. If a customer’s legacy and replacement environments coexist, providers may need to reserve resources for both rather than assume the old footprint disappears as soon as migration work begins. Rymvard’s quarter-by-quarter view is intended to make possible shortfalls visible against scheduled demand, while probability weighting distinguishes tentative plans from more likely go-lives. The company has not provided independent evidence that the product improves capacity use or migration outcomes.

For customers, capacity planning can affect whether a hosting provider can support the target environment on the intended schedule. For providers, a clearer view of used, reserved, replica and free memory may help expose where commitments exceed physical capacity. The tool’s announcement describes a planning approach, not a guarantee that HANA resources will be available or that migrations will finish by a particular date.

SAP’s Business Suite 7 Maintenance Dates

SAP announced on 4 February 2020 that mainstream maintenance for core SAP Business Suite 7 applications, including SAP ERP 6.0 (ECC), would end at the end of 2027. It also offered optional extended maintenance through the end of 2030 at a premium. These dates create a migration planning horizon for organizations still running the covered applications, although the announcement does not mean every customer must complete a migration by the same date.

Rymvard’s new feature is positioned around the infrastructure side of that change rather than SAP’s maintenance policy itself. The company says its product is in early access and currently runs; the screens it describes are from a running product applied to an illustrative estate, not a customer’s environment. Pricing is not published, and Rymvard says terms are agreed with early-access partners.

“Mainstream maintenance for the core applications of SAP Business Suite 7, including SAP ERP 6.0 (ECC), would end at the end of 2027.”

— Rymvard

Product Evidence and Customer Demand

Rymvard has not identified a customer, disclosed a live customer estate or reported results from a deployment. Its Frankfurt example is illustrative only, and no customer site or outcome is implied. The announcement also does not quantify how many providers face memory shortages, how much additional capacity migrations require, or how often old and new systems overlap for months.

It remains unclear how early-access partners will use the tool in production, what commercial pricing will be, and whether the capacity model will be validated against observed migration outcomes. Rymvard’s description sets out the product’s classifications and planning method, but does not provide independent performance testing or evidence that its forecasts prevent overbooking.

Early Access and Migration Planning

The next developments to watch are Rymvard’s early-access program and whether the company publishes customer deployments, pricing or measured results. Until those details are available, the product’s stated capabilities should be treated as a description from the company, not proof of operational impact. Hosting providers can assess the approach against their own host-level memory records, replica policies and customer migration schedules.

For organizations using covered Business Suite 7 applications, the end-of-2027 mainstream maintenance date remains the central planning marker, with optional extended maintenance available through the end of 2030 at a premium. The precise migration timetable for each company, and the capacity its hosting provider will need, depends on its systems and rollout plan. Rymvard lists contact@rymvard.com for early-access inquiries and says pricing is agreed with partners.

Primary source: ASUG · via Rymvard

Key Questions

What SAP maintenance deadline is driving the planning concern?

SAP announced that mainstream maintenance for core Business Suite 7 applications, including SAP ERP 6.0 (ECC), ends at the end of 2027. Optional extended maintenance is available through the end of 2030 at a premium.

Why can a migration temporarily increase HANA memory needs?

During migration, a customer may run its existing environment alongside the new S/4HANA system for a period. That overlap can mean the hosting provider must support both systems at once, as well as capacity for a replica.

What does Rymvard’s new support track?

Rymvard says it classifies HANA host memory as operating-system reserve, system use based on a 30-day peak, allocated but unused memory, replica capacity and genuinely free memory. It compares probability-weighted planned go-lives with free memory by quarter.

Is the Frankfurt scenario a real customer deployment?

No. Rymvard describes the Frankfurt hosting-provider scenario as illustrative. The company says the screens come from its running product applied to an example estate, not from a customer.

Is Rymvard’s product generally available, and what does it cost?

Rymvard says the product is in early access. It has not published prices and says pricing is agreed with early-access partners.

Primary source: ASUG · via Rymvard