How Does a Business Central Implementation Work? A Migration Guide

Choosing Business Central is the easy part. Getting it live with clean data, working integrations and a team that trusts the numbers is where projects succeed or stall.

This guide walks through how a Business Central implementation runs, what shapes its timeline and cost, and how to move from Dynamics GP, Dynamics NAV, QuickBooks or another system using Microsoft's own migration tools.

What Does a Business Central Implementation Involve?

An implementation is more than installing software. It is a set of workstreams that run in parallel and meet at go-live:

• Process design: deciding how each workflow will run in Business Central.
• Configuration: setting up companies, the chart of accounts, dimensions, posting rules, approvals and permissions.
• Data migration: moving master data, open balances and the history you need.
• Integrations and extensions: connecting other systems and filling functional gaps.
• Testing and training: proving the system works and preparing users to run it.
• Cutover and support: switching over and stabilizing after go-live.

Each workstream needs an owner on your side as well as on the partner's. In practice that means a project lead, a finance owner and a process owner for each department involved.

What Are the 5 Stages of a Business Central Implementation?

Microsoft's Success by Design framework, used across Dynamics 365 projects, splits an implementation into five stages. Most partners use their own phase names, but the work maps closely to these:

Each stage should end with a sign-off before the next begins. Protect the Prepare stage when deadlines tighten. Testing with real scenarios and real data is what catches problems before customers or auditors do.

How Long Does a Business Central Implementation Take?

There is no standard duration for a Business Central project, and a figure quoted before discovery is an estimate at best. These factors decide how long yours takes:

• Scope: finance-only projects move faster than ones adding inventory, warehousing, manufacturing or projects.
• Number of companies: each legal entity adds setup, testing and reporting work.
• Data quality: duplicate customers, unused accounts and messy item records slow every trial migration.
• Integrations and extensions: each one is a small build-and-test project of its own.
• Team availability: key staff still have day jobs, so plan around busy periods.
• Decision speed: waiting a week for an answer delays everything that depends on it.

Fixed dates matter too. Plan go-live away from your financial year-end, and if you are migrating from Dynamics GP, Microsoft advises running the cloud migration between Business Central's scheduled environment updates.

What Drives Business Central Implementation Costs?

Implementation cost is separate from licensing and depends on the same factors as the timeline: scope, entities, data, integrations, customizations, training and post-go-live support. The other big variable is how the work is priced.

Whichever model you choose, compare proposals line by line. Each one should spell out the number of trial migrations, the integrations included, the training hours and the length of post-go-live support.

A low quote may mean less discovery, fewer trial migrations or minimal training, and those gaps tend to return as change orders. Keep a contingency for scope you only uncover once the project starts.

Which Business Central Migration Path Fits Your System?

Microsoft provides built-in tools for its own legacy products and simpler import options for everything else. Your current system decides the route:

The cloud migration tool needs the source database on SQL Server 2016 or later, at compatibility level 130 or higher. Dynamics SL users have a fixed deadline too: Microsoft's extended support for SL 2018 ends on July 11, 2028.

How Do You Migrate From Dynamics GP to Business Central?

Microsoft ends Dynamics GP support for product enhancements, tax updates and technical support on December 31, 2029. Security patches continue, if needed, until April 30, 2031, and Microsoft encourages GP customers to move to Business Central.

The cloud migration tool brings across:

• Company setup, such as payment terms, shipping methods and sites
• Master data for accounts, customers, vendors and items
• Transactional data, plus customer, vendor and item classes and vendor 1099 data
• A historical snapshot of past transactions, limited to the years you choose

Start with Microsoft's migration assessment tool, which flags likely issues in your GP setup. Run the migration in a sandbox first: data moves table by table, failures are logged, and you can fix issues and rerun replication.

Then use the built-in validation to compare GP with Business Central. Deposit posted cash receipts in GP beforehand, because undeposited receipts aren't migrated, and close any years marked historical in GP once they arrive open in Business Central.

How Do You Upgrade From Dynamics NAV to Business Central?

