Phases that build on one another.
From analysis and gap-fit through data foundation and build to migration, go-live and operation. Every phase with a clear outcome and a gateway where decisions are made together.
Discuss the implementationSequence matters more than speed.
Our project methodology structures a Business Central implementation into clearly separated phases: analysis and gap-fit, target state and template, data foundation and processes, build and configuration, migration and testing, controlled go-live and hypercare. Every phase has defined outcomes, acceptance criteria and a gateway before it continues. Sequence matters more than speed.
If you only clarify processes once the project is running, or migrate data unchecked, you are building on sand. Our phases build on each other: each one ends with a tangible result and a gateway where we decide together whether to continue. This approach grew out of rollouts across up to 25 countries, not off a drawing board.
From analysis into stable operation.
Analysis & gap-fit
We examine processes, data and goals and define what Business Central should really deliver for your business, with full documentation.
Target picture & template
We define the shared core: chart of accounts, standard processes, roles and reporting structure, as a viable template.
Data foundation & processes
We clarify the data model, set creation rules and owners and separate the data foundation rigorously from the application.
Build & configuration
We configure close to the standard, use extensions in a targeted way and keep the core upgradeable.
Migration & testing
Clean, map, validate, a test run with real data, then load. Testing and migration are treated as work in their own right.
Go-live
A controlled go-live with a clear readiness check, instead of a date that forces decisions.
Hypercare & operation
We stabilise operation, reduce the productivity dip and keep developing on the clean base.
AI & further development
On the clean data foundation, AI can be used sensibly, more on this under AI-supported delivery and BC Agents.
Sequence matters more than speed. First the foundation, then the system, then the pace.
Workstreams that run alongside one another.
Large projects do not run linearly. We run the workstreams in parallel and hold them together at the gateways.
Preparation & contracts
Setup, roles, contracts and ground rules for everyone involved, cleanly before project start.
Application & configuration
Template, configuration and targeted development, close to the standard and upgradeable.
Data migration
Mapping, cleaning, validation and test runs, with experts and tools for the transfer.
Finance & accounting
Chart of accounts, consolidation and local obligations, aligned to your structure.
Training & change
Involve the business units early, so they experience the system as their own, instead of returning to old ways.
IT & interfaces
IT environment, integrations and test environments, planned instead of improvised.
Every phase delivers something tangible.
Programme control is not more meetings. It is clear artefacts. At every gateway, what is needed for the next decision is on the table. This keeps control over scope and roadmap with you, not quietly with the implementation partner.
- Decision log with traceable trade-offs
- Backlog prioritised by business value
- Acceptance criteria per module
- Data owner per master-data domain
- Test protocols and migration test run
- Go-live readiness with clear sign-off
Template, pilot, controlled rollout.
A template dropped unchanged onto every subsidiary will be rejected. There is a better way.
Shared core
Processes, data model and standards as a reusable template, cleanly separated from local obligations.
Harden on the real process
A representative entity goes live first, the template is hardened against reality before it is rolled out.
Repeatable and predictable
Standardised kickoff, repeatable migration, clear governance over who may change and who may only configure.
What is asked about the project methodology.
How long does an implementation take with this methodology?
That depends on the data situation, the number of entities and the degree of adaptation. Simple setups are possible in weeks, complex transformations need an honest, longer span. We name it upfront, instead of a wishful number.
What is a gateway?
A defined point at the end of a phase where the outcomes are on the table and it is decided together whether to continue. This way no open items pile up until go-live.
Can you pick up a project that is already running and fit it to these phases?
Yes. We first assess the situation, secure what is viable and re-establish control at the appropriate phase.
Let's assess your implementation.
A first conversation in which we clarify your starting position and the appropriate phases. Senior-led, without detours.
Arrange a conversation