D365 Upgrade Risks That Most Partners Won't Tell You (And How to Avoid Them)

You have been running Dynamics AX 2012 for years. It works. Your team knows it. Your processes are built around it. And then someone - your IT director, your Microsoft account manager, or a partner who just walked in with a slide deck - tells you it is time to upgrade to Dynamics 365 Finance.

They are right, of course. AX 2012 R3 mainstream support ended in January 2023. Extended security patches are gone. Every month you stay on AX is a month of compounding technical debt, compliance exposure, and infrastructure risk.

But here is what most partners will not tell you: the upgrade itself is where the real risk lives. Not in the decision to move, but in how the move is executed - and specifically, in the gaps between what a partner promises in the sales process and what actually happens once the project starts.

This guide is written for IT directors and CIOs in the UAE and GCC who are evaluating an AX 2012 to D365 Finance upgrade. It covers the risks that rarely appear in a partner's proposal, the questions you should be asking before you sign anything, and the decisions that will determine whether your upgrade takes 32 days or 32 months.

The Upgrade vs Re-Implementation Decision Gets Made Too Quickly

The first risk is one that happens before the project even starts.

Most partners will frame the AX to D365 journey as an upgrade. It sounds cleaner, faster, and cheaper. But the honest answer is that whether you should upgrade or re-implement depends entirely on your customisation footprint - and many partners will not invest the time to tell you which path is right for you before they have your signature.

Here is the practical distinction:

A technical upgrade converts your existing AX database to Dynamics 365 Finance. Your historical data comes across. Your customisations are migrated. It is faster in theory, but only viable if your AX environment has limited custom code and your ISV solutions have D365-compatible versions.

A re-implementation starts fresh in D365 with clean configuration. Historical data is archived separately. Customisations are rebuilt or replaced with standard D365 functionality. It takes longer upfront but often produces a cleaner, more maintainable system - particularly for organisations that have spent years layering custom code onto AX.

The decision matters enormously for cost, timeline, and risk. Yet across the GCC, we regularly see organisations pushed toward the technical upgrade path because it is easier to sell - not because it is the right answer for their environment.

The question to ask your partner: Before you scope this as an upgrade or a re-implementation, have you completed a code upgrade estimation using LCS tools? What is the volume and complexity of our existing customisations, and how does that change the recommended path?

If they cannot answer that with data, they have not done the analysis.

Customisation Debt Is the Silent Budget Killer

The second risk is one that Dynamics AX clients in the UAE carry in disproportionate volume: customisation debt.

Over the typical AX 2012 lifecycle - often seven to ten years for GCC enterprises - organisations accumulate layers of custom development. Industry-specific modifications, localisation workarounds, integrations built before standard connectors existed, and reporting customisations that predate Power BI. Each one made sense at the time. Together, they create a system that is increasingly difficult and expensive to move.

According to industry data, over-customisation adds an average of $50,000 or more in unplanned costs to an upgrade project. That figure understates the real exposure for heavily customised AX environments, where the effort to analyse, migrate, and test custom code can consume 60 percent or more of total project effort.

The risk is not just cost. Every customisation you carry into D365 creates upgrade debt - ongoing maintenance burden, compatibility testing with every Microsoft update, and constraints on your ability to adopt new D365 capabilities cleanly.

A credible upgrade partner will conduct a thorough customisation analysis before scoping the project. They will identify which custom developments map to standard D365 functionality that now exists out of the box, which ones provide genuine competitive advantage and should be rebuilt, and which ones should simply be retired. Partners who skip this step are either inexperienced or are scoping the project to maximise billable development work.

What good looks like: A fit-gap analysis that actively challenges each customisation and recommends retiring or replacing the majority of them with standard D365 functionality.

UAE Compliance Requirements Get Discovered Mid-Project

This is the risk that is almost entirely absent from the content produced by global Dynamics partners - and it is acutely relevant for organisations operating in the UAE and GCC.

