Business Central
A Business Central implementation runs in six phases: process discovery, chart of accounts and dimension design, master data cleanup and migration.
Reviewed 2026-08-24 by the Machina IT engineering team.
A Business Central implementation runs in six phases: process discovery, chart of accounts and dimension design, master data cleanup and migration, configuration and integration build, user acceptance testing with a sandbox month-end close, then a rehearsed cutover with staffed hypercare. Single-entity manufacturing rollouts typically take three to six months, and the schedule is driven by data quality and integration count far more than by software configuration.
Document how quote to cash, purchase to pay, and production actually run today, including the spreadsheets and verbal handoffs. Decide deliberately which of those processes change at go-live and which are preserved.
The output is a written process map with named owners per step. Without it, configuration decisions get made by whoever is in the room.
Most legacy charts encode site, department and product line into account numbers. Business Central handles those as dimensions, which collapses the account list and makes reporting flexible.
Getting this wrong is expensive to reverse after transactions post, so it is designed and signed off before any data loads.
Cut over at a period boundary: freeze the legacy system, load verified opening balances and open documents, reconcile, then open the doors.
Staff the first two weeks for floor-side support at the transaction points — shipping, receiving, production posting — because that is where adoption is won or lost.
Common mistakes
Common questions
Three to six months for a focused single-entity manufacturing rollout. Multi-site, multi-entity or heavily integrated programs run longer, driven by data quality and integration count.
An executive sponsor, a finance owner, an operations owner, and one person per transacting area. Roughly a day a week each during configuration and testing is realistic.
Yes — finance and inventory first, then production, then warehouse automation is a common sequence. Phasing reduces risk but extends the period of dual processes, so time-box it.
We review your network, security posture, cloud tenant and recovery plan, then hand you a plain-language report of what we found and what it means for the business.
