Microsoft Dynamics 365 ERP · Mid-Market
Microsoft Dynamics 365 ERP is no longer a single product but a family of standalone apps. This page sorts out the terminology (Microsoft ERP, Dynamics ERP, D365 ERP), explains the F&O successor apps after the further 2024 split, lays out six selection criteria for a Microsoft ERP partner, and describes three concrete implementation scenarios from mid-market practice.
Terminology
Four terms, one product universe. Anyone searching Google for "Microsoft ERP", "Dynamics ERP", "Microsoft Dynamics ERP", or "Dynamics 365 ERP" ends up in the same topic area — and yet behind these umbrella terms today sit two distinctly different worlds. This page separates them clearly and shows which world fits which company constellation.
Microsoft itself officially uses "Microsoft Dynamics 365" and treats "ERP" as a descriptive suffix. In daily usage — with partners, in RFPs, in advisor comparisons — all four spellings are interchangeable. Saying "Microsoft ERP" means the same as saying "D365 ERP". The differentiation isn't by term but by the specific app.
Until 2020, Microsoft's enterprise ERP suite was called "Dynamics 365 Finance & Operations" (F&O for short) — a shared brand umbrella for Finance, Supply Chain, Retail, Human Resources, and Project Management. In 2020, Microsoft dissolved this bundle and released the disciplines as standalone applications. In 2024, this separation was sharpened further: license models, module boundaries, and roadmaps now differ significantly across the apps. Anyone searching for "F&O" today is really searching for four or five separate products, each with its own license.
Today, the Microsoft ERP family consists of two clearly separated worlds:
Both worlds share Microsoft Dataverse as the data foundation for adjacent apps, Microsoft Power Platform for extensions, Power BI for reporting, and Microsoft Copilot for AI-assisted features. But they differ fundamentally in license logic, implementation depth, and typical project duration.
In discovery conversations we regularly encounter the expectation that both worlds can be handled the same way — one partner, one contract, one migration. In reality, Business Central and the F&O successor apps are two independent delivery disciplines with different implementation methodologies, different developer profiles (AL extensions for Business Central, X++ extensions plus Power Platform pro-code for F&O), and different industry logic. Anyone starting a Microsoft ERP initiative benefits from making the world choice early — partner selection follows the world choice, not the other way around.
F&O successor apps
After the 2020 split and its further differentiation in 2024, five apps now stand at the center — four successor apps from the former F&O world plus Business Central as a standalone SMB line.
| App | Target audience | Core function | Predecessor |
|---|---|---|---|
| Microsoft Dynamics 365 Business Central | SMBs and mid-market companies up to approx. 250 employees | Complete ERP: financials, sales, purchasing, inventory, projects, service, manufacturing (Premium) | Dynamics NAV (Navision) |
| Microsoft Dynamics 365 Finance | Demanding mid-market companies and larger organizations | General ledger, fixed assets, consolidation, multi-entity reporting, cash & bank management, tax engine, IFRS/HGB capability | Dynamics AX Finance |
| Microsoft Dynamics 365 Supply Chain Management | Manufacturing, wholesale, distribution with industry depth | Inventory, purchasing, sales, production planning, master planning, quality control, asset management | Dynamics AX Trade & Logistics |
| Microsoft Dynamics 365 Commerce | Retail and omnichannel commerce | Omnichannel retail, POS, e-commerce platform, store and online inventory, customer loyalty, self-service | Dynamics AX Retail |
| Microsoft Dynamics 365 Project Operations | Project-driven organizations (consulting, engineering, construction) | Project acquisition, resource planning, time tracking, project accounting, billing; bridge between sales and ERP worlds | Project Service Automation / Dynamics AX Project |
Three notes for context: First, Microsoft Dynamics 365 Human Resources and Microsoft Dynamics 365 Intelligent Order Management remain available as standalone apps since 2024 but are not part of the classic ERP core. Second, Finance and Supply Chain Management combine well in licensing — many mid-market projects book both apps together. Third, Business Central is not a "small F&O" but a standalone line with its own codebase, its own data model, and its own extension logic (AL extensions instead of X++).
Selection criteria
Choosing the Microsoft ERP partner, in our experience, has more impact on implementation success than the choice between Business Central and F&O successor. Six vendor-neutral levers — ask any Microsoft ERP partner about these points.
01 · Specialization over breadth
Business Central and the F&O successor apps require different methodologies, different developer profiles, and different industry logic. A partner offering both worlds equally has no real depth in either. Look for a clear focus: Business Central specialist or F&O specialist. Real multi-world partners are rare and usually employ several hundred people.
02 · Industry experience with references
Manufacturing accounting with multi-warehouse valuation is fundamentally different from project accounting with time-and-materials billing. A field service dispatch with technician routes has different requirements than a wholesaler with consignment inventory. Ask for three concrete projects in your industry — not for industry logos on the website.
03 · Documented delivery methodology
Consistent implementation quality comes from documented delivery processes, not individual talent. A partner with an established methodology can clearly describe architecture review procedures, sprint structures, hypercare handovers, and Application Care transitions — and delivers comparably from project to project. Ask for the delivery handbook.
04 · Honest negative recommendation
A good partner will also say "Microsoft Dynamics 365 ERP is not the right choice" even when that loses them a project. Industry-standard solutions, SAP Business One, or specialized mid-market ERPs can be a better fit in specific constellations. Anyone responding "yes, we can do that" to every request puts your project at risk — and their own reputation.
05 · Software development depth
Pure customization with built-in tools rarely supports robust implementations. A partner with real software development depth delivers pro-code extensions, Azure Functions integration, custom web services, and REST APIs for adjacent systems — and can develop outside the Microsoft stack when needed. Pure configurators hit walls quickly.
06 · Partner size & personality
With large Microsoft generalists you negotiate in sales with senior architects and often get a junior or offshore team in delivery. With smaller partners, the same people are active pre- and post-contract, escalations reach management quickly, and responsibility doesn't get lost between hierarchy layers. The right size depends on the project — personal accessibility is often more decisive than absolute firm size.
These six points are market standard for good selection diligence. In the next section we show where arades delivers solidly against each point — and where we don't.
arades as a Microsoft ERP partner
arades is deliberately not an "everything for everyone" partner. We specialize in European mid-market companies with 50–500 employees and focus on the Microsoft ERP areas where we deliver deeply. Where we are not the right partner, we say so openly and refer on where appropriate.
arades delivers Microsoft Dynamics 365 Business Central in-house — from discovery through implementation to Application Care. For mid-market companies with 50–250 employees, Business Central is in many constellations the most economically viable option. We know the data model, AL extensions, extension logic, and typical pitfalls from our own implementation practice.
We do not implement F&O successor apps (Finance, Supply Chain Management, Commerce, Project Operations) ourselves — that discipline demands a dedicated team with its own methodology and multiple years of practice. If you need F&O, we refer you to specialized partners in our network and remain involved on the CRM side or as an architecture sounding board where useful.
arades has worked on the Microsoft Dynamics platform since 2006 — through NAV versions, AX generations, the cloud transition in 2016, and the F&O split of 2020. This platform depth makes the difference for architecture decisions that still need to hold up five years after go-live.
Documented architecture review procedures, defined sprint structures in the implementation phase, standardized hypercare handovers, and clear transitions into Application Care. The result is repeatable quality — independent of the daily form of those involved.
We run several of our own solutions with customers in live operation: Education Institutes app (course management, participant tracking), Associations & Chambers (member management), the License Cost Calculator, and Intercompany Integration. This dual role as implementer and software vendor sharpens our architecture decisions.
You speak in the sales process with the same architects who will later lead your implementation. No handover to an offshore team, no account-manager-to-delivery wall. Management directly reachable. Application Care at a predictable monthly flat fee. Fixed prices for strategy workshops and architecture reviews — no surprises from time sheets.
Migration paths
In discovery conversations with mid-market customers, we see the same starting constellations again and again. Each of these paths has its own data model gaps, its own license math, and its own typical project duration. Here are the five most common migration paths — and what to watch for in each.
The classic enterprise migration path: Dynamics AX installations from the 2010s move to Dynamics 365 Finance plus Supply Chain Management. Caution with X++ customizations — many in-house developments from the AX world must be re-designed for the cloud variant. Data migration is intensive because the data model has changed between AX and the successor apps in several areas. Typical project duration: 12–24 months including parallel operation.
The direct successor path. Anyone running NAV 2013, 2015, 2017, 2018, or NAV 2019 has Business Central as the intended migration path — the data model is largely compatible, and many C/AL customizations can be systematically converted into AL extensions. Microsoft provides migration tools, but advisory in license conversion (perpetual → subscription) and customization refactoring remains essential. Typical duration: 4–9 months, depending on customization depth.
Growing SMBs that hit functional limits with SAP Business One or seek Microsoft Cloud integration often switch to Business Central. Advantage: native connection to Microsoft 365, Power BI, and Power Platform. Challenge: master data migration and business logic translation — the two systems have different patterns in posting and document flow. Typical duration: 5–10 months.
Manufacturing mid-market companies with a Sage history often move toward Microsoft when Microsoft 365 is already established and a homogeneous cloud stack is desired. Sage 100 leans more toward Business Central; Sage X3 in complex manufacturing constellations often toward Finance plus Supply Chain Management. Data migration is in our experience more intensive than NAV migrations because master and transactional data models differ more.
abas customers — typically manufacturers and plant builders — move either toward Business Central (smaller and mid-sized constellations) or Finance plus Supply Chain Management (demanding mid-market with multi-site manufacturing). abas in-house developments must be restructured in the Microsoft world. Important: a realistic assessment of which abas functions can be covered in the Microsoft standard and where in-house development effort arises.
Even within the Business Central world there are paths: upgrade from Business Central on-premises to Business Central Online, switching between Essentials and Premium, or restructuring customization logic after taking over an implementation from another partner. These internal paths are often shorter (2–6 months) but require a clean inventory assessment and a clear cutover plan.
Across all migration paths, data migration is the most common reason for delays — not software configuration. Master data (customers, vendors, items, chart of accounts), open items (receivables, payables, open purchase orders), and transactional data (historical postings, inventory movements) must be extracted from the legacy system, cleaned, mapped, and moved into the new world. Empirical rule: 25–40% of implementation effort goes into data migration. A realistic project budget plans for this effort explicitly — gladly via an upstream data audit.
Implementation scenarios
Three anonymized constellations from current implementation practice. Real projects with real license math and real duration — so you can match our delivery profile against your situation.
Sales focus · 60–120 employees
Mid-market wholesaler with a pronounced sales apparatus. Business Central as the ERP core for financials, purchasing, inventory, and sales — Dynamics 365 Sales on the same Microsoft data fabric for pipeline logic, forecasting, and opportunity management. Power BI as the shared reporting layer. Duration 6–9 months, staggered rollout. Followed by Application Care at a fixed monthly fee.
View →
Finance focus · 150–300 employees
Mid-market corporate group with multiple legal entities, international consolidation, and HGB/IFRS reporting needs. Microsoft Dynamics 365 Finance plus Dynamics 365 Supply Chain Management on the F&O platform. arades refers to a specialized F&O partner, remains involved for Microsoft Cloud architecture (identity, Azure integration, Power BI). Duration 12–18 months, multi-step cutover strategy.
View →
Commerce focus · 80–200 employees
Multi-store retailer with 20–40 locations plus online shop. Microsoft Dynamics 365 Commerce as the retail core (POS, store inventory, customer loyalty), integration with Microsoft Dynamics 365 Finance for the accounting layer and with Power BI for store reporting. arades acts as Microsoft Cloud architect in the background while the Commerce specialist runs the implementation. Duration 9–15 months.
View →
Frequently asked questions
Microsoft Dynamics 365 ERP today is an umbrella term for two worlds: Microsoft Dynamics 365 Business Central for classic mid-market companies (the successor of Dynamics NAV) and the F&O successor apps Finance, Supply Chain Management, Commerce, and Project Operations for demanding mid-market and larger organizations. Microsoft split the former Finance & Operations suite in 2020 into standalone apps with their own licenses and roadmaps. Microsoft ERP, Dynamics ERP, and D365 ERP all refer to the same product universe.
License costs start at Business Central at around €70 per user per month (Essentials) and reach up to around €180 per user per month for the F&O successor apps. Total project costs typically run at a factor of 3–5 above pure license costs — implementation, data migration, training, customization, and ongoing operations. Mid-market Business Central projects run between €60,000 and €250,000 net, F&O projects between €250,000 and more than €1,000,000 net. A solid cost calculation only emerges after a needs analysis — the License Cost Calculator gives an initial license orientation.
Rule of thumb: companies up to around 250 employees with manageable process complexity are well served in the Business Central world. From around 500 employees, with international consolidation, multi-entity structures, or highly complex manufacturing, the path often leads to the F&O world with Finance plus Supply Chain Management. Between 250 and 500 employees, industry, number of legal entities, and integration depth matter more — not headcount alone. Best clarified in an architecture review.
Six criteria matter: specialization in one ERP world (Business Central or F&O — not both superficially), industry experience with concrete references, documented delivery methodology for repeatable quality, an honest negative recommendation when Dynamics 365 isn't the right fit, software development depth for extensions beyond out-of-the-box capabilities, plus partner size and personal accessibility. Anyone offering all Microsoft ERP worlds equally has no real depth in any of them.
Microsoft continued the split of the former Finance & Operations suite — which began in 2020 — with additional changes in 2024: license models, module boundaries, and roadmaps were further differentiated. Today we speak of standalone apps: Dynamics 365 Finance, Dynamics 365 Supply Chain Management, Dynamics 365 Commerce, and Dynamics 365 Project Operations. The umbrella term F&O is still used but is technically outdated — each app has its own license, its own capabilities, and in part its own codebase.
Common starting points for mid-market migrations: Dynamics AX 2009 or 2012 (move to F&O successor apps), Microsoft Dynamics NAV (upgrade to Business Central — the direct successor path), SAP Business One for growing SMBs, Sage 100 and Sage X3 for manufacturers, abas ERP, and older home-grown ERP systems. Each migration path has its own data model gaps, its own license math, and its own typical project duration.
Business Central in a standard setup: 3–6 months for SMBs with 10–50 employees, 6–12 months for mid-market companies with 50–250 employees. F&O successor apps (Finance plus Supply Chain Management): 9–18 months for demanding mid-market companies, 18–30 months for larger constellations with multi-entity setups and international consolidation. Duration depends more on data-migration effort and process depth than on headcount.
Microsoft Dynamics 365 ERP is deeply integrated into the Microsoft Cloud — Microsoft 365, Power Platform, Power BI, Azure, and Microsoft Copilot are available without additional adapters. SAP traditionally relies on its own stack (S/4HANA, Fiori, BTP); Sage and abas are classic on-premises specialists with cloud paths. The Microsoft advantage shows especially where CRM and ERP need to operate on a shared data fabric or where Power BI is planned as the central reporting layer.
Three training duties that should not be missing from any Microsoft ERP project: end-user training (module- and role-specific — accountants need different content than warehouse staff), power-user training for the internal ERP owners (typically 1–3 people, taking on first-level support and master-data maintenance), and admin training (security, permission roles, customization basics, integration). Details under Microsoft Dynamics 365 Training.
An ERP system is not "implemented and done". Microsoft publishes two major releases per year in Business Central and quarterly updates in F&O. On top of that come license changes, new business requirements, and integrations with adjacent systems. Application Care covers this ongoing care at a predictable monthly flat fee — either as full service or as backup for an internal ERP team.
Further reading
Six follow-on topics in the order they typically come up after the initial selection.
Six selection criteria for a Microsoft Dynamics 365 partner — vendor-neutral, with a focus on the European mid-market and personal accountability rather than glossy brochures.
Discovery conversation, strategy workshop, architecture review — three advisory formats for SMB and mid-market. Module choice, license architecture, honest negative recommendation when needed.
Sales, Customer Service, Field Service, Project Operations, Business Central — Base/Attach logic, Copilot Credits, NCE mechanics. With triennial discount and volume rebates.
Microsoft Dynamics 365 Business Central as an arades service page — implementation, extensions, Application Care for SMBs and mid-market companies up to 250 employees.
Turning 50 licenses into 50 users. Role-specific curricula for end users, power users, and administrators. Online-live, on-site, and on-demand.
Calculate yourself what your Microsoft Dynamics 365 licenses would cost with the right mix of full-user, Team Member, and Device licenses — up to date at licenses.arades.de.
30 min · free · no obligation
Tell us about your plan. We listen, classify your situation against the Microsoft ERP worlds, and give an honest assessment — whether Business Central, whether an F&O successor, whether a specialized partner from our network fits better. If another product fits you better, we say so.
