Business Central Implementation
Requirement study, configuration, data migration and go-live support for Business Central.
Typically 8–16 weeks depending on the number of modules, locations and the state of existing data
Implementing Microsoft Dynamics 365 Business Central means moving your finance, sales, purchasing and inventory processes into a single system, with defined roles and a common set of data underneath them.
Most of the effort is not technical. It goes into deciding how each process should work, agreeing the chart of accounts and master data, and getting existing data into a state where it can be migrated.
Where implementations run into trouble
The common causes are familiar: master data that was never cleaned, so duplicate customers and items carry into the new system; processes that were undocumented, so requirements emerge during testing rather than before it; and no one internally given the time to own the project.
None of these is a software problem, and none is solved by configuration. We raise them at the start because they determine whether the timeline is realistic.
Phasing and go-live
Finance is usually implemented first, since everything else posts into it, with sales, purchasing and inventory following. Going live at the start of a financial period makes reconciliation considerably easier than a mid-period cutover.
We run the new system alongside the old through at least one full reporting cycle, so that the first GST and financial reporting from Business Central can be checked against a known position.
Who needs this
- Businesses that have outgrown a basic accounting package
- Businesses with multiple locations or warehouses needing common data
- Businesses where several people need controlled access to the same records
- Businesses whose reporting requirements exceed what their current system produces
Eligibility and conditions
- A Business Central subscription, or willingness to procure one
- Existing accounting data that can be extracted
- An internal owner with time allocated to the project
What this covers
-
Requirement study
How you work today, documented before anything is configured.
-
Configuration
Chart of accounts, dimensions, tax setup, roles and permissions.
-
Data migration
Masters and opening balances moved and reconciled.
-
GST localisation
Tax configuration tested against filing requirements.
-
Training
Users trained on the processes they will actually run.
-
Go-live support
Support through the first reporting cycles.
How the process works
-
Requirement study
Current processes documented and gaps identified.
-
Design and configure
Chart of accounts, masters, tax setup and permissions.
-
Migrate data
Masters and balances moved, then reconciled.
-
Test
Real transactions run through, end to end.
-
Train and go live
Users trained, cutover completed, support through first close.
Documents required
-
Current chart of accounts
From the existing system.
-
Master data
Customers, vendors, items and price lists.
-
Opening balances
Trial balance as at the intended cutover date.
-
GST registration details
GSTIN for each registered location.
-
Existing report formats
The reports your team relies on today.
-
User list and roles
Who needs access and to what.
The list above is indicative. Additional documents may be required depending on your case and the current departmental requirements.
Frequently asked questions
Is Microsoft Dynamics 365 Business Central suitable for a small business?
It is designed for small and mid-sized organisations, but suitability depends on whether your requirements have actually outgrown a simpler system — transaction volume, multiple locations, several people needing controlled access to the same data, or reporting your current package cannot produce.
If a simpler system would serve you, we will say so. An ERP implemented over processes that are not yet settled tends to formalise the problems rather than solve them.
Considering Business Central?
Tell us about your current system and what is not working, and we will set out what an implementation would involve.