# Dynamics AX 2012 Retirement Project Charter Template

> Source: https://netray.co/tools/dynamics-ax-2012-retirement-project-charter-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A one-to-two page charter for getting executive approval to retire or replace Dynamics AX 2012, with scope, drivers, risks and sign-offs.

## Category

microsoft-dynamics

## Erp

Microsoft Dynamics AX 2012

## Audience

- CIO
- ERP project manager
- AX administrator

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Halvorsen Industrial Group

#### Executive sponsor

**Key:** sponsor

**Type:** text

**Default:** CFO

#### Project manager

**Key:** pm

**Type:** text

**Default:** Priya Raman

#### Target platform

**Key:** target

**Type:** select

**Options:**

- Dynamics 365 Finance and Supply Chain
- Business Central
- Another ERP (to be selected)
- Retire to read-only archive

**Default:** Dynamics 365 Finance and Supply Chain

#### Legal entities in scope

**Key:** legal_entities

**Type:** number

**Default:** 6

#### Business drivers

**Key:** drivers

**Type:** textarea

**Default:** AX 2012 hosting hardware is end of life, security patching is no longer available from Microsoft, and two key ISV add-ons are no longer supported.

#### Target go-live

**Key:** target_date

**Type:** date

**Default:** 2027-07-01

#### Approved budget range

**Key:** budget

**Type:** text

**Default:** To be confirmed after discovery

**Blocks:**

#### Project Charter: AX 2012 Retirement

**Body:** Company: {{company}}
Executive sponsor: {{sponsor}}
Project manager: {{pm}}
Target platform: {{target}}
Legal entities in scope: {{legal_entities}}
Target go-live: {{target_date}}
Budget: {{budget}}

#### Business Drivers

**Body:** {{drivers}}

#### In Scope

**Body:** Finance, supply chain, production and trade agreements as currently used in AX 2012. Custom code, SSRS reports, integrations, batch jobs and user security roles will be inventoried before scope is frozen.

#### Out of Scope

**Body:** Process redesign beyond what is needed for the target platform, and decommissioning of unrelated systems, unless added through change control.

#### Success Measures

**Table:**

**Columns:**

- Measure
- Target
- Owner

**Rows:**

**0:** Month-end close time

**0:** Open critical customisations remaining

**0:** Users trained before go-live

**0:** AX 2012 servers powered off

#### Key Risks

**Table:**

**Columns:**

- Risk
- Likelihood
- Impact
- Mitigation

**Rows:**

**0:** Undocumented customisations

**0:** Data quality in item and customer masters

**0:** Key-person dependency on AX developers

**0:** Fiscal year-end overlap

#### Approvals

**Signatures:**

- Executive sponsor
- Project manager
- IT director
- Finance controller

**Notes:** Starting-point template. Add your own governance and procurement requirements. Verify the current Microsoft support dates for your AX 2012 release before citing them.

## Content

**Intro:** Retiring AX 2012 needs a sponsor and a defined scope before anyone can price it. This charter captures the business case, scope boundaries, measures and risks on a single document your steering group can sign.

**Sections:**

#### How to use the charter

**Body:** Fill in the header and drivers, then edit scope in your exported copy. Keep it short enough that executives read it. Details such as the full customisation list belong in an appendix, not in the charter.

**Bullets:**

- Name one sponsor with budget authority
- State drivers in business terms
- Define out of scope as clearly as in scope
- Review at each phase gate

#### Choosing the target

**Body:** Retiring AX 2012 does not always mean moving to Dynamics 365 Finance and Supply Chain. Smaller AX estates sometimes fit Business Central, and some companies take the opportunity to change ERP vendors. If the target is undecided, say so in the charter and make selection the first milestone. Archiving AX data read-only is a valid target for entities that no longer transact.

#### Measures and risks

**Body:** Choose measures you can read from the ERP: close duration, count of open customisations, user training completion. For risks, the two that cause most AX overruns are undocumented customisations and data quality. Plan an inventory early and give data cleansing its own owner.

**Cta:** If you want your AX customisations, reports and integrations inventoried quickly, we can discuss tooling that reads your AX metadata.

**Faq:**

#### Who should sign the charter?

**Answer:** The executive sponsor, the project manager, the IT director and the finance controller at minimum. Add operations if production or warehouse processes are in scope.

#### Should the charter include a budget?

**Answer:** Include a range if you have one. If discovery is not done, state that the budget is to be confirmed and set a date for confirming it, rather than inventing a number.

#### How long should a charter be?

**Answer:** One to two pages. Put detailed inventories, data mapping and test plans in separate documents referenced from the charter.

#### Does this work for D365 upgrades from AX 2012?

**Answer:** Yes, though most AX 2012 to D365 moves are reimplementations with data migration, not in-place upgrades. State the approach in scope.

## Search terms

ax 2012 retirement plan, dynamics ax project charter template, ax 2012 to d365 project charter, erp replacement project charter template, legacy erp decommission charter, dynamics ax end of support plan

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json