If you're planning a Dynamics 365 upgrade and trying to put a number on it, you've probably already discovered the problem: almost nobody gives you a straight answer. Microsoft's pricing page tells you the licence fees. Your partner quotes you a project fee. And then, six months in, you're staring at a budget overrun wondering where the other 40% came from.
We've guided organisations across the UAE and GCC through dozens of D365 upgrades, and the pattern is almost always the same. The licence cost is the easy part. It's the surrounding services — implementation, customisation, data migration, training, and post-go-live support — that catch businesses off guard.
This post breaks down every cost component you need to plan for, with real figures, so you can build a budget that actually holds.
Key insight: A typical Dynamics 365 upgrade involves at least five distinct cost layers. Missing even one of them can blow your project budget by 30–50%.
Layer 1: Licensing Costs — The Starting Point, Not the Full Picture
Licensing is the most visible cost, and Microsoft's per-user subscription model is actually one of the more transparent parts of the whole equation. Prices vary significantly by module and tier.
Here's the current pricing breakdown for the most common Dynamics 365 applications (as of 2026, reflecting the November 2025 price update):
Business Central
- Essentials: $80/user/month
- Premium: $110/user/month
- Team Members: $8/user/month
Finance
- Standard: $210/user/month
- Premium: $300/user/month
Sales
- Professional: $65/user/month
- Enterprise: $105/user/month
Customer Service
- Professional: $50/user/month
- Enterprise: $105/user/month
Field Service
- Standard: $105/user/month
Project Operations
- Standard: $135/user/month
For context, Microsoft's official Dynamics 365 pricing page confirms these figures, though pricing can vary by region and volume agreement.
What the Licence Fee Doesn't Include
The licence is just the right to use the software. It does not cover:
- Initial setup and configuration
- Custom development or workflow builds
- Data migration from your existing system
- User training
- Any third-party integrations
The attach rate advantage: If your organisation runs multiple D365 modules, Microsoft offers significantly reduced pricing for secondary licences. A Finance user adding Supply Chain Management, for example, pays an attach price of $30 per user rather than the full rate. This is one of the most underutilised cost optimisation levers we see in upgrade projects.
Layer 2: Implementation Service Costs
This is where the budget conversation gets serious. Implementation costs are separate from your subscription and are typically a one-time investment, though ongoing support contracts extend the spend beyond go-live.
Implementation covers: requirements gathering, system configuration, custom workflow development, integration with other business systems, data migration, testing, and go-live support. The range is wide because the scope varies enormously by module and business complexity.
Implementation Cost Ranges by Module
- Business Central: $5,000 – $30,000
- Finance: $30,000 – $300,000
- Sales: $5,000 – $30,000
- Customer Service: $5,000 – $20,000
- Field Service: $15,000 – $40,000
- Project Operations: $50,000 – $70,000
For Dynamics 365 Finance and Operations — the most complex implementation in the D365 family — costs can reach $1,000,000 or more for large enterprises with multi-entity structures, complex integrations, and significant data migration requirements.
What Drives Implementation Costs Up
Most organisations underestimate implementation costs because they focus on the standard configuration rather than their actual business requirements. The factors that push costs toward the upper end:
- Number of customisations — every deviation from standard functionality adds development hours
- Integration complexity — connecting D365 to third-party ERP, CRM, or legacy systems is rarely straightforward
- Number of legal entities or business units — multi-entity setups multiply configuration work
- Data volume and quality — large, messy datasets from legacy systems significantly extend migration timelines
- User count — more users means more training, more testing, more change management
The honest reality: A mid-sized organisation upgrading from an older on-premise Dynamics version to D365 Finance, with 25–50 users and a handful of integrations, should realistically budget $80,000–$180,000 in implementation services alone, before licences.
Layer 3: Customisation and Development Costs
Customisation is the cost that surprises organisations most, because it only becomes visible once the discovery phase is complete. Standard D365 functionality covers a lot of ground, but almost every business has processes that don't fit neatly into out-of-the-box workflows.
The general rule: the more your current system has been customised over the years, the higher your D365 customisation costs will be. Legacy Dynamics AX or NAV environments that have been running for 10+ years often carry hundreds of custom modifications, all of which need to be assessed, rebuilt, or retired during an upgrade.
Customisation Cost Ranges by Module
- Business Central: $5,000 – $30,000
- Finance: $30,000 – $300,000
- Sales: $10,000 – $120,000
- Customer Service: $10,000 – $100,000
- Field Service: $15,000 – $150,000
- Project Operations: $15,000 – $150,000
The Customisation Trap
One of the most common mistakes we see is organisations trying to replicate their old system exactly in D365. This approach is expensive and often counterproductive. D365 has evolved significantly, and many workflows that required custom code in older versions are now handled natively.
A good upgrade partner will push back on unnecessary customisation — not because it's easier for them, but because every custom modification is a maintenance liability you'll carry forward. The right question isn't "can we build this?" but "should we, given what D365 already does?"
Our recommendation: Before agreeing to any customisation spend, ask your partner to demonstrate whether the standard functionality genuinely can't meet the requirement. In our experience, roughly 30–40% of requested customisations turn out to be unnecessary once teams properly understand the standard product.
Layer 4: Data Migration and Infrastructure
Data migration is unglamorous, time-consuming, and almost always underestimated. Moving your historical data from a legacy Dynamics environment (or any other ERP) into D365 involves extraction, cleansing, transformation, validation, and loading — and the quality of your source data determines how painful each step is.
Infrastructure and Migration Cost Ranges
- Business Central: $2,500 – $10,000
- Finance: $10,000 – $60,000
- Sales: $1,000 – $6,000
- Customer Service: $1,000 – $6,000
- Field Service: $2,500 – $15,000
- Project Operations: $2,000 – $10,000
These figures cover Azure environment setup, data migration tooling, and infrastructure configuration. They do not include the professional services time required to actually run the migration — that's bundled into the implementation cost.
Why Data Migration Takes Longer Than Expected
Three factors consistently extend data migration timelines:
- Data quality issues in the source system — duplicate records, inconsistent formats, missing fields, and years of workarounds all need resolving before migration
- Business decisions required mid-migration — which historical records to bring across, how far back to go, and what to archive are business decisions that require stakeholder input, not just technical work
- Iterative testing cycles — a proper migration runs multiple test loads before the final cutover, and each cycle surfaces new issues
One practical note for UAE and GCC organisations: if your current system holds data in Arabic or mixed-language formats, factor in additional time for character encoding, field mapping, and validation against local compliance requirements.
Layer 5: Training, Change Management, and Post-Go-Live Support
The costs that come after go-live are the ones most frequently dropped from the initial budget — and the ones that determine whether the upgrade actually delivers value.
Training Costs
User adoption is the single biggest risk factor in any ERP upgrade. A technically successful implementation that nobody uses properly is a failed project. Training costs scale with user count, role complexity, and how different D365 is from your previous system.
Typical training cost benchmarks:
- End-user training: $500 – $1,500 per user (depending on role complexity)
- Power user / super user training: $2,000 – $5,000 per user
- Administrator training: $3,000 – $8,000 per person
- Custom training material development: $10,000 – $30,000 for a full library
For a 50-user deployment, training alone can realistically add $40,000 – $80,000 to the total project cost.
Post-Go-Live Support
The first 90 days after go-live are critical. Users encounter edge cases, processes that weren't fully tested, and integration issues that only surface under real load. Budgeting for structured hypercare support during this period is not optional — it's the difference between a smooth landing and a chaotic first quarter.
Post-go-live support models typically run as:
- Hypercare period (first 60–90 days): Dedicated on-call support, often included or discounted as part of the implementation contract
- Ongoing managed support: Monthly retainer ranging from $2,000 – $15,000+ depending on scope and SLA
What we've seen: Organisations that skip structured post-go-live support spend 2–3x more resolving issues reactively in the months that follow. Planned support is almost always cheaper than emergency fixes.
What Does a Full D365 Upgrade Actually Cost? Real Budget Scenarios
Pulling all five layers together, here's what realistic total budgets look like across different upgrade scenarios. These figures combine licensing (first year), implementation, customisation, infrastructure, and training.
Small CRM upgrade (10–20 users, Sales Professional) Estimated total budget: $25,000 – $60,000
Mid-market ERP upgrade (25–50 users, Business Central Premium) Estimated total budget: $80,000 – $180,000
Finance transformation (30–60 users, Finance Standard) Estimated total budget: $150,000 – $400,000
Enterprise Finance and Operations rollout (100+ users) Estimated total budget: $500,000 – $1,500,000+
These ranges assume a single-entity organisation with moderate integration complexity. Multi-entity structures, extensive legacy customisations, or complex regulatory requirements (common in UAE financial services and government-adjacent sectors) will push costs toward or beyond the upper end.
The Cost of Delaying an Upgrade
One number that rarely appears in upgrade cost discussions: the cost of staying on an unsupported or outdated system. Legacy Dynamics versions (AX 2012, NAV, GP) are approaching or have passed end-of-support milestones. Running on unsupported software carries real financial exposure — security vulnerabilities, compliance gaps, and the compounding cost of maintaining ageing custom code.
According to Microsoft's Dynamics 365 lifecycle documentation, organisations still on older on-premise versions also miss out on the continuous update model that D365 cloud subscribers receive, including AI capabilities now bundled into base licences at no additional cost.
The business case framing that works: The upgrade cost is not a sunk cost — it's an investment with a measurable return. Faster processes, reduced IT overhead, eliminated maintenance contracts, and access to Copilot AI features all contribute to ROI that most organisations see within 18–24 months of a well-executed upgrade.
How to Get an Accurate Quote for Your Upgrade
The figures in this post give you a solid planning framework, but your actual costs will depend on specifics that only a proper discovery exercise can surface. Here's what a credible upgrade assessment should include:
- Current state audit — a review of your existing system, including all customisations, integrations, and data volumes
- Requirements mapping — matching your business processes to D365 standard functionality to identify genuine gaps
- Licence optimisation analysis — identifying the right mix of full licences, team member licences, and attach pricing to minimise subscription costs
- Data quality assessment — evaluating source data to estimate migration complexity and timeline
- Phased delivery option — for larger projects, a phased approach (core modules first, advanced features later) can spread costs and reduce risk
A partner who gives you a fixed price without running a discovery phase is either very experienced with your exact scenario or cutting corners. In either case, make sure the quote is itemised — you should be able to see what you're paying for at each layer.
As a certified Microsoft Dynamics 365 partner serving organisations across the UAE and GCC, Terracez runs structured upgrade assessments that give you a clear, itemised cost picture before any commitment. If you're in the planning stage, get in touch with our team for a no-obligation conversation about your upgrade scope and budget.
.png)
.png)
.webp)
