Solutions · Microsoft Dynamics AX (Legacy)

Keep your AX 2009 or AX 2012 stable. Move to D365 on your own timeline.

Microsoft Dynamics AX is the on-premise ERP that thousands of Malaysian enterprises still run for finance, supply chain, manufacturing and project accounting. Mainstream support for AX 2012 has ended, but your investment does not have to. Daxonet keeps your AX environment performing, patched and audit-ready, then migrates you to D365 in a structured, parallel-running upgrade for Panasonic, Novelis, Raco Industries and Sorento, with Phase 1 D365 go-live in 4 to 6 months, not 18.

Book a Free AX Health Check → Talk to a D365 Architect

AX 2009 + AX 2012 support
SLA-backed managed service
Phase 1 D365 in 4–6 months
Microsoft Solutions Partner

Trusted by Malaysian enterprises

Who has Daxonet already taken live on D365?

Microsoft Dynamics AX is the on-premise ERP from Microsoft for finance, supply chain, manufacturing and project accounting, that ran as the enterprise tier of the Dynamics line until D365 Finance and D365 Supply Chain Management took over. AX 2009 and AX 2012 are still in production at many Malaysian manufacturers and distributors, but mainstream Microsoft support for AX 2012 ended in October 2021 and extended support ended in January 2023, which means new security patches, statutory updates and regulator changes (SST, MFRS, LHDN MyInvois) are now the responsibility of the implementation partner, not Microsoft. Daxonet, a Microsoft Solutions Partner with 10+ years on AX and D365 and 47 ERP rollouts across Malaysia and ASEAN, keeps Malaysian AX environments stable, patched, performance-tuned and audit-ready under SLA-backed managed-service contracts, and runs structured AX 2009 and AX 2012 to D365 migrations with parallel-running discipline so AX stays the system of record until finance signs off the cutover. Phase 1 D365 go-live runs 4 to 6 months from AX 2012 (5 to 7 months from AX 2009), at reference customers including Panasonic, Novelis, Raco Industries and Sorento.

The AX 2026 reality

Why does running AX in 2026 quietly grow your audit and security risk?

Three risks show up in every Malaysian AX environment we audit. They compound quietly until an external event forces a decision.

3 risks compounding · daily

01 · Security

Patch window has closed

Microsoft mainstream support ended Jan 2023. Critical security updates no longer ship to AX 2012. Every CVE accumulates as exposure on your perimeter.

02 · Compliance

Auditors flag legacy

External auditors increasingly mark unsupported ERPs as a material weakness. PDPA, MFRS, MyInvois changes have to be patched manually by the partner, not by Microsoft.

03 · Cost

TCO drifts upward

Hardware refreshes, SQL Server upgrades, X++ developer scarcity, and shrinking partner pool quietly raise your AX run-rate every year. No replatforming bonus is coming.

Stay on AX vs Migrate to D365

What does each path actually look like over the next three years?

Daxonet supports both paths. Here is the honest comparison we walk Malaysian CFOs through during the AX Health Check.

Dimension

Path A

Stay on AX 2012

Daxonet pick

Path B

Migrate to D365

Microsoft support

Out of mainstream support

Active, with Copilot AI shipping

Security patches

Custom partner-supplied only

Native Microsoft pipeline

LHDN MyInvois

Bridge middleware required

Native MyInvois integration

AI / Copilot

Not available

Embedded across finance + SCM

Infrastructure

On-prem servers + DBA team

Microsoft Cloud, no infra capex

X++ developer scarcity

Shrinking partner bench

Power Platform extends without X++

5-year TCO

Drifts up · 8–12% CAGR

30–45% lower than tier-1 SAP

Capability 01 · AX managed service

What Daxonet does to keep AX stable, patched and audit-ready.

Three service tracks under one SLA, running across both AX 2009 and AX 2012 environments in Malaysia.

Track 01 · Health

Performance + uptime, on SLA

24×7 monitoring of AX, SQL Server, AOS and the integration layer. Tier-1 to Tier-3 escalation. Quarterly performance reviews. Capacity planning so AX still hits month-end without surprise overnight runs.

SLA · 99.5% uptime · 4-hour response on Sev 1

Daxonet engineer monitoring an AX server environment

AX 2012 environment monitoring dashboard with compliance status indicators

Track 02 · Patches + compliance

Statutory + security, kept current

Custom security patching against post-mainstream CVEs. SST and MFRS regulatory updates. PDPA controls reviewed annually. MyInvois bridge maintained for AX. The platform stays operable, the audit trail stays clean.

Coverage · SST · MFRS · PDPA · MyInvois bridge

Track 03 · Customisation

X++ code maintained, documented, ready to migrate

Every X++ object catalogued. Customisations classified as keep, replace with config, rebuild as Power Platform, or rebuild in D365. The migration playbook starts the day Track 03 starts, even if you have no migration date yet.

Inventory · classified · costed · migration-ready

Daxonet developer maintaining X++ customisations on AX 2012

Capability 02 · The migration playbook

