Dynamics 365 Implementation Cost in 2026: What a Mid-Market Project Can Cost You

Key Takeaways

If you need the numbers before the reasoning, here they are:

• Licenses are the smaller half. Business Central Essentials is $80 per user per month and Premium is $110; Dynamics 365 Finance and Supply Chain Management are $210 for the first app and $30 to attach a second. Over three years, partner services usually cost more than the subscription.
• Plan on services at 1.5 to 2.5 times your annual license spend for a standard project. That’s roughly $30,000 to $75,000 for a straightforward Business Central project and $100,000 to $250,000 for a complex mid-market one. Finance and Supply Chain services start around $250,000 and go well past $1 million.
• Three sizes, three first-year ranges. A 25-user Business Central project runs $60,000 to $160,000 in cash outlay for year one. A 100-user mid-market project runs $200,000 to $450,000 on Business Central, or $550,000 to $950,000 on Finance and Operations. A 500-user Finance and Supply Chain program runs $1.75 million to $4.5 million. Each one is built from the same line items, and we show the arithmetic.
• Business Central and Finance and Operations aren’t the same product at a different price. The per-user gap is $130 a month, but the bigger difference is scope: Finance and Operations projects carry a 20-user minimum, longer timelines and more consulting hours per user.
• Five costs catch people out: reports and dashboards, data cleanup, integrations that surface late, customization where configuration would do, and parallel runs that drag on.
• Ask for ranges, hours by role and a change-control process. A single number with no uncertainty band is a quote you can’t defend to a board.

Introduction

Before a Dynamics 365 project can start, someone has to put a budget in front of the board and get it approved. That’s harder than it sounds, because any honest estimate is a range. Most pricing content online doesn’t help much. It gives either Microsoft’s per-user list price, which is the smaller part of the bill, or a vague “implementations start at” figure that says nothing about your own project.

This guide is meant to help you arrive at a number you can defend. It breaks the cost into its line items and gives a range for each. It then shows what those add up to for a 25-user, a 100-user and a 500-user project. It explains why Business Central and Finance and Operations projects cost such different amounts. It covers the costs that most often push a project past its approved budget, and it ends with how to read a partner’s quote before signing. The figures draw on Microsoft’s published 2026 prices and on real implementation projects. Where a range is given, treat the range itself as the answer.

What Line Items Contribute to an Implementation Quote

A Dynamics 365 budget has nine parts. Licenses and hypercare recur; the rest are one-time, and the one-time costs are where the variance lives. One definition first, because it matters for the arithmetic later: when we say “services,” we mean the partner’s total one-time fee, which is made up of implementation, data migration, customization, integrations, training and go-live support. The percentages below are each line’s share of that services total. Change management is your own staff’s time and sits outside it.

Microsoft licenses

The only part with a published price. Business Central is $80 per user per month for Essentials and $110 for Premium, which adds manufacturing and service management. Team Members are $8. Those are the prices after Microsoft’s October 2025 increase. Dynamics 365 Finance and Supply Chain Management are each $210 per user per month as the first app. Microsoft’s licensing guide prices the second app at $30 as an attach license. Operations Activity users are $50 and Team Members $8. Microsoft’s Product Terms set a minimum purchase of 20 full-user licenses on the base app, or 10 for the Premium editions, so a Finance deployment starts at about $50,000 a year before anyone else is licensed. All figures are US list prices on annual commitment, before tax, verified on October 20, 2026. Month-to-month runs about 20% higher, and your CSP or Enterprise Agreement may differ. Over three years, licenses are typically 35% to 50% of total cost of ownership.

Partner implementation

Discovery, solution design, configuration, testing and project management. This is the largest line, usually 40% to 55% of the services total, and it scales with the number of processes you run through the system rather than with headcount. A 25-user distributor with one company and one warehouse is a smaller project than a 25-user manufacturer with three entities.

Data migration

