Most enterprises in Saudi Arabia and the UAE already know they need to move off legacy Dynamics. The decision stopped being theoretical on 10 January 2023, when Microsoft ended extended support for Dynamics AX 2012 R3. What remains genuinely uncertain for most buyers is not whether to upgrade - it is how to do it without budget shock, business disruption, or a partner who underestimates the complexity.
The market is saturated with implementation-first messaging. Most regional providers lead with certifications and delivery speed. Very few lead with risk, readiness, or a clear commercial framework that helps a CIO or CFO make a defensible decision.
This guide fills that gap.
What this guide covers:
- What Dynamics 365 upgrade services actually include - and what they do not
- Realistic cost ranges for Saudi Arabia and UAE enterprises in 2026
- Why some upgrades complete in 31 days and others drag past six months
- How to evaluate and select the right upgrade partner for your organisation
- The risk case for acting now, not deferring further
- A real GCC delivery example and what made it work
Whether you are a CIO building a business case, a CFO reviewing a budget proposal, or a Transformation Director comparing providers, this guide gives you the framework to make a confident, well-governed decision.
What are Dynamics 365 upgrade services?
Dynamics 365 upgrade services cover the full programme of work required to move an organisation from a legacy Microsoft ERP or CRM platform - most commonly Dynamics AX 2012 - to the current cloud-based Dynamics 365 suite.
The term is used loosely in the market. Some providers mean technical migration only. Others include business process redesign, governance, training, and post-go-live support. Buyers should clarify scope before comparing proposals.
Definition: A Dynamics 365 upgrade service is a structured programme that transitions an organisation from an on-premises or legacy Dynamics platform to Dynamics 365 cloud applications, covering technical migration, data integrity, integration continuity, business process alignment, and user adoption.
What a complete upgrade service typically includes
A well-scoped Dynamics 365 upgrade service should cover all of the following:
- Upgrade assessment - current-state analysis, gap identification, scope definition, and risk mapping
- Architecture and environment planning - cloud infrastructure, licensing structure, and deployment model decisions
- Data migration - data cleansing, mapping, validation, and cutover strategy
- Integration review - assessment and rebuild of third-party connections, APIs, and legacy interfaces
- Configuration and customisation - solution design aligned to the target operating model
- Testing - unit, integration, user acceptance, and performance testing
- Training and change readiness - role-based training, adoption planning, and communication
- Cutover and go-live - controlled transition with rollback planning
- Post-go-live support - stabilisation, issue resolution, and optimisation
What it is not
An upgrade service is not the same as a fresh implementation. It carries the additional complexity of legacy data, existing integrations, established business processes, and user expectations built around the old system. Providers who treat an AX 2012 to Dynamics 365 upgrade as a standard deployment often underestimate that complexity, and that is where timelines and budgets begin to slip.
Should you upgrade or reimplement? How we help you decide
Before scoping any programme, Terracez addresses a question most providers skip: is an upgrade actually the right path, or does your organisation need a clean reimplementation?
The answer matters. Choosing the wrong path wastes budget, embeds technical debt, and can produce a system that is technically newer but operationally no better than what you had before.
The honest starting point: An upgrade carries your existing configurations, data, and logic forward. A reimplementation starts from a clean foundation using Dynamics 365 standard processes. One preserves continuity. The other creates transformation. They are not interchangeable.
The two primary signals Terracez looks for
Industry analysis consistently identifies customisation depth and system age as the strongest predictors of whether an upgrade path is viable. ERP advisory research confirms that organisations with years of technical debt, overlapping customisations, and significantly evolved business processes are better served by reimplementation than by carrying legacy complexity into a new environment.
Terracez assesses two primary signals during the upgrade assessment:
Signal 1: Customisation depth and documentation quality
If your AX 2012 environment has been heavily customised over the years, the upgrade path becomes progressively more expensive and risky. Each customisation must be evaluated, re-coded or rebuilt for Dynamics 365, and tested. When customisation volume is high, the cost of carrying that code forward often exceeds the cost of starting clean.
A useful industry benchmark: research suggests that approximately 30% of customisations in long-running ERP environments are no longer required by the business. They were built for processes, reporting requirements, or organisational structures that no longer exist. An upgrade preserves them by default. A reimplementation forces the question of whether they should exist at all.
The documentation gap is where most upgrade assessments break down.
During the Terracez assessment, we ask for all available documentation from the original implementation: Business Requirements Documents (BRDs), Functional Requirements Documents (FRDs), technical design specifications, customisation logs, and any change request records from subsequent enhancements. What we find in most long-running AX 2012 environments tells its own story.
In organisations where the original implementation team has moved on, documentation is often incomplete, outdated, or missing entirely. Customisations were built, tested, and deployed - but the reasoning behind them was never formally recorded. The system works, but nobody can fully explain why it was built the way it was.
This matters for three reasons:
- Upgrade scoping accuracy - without documentation, the assessment must reverse-engineer every customisation from the code itself. This adds time and cost to the assessment phase, and increases the risk of missed dependencies surfacing mid-programme.
- Redundancy identification - documented BRDs and FRDs allow Terracez to compare what the business required at the time of implementation against what the business actually does today. This comparison frequently reveals customisations that are technically active but operationally redundant - code that runs on every transaction but serves a process that no longer exists.
- Reimplementation confidence - when documentation is strong, a reimplementation can be scoped with precision. When it is absent, the reimplementation must begin with a current-state discovery exercise to rebuild the understanding that documentation should have preserved.
What to prepare before your assessment: Gather your original BRDs, FRDs, technical specifications, and any enhancement or change request logs from the lifetime of your AX 2012 environment. If documentation is incomplete, flag this early. It does not disqualify you from an upgrade - but it changes the assessment scope and the risk profile of the programme.
Signal 2: Deployment age and business evolution
If the last full deployment or major enhancement was seven to ten years ago, the gap between what the system was designed to do and what the business actually does today is almost always significant. Business models change. Organisational structures change. Regulatory requirements change. A system that was a good fit in 2014 or 2016 may be constraining operations in ways that an upgrade will not resolve.
The question Terracez asks is not "can we upgrade this system?" but "does this system still reflect how your business operates?" If the answer is no, an upgrade migrates the wrong model onto a new platform.
The third signal: leadership and organisational change
This is the dimension most providers do not address, and it is one of the most important.
When an organisation has experienced significant leadership change, or where the team that originally implemented and shaped the system has largely moved on, the conditions for genuine transformation are often stronger than they appear. A new leadership team is not constrained by the decisions, workarounds, and institutional habits that accumulated in the old system. They have the mandate and the cultural openness to define how the business should operate, not just how it has operated.
In these situations, Terracez recommends reimplementation. Not because the existing system is technically broken, but because the organisation has already moved on culturally. Carrying forward the old system's logic would anchor a new leadership team to decisions made by their predecessors, often for reasons no one can fully explain anymore.
Terracez principle: New leadership is one of the strongest transformation enablers available. A reimplementation in that context is not a risk. It is an opportunity to build the operating model the organisation actually needs, rather than inheriting the one it grew out of.
The decision framework
Neither path is inherently better. The right choice depends on your organisation's specific context. What Terracez will not do is default to the cheaper-looking option without assessing which path actually reduces your long-term risk.
Both paths are available through Terracez. The upgrade assessment determines which one is right for your organisation before any programme commitment is made.
Why upgrading from AX 2012 is now a governance issue, not just a technology issue
Extended support for Microsoft Dynamics AX 2012 R3 ended on 10 January 2023. No new security patches, no regulatory updates, and no compliance fixes have been issued since that date. For organisations still running AX 2012 in 2026, this is not a technology problem. It is a governance and audit exposure.
The risk is compounding. Every quarter on an unsupported platform increases the gap between your system and the current security and compliance baseline. In regulated industries - manufacturing, construction, government, oil and gas - that gap becomes harder to defend to auditors, insurers, and boards.
The cost of staying is rising faster than the cost of moving.
The AX 2012 risk register
The Saudi Arabia and UAE compliance dimension
For enterprises operating under ZATCA e-invoicing requirements in Saudi Arabia, or UAE corporate tax and VAT obligations, an unsupported ERP creates a direct compliance gap. Dynamics 365 Finance includes localised compliance updates delivered through Microsoft's regular release waves, covering both Saudi and UAE regulatory requirements. AX 2012 does not receive these updates.
The question is no longer whether to upgrade. It is how to do it with the lowest possible disruption and the strongest possible governance.
How much do Dynamics 365 upgrade services cost in 2026?
This is the question most providers avoid answering directly. Here is a clear framework based on current market data and Terracez delivery experience across Saudi Arabia and the UAE.
Dynamics 365 upgrade costs have two distinct components: licensing and service delivery. Most budget conversations collapse these together, which is where financial surprises begin.
Licensing costs (per user, per month)
Microsoft revised Dynamics 365 pricing in October 2024, and 2026 proposals now reflect a higher baseline across most SKUs.
Note: Licensing costs are separate from implementation and upgrade service fees. Both must be budgeted. AI add-ons and Copilot capabilities carry additional consumption-based charges that are increasingly appearing in 2026 proposals.
Service delivery costs: Saudi Arabia and UAE ranges
Based on Terracez delivery benchmarks and regional ERP market data, upgrade service costs in Saudi Arabia typically fall into three tiers:
UAE projects follow broadly comparable ranges, though delivery timelines tend to be shorter due to lower localisation complexity in some sectors.
What drives cost up
Understanding cost drivers helps buyers challenge proposals and avoid scope creep. The variables that most reliably inflate budgets are:
- Customisation depth - heavily modified AX 2012 environments require more analysis and rework
- Integration count - each third-party connection adds assessment, rebuild, and testing effort
- Data quality - poor data requires cleansing before migration, which adds time and cost
- Scope discipline - adding modules or features mid-programme is the single fastest way to increase cost
- Internal readiness - organisations without a dedicated internal owner or decision-making authority extend timelines, which directly increases service fees
- Governance maturity - weak governance creates rework cycles; strong governance compresses them
The 2026 pricing trend
Upgrade budgets are running 10-25% higher than equivalent programmes from 2024, driven by Microsoft licence increases, growing demand for AI-enabled rollouts, and the rising complexity of regulatory localisation requirements across Saudi Arabia and the UAE. Organisations deferring upgrades are not avoiding cost - they are deferring into a higher-cost environment while accumulating compliance risk.
What separates a 31-day upgrade from a 6-month one?
The average AX 2012 to Dynamics 365 Finance upgrade runs four to six months. Some programmes compress to four to eight weeks. The difference is rarely the software. It is almost always the organisation.
Timeline is a readiness indicator, not a provider claim.
A provider who promises a fast upgrade without assessing your data quality, integration count, customisation depth, and internal decision-making capacity is not being efficient. They are being optimistic in a way that will cost you later.
What the comparison actually looks like
The real timeline driver
Microsoft's Dynamics 365 release cadence delivers two major waves each year - April to September and October to March - with quarterly service updates for Finance and Operations. A well-prepared organisation can align go-live to a release window with confidence. An unprepared one misses windows and extends timelines.
The providers who consistently deliver faster upgrades do not have better developers. They have better pre-assessment processes that identify and resolve readiness gaps before configuration begins.
What this means for your programme
If your organisation has heavy AX 2012 customisations, multiple integrations, or a history of delayed ERP decisions, plan for five to six months and budget accordingly. If your scope is controlled, your data is clean, and your leadership team is aligned, a significantly shorter timeline is achievable.
The honest answer is that timeline depends on your organisation's readiness more than any provider's capability. The right partner will tell you that before you sign the contract.
How to choose the right Dynamics 365 upgrade partner in Saudi Arabia or the UAE
Most provider evaluation processes in the GCC focus on Microsoft certifications, headcount, and day rates. These are table stakes, not differentiators. The criteria that actually predict delivery success are harder to assess - and most providers do not volunteer them.
Here is a practical evaluation framework built around what matters for enterprise buyers in Saudi Arabia and the UAE.
The provider evaluation checklist
1. Upgrade-specific experience (not just implementation experience) Ask for evidence of AX 2012 to Dynamics 365 upgrades specifically - not general Dynamics 365 implementations. Upgrades carry legacy complexity that fresh deployments do not. A partner with strong implementation credentials but no upgrade history is a different risk profile.
2. Pre-assessment methodology Does the provider conduct a formal readiness assessment before scoping the project? If they are willing to quote a fixed price and timeline before assessing your data, integrations, and customisations, that is a red flag. Reliable partners assess before they commit.
3. GCC regulatory and localisation capability For Saudi Arabia: ZATCA Phase 2 e-invoicing compliance, Arabic language support, VAT reporting, and Zakat configuration. For UAE: corporate tax compliance, VAT, and multi-currency requirements. These are not optional extras - they are delivery requirements that must be confirmed before contract.
4. Governance and change control approach Ask how the provider manages scope change. A partner with no formal change control process will absorb scope creep silently until it becomes a budget conversation you did not expect. Governance discipline directly protects your budget.
5. Executive communication and escalation How does the provider communicate with CIO and CFO-level stakeholders? Can they explain business risk in executive language, or do they default to technical reporting? The quality of executive communication is a strong proxy for overall delivery maturity.
6. Post-go-live commitment Go-live is not the end of an upgrade. The first 60-90 days after cutover carry the highest risk of adoption failure, process breakdowns, and integration issues. Confirm the provider's post-go-live support model before signing.
Provider scoring matrix
Buyer's principle: The right partner will challenge your assumptions about timeline, scope, and internal readiness before the contract is signed. If a provider agrees with everything you say, they are selling - not advising.
The Terracez approach: reduce risk before configuration begins
Most upgrade programmes start with solution design. Terracez starts earlier - with a structured assessment of whether the organisation is ready to transform, not just whether the technology can be migrated.
This is not a procedural difference. It is a risk-reduction philosophy. The majority of upgrade failures - budget overruns, timeline slippage, poor adoption, and post-go-live instability - have their roots in organisational gaps that existed before a single line of configuration was written.
The four-phase delivery model
Phase 1: Transformation Intelligence Before implementation begins, Terracez assesses executive alignment, governance maturity, business readiness, operating model clarity, and decision-making structure. The output is an honest view of where organisational risk sits - and a plan to address it before it surfaces mid-programme.
Phase 2: Business Architecture Before configuring Dynamics 365, the future operating model is defined. This includes process ownership, decision rights, KPI frameworks, and cross-functional governance. Technology is configured to support the agreed business model - not the other way around.
Phase 3: Dynamics 365 Implementation Only after the business foundations are established does configuration begin. This phase covers solution design, data migration, integration build, testing, and deployment - aligned to the operating model defined in Phase 2, not to a generic template.
Phase 4: Adoption and Value Realisation Go-live is the beginning of value creation, not the end of the project. Terracez continues measuring user adoption, process compliance, business KPIs, and value realisation in the weeks and months after cutover. This is where most programmes stop. It is also where most of the business value is created or lost.
Why this matters for buyers: An upgrade partner who starts with configuration is optimising for delivery speed. A partner who starts with readiness is optimising for business outcomes. The difference shows up in post-go-live performance, not in the project plan.
This approach is particularly relevant for enterprises in Saudi Arabia and the UAE where regulatory complexity, multi-entity structures, and executive decision-making patterns create upgrade risks that a purely technical delivery model will not surface until it is too late.
Industries we serve and how we protect business continuity during migration
Dynamics 365 upgrades are not industry-neutral. The complexity, compliance requirements, and operational risk of a migration vary significantly depending on how your business runs, how tightly your ERP is connected to operations, and how much downtime your business model can absorb.
Terracez delivers Dynamics 365 upgrade services across the industries where ERP failure carries the highest operational consequence.
Industries we focus on
Each of these industries carries specific localisation requirements for Saudi Arabia and the UAE - VAT, ZATCA Phase 2 e-invoicing, Zakat configuration, Arabic language support, and government reporting standards. These are built into the delivery scope from day one, not added as afterthoughts.
How we protect business continuity during migration
The most common fear among CIOs and CFOs is not the upgrade itself. It is the disruption that happens around it - finance teams unable to process transactions, operations losing visibility, integrations breaking silently after cutover.
Terracez manages continuity through a structured approach that treats go-live as a controlled handover, not a hard switch.
1. Parallel environment validation Before cutover, the new Dynamics 365 environment runs in parallel with the legacy system. Business processes are validated against real transaction data, not test scenarios. Discrepancies are resolved before the legacy system is decommissioned.
2. Phased cutover planning For complex environments, we sequence go-live by business unit, geography, or module rather than switching the entire organisation simultaneously. This contains disruption to one area while the rest of the business continues operating normally.
3. Integration continuity testing Every third-party connection - whether it is a payroll system, a warehouse management platform, a banking integration, or a government reporting portal - is tested end-to-end before go-live. Integration failures after cutover are one of the most common sources of post-go-live instability. We address them before, not after.
4. Cutover rehearsal We run at least one full cutover rehearsal before the live event. This identifies timing gaps, sequence issues, and data anomalies under realistic conditions. It also gives the internal team confidence that the process is understood and repeatable.
5. Hypercare support window The first 30 days after go-live carry the highest operational risk. Terracez maintains an active hypercare support model during this window - dedicated resource, daily check-ins, and rapid response to issues as they emerge. Most providers reduce engagement after go-live. We increase it.
The principle: Business continuity during a Dynamics 365 migration is not a feature of the software. It is a function of how the programme is planned, sequenced, and governed. The organisations that experience the least disruption are the ones that invested the most in preparation - not the ones that moved the fastest.
Regional proof: what a fast, lower-risk upgrade actually looks like
Theory is useful. Evidence is better. Here is what a compressed, well-governed upgrade looks like in practice, based on a Terracez-delivered programme in the GCC region.
The case snapshot
Programme type: AX 2012 to Dynamics 365 Finance and Operations upgrade Region: GCC Industry: Infrastructure and project-based services Go-live outcome: 31 days from programme start to live operation Scope: Finance and Operations core modules, localised for regional compliance requirements
What made 31 days possible
Speed in this programme was not luck or an aggressive timeline imposed by the client. It was the direct result of four conditions that Terracez assessed and confirmed before configuration began:
- Controlled scope - the organisation agreed to upgrade core Finance and Operations functionality first, deferring non-essential customisations to a post-go-live phase
- Decision clarity - a single empowered internal owner made configuration and process decisions without escalation loops
- Data readiness - the migration dataset had been pre-validated; no significant cleansing cycle was required during the programme
- Governance discipline - a formal change control process prevented scope additions from entering the programme once it was underway
What buyers should take from this
A 31-day upgrade is not a standard offering. It is an outcome that becomes available when readiness conditions are met. The lesson is not "ask your partner to go faster." The lesson is: invest in readiness before you start, and speed becomes a natural by-product.
For organisations with more complex environments, the same principles apply at a longer timeline. Governance, scope control, decision speed, and data quality are the variables that compress or extend every upgrade programme - regardless of size.
Common questions buyers ask before approving an upgrade
How long does a Dynamics 365 upgrade from AX 2012 take?
The average AX 2012 to Dynamics 365 Finance upgrade takes four to six months. Programmes with controlled scope, clean data, and strong governance can compress to four to eight weeks. Programmes with heavy customisations, multiple integrations, or weak internal ownership typically run six months or longer. Timeline is determined by organisational readiness, not provider speed.
How much does a Dynamics 365 upgrade cost in Saudi Arabia?
Upgrade service costs in Saudi Arabia range from SAR 150,000 for smaller single-entity deployments to SAR 4,000,000 or more for large enterprise programmes with multi-entity scope and complex integrations. These figures cover service delivery only and exclude Microsoft licensing fees. Licensing for Dynamics 365 Finance runs $180-$210 per user per month; Business Central Essentials starts at $80 per user per month. Budget both components separately.
Is it still safe to run AX 2012 in 2026?
No. Microsoft ended extended support for AX 2012 R3 on 10 January 2023. No security patches, compliance updates, or regulatory fixes have been issued since that date. For organisations in Saudi Arabia subject to ZATCA e-invoicing requirements, or UAE enterprises managing corporate tax obligations, running an unsupported ERP is a direct compliance gap. The risk increases with each passing quarter.
What is the difference between a Dynamics 365 upgrade and a new implementation?
An upgrade carries legacy complexity that a fresh implementation does not. You are migrating existing data, rebuilding existing integrations, and transitioning users who have established workflows. Providers who scope an upgrade as a standard implementation will underestimate this complexity. The assessment phase should specifically address legacy data quality, customisation depth, integration inventory, and change readiness - not just future-state requirements.
How much internal resource does an upgrade require?
Plan for a dedicated internal project lead with decision-making authority, functional owners for each business area in scope, and IT resource for integration and data work. The most common cause of timeline slippage is insufficient internal ownership - not provider performance. A realistic internal commitment for a mid-market upgrade is one to two full-time equivalents for the duration of the programme, plus part-time involvement from business process owners.
What should I ask a Dynamics 365 upgrade partner before signing?
Ask for evidence of completed AX 2012 to Dynamics 365 upgrades specifically. Ask how they conduct their pre-assessment and what they do if readiness gaps are found. Ask how scope changes are managed and priced. Ask what their post-go-live support model covers and for how long. Ask for a reference from a GCC client with a similar business profile. A partner who answers these questions clearly and confidently is a partner who understands what upgrade delivery actually involves.
Does Dynamics 365 support ZATCA Phase 2 e-invoicing compliance in Saudi Arabia?
Yes. Dynamics 365 Finance includes Saudi Arabia localisation covering ZATCA Phase 2 e-invoicing, Arabic language support, VAT reporting, and Zakat configuration. These are delivered and updated through Microsoft's regular release waves. AX 2012 does not receive these updates, which is one of the primary compliance drivers for the upgrade decision in Saudi Arabia.
When should you start a Dynamics 365 upgrade assessment?
If any of the following are true for your organisation, the assessment should start now - not at the next budget cycle.
- Your organisation is still running AX 2012 or an earlier Dynamics version in any part of the business
- You are facing ZATCA Phase 2 compliance requirements in Saudi Arabia or corporate tax obligations in the UAE
- Your ERP support and maintenance costs have increased in the past 12 months
- You have experienced integration failures, reporting limitations, or data quality issues linked to the legacy platform
- Your board or audit committee has raised questions about ERP support status or compliance risk
- You are planning a business model change, merger, acquisition, or expansion that requires a modernised ERP foundation
- You are beginning a new budget cycle and need a credible cost and timeline estimate to include in planning
The right first step is not buying licences. It is understanding your scope, risk, and readiness.
An upgrade assessment typically takes two to four weeks and produces a clear view of:
- Current-state complexity and legacy risk
- Recommended scope and phasing
- Realistic timeline and budget range
- Internal resource requirements
- Readiness gaps that need to be addressed before the programme begins
The cost of a well-structured assessment is a fraction of the cost of a poorly scoped programme. Organisations that skip the assessment phase are not saving time. They are moving budget risk from a known line item to an unknown one.
Starting the assessment now also protects against the pricing inflation trend - upgrade budgets are running 10-25% higher in 2026 than in 2024, and that trend is not reversing.
Book an upgrade assessment
Terracez works with enterprises in Saudi Arabia and the UAE to plan and deliver Dynamics 365 upgrades with a transformation-led, risk-first approach. Our upgrade assessments are designed to give CIOs, CFOs, and Transformation Directors the clarity they need to make a confident, well-governed decision.
In a Terracez upgrade assessment, you will receive:
- A clear view of your current-state complexity, legacy risk, and compliance exposure
- A realistic scope, timeline, and budget range based on your actual environment - not a generic estimate
- An honest readiness gap analysis covering data, integrations, governance, and internal ownership
- A recommended delivery approach aligned to your business priorities and risk tolerance
The assessment is not a sales process. It is a structured advisory engagement designed to reduce uncertainty before any programme commitment is made.
If you are evaluating a Dynamics 365 upgrade in Saudi Arabia or the UAE, contact Terracez to arrange an upgrade assessment. The conversation starts with your business, not a product pitch.
.webp)
