Dynamics AX end of support: migration options and what each costs

Microsoft Dynamics AX is already past end of support on every version Microsoft still lists. On Microsoft's finance and operations calendar, extended support for AX 2009 Service Pack 1, AX 2012, and AX 2012 R2 ended on 12 April 2022, and extended support for AX 2012 R3 ended on 10 January 2023. The lifecycle pages put those endings one day later, at 6:59:59 AM Pacific. The decision for a 20 to 100 person company is which replacement to fund: a data migration, a code-and-history upgrade to Finance and Supply Chain Management, or a new implementation on Business Central or Odoo.

What Dynamics AX is, and where the product name went

Wikipedia records Dynamics AX as the former Axapta product and states that it was rebranded in 2018, when the thick client was removed, as Microsoft Dynamics 365 for Finance and Operations. The same page calls out X++ and MorphX. The rebrand is a name change. Whether an AX 2012 database can use Microsoft's upgrade tools depends on the version, which the sections below separate: R2 and R3 can upgrade after the latest cumulative update, and RTM is not supported on the current overview. Business Central and Odoo are new implementations with their own setup, because the documented AX upgrade lands on finance and operations.

People still search for microsoft dynamics ax and microsoft dynamics ax axapta because contracts, server names, and old menus use both labels. For a buyer, the label that matters is the version on the About screen: AX 2009, AX 2012 (the original RTM release), AX 2012 R2, or AX 2012 R3. Each one has a different Microsoft path, described below. AX 4.0 and Axapta 3.0 are outside this page. Have any bidder date those builds from a Microsoft lifecycle page you can open, and keep them out of an R3 quote.

When support ended for each Dynamics AX version

All four listed releases follow Microsoft's Fixed Lifecycle Policy, and all four are past extended support as of October 2026. Use the lifecycle timestamps when you need the official product record, and expect the finance and operations article to print the previous calendar day.

• AX 2009 (General availability: 14 August 2008 · Mainstream support ended: 10 October 2018, 6:59:59 AM PT · Extended support ended: 13 April 2022, 6:59:59 AM PT)
• AX 2012 (RTM) (General availability: 25 September 2011 · Mainstream support ended: 10 October 2018, 6:59:59 AM PT · Extended support ended: 13 April 2022, 6:59:59 AM PT)
• AX 2012 R2 (General availability: 19 February 2013 · Mainstream support ended: 10 October 2018, 6:59:59 AM PT · Extended support ended: 13 April 2022, 6:59:59 AM PT)
• AX 2012 R3 (General availability: 1 August 2014 · Mainstream support ended: 13 October 2021, 6:59:59 AM PT · Extended support ended: 11 January 2023, 6:59:59 AM PT)

Dates: AX 2009, AX 2012, AX 2012 R2, AX 2012 R3, seen October 2026.

The original AX 2009 release ended on 12 January 2011. Service Pack 1 carried the product through the same extended end date. Microsoft's lifecycle note says end of support for AX 2009 Service Pack 1 was extended from 12 October 2021 to 12 April 2022. The AX 2012 lifecycle page records the same extension, from 12 October 2021 to 12 April 2022. The AX 2012 R2 lifecycle page records an extension from 12 October 2021 and an extended-support timestamp of 13 April 2022, 6:59:59 AM PT. The finance and operations article dates that R2 end to 12 April 2022. The AX 2012 R3 page says mainstream and extended support were extended, and it records the January 2023 end above.

The finance and operations article uses calendar dates that sit one day earlier: mainstream support for AX 2009 SP1, AX 2012, and AX 2012 R2 ended 9 October 2018, with security hotfixes through extended support ending 12 April 2022. It dates AX 2012 R3 mainstream support to 12 October 2021 and extended support to 10 January 2023. If a proposal quotes a single day, ask which page it used. The practical point is the same on both: waiting for a future AX deadline is no longer a plan.

What Microsoft stopped providing, and what that means now

Under the Fixed Lifecycle Policy, Extended Support includes paid support and no-charge security updates. It excludes warranty support, design changes, and new features. After end of support, that policy lists security updates as available only through the Extended Security Update program. The AX 2009, AX 2012, AX 2012 R2, and AX 2012 R3 lifecycle pages do not list an Extended Security Updates release the way the SQL Server 2016 lifecycle page does. Ask Microsoft, in writing, what security servicing your contract still includes for the AX build you run, and budget the replacement without assuming a patch program will appear.

