1. Home
  2. Services
  3. Business Central implementation

Business Central implementation: Microsoft's tools and the choices you can't undo

A Business Central implementation sets up Microsoft's ERP for the way your company works, moves your data in and trains your team. Microsoft sells the licenses only through its Cloud Solution Provider program; the setup is separate work, done by the team you choose. Our team has taken both Business Central and Dynamics 365 Finance live, and each part of our work can be bought alone or as one project.

Checked 19 November 2026

What a Business Central implementation covers

It takes Business Central from an empty tenant to the system your team runs every day. It covers licenses, environments, setup, data, design choices, tests, training and go-live. Microsoft’s guide points startups and small firms to Business Central. Its full Dynamics 365 guide is aimed at medium-sized and larger firms.

You can buy each service from us on its own, or all of them as one project. The services: discovery and consulting, mapping your processes, the implementation itself, the data move, training, and support once you are live. Training happens on site or remote, whichever your team prefers.

Here is the work in order, with the Microsoft tool or rule behind each step.

Scroll the table sideways to see every column.

Step What gets settled Microsoft’s tool or rule
Licenses Essentials, Premium, Team Members or Device Sold only through Cloud Solution Providers
Environments Production, sandboxes, storage, country One production and three sandboxes included
Company setup Number series, posting setup, approvals Assisted setup guides and configuration packages
Data Customers, vendors, items, opening balances Configuration packages, templates and journals
Design Costing method, dimensions, permissions Choices that cost a lot to change later
Extensions Marketplace apps and your own code Per-tenant extensions, installed from the admin center
Go-live and after Update window, monitoring, restores Admin center, telemetry, 28-day restore

Who sells the license and who does the setup

You can only buy Business Central licenses through CSP, its Cloud Solution Provider program. You must accept the Microsoft Customer Agreement before a CSP reseller can place an order for you. Extra environments and database storage are add-ons, bought through that reseller too.

The setup is a separate job. You can do it in-house, ask your reseller, or hire a team that does implementation work. We are that third kind. You keep your license with your reseller, and we do the consulting, the setup, the data move, the training and any agent build.

One more party can matter. Some countries get no local version from Microsoft. There, other firms sell local apps on Microsoft’s Marketplace. If you trade in such a country, that app becomes part of the setup plan.

Pick the license mix before you set anything up

Each license type changes what people can do. Business Central enforces it through entitlements, which set the objects each user may use.

  • Essentials and Premium. Premium adds service management and manufacturing to everything in Essentials. New users start in the Essential experience, which shows fewer features than the Premium experience.
  • Team Members. A light license. Microsoft says the license always wins over permissions. A Team Member user given SUPER still sees only what a Team Member may see.
  • Device. One device license covers a shared device, such as a point of sale, a shop floor device or a warehouse device, used by several people. A device user can’t be the first user to sign in.
  • Office users. Once your company has Essentials or Premium, staff with only a Microsoft 365 license can open records shared with them in Teams.

Two rules catch teams out. First, a license can’t move to someone else within 90 days of its last move. The exceptions are an absence or a broken device. Second, sandboxes check licenses too, since 2020 release wave 2. That is useful: a test in a Business Central sandbox shows a license gap before go-live does.

Turning the trial into the live company

If you started in the 30-day trial and want to keep that company, the order of sign-ins matters. Microsoft says the first person to sign in after the paid license lands must hold that license. If an admin signs in first, the trial carries on until it expires. Agree who signs in first.

Environments, storage and backups

Essentials and Premium include one production environment and three sandboxes, at no extra charge. Each extra production environment you buy adds three more sandboxes and 4 GB of shared storage. Business Central online has no NAV license files. Rights come from the license itself.

Storage

Each customer gets up to 80 GB of database storage, plus an allowance for each licensed Essentials or Premium user. All environments share that pool. Files and other blob data stored in the database count toward it, including the Tenant Media tables. So does data left behind by an extension you uninstalled without deleting its data.

Going over does not stop daily work. Transactions keep running. What stops is the creation of new environments and copies, until you free space or buy more.

Country and data location

Each environment’s localization fixes the Azure geography where its database lives. Local versions also change. In Business Central 2025 release wave 2, the UK BaseApp moved into the shared W1 version.

Restores

Microsoft backs up production on its own, and often. An admin can restore an environment to any time up to 28 days ago. Microsoft’s restore rules:

Scroll the table sideways to see every column.

Rule Microsoft’s wording, in short
Time limit Any point up to 28 days back
Where Same Azure region and same localization only
Production Restores to production or to a sandbox
Sandbox Restores only to a sandbox
Who Internal or delegated admins with the D365 BACKUP/RESTORE permission set
Plan Paid subscriptions only

Note the time before each big data load. If a load goes wrong, that time is your restore point.

Set up the company with configuration packages

Configuration packages are Microsoft’s setup tool, part of what it calls RapidStart Services. A package holds setup data from one company, so you can apply it to another. Business Central online ships with one package for Microsoft’s default application, local features included.

