How a Business Central implementation runs, from scoping to go-live

A Business Central implementation is the work that turns a licence into a finance, stock and sales system your staff actually trust. The software is the smaller part. Most of the effort goes into understanding how your business really runs, deciding how it should run in future, moving clean data across and getting people comfortable. This page walks through the whole project as a UK finance director or IT lead will experience it.

What "implementation" means for Business Central

Business Central is a cloud-first ERP from Microsoft for small and mid-sized companies. Because the standard product is broad, an implementation is mostly about configuration and fit, not building from scratch. You decide how your chart of accounts, dimensions, posting groups, items, locations and approval flows should look, and the integrator sets them up, tests them with you and trains your team.

Two things shape every project in this country. First, Microsoft supplies the UK localisation directly, so VAT, bank formats and the statutory basics start from a supported base rather than a third-party add-on. Second, online licences are sold through partners only: Microsoft's documentation states they can be bought solely through the Cloud Solution Provider programme. You therefore deal with an integrator for both the subscription and the project, which is why the choice of partner matters from the very first conversation. Our page on choosing a Business Central partner covers how to compare them.

The method: what Microsoft provides and what it does not

Microsoft offers FastTrack for Dynamics 365, a programme run by its product engineering team. Its architects do not design or build your solution. They run workshops aligned with the key project phases so that risks are spotted early. The delivery framework behind it is called Success by Design, and it structures how those solution architects engage with project teams and partners.

Not every project qualifies for FastTrack, and it never replaces your integrator's own method. Ask any candidate how they run the project, what their sign-off gates are and whether they use the Success by Design vocabulary. A partner who cannot describe their approach in plain terms is a risk in itself.

The phases at a glance

Scoping: decide what the project is for

Scoping is where an experienced integrator earns their fee. The questions are unglamorous: how many legal entities, which sites and warehouses, which currencies, which processes stay out of scope for now, and what the board expects to see at the end. A written scope statement stops the quiet growth of requirements that damages budgets later.

Your side should bring a named sponsor with authority over budget and a project lead with real time to spend. Decide at this stage whether you want a single go-live or a phased rollout, for example finance first and manufacturing later. Our guide to the general ERP implementation approach sets out the options in vendor-neutral terms.

Analysis: standard first, gaps second

During analysis the integrator walks through your processes and maps them to standard Business Central functions. Every difference becomes a gap, and every gap should receive one of three answers: adopt the standard way, change your process, or pay for an extension. The cheapest and most upgrade-safe answer is nearly always the first.

Keep a decision log. It records who decided what, and why, so that six months later nobody argues about why a posting rule works as it does. The output is the solution design document, and your sign-off on it is the real start of configuration.

Configuration and the first walkthrough

The integrator sets up the company, the chart of accounts, dimensions, number series, VAT posting groups, items, locations, price lists and user permissions, then shows you the system working with your own examples. Insist on seeing real scenarios such as a purchase to payment, an order to cash, a month-end close, rather than generic demonstrations.

Depending on your needs, the modules involved will include accounting and finance, stock and purchasing, sales and, where relevant, production. Treat each area as a separate acceptance step so problems surface while they are small.

Data migration: the phase that decides the schedule

Migration is rarely the longest task on paper, but it is the one that delays go-live most often. The work breaks down as follows:

• Decide what to bring. Master data (customers, suppliers, items, accounts) almost always. Open transactions yes. Years of closed history is a business decision, not a technical default; summary balances plus an archive of the old system are often enough.
• Cleanse before loading. Duplicate suppliers, inconsistent addresses, inactive items and unreconciled ledgers move across unchanged unless somebody fixes them. That somebody is you.
• Rehearse. Run at least one full trial load into a test environment and reconcile it against the legacy system, so the real cut-over is a repeat, not a first attempt.

If you are coming from Sage or another system, the dedicated page on Business Central migration goes deeper into mapping and reconciliation.