Microsoft is explicit about the years those products spent in Extended Support. "Neither nonsecurity hotfixes nor regulatory updates are available for the Dynamics AX products during the Extended Support phase". The same article says Microsoft does not provide those updates for AX 2009 SP1, AX 2012, AX 2012 R2, or AX 2012 R3, including for customers on Unified Support Advanced and Performance levels, because it determined it cannot do so with commercially reasonable effort.

Regulatory coverage is narrower still for the earlier versions. Microsoft says regulatory updates for AX 2009 SP1, AX 2012, and AX 2012 R2 were provided only for regulatory changes whose law-enforcement date was on or before 9 October 2018. A tax, e-invoicing, or payroll rule with a later enforcement date was outside that commitment. Finance teams on those versions have been closing without Microsoft regulatory updates for years. R3's mainstream window ran longer, until October 2021, so do not copy the 9 October 2018 cutoff onto R3. Do apply the broader statement: during Extended Support, regulatory updates were not provided for R3 either, and that phase ended in January 2023.

For a US or Canadian company, the operational exposure is concrete. Security fixes for the application are not on the public lifecycle record after those extended dates. Statutory changes since the cutoff have to be handled in process, in a spreadsheet, or in the system you move to. That is a larger problem than a lapsed support contract, because the dates are already behind you and the license you will pay next is a separate decision.

Which migration path Microsoft documents for your version

Dynamics AX migration is three different projects wearing one name. Match the path to the version before you compare licenses.

AX 2009 is a data migration, using the Data migration tool

"Using the DMT is the only supported upgrade path from AX 2009." The tool moves data after field mapping, conversions, default values, and query filters. Microsoft does not describe it as a code upgrade. Your team maps financial dimensions, inventory dimensions, and charts of accounts. The tool can consolidate multiple legal entities onto one chart of accounts, which is useful when AX 2009 companies drifted into separate account structures, and costly when those structures disagree on what a dimension means.

X++ written for AX 2009 does not ride along on this path. Reports, integrations, and modifications are rebuilt or retired. Treat an AX 2009 proposal that promises the same customizations, upgraded, as a design project, and ask for the list of objects that will be rewritten.

AX 2012 R2 and R3 can upgrade to finance and operations

Microsoft's upgrade overview says a cloud upgrade to finance and operations is supported from AX 2012 R2 and AX 2012 R3 only, after the latest cumulative update. The tools can bring forward custom X++ and the full transactional database. An on-premises data upgrade is documented separately.

The on-premises upgrade also supports only R2 or R3 on the latest cumulative update, landing on Dynamics 365 Finance + Operations (on-premises). One method, upgrading from an existing on-premises environment, requires version 10.0.31 or later. Code upgrade tooling is available only through Lifecycle Services. Customizations must be installed before data upgrade, or customization-related data is removed. That sequence belongs in the project plan: code first, then data. Reversing it drops the data that depended on those customizations.

AX 2012 RTM is not the same path as R2

The upgrade overview says upgrade from Dynamics AX 2012 RTM is not supported. The older FAQ in the mainstream-support article still says AX 2012 and AX 2012 R2 customers should upgrade to finance and operations through AX 2012 R3. Those two pages disagree. Do not let a proposal collapse them into one sentence. For RTM, ask the bidder to show either a supported route they will execute (including any interim upgrade they still claim is valid) or a data-migration design that does not pretend the R2 and R3 tools apply. For R2, the overview is the page that says a direct upgrade is supported after the latest cumulative update. Have them name which page their statement of work follows.

Business Central and Odoo are reimplementations

Microsoft's documented upgrade from AX lands on finance and operations. Business Central can still be the right system for a single-entity distributor or light manufacturer in the 20 to 100 person range. You configure it from your processes and load the balances, open documents, and master data you choose to bring. That work is separate from the R2 and R3 upgrade Microsoft documents.

Odoo is the same kind of choice. AX X++ does not move into Odoo. Custom work sits on Odoo's Custom plan, covered with the prices below. Companies that want the finance and operations upgrade because they need full history and their X++ should stay on that evaluation. Companies that want a smaller license and are willing to rebuild processes should price Business Central and Odoo as new systems.

What changes the effort on an AX 2012 upgrade

Microsoft's upgrade overview says upgrades from AX 2012 are complex, and that the tools and code should be seen as a framework you still finish with effort, data cleanup, tuning, and customization. These are the items that change a quote.

