// 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.
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.
Cloud migration at a glance
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.
The move from on-premises to Business Central Online normally happens without extended downtime: the production cutover sits on a weekend, preceded by a full dress rehearsal in the sandbox. What you no longer have afterwards is server operation — no hardware cycles, no manual updates, no maintenance windows for database housekeeping. What you should plan for instead is the semi-annual release wave: Business Central Online updates itself automatically in April and October, and extensions have to keep up. That is exactly what sandbox environments are for, letting each release be tested in advance.
Cloud migration: what we deliver
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
Cloud migration in practice
// 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
Cloud migration: step by step
Cloud-readiness check of the existing installation
Migration plan including required adjustments
Sandbox migration and key-user testing
Production cutover and follow-up support
FAQ
Cloud migration: frequently asked questions
Still have open questions? We're happy to clarify them in an initial call.
- 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.
- 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.
- 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.
- In four steps: a readiness analysis of extensions and interfaces, migration into a sandbox, testing by your key users with real data, then the production cutover. The data transfer is handled by Microsoft's cloud migration tool, which sets up a replication of your on-premises database into the cloud tenant. We then verify balances, document chains and permissions against the old system before switching over.
- The project price depends almost entirely on how cloud-ready your customisations and interfaces are today — not on the volume of data. A near-standard installation is a manageable project; database-level integrations and legacy C/AL code drive the effort. On top of that come the recurring Business Central Online licence costs, which Microsoft publishes. After the readiness analysis you get a reliable price rather than an estimate.
- No, not for any length of time. The sandbox migration and all testing run in parallel with normal operation in the old system. Only the production cutover itself needs a window in which no postings are made — usually a weekend. We agree the exact sequence, including the fallback scenario, in writing beforehand.
- Technically such parallel operation is possible and in group structures sometimes sensible, for instance as an interim step in a phased migration. In the long run, though, it doubles the support effort: two release levels, two operating models, two routes for interfaces. We recommend it as a transitional arrangement with a defined end date, not as a target state.
Do we have to redevelop our customisations?
Where is our data stored?
How long does a cloud migration take?
How does an on-premises to Business Central Online migration actually work?
What does a cloud migration cost?
Do we have to stop working during the migration?
Can we run some companies in the cloud and keep others on premises?
Related
More services: Microsoft & Business Central
Microsoft Dynamics 365 Business Central
Implementation, customisation and support of the ERP backbone for your business.
NAV → Business Central: Fixed-Price Upgrade
Structured migration from Navision to Business Central, with a binding fixed-price quote after analysis.
Microsoft Licences
We advise on licensing and procure what you actually need. Without over-licensing.
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.