Dynamics 365 Finance is a global platform. It supports UAE VAT (5%), corporate tax (9%), and multi-entity reporting. But configuring it correctly for the UAE regulatory environment is not automatic. It requires specific knowledge of local requirements, and discovering gaps mid-project is one of the most expensive outcomes in an AX to D365 upgrade.

The compliance areas that most frequently surface as late-stage surprises include:

UAE corporate tax configuration. The UAE corporate tax regime, introduced in June 2023, has specific requirements around exempt income, qualifying group relief, and financial period alignment. D365 Finance supports these configurations, but they must be deliberately designed into the chart of accounts and financial dimension structure during the upgrade. Partners without recent UAE corporate tax implementation experience will not know what to look for.

ZATCA e-invoicing readiness. For organisations with operations or customers in Saudi Arabia, ZATCA Phase 2 e-invoicing compliance requires specific integration architecture within D365. This is not a post-go-live addition - it needs to be designed into the upgrade from the outset.

Wages Protection System (WPS) integration. WPS compliance for UAE payroll requires validated integration between D365 Human Resources or a connected payroll system and the SIF file format required by the Ministry of Human Resources. Partners who have not delivered UAE payroll implementations will treat this as an afterthought.

Multi-entity and free zone structures. Many UAE enterprises operate across mainland, free zone, and offshore entities with different VAT treatment, intercompany transaction requirements, and consolidated reporting needs. These structures need to be mapped and validated during design - not discovered during user acceptance testing.

The question to ask your partner: Can you walk us through how you have configured UAE corporate tax, VAT, and multi-entity reporting in a recent D365 Finance upgrade? Can you provide a reference client?

The Upgrade Assessment Itself Can Mislead You

Here is a risk that almost no partner content addresses: not all upgrade assessments are created equal.

The market for AX to D365 upgrade assessments in the UAE has expanded significantly. Most are offered free of charge, framed as a no-obligation starting point. Some are genuinely rigorous. Many are structured to produce a proposal, not an honest risk picture.

A surface-level assessment will review your AX version, count your customisations, and produce a timeline and cost estimate. It will not tell you that your financial dimension structure will require a full redesign. It will not flag that three of your ISV solutions have no D365 equivalent and will need to be rebuilt. It will not identify that your data quality issues will require six weeks of pre-migration cleansing before a single record can move.

A rigorous Dynamics 365 upgrade assessment should include:

• Code upgrade estimation using Microsoft's LCS Code Upgrade service, producing an actual line count of customisations requiring migration

• ISV and integration analysis confirming D365-compatible versions or identifying rebuild requirements

• Data quality assessment identifying cleansing requirements before migration begins

• UAE compliance gap analysis covering VAT, corporate tax, WPS, and entity structure

• A clear recommendation on upgrade vs re-implementation with supporting rationale

• A realistic timeline based on your customisation volume, not a generic benchmark

The deliverable that matters most is not the timeline or the cost estimate. It is the risk register - a documented list of the issues that could derail the project, with a clear plan for how each one will be managed.

If an assessment does not produce a risk register, it has not done its job.

Go-Live Risk Is Consistently Underestimated

According to Panorama Consulting's 2025 ERP Report, 71 percent of Dynamics 365 projects experience budget overruns and 65 percent run behind schedule. The majority of those delays trace to the final phase of the project - the cutover and go-live period.

D365 go-live risk is distinct from implementation risk. It is the risk that accumulates in the weeks before and immediately after the system goes live, and it is where poorly managed upgrades collapse.

The specific failure points that most partners underplay:

Cutover planning. A D365 Finance upgrade requires multiple mock cutovers - industry best practice is two to three - before the production cutover. Each mock cutover identifies data migration issues, integration failures, and process gaps under realistic conditions. Partners who plan a single cutover rehearsal are cutting corners that will cost you at go-live.