Integrations and extensions

Few UK businesses run on the ERP alone. Banks, card payment providers, e-commerce platforms, payroll, expense tools and logistics carriers all need to talk to it. List them during analysis, because each one needs a specification, credentials, test data and an owner. The page on Business Central integrations explains the options.

Customisation deserves caution. Extensions are legitimate when a real gap exists, but each one must be tested after every update and maintained for the life of the system. See Business Central customisation for how to judge whether one is justified.

Testing: user acceptance is your job

Integrators test their own configuration, but acceptance belongs to you. Write scenarios from your real working month: an order with a part delivery, a supplier credit note, a return, a foreign-currency payment, a VAT return. Staff who will use the system daily should run them, not only the project lead.

For UK companies, include the situations that standard localisation may not fully cover. Microsoft's own guidance says that VAT functions outside the standard set, such as Northern Ireland trade, VAT groups by consolidation or sectors like construction, depend on reseller partners or industry solutions. If any of those apply to you, raise them in scoping rather than discovering them during testing. Our guide to Making Tax Digital and your ERP lists the checks to run before go-live.

Training and change management

Training works best in two layers: key users trained early who help test and later coach colleagues, then role-based sessions for everyone else shortly before go-live. A session held too early is forgotten; one held too late leaves people anxious on the first morning. Details of what to expect are on the Business Central training page.

Do not underestimate resistance. People who have used spreadsheets or an older system for years will find shortcuts that bypass the new controls unless the reasons for the change are explained and the first weeks are supported.

Go-live and hypercare

Cut-over is a short, rehearsed sequence: freeze transactions in the old system, extract final balances and open items, load and reconcile them, then release users. Agree in advance what "go" and "no-go" look like, with the finance director holding the final say on balances.

After go-live, the first period-end close and the first VAT return are the real tests. Plan for close support from the integrator during these. Business Central is also updated by Microsoft on a regular schedule, and Microsoft recommends copying the production environment to a sandbox before each major update and scheduling the update there to test critical scenarios. Build that habit into your support arrangement; the page on support and maintenance explains how.

What drives duration and budget

No responsible adviser can give you a number without an analysis, and any figure quoted before one is a guess. The factors that move both time and cost are consistent:

• the number of legal entities, sites and currencies;
• the volume and quality of data to migrate;
• the number and complexity of integrations;
• how much of your process you are willing to adapt to the standard;
• the amount of extension development;
• how quickly your team makes decisions and finds time for testing;
• the number of users and the licence mix.

Microsoft's public price list shows three user types: Essentials at 80 USD per user per month, Premium at 110 USD and Team Members at 8 USD, all billed annually. Those are figures from the American page, and Microsoft states that displayed prices may differ from the real catalogue price depending on currency, country and regional variant, with the final price shown at purchase. Ask your integrator for a sterling quotation. The Business Central pricing page explains how to read it.

Pitfalls specific to Business Central projects

• Treating the cloud as a reason to skip planning. Quick to provision does not mean quick to implement.
• Choosing dimensions too late. Analysis dimensions drive reporting. Changing them after postings exist is painful.
• Heavy extension use. Each extension adds testing after every Microsoft update.
• Underestimating VAT edge cases. See the Northern Ireland and sector points above.
• No sandbox discipline. Testing updates on live data is avoidable; a sandbox copy is exactly what Microsoft recommends.
• Weak partner selection. Microsoft's partner designation relies on points for certifications and customer success. Individual consultants can hold the MB-800 functional or MB-820 developer certification, so ask which named people will work on your project and what they hold.
• No fallback. If a project is already off course, an independent audit and project rescue can reset it.

For a view tailored to British companies, including the regions where integrators operate, see Business Central in the UK.

Next step

If you are preparing a project, write a one-page description of your entities, users, key processes and must-have integrations. We use it to match you with an independent integrator suited to your sector and size. The service is free, and the integrator, not us, delivers the work.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.