Microsoft & Business Central

Business Central Cloud Migration — from On-Premises to the Microsoft Cloud

You already run Business Central — but on your own hardware, with manual updates and growing maintenance effort. Migrating to the Microsoft Cloud (Business Central Online) ends server operations, brings automatic release updates and opens the door to Copilot, the Power Platform and modern integrations. We plan and guide the move.

More services

The difference between on-premises and online is not merely a change of hosting location. In the cloud Microsoft takes over infrastructure, backups and the semi-annual release waves — in return, clear rules apply: direct database interventions are out, customisations must exist as AL extensions, and integrations run via APIs rather than file shares or SQL access. Clarify these points beforehand and the migration is calm. Skip them and you discover them at go-live.

We therefore start with an inventory: which extensions are in use, which of them are cloud-capable, which interfaces currently access the database directly, how large is the data volume and which companies need to come along? From this we build a migration plan with a clear sequence, test phase and fallback scenario — including an honest statement about where customisations have to be rebuilt.

The actual data transfer runs through Microsoft's cloud migration tooling, supplemented by our own verification routines for balances, document chains and permissions. We migrate into a sandbox first, let your key users test there with real data, and only then go live. After the move we take over ongoing support on request, including preparation for the April and October release waves.

Concrete deliverables

Cloud-readiness analysis for extensions and interfaces
Migration plan with test phase and fallback scenario
Data transfer including verification of balances and document chains
Rebuilding database-level integrations on APIs
Sandbox test with real data before go-live
Support for the semi-annual release waves
Use cases

What this looks like in practice.

// 01

End of server lifetime

The existing server is reaching end of life. Instead of reinvesting, operations move to the cloud — with no hardware cycle and no maintenance windows.

// 02

Using Copilot and Power Platform

Cloud operation as the prerequisite for AI features, Power BI and automated workflows via the Power Platform.

// 03

Consolidating multiple sites

Distributed on-premises installations are consolidated into one cloud tenant and operated uniformly.

How we proceed

Step by step.

1

Cloud-readiness check of the existing installation

2

Migration plan including required adjustments

3

Sandbox migration and key-user testing

4

Production cutover and follow-up support

FAQ

Frequently asked questions.

Still have open questions? We're happy to clarify them in an initial call.

Do we have to redevelop our customisations?
Not necessarily. Customisations already implemented as AL extensions can usually be carried over. Old C/AL code, modifications to standard objects or direct SQL access do not work in the cloud, however, and must be replaced. We tell you what is affected after the readiness analysis — before the project starts.
Where is our data stored?
Business Central Online runs in Microsoft data centres; for EU customers data residency can be set to the EU region. We clarify the data protection assessment including the data processing agreement as part of the project.
How long does a cloud migration take?
For a largely standard installation a few weeks is realistic. The drivers are less the data volume than the number and nature of customisations and interfaces. After the readiness analysis we give you a reliable time frame.

Let's talk about your project.

Free initial consultation, 30–45 minutes, remote. An honest assessment — even if the answer is that you don't actually need it.