Will every AX customisation make it across to D365 cleanly?

The playbook covers every layer your team will ask about: data, code, integrations, statutory, and the cutover weekend. Click any row to open it.

Data migration · master + transactional

Chart of accounts, dimensions, items, BOMs, routings, customers, vendors and open transactions migrated from AX to D365 with reconciliation runs back to AX before go-live. Historical balances kept for audit. Two formal data-migration cycles are standard.

Coverage · COA · items · BOMs · routings · open AR · open AP · WIP · history

X++ code · classified, replaced, rebuilt

Every X++ object catalogued in the AX Health Check. Each object is classified as keep-as-config (replaced by D365 platform configuration), Power Platform extension, Azure function, or full D365 rebuild. Nothing is migrated blind. Most AX 2012 customisations collapse to configuration in D365.

Outputs · X++ inventory · classification report · Power Platform spec · D365 customisation backlog

Integrations · existing endpoints kept live

Bridges from AX to MyInvois, e-Invoice, banks, EDI, WMS, MES and trading partners are catalogued. Each is rebuilt against D365 endpoints during migration, with parallel running so neither system is offline during cutover. Data contracts versioned and pinned.

Channels · LHDN MyInvois · banks · EDI · 3PL · MES · CRM · BI

Statutory + localisation · MY + ASEAN

SST setup, MFRS adjustments and statutory reporting reconfigured for D365 with your auditor in the room. ASEAN entities (Singapore, Indonesia, Vietnam, Thailand) added on the same configuration template, not as separate projects. PDPA controls reviewed.

Localisation · MY (SST + MFRS + MyInvois) · SG · ID · VN · TH · PDPA controls

Cutover weekend · parallel run · sign-off

AX continues to be the system of record while D365 is built and tested. One full month-end close runs in parallel: same period, both systems, reconciled before cutover. Finance signs off, not us. Cutover playbook signed by your operations and finance leads before go/no-go.

Cutover · parallel month-end · UAT 2 cycles · finance sign-off · go/no-go gates

What you unlock on D365

Four capabilities AX cannot ship to you, regardless of partner.

These are the platform shifts only D365 carries. Migration unlocks them all on the same day; no further upgrade project required.

01 · AI

AX No AI on AX

→

D365 Copilot embedded in finance + ops

Microsoft Copilot AI

Variance explanations, AP anomaly flagging, demand explanations, replenishment proposals, status drafts. None of these can be retrofitted onto AX, regardless of customisation budget.

02 · Compliance

AX AX bridge to MyInvois

→

D365 Native LHDN integration

LHDN MyInvois, native

D365 ships with direct MyInvois API integration. UIN tracking, credit/debit notes, self-billed and consolidated flows configured at go-live. The bridge layer disappears.

03 · Extensibility

AX X++ developers required

→

D365 Power Platform low-code

Power Apps + Power Automate

Customisations that needed X++ on AX get rebuilt as Power Apps and Power Automate flows on D365. Your business analysts extend the platform; your developer queue shortens.

04 · Productivity

AX AX client only

→

D365 Microsoft 365 native everywhere

Excel · Outlook · Teams native

Approve POs in Outlook. Edit a journal in Excel and post back. Run a project review in Teams against live D365 data. Microsoft 365 is the front door, no separate client install for casual users.

By the numbers

What Daxonet's D365 customers report after Phase 1.

99% Uptime

SLA · live

AX uptime under Daxonet SLA

Measured across 12-month rolling windows on Malaysian AX 2012 environments.

5-yr TCO comparison −42%

SAP S/4HANAOn request

Stay on AXOn request

Migrate to D365On request

Indexed to RM 100 SAP S/4HANA baseline · Daxonet 5-year TCO model

Months 4–6 Phase 1

Migration tempo

AX 2012 → D365 go-live

Single Malaysian entity, parallel-running discipline. AX 2009 typically 5–7 months for the deeper fit-gap.

ASEAN bench

47 ERP rollouts

Across D365, AX and Business Central in Malaysia and ASEAN. Project leadership averaging 10+ years on the Microsoft enterprise stack.

Parallel-running migration

Will AX stay live every minute that D365 is being built?

Yes. AX is the system of record until cutover weekend. D365 builds in parallel. One full month-end close runs in both systems before sign-off. Operations never goes offline.

Week 0 Wk 4 Wk 8 Wk 12 Wk 16 Wk 20 Wk 24

AX 2012

Live · system of record

AX maintained · operations continue · MyInvois bridge live

Cutover · finance signs off

D365

D365 F&O

Build → parallel → live

Phase 01 Discover · fit-gap

Phase 02 Configure · migrate · X++ rebuild

Phase 03 UAT 1+2 · training

Phase 04 Parallel month-end

Phase 05 Cutover · hypercare

Both systems run side-by-side through one full month-end close · finance reconciles before cutover · neither system is offline at any point in the migration window

Daxonet Microsoft Solutions Partner team running AX and D365 environments in Malaysia

Why Daxonet for AX + D365

The Malaysian bench that has shipped AX since 2009, and is shipping D365 today.