Extracting, cleaning, mapping and loading master data and opening balances, plus whatever history you decide to bring. Budget 10% to 20% of services. The cleaning is the expensive part, and it’s the line most often underestimated, which we’ll come back to.

Customization

Extensions and custom development for anything the standard product doesn’t do. In a well-scoped Business Central project this is 5% to 15% of services. In Finance and Operations it can be more, because the processes are more specific. The discipline is configure first, extend second, and we’ll show where that line gets crossed.

Integrations

Connections to the systems that stay: e-commerce, EDI, payroll, CRM, warehouse automation, banks. Each one is a mini-project with its own testing. Expect 10% to 25% of services depending on count and complexity, and expect at least one to appear after the SOW is signed.

Training

End-user and super-user training, usually 5% to 10% of services. Cheap to skip and expensive to have skipped, because untrained users create support tickets and workarounds for years.

Change management

Process redesign, communication, role mapping and the internal time your own people spend in workshops, testing and training. It’s rarely on the partner’s quote because it isn’t the partner’s work, but it’s real. For a mid-market project, plan the equivalent of 10% to 15% of the services total, almost all of it in your staff’s hours rather than cash. We leave it out of the cash totals below for that reason, and you should put it on the slide as a separate line.

Go-live support

Cutover planning, the go-live weekend, and the first two to four weeks of on-site or on-call support. Usually 5% to 10% of services. Cutting it to save money is a false economy.

First-year hypercare and support

Hypercare is the stabilization period after go-live, when the partner stays close while your team runs the first month-end and year-end closes on the new system. After that comes ongoing support and the work of absorbing Microsoft’s two annual update waves, the spring and autumn releases that change the product and need regression testing against your customizations and integrations. Plan 15% to 20% of the services total per year, or a support contract with a defined hours bank.

Add a contingency of 10% to 20% of services on top, and you have a budget that holds up. With the lines named, the useful next step is to see what they add up to at different sizes.

Cost by User Tier: 25, 100 and 500+ Users

User count is a rough proxy for project size, and we use it here because it’s the number a CFO has in hand. The real drivers are the number of entities, the number of processes and the number of integrations, which is why every figure below is a range. The totals are first-year cash outlay. That means twelve months of licenses, the services total, first-year hypercare at 15% to 20% of services, and contingency at 10% to 20% of services. Internal change-management time isn’t included. These are planning ranges rather than quotes, and the table at the end of this section shows how each one is built.

25 users: the SMB project

A single company, one or two sites, standard finance, purchasing, sales and inventory, on Business Central Essentials with a handful of Team Member licenses. Licenses come to roughly $20,000 a year. Services in this bracket run $30,000 for a quick-start to $75,000 for a standard scope, and around $100,000 if manufacturing or heavy integration is involved. Migration is usually from QuickBooks or a legacy on-premises system, and one or two integrations are typical.

First-year range: $60,000 to $160,000. Timeline: 10 to 16 weeks for the common case, 8 to 10 for a true quick-start.

100 users: the mid-market project

Two to five legal entities and several sites or warehouses. The users are a mix of Essentials and Premium, or the project is on Finance and Operations if the processes demand it. There’s real integration work: e-commerce or EDI, payroll, CRM, possibly a WMS. On Business Central the licenses come to roughly $70,000 to $90,000 a year and services run $100,000 to $250,000, with migration and integration taking a larger share than in the SMB case. On Finance and Operations the licenses are about $250,000 a year for 100 full users and services run $250,000 to $500,000.

First-year range: $200,000 to $450,000 on Business Central; $550,000 to $950,000 on Finance and Operations. Timeline: 4 to 8 months on Business Central, 6 to 12 on Finance and Operations.

500+ users: the enterprise program

