Switching from SAP Business One to S/4HANA Cloud

SAP Business One has served the small-and-medium-business segment of the SAP portfolio for over two decades, with broad DACH mid-market adoption. As organisations grow or transformation requirements outgrow Business One's boundaries, the migration to SAP S/4HANA Cloud (Public or Private Edition) becomes a strategic option. The switch is non-trivial — not a technical upgrade but a complete platform migration with extensive process, configuration and data work.

When the switch makes sense

Three primary drivers. (1) Growth past Business One's comfortable scale: typically above 150-200 employees or 50 million EUR turnover, Business One starts hitting capability ceilings — particularly in advanced manufacturing, multi-entity consolidation, complex variant configuration. (2) International expansion: Business One handles multi-country operations but with limitations around shared services, complex intercompany flows and consolidated reporting. S/4HANA Cloud's native multi-entity capabilities scale better. (3) Strategic alignment with SAP roadmap: organisations standardising on the broader SAP ecosystem (S/4HANA, BTP, Datasphere, Joule AI) benefit from native integration. When not yet: stable mid-market operations under 100 employees, Business One serving the operational needs well, no transformation pressure. Migration is expensive; premature migration rarely pays back.

Key differences

The two products differ fundamentally in architecture and capability. Data model: Business One uses a tightly-coupled SQL Server (or HANA) schema designed for SMB simplicity; S/4HANA uses the much broader S/4HANA data model with deep enterprise capabilities. Customisation: Business One customised via SDK and add-ons; S/4HANA Cloud Public Edition has constrained customisation (clean-core principle), Private Edition supports broader customisation. User experience: Business One has its own UI; S/4HANA Cloud uses SAP Fiori. Functionality breadth: S/4HANA Cloud covers complex manufacturing, advanced supply-chain, sophisticated controlling that Business One approaches less fully. Subscription model: both products subscription-priced but at different tiers (Business One: 60-120 EUR per user per month; S/4HANA Cloud: 120-300 EUR per user per month).

Migration approach

The migration is typically a greenfield exercise. (1) Process redesign: take the opportunity to redesign processes for S/4HANA Cloud standard best-practices rather than replicating Business One's patterns. (2) Master-data migration: customers, suppliers, materials, BOMs, fixed assets migrated with cleansing and harmonisation. Historical transactions typically remain in Business One for audit access. (3) Integration redesign: Business One integrations re-implemented using SAP Cloud Integration plus REST APIs. (4) Custom logic re-platforming: Business One SDK-based extensions rebuilt on SAP Business Technology Platform (Build Apps, low-code). (5) User training: substantial retraining given the different UX and broader functionality. Implementation duration: 12-24 months typical. Cost: 700,000-3,000,000 EUR for mid-market 50-200 user migration depending on complexity. Implementation partner network: Bechtle, NTT DATA Business Solutions, All for One Group, SAP partners in DACH.

Practical considerations

Three patterns. (1) Don't underestimate the scope shift: companies treating the switch as a Business One upgrade consistently underdeliver. S/4HANA Cloud is a different platform with different philosophy. (2) Engage with SAP roadmap consciously: S/4HANA Cloud Public Edition enforces quarterly updates with limited customer control; Private Edition gives more control. Choose the edition matching organisational change tolerance. (3) Plan for parallel operation: Business One typically continues for 6-18 months after S/4HANA go-live in read-only mode for audit access. Budget the operational cost.

Häufig gestellte Fragen

Is the switch from SAP Business One to S/4HANA Cloud an upgrade or a rebuild?

It is not a technical upgrade but a new implementation (greenfield), because Business One and S/4HANA are different products with different data architectures. Processes are remodelled in the S/4HANA standard rather than carried over one-to-one, and data is transferred via the SAP S/4HANA Migration Cockpit (in the Public Edition typically via staging tables filled using CSV or XML templates). With this approach, historical transaction data is generally not migrated in full; instead, master data, open items and usually a limited amount of history are carried over. The legacy system then frequently serves as a read-only archive for the non-migrated data.

When is the Public Edition the right choice, and when the Private Edition?

The Public Edition is a multi-tenant SaaS solution with preconfigured best practices, semi-annual major releases (regularly in February and August) and customisation restricted to extensibility following the clean-core principle, without access to SAP GUI or source code. It suits companies with largely standardisable processes that aim for predictable TCO and shorter implementation times. The Private Edition is a single-tenant operation with full customisation scope up to and including modifications and access via SAP GUI; it follows the on-premise release cadence, with customers able to schedule upgrades at a rhythm of their own choosing rather than being forced onto every release. For most migrations from Business One, the Public Edition is the obvious choice, provided there are no very complex special requirements or regulatory constraints.

How long does a migration from Business One to S/4HANA Cloud take and what does it cost?

For mid-market setups, roughly 12 to 18 months is realistic depending on complexity; simpler constellations can go faster, large corporate group structures considerably longer. Costs depend heavily on company size, process complexity, interfaces and the chosen edition, and for mid-sized companies typically fall in the six- to seven-figure range. The S/4HANA Cloud licence is usually noticeably more expensive than Business One, which can be partially offset in the long run by lower maintenance and hosting effort. Binding figures only emerge from a concrete fit-gap analysis and quotes from qualified SAP partners.

What happens to add-ons and custom code from Business One?

Custom code based on the B1 SDK or the DI API is not carried over; it must be rebuilt in S/4HANA using the extension concepts available there, for example via in-app extensibility or side-by-side developments on the SAP Business Technology Platform. In the Public Edition, these extensions are deliberately limited to release-safe extensibility layers to preserve the clean-core principle. Industry add-ons from the B1 ecosystem do not necessarily have a counterpart in the S/4HANA ecosystem and should be inventoried early and checked for replacements. This add-on and code inventory belongs in the Discover phase, as it significantly influences effort and the edition decision.

What methodology does the project follow?

S/4HANA Cloud implementations follow the SAP Activate methodology with the phases Discover, Prepare, Explore, Realize, Deploy and Run. Discover and Prepare cover the initial assessment, scope, project plan and system environment, while the Explore phase holds fit-to-standard workshops to confirm the solution design. Realize comprises configuration, data migration and testing; Deploy covers the cutover and subsequent hypercare support before the system moves into Run operations. This structure combines preconfigured best practices with agile, iterative ways of working and gives the project a clear phase framework.

Do I have to switch at all, or can Business One keep running?

A switch is not a general obligation: SAP Business One continues to be maintained and enhanced with feature packages, so a stable setup that is not growing strongly can be served without migration. Note, however, the version-based maintenance: SAP offers at least five years of mainstream maintenance per release family without extended maintenance, and a version change within B1 may be necessary to stay in support. The move to S/4HANA Cloud is worthwhile above all when there are noticeable functional or scaling limits, when group consolidation and group reporting are required, or when an S/4HANA parent company demands a uniform platform. If, on the other hand, the company is not tied to SAP and is heavily invested in the Microsoft stack, switching to an alternative such as Dynamics 365 Business Central may be a better fit than S/4HANA Cloud.