Business Central Implementation Timeline: What Happens in Each Phase

One of the first questions we hear is how long a Business Central implementation takes. For a growing company with a single legal entity and standard finance, sales, purchasing and inventory needs, three to six months is a realistic range. Manufacturing, advanced warehousing, multiple entities and integrations push it toward the longer end or beyond.

Here is how that time is spent, and what your team contributes in each phase.

Phase 1: Discovery (2–4 weeks)

Discovery is where the project is won or lost. We run workshops with finance, operations, sales and purchasing to understand how the business actually works today, where the pain points are, and what needs to change.

Your team: key process owners available for workshops, sample documents and reports, and decisions on scope.

Output: a requirements list, a fit/gap analysis against standard Business Central, and a confirmed scope and plan.

Phase 2: Solution design (2–4 weeks)

The architect turns requirements into a written solution design: chart of accounts and dimensions, posting setup, inventory and costing, warehouse flows, approvals, integrations, reports and any extensions.

Your team: review and sign off the design. This is the cheapest point to change your mind.

Phase 3: Build and configure (4–8 weeks)

Business Central is configured to the design in a sandbox environment. Extensions and integrations are developed and tested. Data migration starts in parallel, with the first test loads of master data.

Your team: data cleanup in the legacy system, answering configuration questions, and reviewing work in progress in regular demos.

Phase 4: Testing and training (3–6 weeks)

Testing moves from individual functions to full end-to-end scenarios: quote to cash, procure to pay, inventory and warehouse flows, production if applicable, and a simulated month-end close. Training is delivered by role, using your own data.

Your team: run the user acceptance tests, log issues, and sign off when scenarios pass. Key users become internal champions.

Phase 5: Cutover and go-live (1–2 weeks)

The final data migration is loaded and reconciled: trial balance, receivables, payables and inventory valuation all tie out to the legacy system. Open documents are loaded, users switch over, and the legacy system becomes read-only.

Your team: freeze changes in the old system, verify reconciliations, and process the first live transactions with support close by.

Phase 6: Hypercare and first close (4 weeks)

The weeks after go-live surface questions that no amount of testing finds. We provide hands-on support through the first month-end close, reconcile it in detail, and fix any setup issues before they compound.

What makes projects run late

• Decision delays. Design questions that wait weeks for an answer push everything downstream.
• Data cleanup left too late. Start it in week one, not in testing.
• Key users without time. If the people who know the processes are fully booked with their day jobs, testing and training suffer.
• Customizing before exploring standard. Business Central covers more than most teams expect; try standard first.

Planning your implementation?

At ERPLO, the architect who scopes your project also designs and leads it. Learn more about our Business Central implementation service, or talk to an architect about your timeline.