+1 480 485 7373
Microsoft Teams
Why a credible Business Central implementation timeline comes after discovery
Buyers often ask for a timeline in the first conversation. It is a fair question, since a go-live date drives staffing, contract renewals on the old system and board reporting. The trouble is that the answer depends on facts nobody has gathered yet. How many processes change, how clean the data is, and how quickly your people can make decisions all set the pace more than the software does.
A partner who names a date before understanding those facts is either assuming a very simple project or planning to adjust later. We prefer to run discovery and write down the scope first. Then we build a schedule backwards from a sensible cutover point, such as the start of a fiscal period, with the dependencies visible.
The six phases of a Business Central implementation
- 1
Discovery
Workshops with each department map current processes, reports and integrations. The output is a fit-gap list and a written scope.
- 2
Design
A solution design records decisions on chart of accounts, dimensions, posting groups, inventory method, approvals and integrations.
- 3
Build and configure
We set the system up in a sandbox, install or develop extensions, and connect integrations.
- 4
Data migration
The team extracts, cleans, maps and loads master data, open items and balances, usually in several practice rounds.
- 5
Testing and training
Users run real scenarios end to end, sign off on results, and learn their daily tasks in the configured system.
- 6
Cutover and first close
Final balances load, the old system freezes and users go live. Then the team closes the first period end with support on hand.
What stretches each Business Central implementation phase and what shortens it
Four decisions that set a Business Central implementation timeline
Scope of phase one
Going live on finance and core operations first, then adding modules, often gets value sooner than one large launch.
How much history moves
Balances and open items move quickly. Detailed transaction history adds mapping, loading and reconciliation rounds.
Who decides
A named owner per area with authority to choose keeps design moving. Committees slow every open question.
The cutover date
A fiscal period start gives clean opening balances. A date chosen for other reasons can force extra reconciliation.
Warning signs a Business Central implementation timeline is at risk
- ✓Design decisions are still open once configuration has started
- ✓Nobody has run a full practice data load and reconciled it
- ✓Testers keep postponing sessions because of their normal workload
- ✓Integration partners have not confirmed their side of the connection
- ✓No one has rebuilt or checked the reports finance relies on
- ✓Training sits in the week of go-live rather than before it
Phasing the rollout instead of one big launch
Not every capability needs to be live on day one. Many companies start with the general ledger, payables, receivables, banking, purchasing and sales, then add warehouse automation, manufacturing, advanced reporting or additional entities afterwards. Each later phase runs on a working system, which lowers the stakes of each step.
The trade-off is a period where some work stays in the old tools or spreadsheets. That is fine when you plan and time-box it, and risky when it drifts. The scope should say which phase each process belongs to and what the interim workaround is.
How phasing changes the Business Central implementation timeline
A phased plan also changes how you read a Business Central implementation timeline. Instead of one distant date that everything hangs on, you get a sequence of smaller milestones, each with its own test cycle and sign-off. If one later phase slips, the finance team keeps closing the books in the new system while the delayed piece catches up.
Business Central implementation timeline questions from scoping calls
How long does a Business Central implementation take?
It depends on scope, data and how quickly your team can make decisions, so we set the schedule after discovery. A single-entity distributor with clean data needs far less time than a multi-entity manufacturer with custom integrations. Once we write the scope, we build the Business Central implementation timeline backwards from a sensible cutover date. We share that plan in writing before work starts.
What is the most common cause of delay?
Slow decisions and unavailable staff cause more delay than technical problems. When design questions wait for a meeting that keeps moving, every later phase shifts. Data cleanup that starts late is the second frequent cause. Naming an owner per area and cleaning data early addresses both.
Can we go live in the middle of the year?
Yes, going live mid-year is common and works well at the start of any accounting period. You load opening balances for that period and the year-to-date figures you need for reporting. Year-end is sometimes simpler, but it often clashes with audit and close work. We usually recommend a quiet period start with enough runway to rehearse.
More Business Central implementation timeline questions
Should we run the old and new systems in parallel?
Full parallel running is rarely worth the double workload for your staff. A better approach is a thorough test cycle and a rehearsed cutover, followed by close support through the first period end. Keeping the old system read-only for lookups gives most of the comfort people want from parallel running. Some regulated processes may justify a short parallel check.
What can our team do now to shorten the project?
Start cleaning customer, vendor and item data and document how each department works today. Decide who will own decisions for finance, sales, purchasing and warehouse. Collect the reports people actually use and mark the ones nobody reads. Each of these removes waiting time once the project starts.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.