Key takeaways
- Licenses are a recurring per-user monthly cost, but implementation services are usually the largest one-time part of a Business Central budget.
- Scope, number of entities, data quality, integrations and customization drive implementation cost far more than company revenue does.
- Broad market estimates run from tens of thousands of dollars for small focused projects to several hundred thousand for complex mid-sized ones.
- Phasing the rollout, defaulting to standard features and limiting migrated history are the most practical ways to keep scope under control.
- Compare partner proposals on identical assumptions, including data migration, training and post-go-live support, not on the headline number alone.
"How much will it cost?" is usually the first question a CFO asks about a new ERP, and the hardest one for anyone to answer honestly without knowing the business. The answer depends far more on your processes, data and integrations than on the software itself.
This guide breaks down what a Microsoft Dynamics 365 Business Central implementation actually costs, what pushes the number up or down, and how to keep the project under control. Where we give dollar figures, they are broad market estimates, not quotes.
What you are paying for: the main cost components
Business Central is Microsoft's cloud ERP for small and midsize companies, covering finance, purchasing, sales, inventory, projects and more. A full budget has several parts, and the software license is only one of them.
Licenses (recurring)
Business Central in the cloud is licensed as a subscription per named user per month. Microsoft offers different license types for full users (with a lower and a higher tier, the higher one adding areas such as manufacturing and service management) and a lower-cost option for light users who mainly view data, approve items or make limited entries.
Microsoft adjusts prices and plan details from time to time, so check Microsoft's current Business Central pricing page or ask a partner for current figures. Budget licenses as an ongoing operating cost that grows with headcount.
Implementation services (one-time)
This is usually the largest one-time cost. It covers discovery and design workshops, system configuration (chart of accounts, dimensions, posting setup, approvals, number series), testing, cutover planning and go-live support. Partners typically bill this as time and materials, fixed price, or a phased mix.
Data migration
Moving customers, vendors, items, open documents and balances from your current system takes real effort. Cost depends on how many sources you have, how clean the data is, and how much history you bring over. See our glossary entry on data migration for the basics.
Extensions and customization
Business Central is extended through AL extensions (custom code that sits beside the standard product) and third-party apps from Microsoft AppSource. Apps have their own subscription fees. Custom extensions cost development time up front and maintenance time after each major update.
Integrations
Connecting Business Central to an e-commerce platform, CRM, payroll provider, banking service, EDI partner or warehouse system adds work. Pre-built connectors reduce effort, while custom integrations need design, build and monitoring.
Training
Users need role-based training before go-live, and key users need deeper training so they can support colleagues. Skipping this is a common reason projects struggle after launch.
Ongoing support
After go-live, most companies keep a support arrangement for questions, small changes, update testing and new requirements. This is often a monthly retainer or a block of prepaid hours.
What drives the cost up or down
Two companies with the same revenue can have very different implementation costs. These factors matter most:
| Factor | Pushes cost down | Pushes cost up |
|---|---|---|
| Scope | Finance only | Finance plus inventory, warehousing, manufacturing, projects or service |
| Legal entities | One company | Multiple entities, intercompany transactions, consolidation |
| Processes | Willing to adopt standard Business Central processes | Many unique workflows that require custom code |
| Data | Clean, consistent data from one source | Messy data spread across several systems and spreadsheets |
| History | Opening balances and open items only | Years of detailed transaction history |
| Integrations | None, or pre-built connectors | Several custom integrations |
| Reporting | Standard reports and Power BI templates | Many custom reports and dashboards |
| Internal team | Dedicated project lead and engaged key users | Staff with no time for workshops, testing or decisions |
The last row is easy to underestimate. Slow decisions and unavailable key users extend timelines, and longer timelines cost more.
Typical project shapes and market cost ranges
The ranges below are broad estimates of what US companies commonly report paying for implementation services (excluding licenses). They vary widely by partner, region, scope and delivery model. Treat them as a sense of scale, not a budget, and get scoped estimates from partners for your situation.
Small company, focused scope
A typical profile: one legal entity, fewer than 20 users, mostly finance with basic sales, purchasing and simple inventory, data moving from QuickBooks or a similar system, and one or two simple integrations.
- Estimated implementation services: roughly $20,000 to $75,000
- Lower end: finance-focused, standard processes, clean data, few integrations
- Higher end: inventory added, some custom reports, a custom integration or two
Mid-sized company, broader scope
A typical profile: two or more entities, 20 to 150 users, finance plus distribution, warehousing or manufacturing, migration from Dynamics NAV, Dynamics GP or another ERP, several integrations, and a reporting layer in Power BI.
- Estimated implementation services: roughly $75,000 to $300,000 or more
- Lower end: a structured upgrade with mostly standard processes
- Higher end: manufacturing, complex warehousing, many integrations, significant customization
Add licenses, AppSource app subscriptions and ongoing support on top of these figures. When comparing proposals, make sure each one covers the same items, because a lower number sometimes excludes data migration, training or post-go-live support.
How long implementation usually takes
Timelines follow the same drivers as cost. In general terms:
- Small, focused projects often take a few months from kickoff to go-live.
- Mid-sized projects with operations, multiple entities or significant integrations commonly take several months, and complex ones can run longer.
Most projects move through similar phases: discovery and design, configuration and build, data migration rounds, testing (including user acceptance testing), training, and cutover. Plan go-live at a month or quarter boundary when possible, and avoid your busiest season and year-end close.
How to keep scope under control
Scope creep is one of the most common reasons ERP budgets grow. These practices help:
- Write down the must-haves before talking to partners. Separate "required at go-live" from "nice to have later."
- Default to standard functionality. Change a process before you customize the software, unless the process is a real competitive advantage.
- Phase the rollout. Go live with finance and core operations first, then add advanced features in later phases.
- Limit data history. Bring master data, open items and balances. Keep the old system available read-only for reference, and confirm record retention requirements with your accountant.
- Use a change control process. Every new request gets a written estimate and an explicit yes or no from the project sponsor.
- Name one internal decision maker who can resolve questions within days, not weeks.
- Protect key users' time. Backfill some of their daily work during workshops and testing.
A clear scope also makes fixed-price or capped proposals more realistic, which helps CFOs plan.
Questions to ask a Business Central partner
Use these questions to compare partners on more than price:
- What exactly is included in your estimate? Ask about data migration, training, testing support, documentation and post-go-live support.
- What assumptions is the estimate based on? Number of users, entities, integrations, reports and data sources.
- How do you handle changes in scope? Ask to see a sample change request.
- Which parts will you customize, and why? A good partner explains when standard features are enough.
- Who will work on our project? Ask about the roles, experience and time allocation of the actual team.
- How do you approach data migration? How many trial loads, who cleans the data, and how balances are reconciled.
- What does support look like after go-live? Response times, pricing model and how updates are tested.
- Can we speak to a reference customer with a similar size and industry?
Ask every partner the same questions so the answers are comparable. Also confirm tax, revenue recognition and audit related setup with your accountant or auditor, since those decisions belong to your finance advisors.
Next steps
A realistic budget starts with a clear picture of your processes, data and integrations. Before requesting proposals, spend a few hours listing your must-haves, current systems, user counts and the data you need to bring across. That list alone will make partner estimates far more accurate.
If you would like help scoping the work, our Business Central team can walk through your requirements and outline the options. You can contact us to set up that conversation.
