LHDN e-Invoice Phase 4 is LIVE — All Malaysian businesses must comply. Check your compliance →
ERP Upgrade & System Migration

Move off AX 2009, AX 2012, or On-Premise NAV — Without Losing What Already Works.

Your AX or NAV system has carried the business for a decade. The customisations are real. The integrations are load-bearing. The data has 15 years of history that the auditor needs intact. Daxonet upgrades AX 2009, AX 2012, and on-premise NAV to D365 Finance & Operations and Business Central with a Microsoft FastTrack-aligned methodology, a trial-balance-reconciled data migration, and a phased path that protects your operations through every cutover weekend.

Book an Upgrade Assessment Talk to an Upgrade Lead
AX 2009 / 2012 → D365 F&O On-prem NAV → Business Central Microsoft FastTrack-aligned Reconciled to trial-balance

Daxonet upgrades Microsoft Dynamics AX 2009 and AX 2012 to D365 Finance & Operations, and on-premise Dynamics NAV to D365 Business Central, for Malaysian and ASEAN enterprises. Engagements are Microsoft FastTrack-aligned and run on Lifecycle Services with Azure DevOps as the system of record. Data migration is profiled, cleansed, transformed, validated, and reconciled to the trial balance before cutover — typically across a single weekend with parallel-run support.

Upgrade Paths

Three upgrade paths, scoped to where you are starting from.

The right path depends on your current platform, customisation depth, and target operating model. Daxonet maps each path with the same rigour, regardless of the size of the engagement.

Path 1

AX 2009 / AX 2012 → D365 Finance & Operations

For Malaysian and ASEAN enterprises running AX 2009 or AX 2012 (R2 or R3). Out of mainstream and extended support. Treated as a re-implementation with structured data migration — not a binary lift.

  • → Customisation retire-replace-rebuild-defer matrix
  • → X++ to Extensions modernisation
  • → Microsoft FastTrack engagement
  • → Trial-balance-reconciled cutover
Path 2

On-Premise NAV → Dynamics 365 Business Central

For SMEs and mid-market enterprises running NAV 2013, 2015, 2016, 2017, or 2018 on-premise. Two-wave path: technical upgrade with C/AL to AL conversion, then a deliberate cloud vs. on-premise decision.

  • → C/AL to AL extension conversion
  • → ISV and add-on compatibility audit
  • → Cloud vs. on-prem decision support
  • → Power Platform replaces brittle customisations
Path 3

Other Legacy Platform → D365 (Replatform)

For enterprises on legacy SAP, Oracle E-Business Suite, Sage, or in-house developed ERPs deciding to move to the Microsoft stack. Full re-implementation with structured legacy data migration into Azure data lake.

  • → Platform fit-gap and TCO modelling
  • → Integration map and successor design
  • → Phased entity-by-entity rollout
  • → Historical archive to Azure Data Lake

Why Now

The cost of staying on AX or on-prem NAV is no longer hidden.

Each of these costs was tolerable individually. Together, they are the reason finance leaders are making the upgrade decision in 2026 rather than 2028.

No More Security Patches

AX 2009 has been out of support since 2018; AX 2012 R3 since 2022. Every CVE since is unpatched. Your insurance and audit posture grows weaker each year.

Compliance Drift

e-Invoice, SST changes, transfer pricing, IFRS updates. Each one bolts another patch onto an unsupported customisation. The bolt-ons are now older than some of the consultants maintaining them.

Vanishing Skills Pool

Consultants who can productively work in X++ on AX 2012, or C/AL on NAV 2016, are retiring or moving to D365. The day rate to keep your legacy alive is rising faster than the day rate to migrate off it.

No AI / Copilot Roadmap

Microsoft's investment is in D365 + Copilot. Every quarter, the gap between what your finance team could be doing and what they actually do widens. AX and NAV on-prem are not on the roadmap.

Hidden Hosting & Hardware Costs

Server refresh cycles, SQL Server licensing, DR site, backup tapes, the air-conditioned room nobody enters. Most legacy ERP TCO is invisible until the upgrade business case forces it into the open.

