Implementing Business Central Cloud – The process
The process towards a successful implementation of Business Central Cloud goes through phasing, proof-of-concept, workshops and flow tests
The implementation of Business Central Cloud
Follow a manual added link
Initial meeting
Follow a manual added link
Proof-of-concept
Follow a manual added link
Workshops
Follow a manual added link
Test – Flowtest
The initial meeting
A “Business Central Cloud Implementation” project begins with a general, initial discussion of which areas, workflows, and business processes are important to you. The project is divided into phases so that not all workflows are implemented at the same time.
Breaking the project down into phases and setting priorities makes it easier to get a clear overview of the project and monitor its progress, and it allows the company and its employees to stay up to date and become familiar with existing workflows before new ones are introduced.
Proof-of-concept (POC)
We then propose a proof-of-concept (POC), which consists partly of a practical test of selected key workflows and partly of an analysis, discussion, and planning of the phases of the actual implementation project.
The very purpose of a proof of concept (POC) is to evaluate whether the decisions we make at the outset have the value and functionality we believe they do. It can identify potential challenges and barriers at an early stage, before we begin the actual implementation process.
Testing of key workflows is performed on a Business Central Cloud solution that includes the necessary and/or available vendor-independent apps. In addition, the POC will determine whether data should be converted automatically, manually, or not at all.
For this purpose, we provide a standard accounting system with the most basic setup.
The phasing plan that we initially established together with the customer will be reassessed based on the insights and results we gain from a POC.
After the POC, the actual implementation project begins with detailed project planning.
Workshops
Through a series of workshops, we will determine the final prioritization of functional areas and workflows. We will start with the functions and workflows that we have prioritized and planned for Phase 1.
The workshop series begins with an introduction to Business Central for all participants. As a result, the workshops also serve as training for the superuser group.
Test – Flowtest
In parallel with the workshop series, data is being converted to Business Central, and the necessary commercial documents are being designed and tested.
Once the individual functions and workflows in Phase 1 have been clearly defined, set up, and tested, a flow test is conducted. The flow test ensures that the individual functional areas are integrated into a cohesive system.
Once Phase 1 has been tested and the system is ready for commissioning, the operational conversion is performed (if necessary), and the system is put into operation.
Next, we’ll move on to Phase 2.
The result
By implementing and testing one phase at a time, better control is maintained over project progress and costs.
It also promotes better documentation, as each step in the process can be documented and evaluated separately.
Phasing also allows users to get used to the changes gradually. This often leads to better acceptance of the final system and less resistance to change.
Frequently asked questions about Business Central implementation
When you’re about to implement a new ERP system, many questions naturally arise: What does a typical implementation process look like? To what extent should the organization be involved? And how do we ensure that the solution works in practice—both before and after go-live?
Here, we’ve compiled answers to some of the questions we most frequently encounter in our conversations with customers.
1. What does a typical Business Central implementation process look like at your company?
We always start with an initial meeting where we discuss your business, processes, and ambitions—not just the system. We then break the project down into phases and prioritize which areas should be included in phases 1, 2, 3, and so on.
Throughout the process, we’ll work on workshops, setup, testing, and finally, the go-live. This makes the process clear for both management and employees—and ensures that we consistently incorporate your real-world context into the solution.
2. What do you expect us to have in place before we get started?
You don’t need to have everything documented down to the last detail before we get started. But it helps if you have:
- A clear picture of which business areas are most important (e.g., finance, inventory, production).
- We’ve identified who among your staff could serve as key personnel or power users.
- A shared understanding of why you are implementing a new ERP system right now.
We’ll work out the rest together during the initial meetings and workshops.
3. How much will our employees be involved—and will they be overwhelmed by workshops?
Employees are absolutely essential to the success of the implementation—but they shouldn’t be in workshops all the time.
We plan the process so that the right people are involved at the right times, ensuring a balance between the project and day-to-day operations. Workshops are used both to understand your current workflows and to design new ones—and they also serve as training for key users so they can implement the solution throughout the organization.
4. What is the purpose of a proof-of-concept—and do we always need one?
A proof-of-concept (PoC) is a limited “mini-solution” in which we test critical processes or particularly complex areas before deciding on the final course of action.
This is particularly relevant if you have advanced processes (e.g., in production or logistics) or if you are facing major changes to your workflows. For smaller, more standard projects, we can sometimes skip directly to the actual implementation without a separate PoC process.
5. How do we ensure that the solution works in practice before we go live?
Before go-live, we conduct test runs in which we walk through your most important workflows—such as order-to-invoice, purchase-to-inventory, production, accounting, and reporting.
This typically takes place in close collaboration with your key users, who test the data, processes, and screen layouts. The goal is for you to identify and correct errors and shortcomings in the test environment—not only once you’re in the midst of your busy day-to-day work.
6. What happens after go-live—are we on our own, or will we get help?
Once you go live, the project doesn’t end there. We plan to provide a period of extra-close support, during which we’ll help you address the challenges that only become apparent once the system is being used “for real” in day-to-day operations.
Going forward, we can continue to serve as your partner—whether it’s ongoing optimization, new needs, or further digitalization—so that your solution evolves alongside your business.
Would you like to hear more?
If you would like more information or have any questions, please feel free to contact us.
Feel free to contact us by email, phone, or by filling out the contact form on this page.
Contact us here
We are experts and specialists in Business Central. We’re here to help you. So contact us by email or phone or visit one of our four offices.
Please fill out the form, and we will contact you regarding the next steps.
