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 starts with an overall, 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.
The phasing and prioritization makes it easier to get an overview of the project, keep track of progress, and allows the company and employees to follow and get to know the 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 essential workflows and partly an analysis, discussion and planning of the phases of the actual implementation project.
The purpose of a Proof-of-concept (POC) is to evaluate whether the decisions we made initially have the value and functionality we believe they have. It can identify potential challenges and barriers at an early stage, before we start the actual implementation process.
Testing of the essential workflows is performed on a Business Central Cloud solution containing the necessary and/or possible supplier independent apps. In addition, the POC determines whether data should be converted automatically, manually or not at all.
For this purpose, we provide a standard account containing the most basic setup.
The phasing that we initially set up together with the customer is re-evaluated based on the experience and results of the POC.
After the POC, the actual implementation project starts, with detailed project planning.
Workshops
Through a series of workshops, the final prioritization of functional areas and workflows is determined. We start with the functions and workflows that we have prioritized and planned for phase 1.
The workshop process begins with an introduction to Business Central for all the people who will participate in the workshops. In this way, the workshops also serve as training for the super user group.
Test – Flowtest
In parallel with the workshop process, data is converted to Business Central and the necessary business documents are designed and tested.
Once the individual functions and workflows in phase 1 are clearly defined, set up and tested, a flow test is performed. The flow test ensures that the individual functional areas work together in a unified system.
Once phase 1 is tested and the system is ready for commissioning, operational conversion (if necessary) is performed and the system is put into operation.
We then 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 starting with a new ERP system, many questions naturally arise: What does a typical implementation process look like? How much should the organization be involved? And how do we ensure that the solution works in practice—both before and after go-live?
Here, we have compiled answers to some of the questions we most often encounter in conversations with our clients.
1. What does a typical Business Central implementation process look like with you?
We always start with an initial meeting to discuss your business, processes, and ambitions—not just the system itself. From there, we break the project into phases and prioritize which areas will be included in Phase 1, 2, 3, and so on.
Throughout the process, we work with workshops, configuration, testing, and finally go-live. This approach keeps the project manageable for both management and staff, while ensuring that your real-world business needs are reflected in the solution at every step.
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 smallest detail before we begin. However, it helps if you have:
- A clear understanding of which business areas are most critical (e.g., finance, inventory, production).
- Identified who within your organization can serve as key users or super-users.
- A shared understanding of why you are implementing a new ERP system at this time.
The rest will be developed together during the initial meetings and workshops.
3. How much will our employees be involved—and will they be overwhelmed by workshops?
Employees are central to the success of the implementation—but they won’t be in workshops all the time.
We plan the process so that the right people are involved at the right moments, maintaining a balance between project work and daily operations. Workshops are used both to understand your current workflows and to design new ones, while also serving as training for key users, enabling them to support and carry the solution forward within the organization.
4. What is the purpose of a proof-of-concept, and is it always necessary?
A proof-of-concept (PoC) is a limited “mini-solution” where we test critical processes or particularly complex areas before deciding on the final approach.
It is especially relevant if you have advanced processes (e.g., in production or logistics) or if you are facing significant changes in workflows. In smaller, more standard projects, we can sometimes proceed directly to the full implementation without a separate PoC phase.
5. How do we ensure the solution works in practice before going live?
Before go-live, we conduct testing phases where we run through your most critical workflows—such as order-to-invoice, purchase-to-stock, production, accounting, and reporting.
This is typically done in close collaboration with your key users, who test data, processes, and user interfaces. The goal is to identify and resolve any errors or gaps in the test environment—not when you are already in the middle of daily operations.
6. What happens after go-live—will we be on our own, or will we receive support?
When you go live, the project doesn’t end there. We plan a period of close support to help address any challenges that only become apparent when the system is used “in real life.”
Afterwards, we can continue as a strategic partner—supporting ongoing optimization, new requirements, and further digitalization—so your solution evolves alongside your business.
How to get started with Business Central Cloud
Getting started with a Business Central Cloud?
Then contact us for a chat about how to get started.
Why Vektus
How we work
We work to make your investment in Business Central a success both now and in the long run.