Hypercare gaps. The period immediately after go-live is when your team is most vulnerable. Processes that worked in testing behave differently with live data volumes. Users who completed training two weeks ago are now working in a live system under time pressure. A credible partner will commit to a structured hypercare period - typically 30 to 90 days - with named support resources, defined SLAs, and daily stand-ups during the first two weeks.

Licence cost surprises. The transition from AX 2012 on-premises licensing to D365 cloud subscription licensing is not straightforward. User licence types in D365 Finance - Full User, Team Member, Activity - map differently to your AX user base than most partners will explain upfront. Discovering mid-project that your licence costs are 40 percent higher than estimated is not uncommon.

Evergreen update management. D365 Finance is an evergreen platform - Microsoft releases two major updates per year, with continuous minor updates. Unlike AX, you cannot defer these indefinitely. Your partner should be explaining how update management works and what it means for your customisations from day one of the project, not after go-live.

What a 32-Day AX 2012 R3 to D365 Finance Upgrade Actually Looks Like

Theory is useful. A real example is more useful.

Terracez recently completed an AX 2012 R3 to D365 Finance upgrade for a PIF-backed company in Riyadh in 32 days. That timeline is significantly faster than the industry average, and it was achievable because of decisions made before the project started - not during it.

The factors that made it possible:

A rigorous pre-upgrade assessment identified the customisation footprint accurately. The majority of custom developments mapped to standard D365 functionality, reducing the migration workload substantially. The assessment also confirmed that a technical upgrade was the right path - the client's AX environment was relatively clean, and historical data migration was a business requirement.

Compliance requirements were scoped upfront. ZATCA readiness, entity structure, and reporting requirements were mapped during the assessment phase, not discovered during UAT.

Data cleansing was completed before the project clock started. Three mock cutovers were completed before production go-live, each identifying and resolving issues that would otherwise have surfaced on go-live day.

The result was a go-live with no critical post-launch issues and a structured hypercare period that closed within two weeks.

The 32-day timeline was not the goal. The goal was a clean, compliant, well-adopted system. The timeline was the outcome of doing the preparation work properly.

The Dynamics 365 Finance Upgrade Checklist: What to Verify Before You Sign

Before committing to an upgrade partner or approving a project scope, verify the following:

Assessment quality

• Has a code upgrade estimation been completed using LCS tools?

• Has an ISV and integration compatibility analysis been completed?

• Has a data quality assessment been completed with a cleansing plan?

• Has a UAE compliance gap analysis been completed covering VAT, corporate tax, WPS, and entity structure?

• Does the assessment include a risk register, not just a timeline and cost?

Partner capability

• Can the partner provide references for AX 2012 to D365 Finance upgrades completed in the UAE or GCC?

• Has the delivery team - not just the sales team - been introduced and confirmed?

• Does the partner have demonstrated UAE corporate tax and VAT configuration experience?

Project structure

• Is the upgrade vs re-implementation decision based on data from the assessment?

• Are two to three mock cutovers included in the project plan?

• Is a structured hypercare period included with defined SLAs and named resources?

• Has the licence transition been modelled accurately against your current user base?

• Has evergreen update management been explained and planned for?

If you cannot answer yes to each of these, you have identified the gaps that are most likely to cost you.

Where to Start

The single most important decision in an AX 2012 to D365 upgrade is not which partner you choose. It is whether you start with a rigorous assessment or a proposal.

A proposal tells you what a partner wants to sell you. A rigorous assessment tells you what your upgrade actually involves - the customisation volume, the compliance requirements, the data quality gaps, and the realistic timeline and cost.

Terracez offers a structured Dynamics 365 upgrade assessment for AX 2012 environments in the UAE and GCC. The assessment covers code upgrade estimation, ISV and integration analysis, UAE compliance gap analysis, data quality review, and a risk register. It is the starting point we use before every upgrade engagement, and it is what produced the 32-day delivery for our client in Riyadh.

‍