Microsoft Dynamics GP is being retired. It won't stop working overnight, but the support that keeps it safe and compliant is ending — and the risk of staying grows every quarter. Here's the timeline, the risks, and how to plan around them.
Where GP stands.
In January 2025, Microsoft published a firm end-of-life roadmap for Dynamics GP. New sales have already wound down, and the dates that matter most for existing customers — the end of support and tax updates, then the end of security updates — are now fixed. This isn't speculation anymore; the schedule is set.
| Date | What happens |
|---|---|
| April 1, 2025 | New perpetual license sales ended (passed). |
| April 1, 2026 | New subscription sales end — no net-new GP customers. Existing customers can still add users. |
| December 31, 2029 | End of product enhancements, regulatory and tax updates, service packs, and technical support. |
| April 30, 2031 | End of security updates — the official end of life. |
The practical deadline for most businesses is December 31, 2029: once tax and regulatory updates stop, staying compliant on GP gets hard. April 2031 is the hard security cutoff. Dates are current as of early 2026 — Microsoft has occasionally adjusted GP timelines in the past, so confirm against Microsoft's lifecycle page when you build your plan.
What happens when support ends.
| Area | What stops | Why it matters |
|---|---|---|
| Security | No more patches | Unpatched vulnerabilities accumulate — a real exposure for finance data. |
| Payroll & tax | No tax-table updates | Filings and withholdings drift out of compliance. |
| Integrations | No fixes as other systems change | Connections to banks, payroll, and apps degrade over time. |
| Support talent | Shrinking pool | Harder and more expensive to find people who know GP. |
The part Microsoft won't say out loud.
There's a business reality behind the end-of-life schedule that matters as much as the dates. Once a product is being deprecated, it stops being a profit center for the vendor — and resourcing follows the money. In practice, that means a few things for GP customers:
- Support gets thinner, not just shorter. Even before the official cutoff, a deprecated product isn't where the best engineers, the fastest fixes, or the deepest bench are assigned. You may technically still have support, but not the fully-resourced support you had when GP was a growth product.
- The incentive is to move you, not to maintain you. Microsoft's growth is in the cloud, and its preferred destination is Business Central. Expect the messaging, the partner channel, and the “recommended path” to steer you there — because that's where the vendor's interests point, not necessarily where yours do.
- That pressure is a reason to decide deliberately, not reactively. Being pushed toward one platform is exactly when you should step back and evaluate all the options — QuickBooks, Sage Intacct, and NetSuite included — against your actual business, instead of taking the path of least vendor resistance.
How long can you wait?
GP will keep running after support ends, but every quarter on an unsupported platform adds risk. The organizations that come through this well plan to be off GP before they're forced to, so the migration happens on their schedule — with time to choose the right platform, negotiate with implementation partners, and run a clean parallel close. Waiting until it's an emergency removes all of that leverage.
Common migration mistakes to avoid.
- Choosing a platform by vendor default instead of business fit.
- Underestimating data conversion and clean-up.
- Copying the old GP chart of accounts verbatim instead of redesigning it.
- Skipping process redesign — automating the old mess.
- Treating it as an IT project rather than a finance and change-management one.
Questions we hear.
When does Microsoft Dynamics GP reach end of life?
Microsoft published a firm roadmap in January 2025. New subscription sales end April 1, 2026; product enhancements, regulatory and tax updates, and technical support end December 31, 2029; and security updates end April 30, 2031, the official end of life. Confirm against Microsoft's lifecycle page as you plan, but the schedule is now set.
What happens when Great Plains support ends?
No more security patches, no payroll or tax-table updates, no regulatory or compliance fixes, and no official support for issues. The software keeps running, but it stops getting safer or more current, and the risk grows every quarter.
What are the risks of staying on GP after support ends?
Security exposure from unpatched vulnerabilities, compliance risk from outdated tax tables, fragile or failing integrations as other systems update, and a shrinking pool of people who can support the platform. These risks compound over time.
How long can we realistically stay on Great Plains?
GP will keep operating, but most organizations aim to be off before extended support ends so they migrate on their own timeline. Waiting until you're forced to move usually means a rushed project, less leverage with implementation partners, and more risk.
What are common Great Plains migration mistakes?
Choosing a platform by vendor default rather than fit, underestimating data conversion, skipping process redesign, copying the old chart of accounts verbatim, and treating it as an IT project instead of a finance and change-management project.
Not sure which platform fits?
That's exactly the call we help you make — objectively, before you commit to an implementation. We specialize in QuickBooks, Sage Intacct, and NetSuite.
Get a migration consultation
By Heather Engler, Esq.
Founder & Principal, Capital Advisors
Heather blends legal training with deep expertise in bookkeeping and tax compliance, giving her a unique perspective on financial strategy, risk management, and operations. Under her leadership, Capital Advisors serves hundreds of clients across bookkeeping, tax, payroll, and financial advisory. More about the team →