Reporting You Cannot Modernise

Power BI, Microsoft Fabric, real-time dashboards. Every modernisation request stops at the AX/NAV data layer. The board increasingly notices the lag between "what happened" and "what we can see".

Methodology · FastTrack-Aligned

Five phases tuned for upgrade — not a rebadged implementation playbook.

The five phases mirror Microsoft's Success-by-Design framework but with explicit upgrade-specific deliverables: customisation matrix, data quality assessment, mock cutovers, and trial-balance reconciliation.

  1. 01

    Assess

    Current-state audit of AX/NAV: versions, customisations, integrations, data quality, license posture, ISV add-ons.

    Output: Upgrade Readiness Report, three-option recommendation

  2. 02

    Design

    Solution Blueprint for D365 / BC, customisation retire-replace-rebuild-defer matrix, integration successor design, data migration strategy.

    Output: Solution Blueprint, customisation matrix

  3. 03

    Build & Migrate

    Configuration, extension development, integration build, repeated data migration cycles. The Build phase always overlaps with at least two mock data migrations.

    Output: Configured tenant, two passed mocks

  4. 04

    Cutover

    Final mock cutover, formal Microsoft Solution Assessment, then the live cutover weekend. Every cutover step has a tested rollback. Trial-balance reconciliation closes the weekend.

    Output: Live tenant, signed reconciliation report

  5. 05

    Stabilise

    Hypercare, first month-end close on D365 / BC, performance tuning, knowledge transfer, transition to Managed Services. Legacy AX/NAV moves to read-only archive mode.

    Output: Stabilised production, AX/NAV archive plan

Data Migration · Trial-Balance Reconciled

The workstream that decides whether your auditor signs.

Most upgrade failures we are asked to recover come back to data migration. The configuration was fine. The training was adequate. The cutover weekend went over plan because the closing trial balance in D365 did not match the closing trial balance in AX — and the team improvised reconciling adjustments under time pressure.

Daxonet's data migration is treated as a programme of its own, with three mock cutovers before the live cutover. By the live weekend, the reconciliation is rehearsed, not improvised.

1 Profile & Catalogue

Every entity, every field, every reference data list. Quality issues identified and tagged: orphaned records, duplicate masters, incomplete dimensions, unposted transactions.

2 Cleanse & Transform

Cleansing rules executed in a staging warehouse, never directly into production. Business owners review master data before transformation. Reference data harmonised against the new D365 design.

3 Validate & Reconcile

Trial balance, AR ageing, AP ageing, inventory valuation, fixed assets — reconciled to the cent. Three mock cutovers, each producing a published reconciliation report that owners and auditors review.

4 Cutover & Archive

Live cutover across a single weekend, with parallel-run support. Legacy historical data parked in Azure Data Lake or read-only AX/NAV environment. Auditor receives the final reconciliation report.

What You Inherit on Day One

The seven things that change the moment you go live on D365 or BC.

Each of these was a multi-month wishlist item on AX or NAV. On D365 and Business Central, they are standard. The upgrade is the moment they become available to your finance and operations teams.

Microsoft Copilot embedded across Finance, SCM, and CRM
Copilot summarises overdue invoices, drafts customer collection emails, suggests journal entries from supplier bills, and answers natural-language queries against finance data. On AX 2012, this is a six-month custom build. On D365, it ships standard.
Power BI native, with a real-time data warehouse behind it
Embedded Power BI workspaces pre-wired to D365's data foundation. The "we cannot get a board pack until five working days after month-end" problem stops being a technology problem.
Power Platform extensibility instead of X++ or C/AL
Most customisations that earned their keep on AX or NAV can be rebuilt as Power Apps and Power Automate flows. Lower cost to maintain, easier to recruit for, and not bound to your ERP upgrade cycle.
Continuous compliance updates without dealer-led upgrade projects
Malaysian e-Invoice, SST changes, IFRS updates, and statutory reporting changes ship as platform updates, not as customisation rework projects you pay for line-by-line.
Native Microsoft 365 and Teams integration
Approvals in Teams, financial reports in Excel with live D365 connections, customer cases in Outlook. The integration that took six weeks to mock up on AX is standard out of the box.
Modern security with Entra ID, MFA, and conditional access
Enterprise identity, role-based security, and audit trails aligned to current ISO 27001 and SOC 2 expectations. Your CISO gets to retire a long list of compensating controls.
Predictable platform updates instead of multi-year version skips
D365 and BC ship two major releases a year, governed by a published roadmap. You stop paying for forklift upgrades. You start receiving improvements the way every other modern SaaS platform delivers them.
Why Daxonet