Systems using virtual companies or data partitions cannot currently be upgraded. If either pattern is in production, the code-and-history upgrade stops until Microsoft changes that limit or you switch to a data migration onto a new configuration. Find this out before you compare day rates.

Code changes in AX 2012 should be frozen after code upgrade, except emergencies, which must be ported manually. A finance team that keeps changing X++ during the project pays for every emergency twice: once in AX, once in the upgraded code.

Document attachments stored on a file share or local SharePoint are available after upgrade only if they are migrated into the AX 2012 database first. If your auditors open invoices from a share, that copy is its own workstream. Leave it out of the estimate and users will not find those files after cutover.

Part of the finance and operations subscription cost is based on database size, so cleanup reduces that component and shortens cutover. Microsoft's public pricing pages do not state the included gigabytes or the overage rate. Ask each bidder to price database size as its own line, show what they will archive, and state whose number the subscription estimate uses.

Deprecated features surface in Microsoft's upgrade analysis. The AIM assessment (Accelerate, Innovate, Move) is a partner assessment for on-premises business applications. For Dynamics AX it uses the Lifecycle Services AX Code Upgrade Analysis Tool and a SQL Upgrade Analysis script. It covers process fit, integrations, database size, custom code, workflows, reports, and license counts. Microsoft does not publish a price for the assessment. If a partner offers AIM, ask which of those outputs you will receive and how they map to phases. The tests that decide a bidder are still the named people, the hours, the references, the phase plan, and who owns the code afterward.

What the licenses cost if you leave AX

List prices below are subscription rates as of October 2026, paid yearly, from Microsoft's and Odoo's public pages. They are the license line only. Ask each bidder to price data migration, custom code, integrations, training, and cutover as their own lines, tied to your data volume and the downtime window you can allow.

Business Central list prices

• Essentials (United States: USD 80 per user per month · Canada: CAD 108.50 per user per month, plus tax)
• Premium (United States: USD 110 per user per month · Canada: CAD 149.20 per user per month, plus tax)
• Team Members (United States: USD 8 per user per month · Canada: CAD 10.90 per user per month, plus tax)

Sources: Business Central pricing (US) and Business Central pricing (Canada), October 2026. Premium includes Essentials plus service management and manufacturing. Team Members is limited read, approvals, and selected updates. The public pages do not state a base-license minimum or a required ratio of Team Members to full users. Do not let a quote invent one. Have the bidder show which roles are Essentials, which are Premium, and which can live on Team Members.

Assume 20 users who each need a full license, and no Team Members. At the yearly-paid rate, Business Central Essentials is 20 times USD 80, which is USD 1,600 per month, or USD 19,200 over twelve months. In Canada the same 20 users are 20 times CAD 108.50, which is CAD 2,170 per month, or CAD 26,040 over twelve months before tax. If those users need manufacturing or service management, Premium applies: 20 times USD 110 is USD 2,200 per month (USD 26,400 over twelve months), and 20 times CAD 149.20 is CAD 2,984 per month (CAD 35,808 over twelve months before tax). Essentials is the wrong SKU for that footprint.

A Business Central implementation for a company this size is still a configuration and data-load project.

Finance and Supply Chain Management list prices

A full AX manufacturing and warehouse footprint maps to two product families, Finance and Supply Chain Management, priced separately. The pages below do not describe a single combined SKU that replaces AX.

• Finance (United States: USD 210 per user per month · Canada: CAD 284.90 per user per month, plus tax)
• Finance Premium (United States: USD 300 per user per month · Canada: CAD 407 per user per month, plus tax)
• Supply Chain Management (United States: USD 210 per user per month · Canada: CAD 284.90 per user per month, plus tax)
• Supply Chain Management Premium (United States: USD 300 per user per month · Canada: CAD 407 per user per month, plus tax)

Sources: Finance pricing (US), Finance pricing (Canada), Supply Chain Management pricing (US), and Supply Chain Management pricing (Canada), October 2026. Finance Premium includes 1,000 Copilot Credits per license, with higher capacity and storage than Finance described only in the licensing guide. Supply Chain Management Premium includes 1,000 Copilot Credits per user per month. This page does not restate guide-only capacity numbers.

