Still Running Dynamics AX 2012? 5 Checks Before a D365 Move

-

Microsoft Dynamics AX 2012 is out of support: extended (security) support has ended for every release up to and including R3, the final version. Yet the system keeps running, and many companies still use it as their core ERP. If your organization is one of them, this post gives you a five-point checklist to run now — before anyone asks how long the current system can last or what a move to Microsoft Dynamics 365 Finance & Operations (D365 F&O) would involve.

Support has ended, but the system still runs

Once extended support ends, Microsoft no longer ships security patches or tax and regulatory updates for AX 2012. Nothing stops on that day. What changes is ownership: keeping the platform healthy and reacting to regulatory changes become your own team's job.

The hard part is that the information you need for that job — how the servers are set up, where the customizations live, which systems exchange data with AX — is usually spread across people's memories and old documents. The five checks below pull it into one place.

The checklist at a glance

CheckQuestion to answer
1. Support status and platformWho handles what Microsoft no longer updates?
2. Servers and environmentsIs there a one-page map of every server, and is production kept separate from development?
3. Where customizations liveWhich layers and models hold your changes to standard code?
4. IntegrationsIs every interface listed, with its partner system and method?
5. D365 F&O readinessDo you know which standard objects you have overwritten?

Check 1: Support status and platform

Confirm that AX runs on SQL Server and Windows versions that are still supported, that you have a way to implement tax and regulatory changes as custom development, and that a review of a move to D365 F&O is on the mid-term plan.

Check 2: Servers, services and environments

