The Microsoft messaging is constant. The implementation quote is large. The decision is on you.
Copilot demos, deprecation timelines, AI-FOMO. None of it actually answers whether your business should move now, phase, or wait.
Pillar 04 · Microsoft Dynamics
Three honest paths for your Dynamics estate.
A standalone practice within Artrilogic. Tin Aung Phyoe leads. We assess your estate, recommend a path, and stand behind the recommendation.
Either you commit to a multi-million-dollar D365 programme you are not ready for, or your AI options narrow.
Most businesses default to one or the other. The third option (a phased plan or an extend-and-wrap with MCP) is rarely on the procurement table.
Three weeks. Three paths assessed honestly. One written recommendation.
Including the “wait twelve months” option if that is the right call. We are explicit about that on the call.
What we do
A standalone Dynamics practice with one job: get the call right.
We work end to end on Microsoft Dynamics estates. Discovery, recommendation, implementation across upgrade, phased move, or extend-and-wrap. Our team has run GP, AX, NAV and current D365 programmes for Australian enterprises through every combination of customisation debt, integration sprawl, and compliance horizon you are likely to encounter.
The work is delivered alongside the rest of Artrilogic where it makes sense. Most Dynamics estates carry custom .NET extensions, sit on Azure, and now face decisions about how much AI capability belongs inside Dynamics versus alongside it. We hold all of that in one engagement so the recommendation is grounded in the whole picture, not just the ERP.
Where we focus
Full upgrade. Phased move. Extend & wrap.
The right path is the one that fits your estate, your AI roadmap, and your budget reality. Not the one that fits Microsoft's quarterly target.
Full upgrade
A full move to current D365 with Copilot capability. Highest cost, highest disruption, highest ceiling on AI value if executed well. Worth doing when the conditions above hold.
When this fits
- Customisation debt is clean and well-documented
- Budget is approved and timeline is realistic
- Licensing route to current D365 is clear
- AI capability inside D365 is a strategic priority
Phased move
Modernise the parts that hurt the most, leave the rest stable. Often the right call for mid-market and enterprise. Phased programmes give you the option to stop early if value does not materialise.
When this fits
- Mixed estate where some workloads are stable and others are not
- AI capability is needed in specific areas now, not everywhere
- Risk-averse on big-bang cutover
- Procurement prefers staged budget commitment
Extend & wrap
Keep the existing Dynamics estate running. Wrap it as MCP servers so modern AI agents can use its data and capabilities. The lowest-cost, highest-optionality answer when AI value is the actual goal.
When this fits
- Estate is stable and meets current operational needs
- AI value lives elsewhere in the business, not inside Dynamics
- MCP wrapping over Dynamics gives agentic AI access without disruption
- Compliance horizon is more than 24 months out
Notice all three are framed as legitimate. We are explicit about that because the “extend & wrap” path in particular is rarely on a Microsoft partner's slide deck, and it is often the right call.
Our approach to delivery
Four phases. Honest checkpoints. The same posture across every pillar.
Assessment
A fixed-scope diagnostic. Two to three weeks. We read the estate, name the constraints, and surface the decisions you actually need to make. The deliverable is a written recommendation you could hand to another firm and they could execute against it.
Scoping
Once a path is chosen, we scope the first vertical slice tightly. Time-boxed phases, named exits, and a clear answer to "what does the smallest useful uplift look like." You can stop after phase one if the value is not there.
Build
Senior engineers who have shipped this work before. We work to your existing change processes, your security posture, and your operational posture. The architects you meet in scoping are the architects who deliver.
DevOps practice, on GitHub
Every engagement ships on a modern DevOps practice grounded in GitHub: branch protection, PR review, GitHub Actions for CI/CD, environment promotion, and audit trails your compliance team can defend. We do not run cowboy releases and we do not hand over a codebase your team cannot maintain.
Who would do the work
Tin Aung Phyoe, Microsoft Dynamics practice lead.
Twenty-plus years across Microsoft Dynamics from GP, AX and NAV through to current D365. Specialises in upgrade, phased modernisation and extend-and-wrap strategies for Australian enterprises.
Buyers want to know who would actually deliver. We name our practitioners on the page.
Cross-pillar
Where Dynamics fits with the rest of our work.
Most engagements touch more than one pillar. Here is how Dynamics work typically connects.
Dynamics + AI adoption
Where AI capability lives outside the ERP. MCP wrappers over Dynamics so agentic workflows can read and act on the data without an upgrade.
Open the pageDynamics + .NET modernisation
Most Dynamics estates carry custom .NET extensions, integrations and reporting layers. We modernise those alongside the Dynamics path you choose.
Open the pageDynamics + Infrastructure
Dynamics customers are typically Azure-aligned. We hold the Azure estate, the Dynamics path, and the integration layer between them as one engagement.
Open the page
Common questions
What buyers usually ask first.
We are on Dynamics GP / AX / NAV. Is upgrading to D365 the only option?
No. The upgrade path Microsoft markets is one of three legitimate options. The right call depends on your customisation debt, AI roadmap, and how much of the estate is genuinely earning its keep. We work through all three on the assessment.
Is a Dynamics rescue an IT project or an AI move?
Increasingly the latter. The pressure most leadership teams feel is not 'we need to be on a newer ERP'. It is 'we need to be AI-ready'. The Dynamics practice exists because how you handle the Dynamics estate determines what your AI options are.
Who actually does the work?
Tin Aung Phyoe leads our Dynamics practice. Twenty-plus years across Microsoft Dynamics implementations from GP through to current D365, working with Australian enterprises on both upgrade and extend strategies. He is named on this page because buyers want to know who would actually do the work.
How long does a Dynamics assessment take?
Two to three weeks of senior architect time depending on the estate. The deliverable is a written recommendation across the three paths, with cost ranges and a defensible 'wait' option if that is the right call.
Two ways in
Pick the lower-commitment one if you are weighing this.
A 15-minute call with Tin to talk through your estate is a reasonable first step. If a full review is the right next thing, we will say so.