Multiple countries or regions, many entities, manufacturing or distribution at scale, and a dozen or more integrations. This is Finance and Supply Chain Management territory, usually with a mix of full, Activity and Team Member users. Licenses typically land between $500,000 and $800,000 a year depending on the mix. As a reference point, 200 full users on Finance with Supply Chain attached is about $576,000 before any Activity or Team Member seats. Services run $1 million to $2.5 million. The upper end depends on how many localizations there are, since each country’s tax, statutory reporting and bank formats is its own workstream, on the integration count, and on the state of the data. Hypercare and contingency at this scale are each $150,000 to $500,000.

First-year range: $1.75 million to $4.5 million. Timeline: 12 to 24 months, often phased by region or entity.

Every total above is built from the same four lines, shown here side by side. Services is the partner’s one-time fee, and hypercare and contingency are percentages of it.

Line	25 users, BC	100 users, BC	100 users, F&O	500+ users, F&O
Licenses, 12 months	$20,000	$70,000 to $90,000	$250,000	$500,000 to $800,000
Services	$30,000 to $100,000	$100,000 to $250,000	$250,000 to $500,000	$1,000,000 to $2,500,000
Hypercare, 15% to 20% of services	$4,500 to $20,000	$15,000 to $50,000	$37,500 to $100,000	$150,000 to $500,000
Contingency, 10% to 20% of services	$3,000 to $20,000	$10,000 to $50,000	$25,000 to $100,000	$100,000 to $500,000
First-year cash outlay	$60,000 to $160,000	$200,000 to $450,000	$550,000 to $950,000	$1.75 million to $4.5 million

On sources: the license figures are Microsoft list prices. The services ranges for Business Central are what Folio3 publishes from its own projects; the Finance and Operations ranges are consistent with what we see and with the trade benchmarks linked above. The percentages are our working planning assumptions, and the low and high ends are deliberately combined so the totals show the full band rather than a single likely number.

The rule of thumb that ties these together: for a standard project, services usually come in at 1.5 to 2.5 times your annual license spend, and at 3 to 5 times for a complex one. The ranges above run wider than that on purpose, because they span quick-starts at one end and multi-entity manufacturing at the other. The rule is for checking a single quote. If it falls far outside the band in either direction, ask why. The next thing to understand is why the Business Central and Finance and Operations figures diverge as sharply as they do.

Business Central vs Finance and Operations: The Cost Gap

People sometimes read the two products as a small and large edition of the same thing, priced accordingly. The license gap is real, but it’s the smaller reason the budgets diverge.

The per-user gap

Business Central Essentials is $80 and Premium $110 per user per month. Dynamics 365 Finance and Supply Chain Management are $210 each, $30 to attach the second, and Microsoft’s Product Terms require at least 20 full-user licenses of the base app before you can buy anything else. For 100 full users that’s roughly $96,000 a year on Business Central Essentials against $252,000 for Finance alone, or $288,000 for Finance with Supply Chain attached. Team Member licenses are $8 on both, which is why the mix of full and light users matters so much to the license line.

The scope gap

Finance and Operations is built for organizations with more entities, more countries, deeper manufacturing and warehousing, and more process variation. That means more workshops, more configuration decisions, more testing cycles and more consulting hours per user. A Business Central project runs on 10 to 20 consulting hours per full user in a typical mid-market scope; a Finance and Operations project runs on 30 to 60. It also means a longer timeline, which carries its own cost in internal time and parallel running.

Fit matters more than license price

Fit decides this, and price follows. If Business Central covers your processes, it is the cheaper product and the cheaper project, and pushing it past its design with heavy customization is how you end up paying Finance and Operations money for a Business Central license. If your operation genuinely needs the larger product, choosing Business Central to save on licenses will cost more by the second year. When we’re not sure which side a company falls on, that’s exactly what a scoping call is for.

Whichever product you’re on, the same five things push budgets over. They’re worth knowing before the SOW is written.

Unexpected Costs to Watch Out For

Most overruns don’t come from the partner’s estimate being wrong. They come from scope that wasn’t in the estimate because nobody had named it yet. These are the five we see most, in rough order of how often they show up.