Assume 20 users who each need Finance, and no judgment yet on whether any of them also need a Supply Chain Management license. Twenty Finance users cost 20 times USD 210, which is USD 4,200 per month, or USD 50,400 over twelve months. In Canada, 20 times CAD 284.90 is CAD 5,698 per month, or CAD 68,376 over twelve months before tax. The same arithmetic applies to 20 Supply Chain Management users, because the list price matches. If a role needs both products, price both lines for that person. If warehouse staff need only Supply Chain Management, do not also put them on Finance. Attach rules and base-license minimums were not on these public pricing pages, so ask the licensor to confirm them against your role list.

Set next to the Business Central example, 20 Finance users at USD 4,200 per month cost USD 2,600 per month more than 20 Essentials users at USD 1,600, and USD 2,000 per month more than 20 Premium users at USD 2,200. In Canada the gaps are CAD 5,698 minus CAD 2,170, which is CAD 3,528 per month versus Essentials, and CAD 5,698 minus CAD 2,984, which is CAD 2,714 per month versus Premium. You pay that gap when you need the finance and operations upgrade path, the heavier supply chain scope, or both. You do not pay it merely because the old system was AX. Compare that choice with Finance and Operations in our guide to Business Central vs Finance and Operations after you have the license math, because the product decision and the upgrade-tool decision are different questions.

Odoo subscription prices, and what they leave out

Odoo is a reimplementation. As of October 2026, Odoo's pricing page shows US dollars on the Canada locale as well, so there is no separate CAD list here. The yearly toggle shows two pairs at once. Standard is displayed as USD 24.90 and USD 31.10, and also as USD 31.10 and USD 38.90, per user per month. Custom is displayed as USD 49.00 and USD 61.00, and also as USD 61.00 and USD 76.20. A footnote says the discount is valid for 12 months for the initial users ordered. Keep both pairs in the comparison. Do not collapse them to one number.

Standard is Odoo Online without custom modules. Hosting and support are included. Implementation is not included in the subscription. Custom is required for Odoo Studio, multi-company on the paid plans' terms, an external API, and on-premise or Odoo.sh. Odoo.sh hosting is not included. A Light User is USD 8.90, for limited self-service and shop-floor use, obtained through an advisor quote. One App Free is USD 0 for one app and unlimited users on Odoo Online, which is not an AX replacement.

Odoo says companies under 50 employees usually implement directly with Odoo using Success Packs, companies over 50 employees usually use a partner, and companies over 250 employees should contact Odoo. A Success Pack is the usual direct path under 50 employees. Companies over 50 are usually steered to a partner. For new customers, Success Packs are USD 493, USD 3,060, USD 5,950, USD 10,625, and USD 21,250 for 4, 25, 50, 100, or 200 hours with a dedicated consultant, with 15 percent off the first pack. Returning-customer prices on the same page are USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000. Onsite travel and custom-module maintenance are both billed extra on that page. Those packs are not AX migration prices. Use the pack table to see Odoo's own services rate card, then ask any implementer to price discovery, data migration, custom modules, and training as separate lines.

Assume 20 Custom users and, for a moment, the lower figure in the first displayed pair, USD 49.00. That is USD 980 per month before Odoo.sh, implementation, and custom-module maintenance. The higher figure in the second pair, USD 76.20, is USD 1,524 per month on the same 20 users. Even the higher of those two sits under 20 Business Central Essentials users at USD 1,600 per month, and far under 20 Finance users at USD 4,200. The license gap is real. The work to rebuild AX processes, and the Custom plan requirement for custom code, is the other half of the comparison.

A second deadline if the servers are from 2016

AX running out of support is the application problem. The operating system and the database can expire on their own calendar. Do not assume every remaining AX estate is on these builds. Check the version on the AOS host and on the SQL instance.

SQL Server 2016 extended support ended 15 July 2026 at 6:59:59 AM Pacific. Microsoft lists paid Extended Security Updates for three years after that, through 17 July 2029. That offer is for SQL Server only, not for AX. Windows Server 2016 extended support ends 13 January 2027 at 6:59:59 AM Pacific for Datacenter, Essentials, MultiPoint Premium, and Standard.

If you are on those versions, the application left support in 2022 or 2023, the database platform left extended support on 15 July 2026, and the operating system reaches the end of extended support on 13 January 2027. Paid Extended Security Updates for SQL Server 2016 run through 17 July 2029 and cover SQL Server only. The AX lifecycle pages do not list an equivalent. If you are on a newer SQL Server or Windows Server, this second clock does not apply, and you should say so in the RFP so bidders do not pad the infrastructure line. If you are on an older build, pull that product's own lifecycle page before you accept a date in a slide.