The upgrade partner that has done this before — including when it went wrong elsewhere.

Daxonet has been delivering Microsoft Dynamics across Malaysian and ASEAN enterprises for over a decade — through AX 2009, AX 2012, NAV, and now D365 and Business Central. The same team that knows your legacy platform inside out is the team rebuilding you on the new one.

  • ✓   Microsoft Solutions Partner — Business Applications
  • ✓   FastTrack-aligned delivery on every qualifying upgrade
  • ✓   Trial-balance reconciliation as a programme deliverable, not an afterthought
  • ✓   Recovery-capable: we have rebuilt stalled upgrades from other partners
  • ✓   Single accountable principal from kickoff to stabilisation
  • ✓   Trilingual delivery for ASEAN multi-country rollouts
Get In Touch

Daxonet Group Sdn Bhd

Petaling Jaya HQ · Selangor, Malaysia

Johor Bahru Office · Johor, Malaysia

Phone · +603-9212 8336
Email · sales@daxonet.com

Assessment format: 2 to 4 weeks. We document current state, cost three options (salvage / pivot / replatform), and present a phased migration plan with explicit assumptions before you commit.

Book an Upgrade Assessment
Related Services

Services that wrap around an upgrade.

Implementation & Rollout

Greenfield D365 and Business Central rollouts, Success-by-Design.

Consulting

Upgrade readiness assessments, fit-gap analysis, transformation roadmaps.

Managed Services

Tiered SLA support after go-live with quarterly reviews.

Data & Analytics

Microsoft Fabric, Power BI, archive lake design for legacy history.
FAQ

Questions IT and finance leaders ask before kicking off an upgrade.