AX 2012 has three tiers: the client, the Application Object Server (AOS, the server where all business logic written in X++, AX's programming language, runs), and the SQL Server database. Around the AOS sit SQL Server Reporting Services (SSRS) for reports, SQL Server Analysis Services (SSAS) for analytics cubes, Enterprise Portal (a SharePoint-based web portal) and the Application Integration Framework (AIF, the standard integration gateway). Draw all of this on one page, including any AOS dedicated to batch jobs and whether the model store — the database that holds code objects — is separate from the transaction database (it is from R2 onward).

Then check the environments. There should be a path from development (DEV) to integration test (TEST), user acceptance (UAT) and production (PROD), with no development directly in production and only tested models or XPO files (AX export files for development objects) promoted to it.

Check 3: Where your customizations live

AX 2012 separates standard and custom code across 16 layers. Microsoft's standard code sits in the bottom layers (SYS, GLS, FPK); a customer's own customizations normally belong in the CUS (customer) layer, and light per-user adjustments in USR. A definition in a higher layer overrides the one below it. If Microsoft changes a standard object in a new version or hotfix and you have modified the same object in a higher layer, the upgrade produces a conflict that someone has to merge.

Three questions matter: are your customizations gathered in the CUS layer, are they split into models by function (for example finance, logistics, interfaces), and can you use the Compare tool to see exactly what changed against standard? Keeping changes in the CUS layer and in models by function prevents many promotion mistakes and lets you deploy one function at a time; the more cleanly custom code is separated from standard code, the lower the cost of each upgrade.

Check 4: Integrations

List every place where AX exchanges data, grouped by method. The training material we used for this checklist recommends a method for each situation:

SituationTypical AX 2012 method
Exchanging standard business entitiesAIF document services
Periodic file exchangeFile import/export (CSV, Excel) plus batch
Special formats, encryption, external SDKs.NET library calls
One-off queries or migration from an external databaseOLEDB / ODBC, with connection details kept out of the code
Notifications and report distributionSMTP email plus batch

Check 5: Readiness for D365 F&O

AX 2012 customizations work by overlayering: a higher layer overwrites the standard definition. D365 F&O does not overwrite standard code; it extends it from the outside with extensions and Chain of Command (CoC). The goal of keeping custom code apart from standard code is the same — only the technique has changed. That is why you need to know which standard objects you have overwritten and how each requirement is implemented in AX before you can scope a migration.

AX 2012
Layers + models + overlayering — a higher layer overwrites the standard definition
D365 F&O
Packages + models + extensions and CoC — standard code is extended from the outside

Walkthrough: running the checklist once

Here is how a fictional IT operations lead at a manufacturer might fill in the checklist for the first time. It is an illustration, not a customer case.

1. Platform. Record whether the SQL Server and Windows versions are still supported, and who implemented past tax and regulatory changes, and how.

2. Server map. Put the AOS instances (including any batch AOS), SQL Server (transaction database and model store), SSRS, SSAS, Enterprise Portal and AIF on one page, and mark whether DEV, TEST, UAT and PROD are separate.

3. Customizations. In the AOT (Application Object Tree, the AX development tree), review the objects in the CUS and USR layers and use the Compare tool to see the changes against standard. Note whether they are split into models by function.

4. Integrations. Write one line per interface: partner system and method (AIF, file, .NET, external database, email).

5. Migration scope. Extract the list of overwritten standard objects and hand it over as the list of candidates to redesign as extensions and CoC in D365 F&O.

Information that used to be scattered ends up on one sheet, and that sheet becomes the starting point for a migration review.

After the checklist

The same checklist serves two purposes: running AX 2012 safely today and scoping a move to D365 F&O. The layer and model inventory and the integration list in particular are essential inputs for scoping a migration. JGS Consulting supports AX 2012 maintenance, AX 2012 to D365 F&O migrations and system integration.

Compiled from JGS Consulting's internal Microsoft Dynamics AX 2012 development training guide (volumes 1, 2, 4 and 11, version 1.0, 2026).

If you would like help working through these checks or scoping a migration, contact us.

Korean version: blog.naver.com/jgsconsulting

AX 2012 extended support has ended. Five checks to run now: platform, servers and environments, customization layers, integrations, D365 readiness.
Location: 한국

Comments

Post a Comment

Popular posts from this blog

Korean VAT Filing in D365 With Less Spreadsheet Rework

-
If you run Microsoft Dynamics 365 Finance & Operations (D365 F&O) for a Korean legal entity, VAT filing probably still happens in Excel. This post shows what standard D365 leaves out, how the JGSKVAT package fills the gap in five steps, and what one filing period looks like when the whole job stays inside D365. The same double work every quarter D365 F&O is a global standard ERP. Its standard tax features cover tax rate calculation and settlement periods. For a Korean legal entity, the trouble starts after that. Every quarter a Korean entity has to file a VAT return in the format set by the National Tax Service (NTS), issue and receive e-Tax invoices, and reconcile its books against the data the NTS holds. Standard D365 does not do this. So many companies export data from D365, total it in Excel, and move back and forth between D365 and Hometax (the NTS e-filing portal). The manual work repeats every quarter, and a transcription error can lead to penalty tax. Where stan...
Read more

How JGS Uses AI Agents in D365 Projects: Two New Series

-
Image
On a D365 implementation project, the sentence you hear most often is "But we said that in the meeting." Requirements come out of meetings, while the design document, the code, the tests and the manual are each written later, by different people. Along the way, things get left out or read differently. These days there is a lot of talk about drafting documents quickly with AI agents. But someone still has to check that a quickly drafted document is right. JGS Consulting is testing, first-hand on an internal project, how to use AI in Microsoft Dynamics 365 Finance & Operations (D365 F&O) implementations. Starting next week, we will share that work in two blog series. Why we are starting two series JGS is doing two things at once right now. Building JGS Agile Package (in testing), a package that bundles the requirements that come up again and again on implementation projects Building that package with an AI-agent-based delivery method, the JGS D365 F&O AI D...
Read more

Welcome to the JGS Consulting Blog: Dynamics 365 Insights from Korea

-
Hello from JGS Consulting. In every ERP project we hear the same questions. "How should we set standard costs?" "Can we file Korean VAT directly from D365?" "How long can we stay on AX 2012?" We started this blog to put the answers in one place. Who we are JGS Consulting is a Microsoft Dynamics 365 Finance & Operations (D365 F&O) consulting firm based in Korea. We were founded in May 2022 by consultants and architects who each have more than ten years of Microsoft ERP experience. Since then we have delivered more than ten projects across securities, biotech, chemicals, fashion and manufacturing. What we do D365 F&O implementation and enhancement : finance, costing and supply chain process design, development, and improvement after go-live Cost management : costing and allocation models that standard systems do not cover System integration : MES, APS, WMS and groupware AX 2012 operations and upgrade : automated source control, and readi...
Read more