Companies that also still run Dynamics GP have a separate support calendar and a separate set of choices. Our note on Dynamics GP end of life migration options covers that product. Do not reuse an AX plan for GP, or the reverse.

How to sequence the move at 20 to 100 users

The length of an AX 2012 upgrade follows data volume, custom code, and how long you can stop operations for cutover. A practical sequence looks like this.

1. Write down the version, the latest cumulative update, the legal entities, and whether virtual companies or data partitions exist. RTM, R2, R3, and 2009 do not share a statement of work.
2. List the custom X++, the integrations, the reports, and where attachments live. Freeze non-emergency code once an upgrade project starts, and move file-share attachments into the AX database before an R2 or R3 upgrade if you need them afterward.
3. Clean master data and historical transactions you do not need in the new database. On finance and operations, database size is part of the subscription. On a reimplementation, every extra year of history is a mapping argument.
4. Price licenses from roles, using the tables above, in USD or CAD to match the entity that will be billed. Separate Finance from Supply Chain Management. Use Premium on Business Central when manufacturing or service management is in scope.
5. Choose the path: DMT data migration from AX 2009, upgrade from R2 or R3, or a reimplementation on Business Central or Odoo. For RTM, make the bidder reconcile the two Microsoft documents before you sign.
6. Phase the first go-live around the work the business cannot do without: typically the chart of accounts, open payables and receivables, inventory on hand, and the orders that must ship that week. History, satellite warehouses, and rarely used customizations can follow.

Our target for a first usable phase is 8 to 12 weeks, using the Flectic Accelerated Delivery Framework, with a consultant reviewing the configuration before you cut over. That target is ours, for a bounded first phase. It is not a claim about how long Microsoft's upgrade tools take on a large AX 2012 database. A database with years of transactions, heavy X++, and a short downtime window will run longer, and the statement of work should say so.

ERP implementation for a company this size should show named consultants, hours by phase, references on a similar version, and a written rule for who owns the code and the data extracts. If you want the finance and operations family more broadly, start from Dynamics 365 implementation options and then narrow to the SKUs your roles need. If Business Central is the fit after the license comparison, the rollout shape is a phased configuration and data load, described on our Business Central implementation page, with discovery before anyone promises a date.

Ask each bidder for five exhibits: the Microsoft page their path follows, the license count by SKU at current list, the attachment and database-size plan, the list of customizations that will not be ported, and the downtime window for cutover. Those exhibits tell you whether the price is for your AX system or for a template.

How Flectic can help

Flectic implements Microsoft Dynamics 365 for companies of 20 to 100 people in the US and Canada that are leaving Dynamics AX or another system its vendor no longer supports. Our Business Central finance foundation covers the general ledger, accounts payable and receivable, dimensions and bank reconciliation, and opening balances are reconciled before go-live. We work alongside your team through the first month-end close on the new system. Book a free discovery call with Flectic through our Dynamics 365 implementation service to compare migration paths for your version.

Sources

Microsoft Dynamics 365, Wikipedia, October 2026.

Dynamics AX 2009 lifecycle, Microsoft, October 2026.

Dynamics AX 2012 lifecycle, Microsoft, October 2026.

Dynamics AX 2012 R2 lifecycle, Microsoft, October 2026.

Dynamics AX 2012 R3 lifecycle, Microsoft, October 2026.

End of mainstream support for AX 2009 and AX 2012, Microsoft, October 2026.

Fixed Lifecycle Policy, Microsoft, October 2026.

Upgrade from AX 2012 to finance and operations, Microsoft, October 2026.

AX 2009 Data migration tool, Microsoft, October 2026.

AX 2012 on-premises data upgrade, Microsoft, October 2026.

AIM Assessment, Microsoft, October 2026.

SQL Server 2016 lifecycle, Microsoft, October 2026.

Windows Server 2016 lifecycle, Microsoft, October 2026.

Business Central pricing (US), Microsoft, October 2026.

Business Central pricing (Canada), Microsoft, October 2026.

Dynamics 365 Finance pricing (US), Microsoft, October 2026.

Dynamics 365 Finance pricing (Canada), Microsoft, October 2026.

Supply Chain Management pricing (US), Microsoft, October 2026.

Supply Chain Management pricing (Canada), Microsoft, October 2026.

Odoo pricing, Odoo, October 2026.

Odoo Success Packs, Odoo, October 2026.