Report requests multiply after testing starts

The SOW says “standard reports plus ten custom reports.” By user acceptance testing, finance has asked for a dozen more, each department wants a Power BI dashboard, and the board pack needs to look like the old one. Reports are easy to request and each one is a few hours to a few days, so the line doubles quietly. Fix it by inventorying every report you run today before discovery, marking which ones the standard product replaces, and putting a number on the rest.

Data cleanup is always underestimated

The migration estimate assumed the data was clean, and it rarely is: duplicate customers, vendors with three spellings, items with no unit of measure, open orders from 2019. Cleaning is your work rather than the partner’s, and if it isn’t done the partner either does it at consulting rates or loads bad data and you pay for it in support. Start the cleanup the day you sign, and have the partner take on data-quality risk only up to a stated limit.

Integrations surface after the SOW is signed

Someone mentions in month three that the freight system has to talk to the ERP, or that the bank file format is non-standard, or that the e-commerce platform is being replaced next year. Every integration found after design is a change order. Walk every connection in discovery: every system that sends data in or takes data out, including the spreadsheets.

Customization where configuration would do

A user asks for the system to work the way the old one did. The partner can build it, and a partner on time and materials has no reason not to. Six months later you have a product that’s expensive to upgrade and a process you could have changed instead. The rule is configure first, extend only when a process is genuinely a competitive advantage, and have someone on your side with the authority to say no.

Parallel runs that don’t end

Running the old and new systems side by side for one close is prudent. Running them for three because nobody will sign off on the cutover is a cost with no end date: double entry, double licenses, and a partner team on standby. Set the parallel-run exit criteria before go-live and treat them as binding.

Each of these is manageable if it’s named in the contract. Which raises the question of what kind of contract to sign.

Fixed Price or Time and Materials

There are two ways to buy an implementation, and partners will usually steer you toward the one that suits them. Neither is wrong; each wins in different circumstances.

Fixed price suits a well-defined scope

A fixed fee gives you a number for the board and moves overrun risk to the partner. It works when the scope is genuinely known: a standard Business Central deployment, a single entity, clean data, integrations you can list today. The trade-off is that the partner prices in contingency, so the number is higher than the expected T&M cost, and every change becomes a negotiation. If your project is the quick-start or standard mid-market kind, fixed price is a reasonable ask, and a partner who won’t offer it for a well-defined scope is telling you something.

Time and materials suits real unknowns

T&M reflects the work actually done and lets scope evolve without a change order for every adjustment. It suits projects with real unknowns: multiple entities, a legacy system nobody fully understands, integrations still being defined. The risk is open-ended cost, so it should never be signed bare. Insist on a not-to-exceed cap, hours reported by role every two weeks, and escalation gates at 75% and 90% of the cap.

Most mid-market projects sign a hybrid

A hybrid: fixed price for discovery, design and core configuration, where the scope is clear, and T&M with a cap for migration, integration and customization, where it isn’t. That’s the model we recommend for most 100-user projects, and it’s the one most partners are comfortable with once you ask.

Whichever model you choose, the quote itself tells you a lot about the partner.

How to Read a Partner Quote

Two quotes for the same project can differ by half and both be honest. What matters is whether you can see what’s inside the number. These are the things to push back on, and the things to insist on before you sign.

Push back on these

• A single blended number. If the quote is one figure for “implementation,” ask for hours by role and by phase. A partner who can’t produce that hasn’t estimated the project; they’ve priced it to win.
• A quote far below the others. Forty percent under comparable bids usually means scope has been left out, junior staff will do the work, or change orders are the business model. Ask what’s excluded, line by line.
• Data migration as one line. Migration is extraction, cleaning, mapping, trial loads and reconciliation. One line with no breakdown means the partner hasn’t looked at your data.
• An engagement that ends at go-live. If hypercare and the first close aren’t in the SOW, they’ll be priced separately at the worst possible moment.
• Enthusiasm for every customization. A partner who says yes to everything in the sales cycle will say yes to everything on T&M.