Dynamics NAV is running out of support. Extended support for NAV 2017 ends on January 11, 2027, and for NAV 2018 on January 11, 2028. After those dates, Microsoft stops releasing security updates.

There is no one-step move from NAV to Business Central online. Microsoft's route has three steps:

• Upgrade NAV to Business Central version 14 on-premises. Microsoft's documented upgrade path starts from NAV 2015.
• Rebuild customizations as extensions. Data in tables changed through code customizations can't be carried forward, so those changes must first become apps.
• Move to the cloud. Either upgrade to version 25 or later and run the full cloud migration, or use Microsoft's reimplementation tool, currently in preview, to bring only master data, opening balances and setup.

Step 2 needs the most planning. It is also the right moment to drop customizations that standard features or Marketplace apps now cover.

How Do You Migrate From QuickBooks or Another System?

Business Central includes Microsoft migration extensions for QuickBooks Desktop and QuickBooks Online, run from the Data Migration assisted setup guide. They bring across customers, vendors, items and accounts. The Desktop version can also move on-hand inventory and open invoices, credit memos and payments.

Check three limits before you start:

• Partial payments don't migrate; only full document amounts do
• The QuickBooks Desktop exporter currently supports only the 2017 and 2018 versions
• Beginning balances need checking, because QuickBooks doesn't store current balances for all accounts

For Sage, Xero or other systems, data moves through configuration packages: Excel templates for setup, master data and opening balances.

What Data Should You Migrate to Business Central?

Migrating everything is rarely worth it. Old, unused records clutter the new system and slow down every trial run. A practical split looks like this:

Keep detailed history accessible elsewhere: a read-only copy of the old system, an archive database or a reporting tool. Decide early whether to redesign the chart of accounts, and clean data in the source system before the first trial migration, not after.

How Should You Handle Integrations and Customizations?

List every system that exchanges data with your finance team today: ecommerce, payroll, banking, CRM, EDI and reporting tools. For each one, decide whether a ready-made Marketplace app covers it or a custom connection is needed, and who will maintain it. Where a custom connection is needed, build it on Business Central's standard APIs so it stays supportable.

Apply the same discipline to customization. Business Central is changed through extensions rather than edits to its core code, so ask three questions of every request:

• Can a standard feature or setting do this?
• Does a Marketplace app already do it?
• Is the business value worth maintaining custom code through every Microsoft update?

Build a custom extension only when the first two answers are no and the third is yes.

How Do You Test, Train and Go Live Safely?

Test in a sandbox environment with your own migrated data, not demo data. Walk through complete scenarios, such as order to cash, procure to pay and month-end close, and reconcile balances between the old and new systems before signing off.

Document how each scenario should end, so testers know what a pass looks like. Run more than one trial migration so the final cutover holds no surprises.

Train by role, so each person learns the tasks they actually do. Microsoft Learn offers free Business Central training modules that work well for preparation and refreshers.

For cutover, agree a freeze date in the old system, run the final migration, reconcile opening balances and keep the old system read-only for reference. Name super users in each department to handle first-line questions during the first weeks.

What Happens After Go-Live?

Go-live starts the payoff, not the end of the project. Plan for:

• Stabilization: a defined support period to fix issues and answer questions quickly.
• Update testing: before each major Microsoft update, test your extensions in a preview environment. If Microsoft can't update an incompatible extension, it can be uninstalled during the update, with its data kept until a compatible version is installed.
• Adoption reviews: check which processes still run outside the system and close those gaps.
• Ownership: decide who approves new users, permissions and setup changes once the partner steps back.
• A backlog: park nice-to-have requests from the project and deliver them in planned phases.

What Should You Ask a Business Central Implementation Partner?

The partner shapes the outcome as much as the software. Ask each one:

• Are you a Microsoft Solutions Partner, and how long have you worked with Business Central?
• How many migrations have you completed from our current system?
• Who exactly will work on our project, and will they stay on it?
• How do you run trial migrations and validate the results?
• What is included in your quote, and what triggers a change order?
• How much training and post-go-live support is included?
• How do you test our extensions before each Microsoft update?
• Can we speak with a client in our industry?