Templates fill in default values on imported records, so each imported customer or item gets your default settings. A questionnaire can be exported to Excel for your team to fill in. The person who imports a package needs Direct Insert and Direct Modify permissions.

Microsoft’s rules for packages are strict:

  1. Start in a sandbox. Microsoft says to set up the company in a sandbox first, so users can practice before production.
  2. Match versions. A package must use the same Business Central version as the environment it goes into.
  3. First setup only. Packages are not meant for companies already in production. A large import can slow the system and keep every user out while it runs.
  4. Use an XMLport later. For data moves into a live company, Microsoft strongly recommends an XMLport instead.
  5. No posted entries. You can’t import into tables that hold posted entries, such as customer, vendor and item ledger entries. Opening balances go in through journal lines once the master data is in place, for G/L accounts and the same way for customers, vendors and items.
  6. Bank accounts are different. Microsoft warns not to post bank opening balances straight to the G/L accounts linked to the bank accounts.

If you run more than one company, common values can be copied from one company to another in the same tenant. Microsoft’s example is a standard list of symptom codes for service management.

Microsoft’s Assisted Setup page covers other first tasks. One sets up approvals, such as a sign-off for amounts above a set limit. Another invites your outside accountant into Business Central to work on the books with you.

Five design choices that are hard to undo

Most settings in Business Central can change later, but these five cost a lot to change. The first two lock in as entries post.

1. The costing method for each item

Microsoft says you can’t change an item’s costing method once item ledger entries exist for it. FIFO, LIFO, Average and Specific value stock increases at what you paid. Standard values them at a set standard cost. Agree the method with your finance lead before the first receipt posts. Then leave it.

2. Global and shortcut dimensions

Dimensions tag entries for reports, such as by department or region. You get only two global dimensions, and up to eight shortcut dimensions. Changing a global dimension later can take a long time, slow the system and lock tables while it runs. So pick the two you filter by most.

3. Permissions and security groups

Security groups replaced user groups from 2023 release wave 1 (version 22). User groups were removed in 2024 release wave 2 (version 25). Build access on security groups and permission sets from day one. One rule surprises people: if a permission sits in both an included and an excluded set, it is excluded.

4. The environment’s localization

The localization ties an environment to a country version and an Azure geography. A restore can’t cross it. Pick it once.

5. Standard features or your own code

Extensions add features on top of Microsoft’s existing objects. Each one is code you test before every major update, so try standard features first.

Moving data in from your old system

Microsoft’s migration FAQ sets the rules for its cloud migration tools. The source database must run on SQL Server 2016 or later, at compatibility level 130 or higher.

Scroll the table sideways to see every column.

Coming from Microsoft’s route
Business Central on-premises, version 25 or later Migrate straight to Business Central online
Business Central on-premises, versions 15 to 24 Upgrade on-premises to at least version 25, then migrate
Business Central 14 The Reimplementation tool moves selected data to the cloud with no upgrade first
Dynamics NAV Upgrade to Business Central on-premises, then switch online
QuickBooks or Excel An assisted setup imports vendors, customers and items
A product with no Microsoft tool Configuration packages, mapped in Excel

NAV owners face a deadline: Microsoft’s lifecycle page shows extended support for NAV 2018 ending on January 11, 2028 (Pacific time), with mainstream support over since January 10, 2023.

Microsoft’s pages we read name a built-in tool for QuickBooks and none for Xero or Sage. So data from either goes in through configuration packages. Microsoft’s data migration overview did not load when we tried it on 19 November 2026. Our Dynamics 365 AI agents page sets out what Microsoft’s QuickBooks tool moves and what it leaves behind, and how Dynamics GP moves across.

Extensions, Marketplace apps and the update window

A Business Central environment is a set of apps. You install each one as a global app from Microsoft’s Marketplace, as a per-tenant extension (PTE), or as a DEV extension while you build.

  • Marketplace apps. Microsoft checks each new version against the Business Central versions the publisher supports. Preview versions install only in sandboxes.
  • Your own extensions. An admin uploads them in the admin center. Each can install at once, in the next update window, or with the next minor or major update.
  • Removing apps. You can delete an app’s data when you remove it. After that, Microsoft says, a point-in-time restore is the only way back.

The update window

Business Central gets two major releases a year, one in April and one in October. Plan for both. Every environment has an update window, set by default from 8:00 PM to 6:00 AM local time. You can move it, but it must be at least six hours long. An update that doesn’t finish inside the window is canceled and tried again seven days later.

So set the window to your quiet hours, and test every per-tenant extension in a sandbox before each major release.

After go-live: monitoring and training

Business Central can send telemetry to Azure Application Insights, online or on-premises. Since 2020 release wave 2, each extension can send its own telemetry too. Microsoft’s telemetry list covers configuration package work: exporting, importing, applying and deleting. So once telemetry is on, each data load leaves a record.

Training does not stop at go-live. New staff, new modules and Microsoft’s twice-yearly releases each need it.