Insist on these in the SOW

• A scope document that lists inclusions, exclusions and what triggers a change order.
• Hours by role, with named roles and rates rather than one blended figure.
• Milestone acceptance criteria tied to payments, with no more than 10% to 25% due at signing.
• The partner carrying data-quality risk up to a stated limit, with your cleanup obligations spelled out.
• Post-go-live support defined by hours and duration, including the first month-end and year-end close.
• A plan for Microsoft’s two annual update waves, including who does regression testing.
• Ownership of all customizations, code and documentation sitting with you.

A quote that survives that list is one you can take to a board. If yours doesn’t, or you’d like a second opinion on the number, a scoping call is the next step.

Book a Scoping Call for Your Project

The ranges in this guide are the right starting point for a budget conversation, but your number depends on your entities, your data and the systems that have to connect. A scoping call takes that into account. Bring your user count by role, a list of the systems that stay, and a rough sense of how clean your data is. We’ll give you a defensible range for your project, with the line items broken out and the assumptions written down, so you can take it to a board and answer the questions that follow.

Folio3 is a Microsoft Solutions Partner for Business Applications with 20 years of Dynamics delivery and 300+ implementations across four continents. If the honest answer is that your project is smaller than you feared, or that Business Central fits where you’d assumed Finance and Operations, we’ll say so.

Book an implementation scoping call with the Folio3 Dynamics team.

Folio3 Dynamics implements and supports Business Central, Finance and Operations and the wider Dynamics 365 suite for mid-market companies.

Frequently Asked Questions

The questions that come up most when a finance team is building a Dynamics 365 budget.

How much does a Dynamics 365 implementation cost?

For Business Central, partner services typically run $30,000 to $75,000 for a standard SMB project and $100,000 to $250,000 for a complex mid-market one, on top of licenses at $80 to $110 per user per month. For Finance and Operations, services start around $250,000 and commonly exceed $1 million, with licenses at $210 per user per month. Add first-year hypercare and contingency, each 10% to 20% of services, for the cash total. A reliable check is that services land at 1.5 to 2.5 times annual license spend for a standard project.

How much does Business Central implementation cost for 25 users?

Plan on $60,000 to $160,000 in first-year cash outlay: about $20,000 in licenses, $30,000 to $100,000 in partner services depending on scope, and hypercare plus contingency at roughly 25% to 40% of services on top. A quick-start with clean data sits at the bottom of that range; manufacturing or heavy integration sits at the top.

What’s the difference between Business Central and Finance and Operations cost?

Licenses are $80 to $110 versus $210 per user per month, and Finance and Operations requires a minimum of 20 full-user licenses on the base app. The larger gap is in services: Finance and Operations projects run two to three times the consulting hours per user because of deeper process scope, more entities and longer timelines.

What is included in an ERP implementation cost?

Licenses, partner implementation (discovery, design, configuration, testing, project management), data migration, customization, integrations, training, change management, go-live support and first-year hypercare. Most quotes leave out change management and understate migration, so check both.

Is fixed price or time and materials better for a Dynamics 365 project?

Fixed price when the scope is known and stable; T&M with a not-to-exceed cap when there are real unknowns. Most mid-market projects sign a hybrid: fixed for discovery and core configuration, capped T&M for migration, integration and customization.

How long does a Dynamics 365 implementation take?

Business Central: 8 to 10 weeks for a quick-start, 10 to 16 weeks for a standard scope, 4 to 8 months for a complex multi-entity project. Finance and Operations: 6 to 12 months, and 12 to 24 for a multi-country program.

How much contingency should I budget?

Ten to twenty percent of the implementation cost. Use the lower end for a fixed-price, single-entity project with clean data, and the upper end for anything with multiple entities, legacy data or integrations still being defined.

If your question isn’t here, bring it to the scoping call.