Aditya's decided he needs an ERP. His IT vendor pitched Microsoft Dynamics. Then handed him two quotations — one for "Business Central" at ₹6L, one for "D365 F&O" at ₹38L.
Same Microsoft. Same brand. 6× price gap. Aditya wants to know why — and which one he actually needs.
- Business Central — built for SMBs (≤ 300 employees, ≤ ₹500 cr revenue). All-in-one. Faster, cheaper.
- D365 Finance & Operations — built for mid-large enterprises. Modular, deeper, much more complex.
- Licence cost gap: 3–4×. Implementation effort: 2–3×. Decide by size, complexity, multi-entity needs.
- Both run on Microsoft Cloud. Both speak to Office 365, Teams, Power BI, Power Platform.
The two products in one sentence each
Business Central (formerly NAV / Navision) is Microsoft's cloud ERP for small and mid-sized businesses — typically up to 300 users. Bundles finance, sales, purchasing, inventory, light manufacturing, project, service, operations — in one product.
Dynamics 365 Finance & Operations (often shortened to F&O, or split into Dynamics 365 Finance + Supply Chain Management) is Microsoft's enterprise ERP. Modular, deep, designed for multi-entity, multi-country, complex operations.
Side by side — the honest scorecard
Business Central
SMB sweet spot
~₹6k–8.5k / user / month. Implementation ₹6–20 L. Manufacturing + warehousing covered to a good-enough depth.
D365 F&O
Enterprise depth
~₹16k–22k / user / month. Implementation ₹20L–₹1cr+. Deep WMS, intercompany, advanced manufacturing.
The 3-question decision tree
👉 Over ₹500 cr → D365 F&O. Skip the rest.
👉 ₹100–500 cr → continue to Q2.
👉 Under ₹100 cr → Business Central (almost always). Continue only if multi-entity.
👉 Multiple legal entities, especially across countries, with intercompany flows → lean F&O.
👉 Single entity → Business Central handles you well even at ₹400 cr.
👉 Process / mixed-mode / batch manufacturing, multi-warehouse WMS, transportation management, demand forecasting → F&O.
👉 Discrete or light manufacturing, standard distribution → Business Central.
When Business Central is the right call
Pick BC if you:
👉 Are a single-entity SMB or family business
👉 Want one ERP doing finance + sales + purchase + inventory + light manufacturing without buying separate modules
👉 Have a small IT / finance team and want quick rollout
👉 Want predictable monthly licence costs
👉 May grow to 200 users — BC handles that comfortably
If you're a single-entity company under ₹500 cr revenue running standard distribution / trading / light manufacturing, you'd be paying for things you'll never use with F&O. BC was built exactly for your shape.
When D365 F&O is the right call
Pick F&O if you:
👉 Have multiple legal entities, possibly across countries
👉 Run complex manufacturing — process, mixed-mode, batch, MRP at scale
👉 Need advanced supply chain — multi-warehouse WMS, route optimisation, demand forecasting
👉 Have specific regulatory needs — consolidations, transfer pricing, intercompany eliminations
👉 Are 500+ employees with sub-teams that need role-tailored apps
If you're at ~₹150 cr with moderate complexity, you're in the grey zone. Both can work. Decision usually comes down to: budget, team strength, and whether you anticipate global expansion in 3 years. Don't pick F&O for prestige.
Three real scenarios
Apparel maker
₹40 cr · 60 emp
BC. Single factory, single entity. BC's manufacturing module is plenty. Migrate to F&O in 5 years if you scale 4×.
Pharma distributor
₹200 cr · 80 emp
BC. 3 regional offices but single entity. Distribution well-handled. Better TCO at this scale.
Auto components
₹800 cr · 400 emp
F&O. Complex manufacturing, 2 factories + 1 export entity, intercompany flows. F&O's depth pays off.
The wrong ERP doesn't fail because it's bad software. It fails because it's the wrong fit. Pick by your actual complexity — not your dream size.
What it actually costs over 3 years
Both numbers include licences + implementation + customisation + support. The hidden cost is internal team time — typically 30% of an FY for the project lead and key users during rollout. Budget it.
Aditya's call
Aditya: ₹12 cr distribution, single entity, 25 employees, standard inventory.
Recommendation: Business Central. No real F&O justification at this size and shape. Comfortable runway to grow 5× without switching.
Three frequent worries
👉 "Can we start on BC and migrate to F&O later?" Yes, but it's a re-implementation, not an upgrade. Data and business logic don't directly port. Plan it as a multi-year decision.
👉 "What about India GST / e-invoice / TDS?" Both have it. F&O goes deeper on composite supplies and refund-of-ITC workflows.
👉 "Do we need a Microsoft partner?" Yes for both. Licences go through a CSP. Implementation needs functional + technical consultants.
Quick answers
Same lineage. Business Central is the cloud-first evolution of NAV (Navision). NAV is discontinued; BC is the current product with ongoing semi-annual updates.
Yes — Microsoft has India South / India Central / India West regions. Data residency for regulatory compliance can be enforced for both BC and F&O.
Yes, in some group structures — parent on F&O, smaller subsidiaries on BC. Connected via Dataverse / APIs. Less common but used by groups with very mixed scale.
Under ₹10 cr — consider Zoho Books / Tally / Odoo. Microsoft starts adding real value above that. Read our "Do you need an ERP?" guide.
3-year rule: licences + implementation + customisation + support. BC: ₹25–60L total. F&O: ₹60L–₹2cr+. Plus your internal team's time, which is the biggest hidden cost.
When you might want help
The choice between BC and F&O is rarely just about features. It's about your likely 3-year trajectory, your team's capacity to absorb change, and the partner ecosystem near you. We do fit assessments — 30 minutes mapping size + complexity + team + roadmap, ending with a clear recommendation (sometimes "neither yet").
Want a 30-minute fit assessment?
We map your size, complexity and team, and tell you which Microsoft ERP fits (or whether you need one at all).