SAP Business ByDesign Still Runs—but New Customers Can’t Buy It

As of August 13, 2026, SAP Business ByDesign is no longer a straightforward “best buy.” Existing customers can continue running the cloud ERP and receiving updates, but SAP removed it from the price list for net-new customers on April 20, 2026. A statement from SAP partner Navigator Business Solutions says the change did not retire the product or establish an end date for maintenance.

The distinction changes the practical answer. For an organization already using ByDesign, its SaaS operating model may still justify continued investment. For a company selecting a new ERP, however, ByDesign should not be placed on the shortlist as an ordinarily purchasable SAP product: SAP’s current Business ByDesign page directs companies new to SAP toward GROW with SAP and presents migration to SAP Cloud ERP as the modernization path for ByDesign customers.

The cloud advantage now applies mainly to existing customers

Business ByDesign remains a genuine cloud ERP rather than an on-premise application moved onto hosted servers. Finance, sales, purchasing and product-related processes operate within one SaaS suite, with SAP responsible for the underlying service and release delivery. That can remove the need for a customer to maintain the ERP’s application stack and coordinate conventional software upgrades on its own infrastructure.

This operating model can make costs and responsibilities more predictable, but “cloud” does not mean “effortless.” The customer still owns configuration decisions, user administration, access governance, integrations, data quality and change management. Internal teams must also assess every release against extensions, connected applications and business-critical workflows, even when SAP deploys the software centrally.

ByDesign is demonstrably still being updated after its removal from new-customer sales. SAP’s May 2026 release announcement documents version 26.05 and changes spanning finance, supply chain, customer relationship management, legal requirements and extension capabilities. That is evidence of an operating product for installed customers, not evidence that it remains available for a fresh purchase.

What existing customers still gain from the SaaS model

The strongest reason to retain ByDesign is operational continuity when the product already fits the business. Replacing an ERP affects master data, financial controls, integrations, reporting, user roles and established processes. Staying on a maintained SaaS platform can avoid forcing that disruption before a replacement produces enough benefit to justify it.

Central release delivery is another material advantage. Security fixes, legal changes and functional updates can arrive through the service instead of requiring a traditional upgrade project built around new application servers and locally installed software. The value is highest when the organization keeps its configuration disciplined and can adopt standard changes without repeatedly rebuilding extensive custom behavior.

A unified suite may also reduce some integration work between core functions. When sales, purchasing and finance use the same transactional foundation, fewer handoffs need to be recreated between separate systems. That does not eliminate integrations with payroll, banking, e-commerce, warehouses or specialist industry tools, so the relevant measure is the company’s actual application landscape—not the number of modules listed in a brochure.

Why “cloud” alone is not a purchasing case

A SaaS subscription changes the allocation of infrastructure work; it does not automatically prove lower total cost. A sound comparison must include subscription charges, implementation, partner services, data migration, integrations, testing, training, internal administration and eventual exit costs. An on-premise comparison should likewise include hardware, database and operating-system administration, backup operations, security work, upgrade projects and the staff needed to perform them.

The same caution applies to scalability. A cloud service can make technical capacity less visible to the customer, but business scaling also depends on supported countries, currencies, tax requirements, transaction patterns, organizational structures and integration throughput. A growing company should validate those requirements contractually and through solution design rather than infer them from the deployment model.

Availability and security must also be evaluated through the applicable agreement and operating procedures. Cloud hosting does not transfer responsibility for excessive user privileges, weak approval design, inaccurate master data or unsafe exports. Buyers and existing customers need to distinguish controls operated by SAP from controls that remain with their own administrators and process owners.

The decision is different for each customer group

Net-new SAP customers should treat ByDesign as closed to normal new procurement. The relevant comparison is now among products SAP actively offers for new implementations and credible alternatives from other vendors. Product fit, implementation capacity, migration options and long-term portfolio direction matter more than the historical appeal of ByDesign’s cloud architecture.

Existing ByDesign customers do not need to interpret the sales change as an immediate shutdown. Continued maintenance and the 26.05 release support a keep-running decision where the system remains fit for purpose. Nevertheless, SAP’s public emphasis on migration means customers should establish a planning horizon, document dependencies and estimate replacement effort before a future business change creates an urgent deadline.

Companies undergoing major structural change should reassess earlier. A large acquisition, entry into additional jurisdictions, a new manufacturing model or a requirement for capabilities outside ByDesign may shift the economics toward migration. The relevant question is not whether the current system still operates, but whether investing further in its configuration and integrations offers a better return than moving those resources to the target platform.

Build the decision around workload and exit risk

For an installed customer, the retention case should identify which infrastructure and upgrade responsibilities the SaaS model removes, which duties remain internal, and what it costs to operate integrations and extensions. It should then compare those recurring costs with a realistic migration program, including parallel operation, data reconciliation, control testing and user transition.

The exit plan deserves equal weight. Organizations should maintain an inventory of interfaces, extensions, reports, authorization roles and data-retention obligations while the current environment is stable. That work has immediate operational value and reduces dependence on undocumented knowledge, even if migration remains several years away.

The updated conclusion is therefore narrower than the old cloud-versus-on-premise argument. Business ByDesign’s cloud delivery can still be an economically sensible operating choice for customers who already have it, especially when it supports their processes without heavy customization. It is no longer a general recommendation for new buyers, because after April 20, 2026 the decisive constraint is availability—not whether SaaS is preferable to owning servers.

Also read:

• Business Blogging Still Works—But Publishing More Is No Longer the Strategy
• Business Blogs Still Matter—But Search Traffic Can’t Be the Only Goal
• Five Business Technology Bets for 2026—AI Agents Are Still the Weak Link