Microsoft Dynamics AX to QuickBooks
Every version of Dynamics AX is out of support. Not approaching it. Past it.
Microsoft ended extended support for Dynamics AX 2012 R3 on 10 January 2023. AX 2012 and 2012 R2 ended on 12 April 2022. AX 2009 went years before that. If you are running AX today you are running an unsupported ERP with no security updates, and that is a board-level fact rather than an IT preference.
15,000+ migrations completed. 90+ source platforms. Client data processed in Canada.
The dates
The lifecycle, as Microsoft published it
These are not vendor scare tactics. They are Microsoft’s own lifecycle dates, and they have all passed.
| Version | Mainstream support ended | Extended support ended |
|---|---|---|
| Dynamics AX 2012 R3 | 12 October 2021 | 10 January 2023 |
| Dynamics AX 2012 and 2012 R2 | 9 October 2018 | 12 April 2022 |
| Dynamics AX 2009 and earlier | Ended | Ended |
Extended support ending means no security updates, no hotfixes and no regulatory updates. For a finance system that is different from an inconvenience. It is an open risk your auditor is entitled to ask about.
What that actually costs you
Four consequences that are already running
No security updates on a system holding everything
Your ERP holds banking details, supplier records, employee data and the full financial history of the business. Running it on software that will never receive another security patch is a decision, whether or not anyone consciously made it.
The usual mitigation is to isolate the server from the network, which works right up until somebody needs remote access, an integration, or a report that leaves the building.
No regulatory or tax updates
Canadian sales tax rates and rules change. Payroll requirements change. An unsupported ERP receives none of those updates, so every change becomes a manual configuration job somebody has to remember, document and get right.
A shrinking pool of people who can help
AX expertise has been migrating toward Dynamics 365 for years. Finding a consultant who knows AX 2012 in depth is harder and more expensive every year, and the ones who remain are rarely available at short notice when something breaks during close.
Compliance questions you cannot answer well
Auditors, lenders, insurers and enterprise customers increasingly ask whether core systems are vendor-supported. There is no good answer when the honest one is no. That question tends to arrive at the worst possible moment, usually in the middle of a financing round or a large contract review.
The real decision
Dynamics 365, or right-size to QuickBooks
Microsoft’s answer is Dynamics 365 Finance and Operations. For some organizations that is correct. For a large number of Canadian AX sites it is the wrong answer for a specific reason, and it is worth being blunt about which one you are.
When Dynamics 365 is right
You genuinely use the depth. Multi-company consolidation across many legal entities, complex manufacturing with production orders and capacity planning, warehouse management at scale, statutory reporting across several countries. If those describe your operation, you need an ERP and the upgrade path exists.
Be clear-eyed about what it is though. A Dynamics 365 upgrade from AX is a re-implementation, not an upgrade. Budget and timeline accordingly.
When right-sizing is right
AX was frequently sold into Canadian organizations that never needed it. The deployment was scoped for a business that was projected rather than actual, most modules were never switched on, and the annual cost has been carried for years out of inertia rather than value.
If your finance team uses general ledger, receivables, payables, a chart of accounts with dimensions and a reporting pack, that is a QuickBooks Online Advanced or QuickBooks Enterprise workload. Moving to it is not a downgrade. It is stopping the payment for capability you never used.
We will tell you which one you are. Turning down a migration is cheaper for us than delivering the wrong one.
Scope
What moves out of an AX environment
AX stores financial data across a relational schema with dimensions, financial dimension sets and posting profiles that have no direct equivalent in the destination. Mapping that model is the project. Extracting the rows is the easy part.
| Item | Outcome | How we handle it |
|---|---|---|
| Main accounts and chart of accounts | Moves | Rebuilt with correct account and detail types against your actual reporting, not a mechanical copy |
| Financial dimensions | Remodelled | Mapped to classes, locations, custom fields or projects depending on how many dimensions you genuinely use and which reports depend on them |
| Full transaction history | Moves | General journal, customer and vendor transactions, payments, settlements, at transaction level with original dates and references |
| Customers, vendors and contacts | Moves | Including addresses parsed into proper fields, payment terms and outstanding balances |
| Open AR and AP with settlements | Moves | Aged detail reconciled to the source ageing before sign off, with settlement history preserved as transaction links |
| Sales tax codes and groups | Rebuilt | AX item sales tax groups and tax groups rebuilt as GST, HST, PST and QST codes against the correct Canadian agencies |
| Inventory and product master | Moves, with a decision | Costing method in the destination is set once and cannot be changed, so it is agreed in writing before any build work starts |
| Projects and project transactions | Remodelled | AX project accounting has no direct destination equivalent. Mapped to customers, sub-customers and classes, then reconciled on project profitability |
| Production orders and BOMs | No equivalent | If manufacturing is load bearing this is where the conversation turns to whether you should be leaving an ERP at all |
| Posting profiles and setup | Redesigned | Destination posting behaviour is configured deliberately rather than inferred |
| Custom X++ code and modifications | Does not move | Inventoried, and each modification is either replaced with native functionality, replaced with a connected application, or explicitly dropped with your sign-off |
| Management Reporter and SSRS reports | Does not move | The reports that actually leave the building are rebuilt and tested against the source. The rest are archived |
| Workflow and approvals | Redesigned | Rebuilt using the destination’s native approval capability, which is a change management exercise as much as a technical one |
| Attachments and document handling | Does not move | Extracted into a structured archive keyed to the original records |
| Payroll | Basic only | Basic payroll data migrated, detailed pay type and year to date history archived from the source |
Discovery
What we look for before quoting an AX environment
An AX estate is rarely documented accurately, and the gap between what was implemented and what is actually used is usually where the timeline lives.
Which modules are genuinely in use
Almost every AX site we assess was licensed for more than it runs. We check which modules carry live transactions in the last two fiscal years rather than which are switched on. That single check often halves the perceived scope and is the fastest way to find out whether you need an ERP at all.
The dimension model, measured not described
How many financial dimensions exist, how many appear on transactions, and how many appear in reports anybody reads. Those are three different numbers on most sites. Only the third one has to be modelled in the destination.
The customisation inventory
X++ modifications, custom tables, custom fields and third party ISV modules. Each one is a decision: replaced natively, replaced with an application, or dropped. We would rather have that argument in week one than discover it in week nine.
Integrations and what depends on them
Warehouse systems, e-commerce, CRM, payroll providers, EDI and bank connections. Some have a QuickBooks connector and need re-authorising. Some do not and need a replacement chosen, implemented and costed inside the same project.
The reporting pack that leaves the building
The board pack, the lender schedule, the file the external accountant asks for. Those get rebuilt and tested against the AX source before go live. The rest of the report library is archived, and on most AX sites that is the larger half.
Data quality across the years
Long-lived AX environments accumulate inconsistencies: dimension values retired mid-year, accounts repurposed, entities merged. We profile that before quoting because remediation is a phase, not a surprise.
Canada
The Canadian details a global AX plan misses
Sales tax groups are not tax codes
AX models tax through sales tax groups and item sales tax groups intersecting to produce a rate. QuickBooks models it as a code on the transaction. That is a structural translation, not a lookup, and it has to be done so that every historical transaction keeps the effective rate it was actually filed under.
HST at 13 percent in Ontario. 14 percent in Nova Scotia. 15 percent in New Brunswick, Prince Edward Island and Newfoundland and Labrador. GST plus PST in British Columbia at 7 percent, Saskatchewan at 6 percent and Manitoba at 7 percent. GST plus QST in Quebec at 9.975 percent. GST only in Alberta and the territories.
Input tax credits have to be reproducible
An AX environment usually holds several years of filed returns behind it. Move summary balances and you can still file going forward, but you cannot substantiate what was already filed. We migrate at transaction level specifically so the ITC position for every filed period can be rebuilt from the new system.
Six years, at a Canadian place of business
The CRA requires records to be kept for six years from the end of the last tax year they relate to, and to be kept at your place of business in Canada unless you have written permission otherwise. Retiring an AX environment without a readable archive creates a compliance gap. We deliver the archive as part of the project.
Your data is processed in Canada
Extraction, staging, transformation and validation all happen in Canada. We do not move a Canadian client file offshore to be worked on, and it goes in the statement of work rather than being asserted on a web page.
Process
How an AX migration runs
Assessment
We profile the AX environment: modules genuinely in use, dimension structure, transaction volumes by year, customisations, integrations and the reports that leave the building. Output is a written scope with the exclusions named and signed.
Destination design
Chart of accounts, the dimension-to-class-and-location model, tax codes and agencies, custom fields, user roles and approval flow. Designed against your reporting rather than mirroring AX.
Extraction and remediation
Data extracted and audited. Long-lived AX environments frequently carry inconsistencies, and those are resolved inside the migration where they can be reconciled rather than beforehand in a spreadsheet.
Test migration
Full conversion into a sandbox. Trial balance, balance sheet, profit and loss, AR and AP ageing, sales tax summary, project profitability and inventory valuation reconciled line by line against AX. You receive the comparison.
Cutover
Final delta migration in a quiet window. Your team keeps working in AX until we switch. Reconciliation repeats against the final numbers before anyone is asked to use the new system.
Hypercare and archive
Thirty days of support after go live, role training, and your first month end with us on the line. The AX environment is archived in a structured, readable form to meet the six year requirement.
Timeline
How long it takes
AX sits at the complex end of what we migrate. Timelines reflect the dimension model and the customisation inventory rather than transaction volume.
| Profile | Timeline |
|---|---|
| Single legal entity, few dimensions, little customisation, standard modules | 2 to 3 weeks |
| Multiple legal entities, active dimension model, several integrations, project accounting in use | 3 to 6 weeks |
| Heavy X++ customisation, manufacturing or warehouse modules in use, consolidation across entities | 6 to 10 weeks |
Those windows run from kickoff to go live and include the test migration and the reconciliation cycle. They exclude the thirty days of hypercare that follow every project. Software subscriptions are paid to Intuit directly and are never marked up by us.
Proof
A national organization, off an on-premise ERP in four weeks
Dairy Farmers of Canada
A national organization representing more than 9,000 dairy farms moved off an on-premise Sage 300 ERP onto QuickBooks Online Advanced. Zero days of downtime, full data integrity, four weeks to go live. The source environment had data corruption across General Ledger, Accounts Payable and Accounts Receivable, and we provided a production file so the organization kept operating while it was resolved.
Different source platform, same shape of problem. An on-premise ERP that had become a maintenance burden, a distributed team that needed access, and no tolerance for a reconciliation gap.
Questions Canadian finance teams ask
Before you book
Is Dynamics AX really unsupported?
Yes. Microsoft ended extended support for AX 2012 R3 on 10 January 2023, and for AX 2012 and 2012 R2 on 12 April 2022. Earlier versions ended before that. No version of AX receives security updates today.
Can we just keep running it?
Technically the software keeps working. What stops is security patching, hotfixes and regulatory updates, and what starts is a question your auditor, insurer or enterprise customers are entitled to ask. Many organizations run unsupported for a while. Few do it deliberately once the position is written down.
Shouldn’t we move to Dynamics 365 instead?
Sometimes. If you genuinely use multi-entity consolidation, complex manufacturing or warehouse management at scale, an ERP is still the right category and we will say so. Understand that moving AX to Dynamics 365 is a re-implementation rather than an upgrade, and price it that way before comparing.
What happens to our financial dimensions?
They are remodelled rather than mapped one to one. Most AX sites use two or three dimensions meaningfully and carry several more that nobody reports on. We identify which is which from your actual reports, then model the live ones as classes, locations, projects or custom fields.
We have significant X++ customisation. Does that block the project?
No, but it defines the scope. Every modification is inventoried and then either replaced with native functionality, replaced with a connected application, or explicitly dropped with your sign-off. Nothing gets discovered missing after cutover.
Will our GST and HST history survive?
Yes, when the conversion runs at transaction level. AX tax groups are translated into Canadian tax codes against the correct agencies, and we reconcile a sales tax summary from both systems before go live so you can see the position.
How much history can we bring?
All of it in most cases. The practical question is whether you want to. Many teams bring two to three years live and keep the rest as a structured archive, which also satisfies the six year record requirement.
What happens to the AX environment afterwards?
It is archived in a structured, readable form and handed to you, built to meet the CRA requirement to keep records for six years at a place of business in Canada unless you have written permission otherwise.
Accounting firm with a client on this platform?
Refer, white-label, or co-deliver the migration with our team while you keep the client relationship.
Playbooks
Before you decide, read the mechanics
Short, checkable pieces on the contract clauses and system limits that usually decide this. Each one names a document or a report you already own.
The uplift clause costs more than the discount you win
A 6 percent discount erased by a 7 percent annual escalator. All three years priced out, and the four documents to pull before you respond to a renewal.
Your renewal did not go up, your discount ran out
Why a 20 percent introductory discount unwinds as a 25 percent increase, and where in the original order form that condition is written.
Discovery Call
Book a Dynamics AX migration assessment
Ninety minutes on your modules in use, your dimension model and your customisation inventory. A fixed-scope quote after, or an honest recommendation to move to Dynamics 365 instead.
