+1 480 485 7373
Microsoft Teams
The real difference is operational, not functional
Open both versions side by side, and a finance user will struggle to tell them apart. The same pages, the same posting routines, the same reports. What differs is everything behind the screen. Who patches the operating system and sizes SQL Server? Who tests and applies each update? And who restores the database at two in the morning when something breaks?
Online, Microsoft does that work on Azure. You manage environments through the Business Central admin center, choose an update window, and keep sandboxes for testing. On-premises, your IT team or a hosting partner owns the servers and the Windows Server and SQL Server licenses. They also own the backup routine and the upgrade schedule.
So the Business Central cloud vs on-premises decision is less about features. It is about whether your company wants to be good at running an ERP platform.
Business Central cloud and on-premises side by side
What Business Central in the cloud takes off your plate
No upgrade projects
On older on-premises systems, a version upgrade was a project in its own right. Online, updates arrive on a schedule and your job shrinks to testing extensions in a sandbox before the window.
Security patching
Operating system, database and application patching is Microsoft's job. Your job is user access, permission sets and multi-factor sign-in through Microsoft Entra ID.
Hardware refresh cycles
No servers to replace, no SQL Server licenses to renew, and no capacity planning for month-end peaks.
Faster test environments
You can make a sandbox copy of production from the admin center to train, test an app or try a new process. Then you delete it when you are done.
When Business Central on-premises still earns its place
- ✓Sites with unreliable internet, such as remote plants or yards, where the ERP must keep running during an outage.
- ✓Contracts or rules that require data to stay on hardware you control, where Microsoft's cloud compliance terms do not satisfy the customer or regulator.
- ✓Heavy use of direct SQL reports or .NET parts that would take real effort to rebuild as APIs and cloud-safe extensions.
- ✓A large recent investment in on-premises infrastructure and an IT team that already runs it well, where moving now would waste that spend.
- ✓A modified base app carried over from NAV that nobody can rewrite as extensions yet. Treat this as a temporary state, not a strategy.
- ✓Scales, label printers or machine controllers wired to the ERP server over the plant network, until someone builds a cloud-friendly link for them.
Moving on-premises Business Central to the cloud
- 1
Inventory the customizations
We list every extension and change and check each against cloud rules. We redesign anything that uses .NET or direct database calls.
- 2
Check version and data
Microsoft's cloud migration tool replicates data from supported on-premises versions into an online environment. Older versions need an upgrade first.
- 3
Replicate and test
We copy data to an online sandbox and test reports and integrations. Users then try their daily tasks there.
- 4
Switch over
A final copy runs and the on-premises system turns read-only. Then users sign in to the online environment.
Business Central cloud vs on-premises questions
Is our data safer on our own servers?
Not automatically. Microsoft runs Business Central online on Azure. It has security teams, encryption and physical controls few mid-sized firms can match. What stays your responsibility in both cases is who has access and with which permissions. On-premises can be very secure, but only when your team patches, backs up and monitors without fail.
Can we still customize Business Central online?
Yes, through AL extensions, the same way you build them on-premises. The cloud does not allow edits to the base app, .NET interop or direct database access. So a few older methods are off the table. In practice those limits are what keep online updates painless.
Can we report straight from the database online?
Not with direct SQL. You reach online data through API pages, OData web services, Power BI apps and the Excel add-in. For heavy analytics, you can export data to Azure storage or a data lake. Teams used to writing SQL queries against the ERP need a short adjustment.
What about a partner-hosted private cloud?
That is on-premises software running in someone else's data center. It takes the hardware out of your office but keeps the upgrade and patch work. You also still miss the features kept for the online service. It can be a sensible stepping stone, but it is not the same as Business Central online.
Can we move from online back to on-premises?
You can get your data out, and Microsoft offers ways to export a copy of an online database. But it is rare and takes real effort. Most companies that go online stay there. If an on-premises need might appear later, raise it before the Business Central cloud decision, not after.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.