HOLYERP
← Back to blog

Business Central Implementation: Phases and Process

8 min read
Business Central Implementation: Phases and Process

A Business Central implementation stays on schedule when scope, responsibilities and data migration are settled before the first configuration step. For a standard scope, rolling out Microsoft Dynamics 365 Business Central in the cloud typically takes 12 to 18 weeks – provided the project follows clear phases and decisions are not postponed for months. This article explains what those phases look like, which roles you need internally and where projects usually stall.

Why a structured implementation matters

Many companies choose Business Central to replace parallel Excel spreadsheets, outdated on-premise systems or isolated accounting tools. The software itself is quick to provision: a cloud environment is ready in a short time. The real effort lies elsewhere – in processes, master data and user adoption.

Typical reasons ERP projects take longer than planned:

A structured implementation addresses exactly these points before they become expensive.

The phases of a Business Central implementation

A proven approach divides the project into six phases. The length of each phase depends on scope; the overview below shows the typical flow of a standard project.

PhaseContentResult
1. AnalysisCurrent processes, requirements, interfacesAgreed project scope
2. DesignTarget processes, chart of accounts, dimensions, permissionsSolution design
3. ConfigurationSetup, extensions, integrationsSystem ready for testing
4. Data migrationMaster data, open entries, opening balancesVerified data
5. Testing and trainingProcess tests, key-user trainingGo-live approval
6. Go-live and hypercareProduction start, close supportStable operation

Phase 1: Analysis and scope

The analysis captures how work is actually done today: how do purchasing, sales, inventory, finance and project billing run? Which reports does management need? Which systems must be connected – e-banking, an online shop or a document management system?

The result is a written, agreed scope. It is the most important basis for timeline and budget. Anything outside it is assessed later as a change – which protects both sides.

Phase 2: Solution design

Design defines how Business Central will map your processes: chart of accounts, dimensions for cost centres and projects, approval workflows, number series and user permissions. This is also where you decide where the standard is enough and where an extension is needed.

Our recommendation: as much standard as possible. Every custom extension has to be maintained through updates. Microsoft updates Business Central regularly, and lean customisations make those updates much simpler.

Phase 3: Configuration and extensions

Now the system is set up. Extensions are built as AL extensions, interfaces are connected and reports prepared. Groups with companies in several countries also set up each localisation here – including the appropriate tax, e-invoicing and reporting requirements for Germany, Switzerland and Austria.

Phase 4: Data migration

A new implementation usually migrates master data (customers, vendors, items, G/L accounts), open entries and opening balances. Full transaction history from previous years is usually archived in the legacy system rather than migrated.

Plan at least one migration trial run. Only then do you see how clean the legacy data really is: duplicate customers, missing tax numbers or incomplete item records.

Phase 5: Testing and training

Testing goes process by process rather than function by function: from purchase order to payment, from sales order to invoice, from bank statement to applied open entries. Key users from each department test with real cases and then train their colleagues.

Phase 6: Go-live and hypercare

Ideally, go-live happens at the start of a month or quarter. In the first weeks afterwards – the hypercare phase – close support matters: questions are answered quickly and small adjustments are made promptly.

How long does the implementation take?

For a standard scope, 12 to 18 weeks is a realistic range. It is essential to distinguish a new implementation from a migration from Dynamics NAV (Navision). A NAV migration is a separate, longer project and takes 2 to 8 months depending on the number of companies, customisations and historical data. We describe that path in Migrate Dynamics NAV to Business Central.

The timeline grows mainly with:

Roles you need internally

A successful implementation is never only the partner's job. On your side, these roles should be filled:

  1. Project owner with decision-making authority, usually from finance or management.
  2. Key users in each department who know the processes and have time for testing and training.
  3. IT contact for users, security and interfaces.
  4. Data owner who cleans legacy data and signs off the migration.

Plan realistically: during testing and training, key users need noticeable time alongside their daily work.

Business Central in international groups

Companies with entities in Germany, Switzerland and Austria need consistent processes and reporting while each entity meets its local requirements. Chart of accounts, taxes, e-invoicing, currencies and permissions should be agreed during solution design.

HOLYERP implements Business Central for DACH groups with shared reporting, local requirements and EUR/CHF workflows. Holy Document Capture automates invoice receipt and reading, while each company retains clear approval rules. Read more in ERP for finance, projects and company growth.

After go-live: operation and improvement

Go-live is the start of operation. Legal changes, new requirements and Microsoft updates are part of everyday life. What matters is that issues do not wait days for a ticket.

That is why we use the HOLY BC Agent – an integrated Holy AI assistant for fast diagnostics, planning changes and resolving blockers without long waits for developers. Licences, implementation, training and ongoing maintenance come from one place.

Microsoft's official product documentation is available on Microsoft Learn: Business Central documentation.

Common implementation mistakes

From practice, a few patterns stretch projects unnecessarily:

Checklist before the project starts

Conclusion

A Business Central implementation is not purely an IT project but a reorganisation of your processes. With a clear scope, filled roles, a migration trial run and process-based testing, a standard project stays within 12 to 18 weeks.

Planning a Business Central rollout? Send a question to HOLYERP and we will discuss what the process could look like for your company.

Questions we get asked

For a standard scope, 12 to 18 weeks is realistic. A migration from Dynamics NAV (Navision) is a separate, longer project of 2 to 8 months depending on companies, customisations and data.

Related posts