Business Central
What to check before hiring a Dynamics 365 Business Central consultant: process depth, data migration approach, integration experience and post go-live support.
Reviewed 2026-08-24 by the Machina IT engineering team.
Choose a Business Central consultant on process depth rather than product familiarity. The questions that predict a successful implementation are how they map your quote-to-cash and production processes, how they handle master data cleanup, how many integrations they have actually built against Business Central APIs, whether they design your chart of accounts and dimensions before loading data, and who staffs hypercare through the first month-end close.
Most consultants can configure posting groups. Far fewer will tell you that your legacy chart of accounts should collapse into dimensions, that half your BOMs do not match what the floor builds, or that a planned integration should be replaced by a native API.
Ask them to describe a decision they talked a client out of. Consultants who only take direction will hand you your current problems in a new system.
If you run production, BOMs, routings, costing methods, subcontracting and shop-floor data capture are the hard parts. A consultant strong in distribution or professional services may be excellent and still be the wrong fit.
Ask specifically what they have implemented on a plant floor, and whether they also support the network, scanners and workstations the ERP depends on — or hand that off.
Common questions
They map current processes, design the chart of accounts and dimensions, plan and execute data migration, configure modules and integrations, run testing including a sandbox month-end close, train users by role, and support the business through go-live and the first closes.
Small, single-entity finance-only rollouts are self-implementable. Manufacturing, multi-entity, integration-heavy or migration-heavy projects fail far more often without experienced help, and the failure is usually data and process design, not software.
It depends on scope — entities, integrations, data condition and how much process redesign is in scope. Ranges and the factors that move them are broken down on our Business Central implementation cost page.
Three to six months for a single-entity manufacturing rollout is typical. Data quality and integration count drive the schedule far more than configuration does.
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.