Where AI fits in a Business Central rollout

Microsoft’s Sales Order Agent finds customers by matching email addresses. Contacts with no email, or an old one, need manual work for each request. So clean contact emails during setup, before the agent is turned on.

Microsoft lists its Sales Order Agent as generally available. Its Payables Agent watches mailboxes for vendor invoices and credit notes, and shows drafts for a person to review. Microsoft says it is validated and supported in English only. Agents use Copilot Credits when a user runs them, and your company is charged for those. Agents also need an Azure subscription, Microsoft says. For what each Microsoft agent reads, see Dynamics 365 AI agents. Business Central MCP server covers how assistants such as Claude connect.

In the RFQ system our team built on ERPNext, a person approves every quote before it goes out to a customer. Read the case study: a multi-agent RFQ system in ERPNext.

What our team brings to a Business Central project

Our team has taken both Business Central and Dynamics 365 Finance live.

Our team has taken nine ERPs live, from SAP to QuickBooks, so the system is your choice. That helps when Business Central is still one option on your list.

Our team has moved companies off QuickBooks, Xero or Sage into a full ERP.

On-demand ERP modules, each made for one business problem, are something our team has delivered. Our ERP consulting page covers that choice.

For links to your store, CRM or warehouse system, see Business Central integration. If you run Dynamics 365 Finance as well, see Dynamics 365 implementation.

What sets the time and cost of a rollout

Microsoft publishes license prices. Setup work has no list price. It grows with a handful of things you can count before you start:

  • License mix. Each license type sets what its users may open, so each needs its own tests.
  • How many companies. Each company needs its own setup, even when values copy across.
  • Environments and storage. Extra environments and storage are add-ons bought through your reseller.
  • Country. A country without Microsoft’s own local version needs a localization app from another firm.
  • Old systems. Each source system needs its own route from the migration table above.
  • Your own code. Each extension is built once and tested before each major release.
  • Links. Each system Business Central must talk to adds build and test work.

Microsoft publishes no typical length for a Business Central project on the pages we used. Each plan’s list price sits in our Business Central pricing article, and other firms’ published ranges for ERP work sit in ERP implementation cost. Our own fee is set in each project’s contract. The first call is free.

Questions

Do we need an official Microsoft partner to implement Business Central?

Not for this work. What decides a go-live is a team that knows Business Central from the inside and builds on Microsoft's published APIs. Our team has taken Dynamics 365 Business Central live. You buy the licenses through a reseller in Microsoft's Cloud Solution Provider program, the only channel Microsoft names for them. We take the consulting, setup, data move, training and agent build from there.

Can we turn our Business Central trial into our live company?

Yes, but the order of sign-ins matters. Microsoft says the first person to sign in after the paid license lands on your tenant must hold that license. Then the 30-day trial ends and its notices go away. If an administrator signs in first instead, the trial keeps running until it expires. So agree who signs in first before the license is applied.

How many test environments come with Business Central?

Three sandboxes and one production environment come with Essentials or Premium, at no extra charge. Each extra production environment you buy adds three more sandboxes and 4 GB of shared storage. Sandboxes count toward your storage too, so a full copy of a big company uses real space. If storage runs over, Microsoft stops new environments from being created until you free space or buy more.

Can we undo a bad data load in Business Central?

Yes, within limits. An admin can restore an environment to any point in the last 28 days. The restore stays in the same Azure region and localization. Production can restore to production or to a sandbox, and a sandbox only to a sandbox. The admin needs the D365 BACKUP/RESTORE permission set, and the subscription must be a paid one. Note the time before each big load.

We run Dynamics NAV. How do we get to Business Central online?

In two steps. Microsoft's migration FAQ says a NAV system is upgraded to Business Central on-premises first, and switched online after that. The cloud migration tools need SQL Server 2016 or later, at compatibility level 130 or higher. On-premises version 25 and later moves online directly. Extended support for NAV 2018 runs out on January 11, 2028, Pacific time.

Which costing method should we pick in Business Central?

Pick it with your finance lead before any item posts. Microsoft says you cannot change an item's costing method once item ledger entries exist for it. FIFO, LIFO, Average and Specific value stock at what you paid. Standard uses a set cost. The right one depends on how your accountant values stock today.

How much database storage does Business Central include?

Microsoft gives each customer up to 80 GB, plus an allowance for each licensed Essentials or Premium user. All environments in the tenant share that pool. Files stored in the database count, and so does data left behind by an uninstalled extension. Going over does not stop daily work, but it blocks new environments and copies until you free space or buy more.

Will you sign an NDA before we share our data?

Yes. We sign your NDA before you share any data, if you ask. For a first talk we do not need your data at all. A list of your current systems, your company count and your user count is enough to talk through the steps on this page.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Bring your Business Central plan

Tell us the system you run today, how many companies and users you have, and the date you are working to. On the first call we talk through the steps on this page for your case. The first call is free.

Talk through your rollout