Why should we upgrade off AX 2009 or AX 2012 now?
AX 2009 mainstream support ended in 2018; extended support ended in 2021 for AX 2012 R2 and 2022 for AX 2012 R3. There are no further security or regulatory updates from Microsoft. Every Windows Server upgrade is now an unsupported risk. Customisations made for legacy regulatory regimes are diverging from current Malaysian compliance requirements (e-Invoice, SST, transfer-pricing). Beyond compliance, the business case is straightforward: the cost of carrying an unsupported ERP — third-party patches, security exposure, audit findings, and the inability to recruit new functional consultants — typically exceeds a phased migration to D365 within 18 to 24 months.
Is the AX 2012 to D365 Finance migration really a 'lift and shift', or do we have to redesign?
It is closer to a redesign than a lift-and-shift, and any partner who tells you otherwise has not delivered enough of these. D365 Finance & Operations is the cloud successor to AX 2012, but the data model, the customisation extensibility model (Extensions instead of Overlayering), the security architecture, and the reporting platform have all changed. Daxonet runs every AX → D365 engagement as a re-implementation with data migration — never as a binary code lift. You will get to retire the customisations you have outgrown, modernise the integrations, and inherit the design discipline of a current Microsoft platform.
How does the on-premise NAV to Business Central upgrade work?
On-premise Dynamics NAV (versions 2013 through 2018) upgrades to Business Central via a structured path that depends on your starting version, the complexity of your customisations, and whether you are moving to Business Central online (cloud) or on-premise. Daxonet typically moves customers in two waves: first, technical upgrade from NAV to a current Business Central on-premise version with extensions converted from C/AL to AL; second, evaluation of cloud vs. on-premise based on your data residency, integration footprint, and licensing economics. Most Malaysian SME and mid-market customers land on Business Central online for the operating cost savings — but we will tell you honestly when on-premise is still the right call.
What happens to our AX customisations during the upgrade?
Every customisation gets one of four verdicts during the upgrade design phase. Retire — the requirement is now standard in D365. Replace — the requirement still exists but the customisation is no longer the right shape (often replaced by Power Platform low-code instead of X++ rebuild). Rebuild — the requirement is genuinely unique and gets rebuilt as a supported D365 Extension. Defer — the requirement is real but not Phase 1; logged in the backlog and revisited after stabilisation. The retire-replace-rebuild-defer matrix is the single most important deliverable from the upgrade design phase. Most projects we recover failed because this work was skipped.
How do you handle 15 years of historical data?
Honestly, by design. Most enterprises do not need 15 years of fully active transactional data in the new system — they need confident access to it. Daxonet's standard pattern: migrate open balances, open transactions, master data, and 1-2 years of closed history into D365 (the operational data set); preserve the full historical archive in an Azure data lake or read-only AX environment with a defined retention policy aligned to your statutory requirements (typically 7 years for Malaysian tax purposes). This keeps D365 fast, keeps the audit trail intact, and reduces the migration effort by an order of magnitude versus a full-history move.
Can we phase the upgrade by legal entity or business unit?
Yes — and for multi-entity groups, we strongly recommend it. Phasing by legal entity (one entity goes live on D365 while others remain on AX) requires a co-existence integration layer for intercompany transactions and consolidated reporting; Daxonet builds this with Azure-native integration patterns. Phasing by business unit (warehouse, sales region, manufacturing site) within a single entity is also viable but technically harder. We recommend whichever phasing minimises business disruption while keeping the total programme under 18 months — beyond that, sustained dual-running becomes its own risk.
How long does an AX 2012 to D365 F&O upgrade take?
For a single legal entity with moderate customisation, plan 9 to 14 months from kickoff to go-live. Multi-entity groups in a phased rollout typically run 14 to 24 months total, with each entity going live every 4 to 6 months after the first. The dominant variables are customisation count, integration count, data volume, and the speed of business-side decisions on retire-replace-rebuild-defer. Daxonet does not quote 6-month upgrades for AX 2012 — that timeline is only realistic if you are content to lose customisations the business will miss in the first month.
What about NAV 2009 or older — is upgrade still possible?
Yes, but the path is different. NAV 2009 and earlier require a multi-step technical upgrade through intermediate NAV versions before the AL conversion to Business Central. For most clients on NAV 2009 or earlier, Daxonet recommends a re-implementation of Business Central instead — same outcome, lower risk, faster timeline, and you inherit current best-practice configuration rather than 15-year-old design decisions. We will model both paths in the upgrade assessment and recommend honestly.
Will Microsoft FastTrack be involved?
Daxonet works hand-in-hand with Microsoft FastTrack on every qualifying engagement — Solution Blueprint review, Solution Assessment review, and go-live readiness review are formal milestones in our delivery plan. For Business Central engagements, FastTrack involvement is lighter but the same Success-by-Design framework applies. The FastTrack partnership gives you an independent quality gate at Microsoft's expense — a meaningful risk reducer for the board.
What does 'reconciled to the trial balance' actually mean for data migration?
It means that on cutover day, the D365 trial balance for every legal entity matches the AX or NAV closing trial balance to the cent — and we have a published reconciliation report that proves it. This is non-negotiable for audit-ready cutover. The reconciliation report covers GL by account, AR by customer, AP by vendor, inventory by item and location, and fixed assets by asset. We run this reconciliation in three mock cutovers before the live cutover, so the live weekend is rehearsed, not improvised.
Ready to Move Off Legacy?

Don't wait for the next failed Windows update to force the conversation.

Book a Daxonet upgrade assessment. We map your current state — versions, customisations, integrations, data quality, license posture — and produce a phased migration plan with three options costed and timed before you commit to any.

Book an Upgrade Assessment +603-9212 8336
Hi! What can I do for you?
DAX AI Assistant · Online now