10+ years on AX and D365. 47 ERP rollouts across Malaysia and ASEAN. Reference customers (Panasonic, Novelis, Raco Industries, Sorento) across multi-entity manufacturing, global supply-chain finance and distribution. Project leadership averaging more than a decade on the Microsoft enterprise stack.

About Daxonet →

10+ yrs

AX 2009 + AX 2012 + D365 bench

ERP rollouts across MY · SG · ID · VN

Microsoft

Solutions Partner · Business Apps

FAQ

Questions Malaysian AX customers ask before they decide.

What is Microsoft Dynamics AX and is it still supported?

Microsoft Dynamics AX is the on-premise enterprise ERP from Microsoft, originally Axapta, that became Dynamics AX in versions 2009, 2012 and 2012 R3. Mainstream support from Microsoft for AX 2012 ended in October 2021 and extended support ended in January 2023 for most editions. The platform still runs in production at many Malaysian enterprises. Daxonet provides ongoing managed-service support, performance tuning, security patching, custom-code maintenance and integration support under SLA-backed contracts, with a planned migration path to D365.

Should we keep running AX or migrate to D365 now?

It depends on your risk appetite, audit profile and total cost of ownership, and the answer is rarely binary. Daxonet runs a free AX Health Check that quantifies the trade-off in writing: security and compliance risk on AX, infrastructure and customisation cost over the next 3 years, business cost of disruption during migration, and the TCO model for D365 over 5 years. For most Malaysian mid-large enterprises the AX-to-D365 model lands 30 to 45 percent below an equivalent SAP S/4HANA scope and below the cost curve of continuing to maintain AX past 2026. Until the migration date is set, Daxonet keeps AX stable under SLA so the decision stays a finance decision, not an operations crisis.

How does Daxonet keep AX 2009 and AX 2012 stable in 2026?

Daxonet maintains AX environments under managed-service contracts that include performance monitoring, SQL Server tuning, security patching, custom X++ code maintenance, integration support, statutory localisation updates for Malaysia (SST, MFRS, MyInvois bridging), backup and disaster recovery, and Tier-1 to Tier-3 support. Mainstream Microsoft support has ended, but the platform itself remains operable for years if maintained correctly by an experienced partner.

Can AX still issue LHDN MyInvois e-Invoices?

Yes. Daxonet implements an e-Invoice middleware bridge from AX to the LHDN MyInvois portal. The bridge handles standard invoices, credit and debit notes, self-billed invoices and consolidated invoices. AX continues to be the system of record for orders and accounting; the bridge handles MyInvois submission, UIN tracking and validation responses. The same bridge migrates with you when you move to D365 if needed, although D365 ships with native MyInvois integration.

What is the migration path from AX 2012 to D365?

Daxonet runs AX 2012 to D365 migrations as a structured upgrade. Chart of accounts, dimensions, items, BOMs, routings, customers, vendors, open transactions and historical balances are migrated with reconciliation back to AX before go-live. Custom AX X++ code is assessed: in-platform configuration replaces most customisations; the rest is rebuilt as Power Platform extensions or Azure functions. Parallel running of AX and D365 through one full month-end close is standard, so finance signs off before cutover. Total elapsed time runs 4 to 6 months for Phase 1, with multi-entity rollouts added in waves.

What about AX 2009: is the migration different?

Yes. AX 2009 customisations are usually deeper than AX 2012, the data model has more gaps versus D365, and statutory localisation is older. Daxonet treats AX 2009 migrations as a longer fit-gap exercise: typically 5 to 7 months for Phase 1 rather than 4 to 6 months from AX 2012. The same parallel-running discipline applies, and the destination platform is the same D365 Finance and D365 Supply Chain bench.

Will Daxonet support our existing AX customisations during migration?

Yes. Daxonet maintains AX X++ customisations during the entire migration window so your operations team is not running on a frozen system while D365 is being built. The customisation inventory is one of the first deliverables of the AX Health Check, where every X++ object is assessed for retention as configuration, replacement with Power Platform, or rebuild in D365. Nothing is migrated blind.

Which Malaysian enterprises has Daxonet already migrated from AX to D365?

Reference customers include Panasonic, Novelis, Raco Industries and Sorento, across multi-entity manufacturing, global supply-chain finance, and distribution. Each reference is available for a peer call from a CFO or operations leader evaluating an AX-to-D365 migration, by arrangement with Daxonet. Daxonet has completed 47 ERP rollouts across D365, AX and Business Central in Malaysia and ASEAN, with the project leadership bench averaging more than 10 years on the Microsoft enterprise stack.

Where AX customers go next on daxonet.com.

Free AX Health Check

Find out, before your auditor does.

A 60-minute review of your AX environment by Daxonet's AX bench. We come back in 7 days with a written report: risk register, customisation inventory, TCO model and a phased migration plan. No obligation. No upgrade-or-walk pitch.

Build your own copilots — no code required.

From shop-floor to finance — one connected system.

From experiment to operations — in 90 days.