🔍 Read the full analysis: SAP S/4HANA Migration 2027: Why Hosting Providers Face HANA Memory Pressure on Rymvard

Buying for a business?Offer from Amazon

Get business pricing on networking and server gear

• Business-only prices and quantity discounts
• Tax-exempt purchasing
• Multiple users, one account, clear invoices

Create a free Business account →Free to register

As an affiliate, we earn on qualifying purchases.Hide

TL;DR

Rymvard added SAP and HANA support to its early-access data-center capacity product on Oct. 4, 2026. The tool tracks host memory use, allocations, replicas and planned go-lives, addressing a potential pinch point as customers migrate from SAP Business Suite 7 before mainstream maintenance ends in 2027. The Frankfurt example is illustrative, not a reported customer case.

Rymvard added SAP and HANA support to its data-center capacity product on Oct. 4, 2026, aiming to help hosting providers plan for memory demand during migrations to SAP S/4HANA. The company says the tool accounts for periods when old and new systems run at once, a potential strain as SAP Business Suite 7 mainstream maintenance is scheduled to end in 2027.

The feature is designed to break down memory on each HANA host into several categories: an operating-system reserve, memory in use by each HANA system, memory allocated but unused, memory reserved for replicas at other sites, and memory that remains free. Rymvard says system usage is measured using the 30-day peak. Its default operating-system reserve is 10% of the first 64 GiB and 3% of memory above that, unless the host has a separately declared reserve.

The product also displays allocations that exceed a host’s physical memory as overbooking, rather than disguising the shortfall as negative free capacity. Planned go-lives can be weighted by probability and compared quarter by quarter with memory it classifies as genuinely free. Rymvard says its planning model assigns a new system to a host with sufficient room and identifies a partner host for its replica.

Rymvard illustrates the capability with a scenario involving an SAP hosting provider in Frankfurt. The company says the screens are from its running product and use an illustrative example estate, not a customer environment. It says no customer, site or outcome is implied. The product is in early access, and Rymvard does not publish prices; pricing is agreed with early-access partners.

Why Migration Overlap Strains Host Memory

The planning problem is not simply how much memory a provider owns overall. It is whether usable HANA capacity is available on the right host and site when a customer is ready to go live, while preserving room for replication and other workloads. A provider may have capacity in its fleet but still face a local or timing mismatch if memory is already allocated, reserved, or needed at another site.

During a migration, customers may keep their existing systems running alongside the replacements for months. That overlap can temporarily raise demand, and the need to accommodate replicas adds another constraint. For hosting providers serving multiple customers, a quarter-by-quarter view of likely go-lives could help surface conflicts earlier. Rymvard’s announcement describes a tool for tracking those constraints; it does not establish that providers are already experiencing a particular level of shortage or that the product has reduced one.

The feature also makes a distinction between memory that appears free in an allocation ledger and capacity that can actually be committed. Showing unused allocations and overbooking separately may help operators see where nominal capacity differs from physical headroom. Whether that view improves deployment decisions will depend on the quality of the underlying host data and migration forecasts.

SAP’s Business Suite 7 Timeline

SAP announced on Feb. 4, 2020, that mainstream maintenance for the core applications of SAP Business Suite 7, including SAP ERP 6.0, known as ECC, would end at the close of 2027. SAP also set out optional extended maintenance through the end of 2030 at a premium. The approaching mainstream-maintenance date gives customers a reason to plan moves to S/4HANA, although the timeline does not mean every customer will migrate at the same time.

For infrastructure providers, staggered customer plans still create possible periods of concentrated demand. Rymvard’s case focuses on capacity planning rather than the migration process itself: it tracks host memory, site replicas and projected go-live timing. Its Frankfurt scenario is an example of how the product is presented, not evidence of a named provider’s migration schedule or actual capacity position.

“The operating-system reserve is 10 percent of the first 64 GiB plus 3 percent of the rest, unless a host declares its own.”

— Rymvard

Customer Results Have Not Been Reported

Rymvard says the product is in early access, but it has not provided customer deployments, measured results, or evidence that the feature has prevented capacity shortfalls. The Frankfurt example is illustrative and does not identify a customer or confirm a real site’s memory pressure. The company also has not published pricing, saying terms are agreed with early-access partners.

The scale and timing of any HANA memory constraints among hosting providers remain unknown. The announcement does not quantify expected migrations, the number of systems likely to overlap, or how much additional capacity a provider may need. Actual demand will depend on customer migration schedules, workload sizes, infrastructure configuration and replica arrangements.

Early Access Will Test Planning Use

Rymvard says it is making the capability available through its early-access program; interested parties can contact the company at contact@rymvard.com. The next useful evidence would be deployments using real provider estates, along with details about how forecasts compare with actual HANA demand and go-live dates. No such customer results or a broader availability date have been announced.

For providers, the immediate planning task is to map migration timing to host-level memory and replication requirements, rather than rely only on a fleet-wide capacity total. SAP’s stated maintenance schedule remains the key date in the background, while individual customer timelines and the resulting demand profile continue to vary.

Key Questions

What did Rymvard announce?

Rymvard added SAP and HANA support to its capacity-planning product on Oct. 4, 2026. The features track memory categories, overbooking, replica reservations and planned go-lives.

Why can SAP migrations raise memory demand?

During a migration, the existing system and its S/4HANA replacement may run side by side for months. That can temporarily require memory for both, with additional capacity reserved for replicas.

When does SAP Business Suite 7 mainstream maintenance end?

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

Does Rymvard have confirmed customer results?

None are reported in the announcement. Rymvard says it is in early access, and its Frankfurt scenario uses an illustrative example estate rather than a customer deployment.

Primary source: ASUG · via Rymvard