The SAP Business One server sits in a room behind accounting. It's five years old, the warranty has expired, and backups go to an external drive that someone swaps out on Fridays. When the general manager asks whether it can "move to the cloud," nobody is quite sure what that means for an ERP the company uses all day.
Moving SAP Business One to the cloud isn't a single path. There are at least three ways to do it, and the choice between the SAP HANA version and the Microsoft SQL Server version changes which features you get, how much infrastructure you pay for and who runs it. This article walks through the real SAP Business One cloud options, what changes for users and what to settle before you migrate.
SAP B1 in the cloud is not classic SaaS
Business Central and Salesforce are services the vendor operates and updates for you. SAP Business One works differently. SAP doesn't run your installation: the software is the same one you would install on your own server, and "the cloud" means it runs on someone else's infrastructure, whether that's a partner, a hosting provider or a hyperscaler such as Azure.
For partners that offer SAP B1 as a service to several customers, SAP ships a set of components called SAP Business One Cloud. Its core is the Cloud Control Center, a web console the cloud operator uses to manage tenants (each company database with its licenses), users, services, backups and monitoring in a multi-tenant environment. SAP's documentation describes two roles: the cloud operator, typically a hosting provider, and the reseller, which is the partner that implements and supports the system.
So whoever offers you "SAP Business One in the cloud" is offering one of these variants. It's worth asking which one.
Three ways to take SAP Business One to the cloud
| Model | Who manages the infrastructure | When it fits | What to check |
|---|---|---|---|
| Multi-tenant hosting (SAP Business One Cloud) | The provider, using Cloud Control Center | Companies that want to pay for a service and not manage servers | Which version the service unit runs, when upgrades happen, whether you can install your add-ons |
| Dedicated virtual machines on Azure or another hyperscaler | Your IT team or a partner, in your own subscription | Companies with their own integrations, security requirements or enough volume to justify a dedicated environment | Sizing, networking, backup, high availability and the monthly VM bill |
| Your own server with remote access | Your team, in your server room or data center | Organizations that need to keep data on their premises | Hardware refresh, business continuity and who answers after hours |
The third model isn't cloud, but it's a useful baseline. Plenty of companies that say "our SAP is in the cloud" actually have their own server published over remote desktop.
What changes in the infrastructure when you move to Azure
Microsoft publishes a guide for deploying SAP Business One on Azure virtual machines with several points worth knowing before you ask for a quote:
- The desktop client and the database talk to each other constantly and are sensitive to latency, so both have to live in Azure. Users usually connect through Remote Desktop Services to one or more VMs running the client.
- If you use SAP HANA, only VMs on SAP's certified HANA IaaS list are supported. That restriction doesn't apply to the client components.
- For SQL Server, the guide gives a starting point for sizing: up to 20 users, 4 vCPUs and 16 GB of memory; up to 40 users, 8 vCPUs and 32 GB; and it scales up from there.
- It recommends managed Premium SSD disks and putting the client VM and the server VM in separate subnets, with network security groups limiting access.
What the guide doesn't cover, and where much of the project is won or lost, is day-to-day operations: who applies patches, how backups get tested, what happens when an integration fails at two in the morning.
SAP B1 HANA or SQL Server: the decision that matters more than the cloud
SAP Business One comes in two database versions: SAP HANA and Microsoft SQL Server. Both are current; SAP released Feature Package 2602 in February 2026 with separate release notes for HANA and MSSQL. The Web Client, the browser interface where SAP has put much of its recent work, runs on both, although some features exist only on HANA.
According to SAP's documentation, these capabilities are specific to the HANA version:
- Pervasive analytics, the dashboards and KPIs you build inside the ERP itself.
- Excel Report and Interactive Analysis, which works on HANA's semantic layers.
- Enterprise Search, the cross-system search over data replicated in HANA.
- The cash flow forecast, which SAP describes as a feature of the HANA version.
If your finance team already handles analytics in Power BI, several of those advantages matter less. If you want operational reporting inside the ERP without building a separate model, HANA makes a case for itself.
Infrastructure cost changes too. HANA is an in-memory database that runs on Linux and needs certified VMs, usually larger ones. SQL Server runs on Windows and is easier to size for smaller companies. Switching from one to the other is a migration with its own testing, so it's better decided together with the cloud move, not afterwards.
What to ask before migrating SAP B1 to the cloud
Before you sign with a hosting provider or build the environment in Azure, get clear answers on these:
- Version and upgrades. In a multi-tenant environment, every company in a service unit runs the same version. Ask how much notice you get before upgrades and whether you can request a test window.
- Add-ons and custom development. Inventory everything running on top of your SAP B1: third-party add-ons, DI API or UI API developments, Service Layer integrations. Some work unchanged in the cloud; others depend on local paths or direct database access.
- Integrations. If your e-commerce site, WMS or e-invoicing connects to SAP, decide how it will reach the new environment: VPN, a published endpoint or a middleware service.
- Backup and recovery. Get the RPO and RTO in writing, and ask to see an actual test restore. A backup policy in a PDF doesn't prove much.
- Version lifecycle. SAP provides at least five years of mainstream maintenance per release family, offers no extended maintenance for Business One and has said version 11 will follow version 10. The dates are on its maintenance strategy page, flagged as subject to change. A cloud migration is a good moment to plan that jump.
If you're thinking about day-to-day support after the move, we looked at what an SAP Business One support contract should include, including the points that usually get left out.
What doesn't change, and it's worth saying
A messy SAP B1 on your own server is still messy in the cloud. Duplicate item master data, uncleaned business partners or approval processes built outside the system don't get fixed by changing infrastructure. The migration does force you to look at all of it, because every piece has to be inventoried and tested. Use that.
You also still need someone who knows the system. Hosting takes care of servers and backups. It won't fix a journal entry posted to the wrong account or a report that stopped reconciling after the upgrade.
And if you're also wondering whether to stay on SAP B1 or switch ERPs, our comparison Business Central vs SAP Business One may help.
Frequently asked questions
Does SAP offer SAP Business One in the cloud directly?
SAP provides the software and the cloud tooling, such as Cloud Control Center, but a partner or hosting provider runs the environment. You can also install it in your own Azure subscription or on another hyperscaler.
Can I run SAP Business One cloud on SQL Server, or do I need HANA?
Either one works. The HANA version adds analytics, search and cash forecasting features that the SQL Server version lacks, in exchange for more demanding infrastructure.
Will my add-ons work in the cloud?
It depends on how they're built. Those that use Service Layer or 64-bit DI API usually migrate without trouble; those that read local files or write straight to the database need a review before the move.
Planning to move your SAP Business One?
At Disrupsoft we handle SAP Business One migrations and upgrades, from on-premise to the cloud and between HANA and SQL Server, including performance tuning and a review of integrations with Azure and Power Platform. Afterwards, if you need it, we stay on with corrective and evolutionary support. See the service details at disrupsoft.cl/en/service/sap and tell us what you're running today.
