The Retirement of Dynamics GP: What Your Specific Version Means for You

The Retirement of Dynamics GP: What Your Specific Version Means for You

Most articles about the Dynamics GP retirement treat it as one single deadline. It isn’t. Depending on which version of GP your business is actually running, your real support window could already be closing, or it could still stretch out for several more years. That distinction rarely gets explained clearly, and it’s exactly the detail that should be shaping your planning right now.

Microsoft confirmed the official retirement date for Dynamics GP: December 31, 2029, when product support and updates end for all versions, with security patches continuing a bit longer, through April 30, 2031. That’s the headline. But “all versions” is doing a lot of quiet work in that sentence, because not every version of GP is actually covered by that date in the same way.

Two Different Support Policies, Two Very Different Timelines

Here’s the detail most coverage of this announcement skips entirely: Dynamics GP versions fall under one of two different Microsoft support policies, and which one applies to your version changes your real timeline significantly.

The Modern Lifecycle Policy covers the current, actively updated version of GP (currently v18.7 as of this writing). Customers on this version continue receiving product updates, regulatory and tax updates, and security patches through the full announced timeline, meaning support runs through December 31, 2029, with security patches following through April 30, 2031.

The Fixed Lifecycle Policy covers older, legacy GP versions that stopped receiving regular updates some time ago. If your business is running one of these versions, your support window isn’t tied to the 2029 headline date at all. It’s already shorter, and in some cases, it’s already closed.

Support End Dates by Dynamics GP Version

Here’s how the actual timeline breaks down depending on your version:

GP Version Support Policy Extended Support Ends
GP 2016 and 2016 R2 Fixed Lifecycle July 14, 2026
GP 2018 and 2018 R2 Fixed Lifecycle January 2028
GP 18.x (current, v18.7) Modern Lifecycle December 31, 2029 (product updates), April 30, 2031 (security)

If your business is running GP 2016 or 2016 R2, extended support closes in mid-2026, years ahead of the widely quoted 2029 date. If you’re on GP 2018 or 2018 R2, your window closes in early 2028, still well before the general retirement date most articles reference. Only businesses on the current, actively maintained version of GP actually get the full runway through 2029 and 2031.

This is the single most important thing to check before making any plan based on GP’s retirement: confirm which version you’re actually running, and don’t assume the 2029 date automatically applies to you.

What Happens After April 30, 2031, Specifically

Beyond the support and security patch dates, there’s a second, more absolute deadline worth understanding clearly. Effective April 30, 2031, Service Plan coverage for Dynamics GP ends entirely, and subscription licenses can no longer be renewed. Perpetual license users on existing systems can no longer add new users, and subscription access through Services Provider License Agreement (SPLA) licensing ends as well.

In practical terms, that means after April 30, 2031, businesses using GP under a subscription license will lose access to the software altogether, not just support for it. Perpetual license holders can likely continue running the software they already have installed, but without any path to expand licensing or receive further support of any kind.

Why Microsoft Is Retiring Dynamics GP

It’s worth understanding the reasoning behind this decision, not just the dates. Microsoft has been clear that its ongoing investment is shifting toward cloud technology, driven by the belief that cloud-based solutions deliver stronger security, deeper AI capabilities, and better long-term business performance than on-premises software can offer.

That shift shows up directly in how Microsoft is investing in Dynamics 365 Business Central, which Microsoft has positioned as its flagship ERP platform for small and mid-sized businesses going forward. Business Central is built specifically to take advantage of cloud and AI computing in ways an on-premises platform built decades ago simply can’t be retrofitted to match. Retiring GP isn’t really about the product falling short technically. It’s about where Microsoft has decided its future investment, and its customers’ future needs, are actually headed.

What This Means for Your Planning

Knowing your specific version’s timeline changes the planning conversation considerably. A business on GP 2016 has a meaningfully different runway than a business on the current v18.7 release, and treating them the same way leads to either unnecessary panic or dangerous complacency, depending on which direction the mistake runs.

A few practical steps worth taking now, regardless of your version:

  1. Confirm your exact GP version and build number. Don’t assume. Check it directly, since the difference between versions can mean years of difference in your actual support timeline.
  2. Identify which lifecycle policy applies to you. If you’re not certain whether you fall under Fixed or Modern Lifecycle support, that’s worth confirming with a partner who can check your specific environment.
  3. If you’re on a legacy version, treat your timeline as already active, not future. Businesses on GP 2016 or 2018 in particular are closer to the edge of their support window than the general 2029 headline suggests.
  4. Use whatever runway you have to plan deliberately. Whether your realistic window is one year or four, the planning itself, budget, risk assessment, staffing, and data strategy, should start now rather than at the deadline.

For a fuller breakdown of what to actually put in that plan, see Dynamics GP in 2027: What Should Be in Your Business Plan.

How Nevas Technologies Can Help

Understanding exactly where your business stands in the Dynamics GP retirement timeline is the first real step toward a plan that actually fits your situation, not a generic one built around the headline date alone. Nevas Technologies has spent over 20 years helping businesses navigate Microsoft Dynamics transitions, with 200+ clients and a team of certified Microsoft Dynamics consultants who understand the version-specific realities of legacy GP environments.

Here’s how we help:

  1. Confirming your exact GP version, build, and applicable support policy, so your planning is based on your real timeline
  2. Assessing your current environment, customizations, and integrations to inform a realistic transition roadmap
  3. Helping you weigh the cost and risk of staying on GP short term against the benefits of migrating sooner
  4. Planning and executing a structured migration to Business Central when you’re ready to move
  5. Providing ongoing support throughout the transition, from assessment through go-live

Frequently Asked Questions

Does the December 31, 2029 retirement date apply to every version of Dynamics GP?

No. That date applies to the current, actively maintained version of GP under Microsoft’s Modern Lifecycle Policy. Legacy versions under the Fixed Lifecycle Policy, including GP 2016, 2016 R2, 2018, and 2018 R2, have earlier extended support end dates.

When does support end for Dynamics GP 2016?

Extended support for GP 2016 and 2016 R2 ends July 14, 2026.

When does support end for Dynamics GP 2018?

Extended support for GP 2018 and 2018 R2 ends in January 2028 (specifically, January 12 at 6:59 a.m. Pacific Time, per Microsoft’s official lifecycle listing).

What happens to Dynamics GP subscription licenses after April 30, 2031?

Service Plan coverage ends entirely on that date, and subscription licenses can no longer be renewed. Subscription users will lose access to the software at that point, while perpetual license holders can likely continue using their existing installation without further support or the ability to add users.

How do I find out which version of Dynamics GP my business is running?

Your version and build number can typically be found within the application itself, or confirmed by your Microsoft Dynamics partner as part of an environment assessment.

Why is Microsoft retiring Dynamics GP instead of continuing to update it?

Microsoft has shifted its ERP investment toward cloud-based platforms, citing stronger security, AI capabilities, and long-term business performance. Dynamics 365 Business Central is now positioned as Microsoft’s primary ERP platform for small and mid-sized businesses going forward.

Next Steps

The Dynamics GP retirement isn’t a single deadline that applies equally to everyone. Your real timeline depends on your specific version, and confirming that timeline is the first step toward a transition plan that actually fits your business.

Schedule a free GP version and environment assessment with our Microsoft Dynamics team, or get a custom quote to start planning your path to Business Central.

John Solomon
About the author:

John Solomon

Director, Business Central

John Solomon is a technology professional with extensive experience helping businesses improve their systems, processes, and digital transformation.

You might also like: