Before examining how upgrades are delivered, it is worth understanding why the urgency of upgrading has increased significantly in 2026.
Microsoft Dynamics AX 2012 mainstream support ended in October 2021. Extended support ends in January 2023. Organisations still running AX 2012 in 2026 are operating on a platform that receives no security updates, no feature development, and no regulatory compliance updates - including ZATCA e-invoicing requirements that are now mandatory for most Saudi businesses. Every month on AX 2012 in the current environment is a compounding compliance and security liability.
Microsoft Dynamics NAV mainstream support has ended across all versions prior to NAV 2018. NAV 2018 extended support ends in January 2028 - but organisations waiting until 2027 to begin their upgrade will be competing for partner capacity at exactly the moment when demand peaks. Starting now means access to the best partners, the most experienced consultants, and the least compressed timelines.
The 2026 Release Wave 1 introduces agentic ERP capabilities - autonomous AI agents across Finance, Supply Chain, Sales, and HR - that are only available on current Dynamics 365 cloud instances. Organisations on legacy on-premise versions cannot access these capabilities at all. The competitive gap between organisations on current D365 and those on legacy Dynamics versions is widening with every release wave.
ZATCA Phase 2 e-invoicing compliance is now mandatory for Saudi businesses with VAT revenues above SAR 375,000. Configuring FATOORA API integration, CSID digital signing, and QR code generation is only possible on a current D365 Finance instance. Organisations on AX 2012 or NAV cannot achieve ZATCA Phase 2 compliance without upgrading first.
The cost of delay is no longer theoretical. It is a measurable, compounding liability - in compliance risk, security exposure, and competitive capability.
What a Dynamics 365 Upgrade Actually Involves
The word "upgrade" is used loosely in the market. Before evaluating timelines and providers, it helps to understand what a D365 upgrade actually comprises - because the scope varies significantly depending on your starting point.
Legacy platform migration (AX 2012 or NAV to D365) is the most complex upgrade type. It involves moving from an on-premise, heavily customised legacy system to a cloud-native D365 instance. The work includes code analysis and remediation, data migration and cleansing, integration redevelopment (because legacy integrations rarely translate directly to the D365 architecture), ZATCA and VAT configuration for Saudi and UAE clients, Arabic localisation, and user acceptance testing. This is the upgrade type where the 31-day delivery story is most relevant - and most surprising to the market.
Version-to-version cloud updates are less complex. If you are already on D365 cloud and need to move from an older release to the current wave, the work is primarily configuration validation, customisation compatibility testing, and regression testing. These should take weeks, not months - and if your partner is quoting months for a cloud-to-cloud update, that is a methodology problem, not a complexity problem.
Module additions to an existing D365 environment - adding Supply Chain Management to a Finance-only instance, or adding Sales to a Business Central deployment - are scoped separately and should not be conflated with a full upgrade. These are enhancement projects, not migrations.
Understanding which of these three categories your project falls into is the first step in evaluating whether a quoted timeline is realistic or inflated.
The 31-Day Upgrade: What Made It Possible
The 31-day AX 2012 to D365 Finance and Operations upgrade Terracez delivered for a Saudi Recycle and Waste Management client is not a marketing claim. It is a documented delivery outcome. Understanding what enabled it reveals the variables that determine upgrade speed for any organisation.
The client completed Alignyx before the project began.
Alignyx - Terracez's AI-enabled ERP readiness and governance assessment - was run in the weeks before the upgrade engagement started. It evaluated the client's process maturity, data quality, and stakeholder alignment, and produced a risk heatmap that identified exactly where the upgrade would encounter friction and where it would not.
The result was that when the project kicked off, there were no discovery surprises. The scope was defined before day one. The data migration plan was pre-validated. The stakeholders were aligned on go-live criteria. The ZATCA compliance requirements were mapped into the configuration plan before a single line of code was written.
This is the single most important variable in upgrade speed. Organisations that begin upgrades without a completed readiness assessment spend the first 4-8 weeks of their project doing the discovery work that should have been done before the engagement started. That is where most of the "standard" 3-6 month timeline goes - not into the upgrade itself, but into the preparation that should have preceded it.
The customisation footprint was rationalised before migration.
One of the most time-consuming elements of any AX 2012 migration is the customisation inventory. AX 2012 implementations typically accumulate years of custom code - workarounds, bespoke reports, non-standard integrations - much of which is no longer used or no longer necessary because D365 natively supports the underlying requirement.
The Alignyx assessment identified which customisations were actively used, which could be retired, and which genuinely needed to be rebuilt in the D365 architecture. The client entered the upgrade with a clean, rationalised customisation scope rather than a full inventory of legacy code to migrate. This alone removed weeks from the technical delivery timeline.
Data was cleansed before migration, not during it.
Data migration is the most common cause of upgrade delay. Organisations that begin data migration without a prior data quality audit discover inconsistencies, duplicates, and missing values during the migration process - when the pressure of a go-live deadline makes remediation expensive and stressful.
The Alignyx assessment included a data quality evaluation that identified the specific remediation required before migration began. The client's data arrived at the migration phase in a state that could be processed cleanly, without the iterative cleansing cycles that extend most upgrade timelines by weeks.
Stakeholder alignment was achieved before configuration began.
The second most common cause of upgrade delay is requirement changes mid-project - when department heads who were not engaged during scoping raise new requirements once they see the system being configured. This is not a technical problem. It is a governance problem.
The Alignyx process includes a structured stakeholder alignment exercise that brings finance, operations, IT, and commercial leadership into agreement on scope, priorities, and go-live criteria before the implementation partner begins work. When everyone is aligned on what the upgrade is delivering and what it is not, there are no mid-project escalations to resolve.
The delivery team was experienced in Saudi-specific requirements.
ZATCA configuration, Arabic localisation, Hijri calendar support, and bilingual document design are not optional extras for a Saudi client - they are core requirements that must be built into the configuration from day one. A delivery team that has completed these requirements multiple times for Saudi clients does not need to research or learn them during the project. That expertise compresses delivery time significantly compared to a team encountering Saudi-specific requirements for the first time.
What Slows Most Upgrades Down
Understanding the 31-day delivery is more useful when set against the reasons most upgrades take far longer. These are the variables that inflate timelines - and the ones that Alignyx is specifically designed to resolve before they become expensive.
Undefined scope at project start. When the upgrade scope is not fully defined before the engagement begins, the first phase of the project becomes a paid discovery exercise. Every week spent defining requirements during the project is a week that could have been spent delivering the upgrade.
Legacy customisation debt. AX 2012 and NAV implementations that have been running for 5-10 years typically carry significant customisation debt - code that was written for requirements that no longer exist, integrations that connect to systems that have been retired, and reports that duplicate functionality now available natively in D365. Migrating this code without first rationalising it adds weeks of technical work for zero business value.
Poor data quality discovered during migration. The most reliable predictor of upgrade delay is the state of master data at the point migration begins. Customer records with missing fields, vendor accounts with duplicate entries, item masters with inconsistent unit-of-measure configurations - all of these create migration exceptions that must be resolved manually, one by one, under go-live pressure.
Stakeholder misalignment surfacing mid-project. When the finance director and the operations director have different views of what the upgraded system should do, and those differences are not resolved before configuration begins, they surface as change requests during UAT - at the most expensive point in the project to make changes.
Partner unfamiliarity with local requirements. For Saudi and UAE clients, ZATCA, VAT, Arabic localisation, and Nitaqat are non-negotiable configuration requirements. A partner who has not delivered these requirements multiple times will spend time during the project learning them - and that learning time is billed to the client.
How to Evaluate Whether Your Organisation Can Move at Speed
Not every organisation is positioned to deliver a 31-day upgrade. The variables that enabled it for the Saudi client are specific and replicable - but they require preparation. Here is a self-assessment framework.
Readiness Variable
Ready to Move Fast
Remediation Needed First
Process documentation
Processes are mapped and owned
Processes are informal or undocumented
Data quality
Master data has been audited recently
Data quality is unknown or known to be poor
Customisation inventory
Legacy customisations are catalogued and rationalised
Customisation scope is unknown
Stakeholder alignment
Leadership is aligned on scope and go-live criteria
Stakeholders have not been engaged on upgrade scope
Compliance readiness (KSA)
ZATCA, VAT, and localisation requirements are mapped
Compliance requirements have not been assessed
Internal project resource
A dedicated project owner is identified and available
Project ownership is unclear or shared with other priorities
Organisations that score "ready" across all six variables are positioned to deliver an accelerated upgrade. Those with remediation gaps in two or more areas should expect a longer timeline - not because the upgrade itself is complex, but because the preparation work needs to happen before or alongside it.
What to Demand from a D365 Upgrade Provider in 2026
The market for D365 upgrade services has matured significantly. Organisations evaluating providers in 2026 should hold them to a higher standard than the generic criteria that circulate in most evaluation guides.
Demand a readiness assessment before a scoped proposal. Any provider who produces a fixed-price upgrade proposal without first assessing your process maturity, data quality, and customisation inventory is guessing at the scope. The proposal will either be inflated to cover unknown risk, or it will be underscoped and grow during delivery. A provider who insists on a readiness assessment before scoping is protecting both parties.
Ask for a customisation rationalisation methodology. How does the provider decide which legacy customisations to migrate, which to retire, and which to rebuild natively? A provider without a clear answer to this question will migrate everything - including the code that should be retired - and charge you for the privilege.
Ask for a data migration validation process. When does data quality assessment happen in their methodology - before migration begins, or during it? The answer tells you whether data surprises will delay your go-live or whether they have been resolved in advance.
Ask for Saudi-specific delivery evidence, not Saudi-specific marketing. Can they show you a completed ZATCA Phase 2 integration? Can they demonstrate a live bilingual D365 Finance environment? Can they name a Saudi client who will take a reference call? Claims are easy. Evidence is not.
Ask directly: "What is the fastest you have delivered an upgrade of this type, and what made it possible?" A provider who can answer this question with specifics - as Terracez can, with the 31-day Saudi delivery - has a track record that generic marketing cannot replicate. A provider who responds with a range and a methodology slide has not delivered at speed before.
The Upgrade Timeline Comparison
To contextualise what accelerated delivery actually looks like, here is how timeline variables compound across different upgrade profiles.
Upgrade Type
Industry Average
With Alignyx Pre-Assessment
Key Accelerator
AX 2012 to D365 Finance (mid-market, KSA)
4-6 months
4-8 weeks
Readiness-first, rationalised customisations
NAV to Business Central (SME, UAE)
3-4 months
3-6 weeks
Clean data, standard configuration
D365 cloud version update
4-8 weeks
1-2 weeks
Compatibility pre-validated
Module addition to existing D365
6-10 weeks
2-4 weeks
Scoped against existing architecture
The Alignyx pre-assessment does not change the technical work required. It changes when that work happens - moving discovery, data remediation, and stakeholder alignment from the billable project phase into the pre-project phase, where it is faster, cheaper, and less disruptive.
The 31-day Saudi upgrade was not an accident. It was the outcome of a structured preparation process that resolved every variable that typically delays an upgrade before the project clock started.
Alignyx is the tool that makes that preparation structured, objective, and fast.
Terracez's complimentary AI-enabled ERP readiness and governance assessment evaluates your upgrade readiness across six dimensions - process maturity, data quality, customisation inventory, stakeholder alignment, compliance obligations, and internal resource capacity. The output is a risk heatmap and executive dashboard that tells you exactly where you are ready to move at speed and where remediation is needed first.
For Saudi clients, Alignyx maps your ZATCA compliance status, VAT configuration requirements, and Arabic localisation obligations into the readiness picture - so the upgrade scope includes every compliance requirement from day one, rather than discovering them mid-project.
The output is not a generic report. It is a fixed-price upgrade proposal scoped to your actual situation - with a timeline that reflects your real readiness, not an industry average.
Over 100 Dynamics 365 projects delivered across the GCC. The only Microsoft Catalyst partner executing locally in the region. A documented 31-day upgrade delivery for a Saudi
.webp)
