Great Plains is on its way out, and the smart money is already moving. Microsoft has closed the door on new GP sales, and the support that keeps the system compliant runs dry at the end of 2029, with security coverage trailing off in 2031. None of that forces a rushed exit today but what it does mean is that GP has quietly shifted from a system you build on to a system you plan around, and the businesses that treat 2026 as their starting line, rather than 2029 as their finish line, end up with the calmest projects and the best terms.
Request More Info About Dynamics GP End of Life
Table of contents
- Is Dynamics GP Being Discontinued?
- The End-of-Life Timeline for GP, and What It Actually Means
- The Real Cost of Waiting to Change ERP’s
- Business Central Is the Default, Not the Decision
- Where NetSuite Fits for GP Customers
- Action Your Great Plains Migration With GURUS Solutions
- Frequently Asked Questions
Is Dynamics GP Being Discontinued?
New GP licenses are no longer for sale in any form, which quietly changes what the product is. Microsoft ended perpetual license sales in April 2025 and subscription sales in April 2026, and while existing customers can still add users, no one can start a fresh GP deployment. Read that plainly and the conclusion writes itself: nobody is choosing Great Plains anymore. Everyone still on it is on a platform they will eventually leave. The only decisions left are when to go and where to land, and both reward a business that starts thinking early.
We built our NetSuite vs. Dynamics GP comparison to handle the feature-by-feature detail. This piece is about something that comparison only brushes against, which is why the timing of your move carries as much weight as where you end up.
The End-of-Life Timeline for GP, and What It Actually Means
The next milestone is the one finance teams should circle. At the close of 2029, Microsoft stops shipping enhancements, service packs, technical support, and, critically, the regulatory and tax updates that keep the system filing correctly.
After that point the software still runs, but an ERP that no longer receives payroll and tax-table updates becomes a reporting liability rather than a reliable tool. Two years later, in the spring of 2031, the final security patches stop and GP reaches its formal end of life.
A quick correction on a figure that still circulates: if you have read that support ends in 2028, that guidance is stale. Microsoft nudged the cutoff from October 2029 to the end of December so customers could run one last year-end close on supported software.
There is also a trap in treating 2029 as a universal deadline. Older builds are already dark, with GP 2016 having lost extended support in mid-2026 and GP 2018 losing it in early 2028. Plenty of companies assume they have years of runway when their specific version leaves them exposed much sooner. The first question in any planning conversation should be which version you are actually running.
The Real Cost of Waiting to Change ERP’s
The instinct to wait is understandable. GP works, the deadline looks distant, and no one likes an ERP project. The problem is that waiting is not free, and the meter runs in three directions at once.
You pay more to stand still
Holding position on GP costs more every year, not less. The annual plan rates that keep GP maintained have crept steadily upward, with Enhancement pricing rising from 16 percent to 20 percent over roughly five years and Advantage pricing climbing from 18 percent to 22 percent.
At the same time, the reward for making the jump keeps shrinking. The migration incentives Microsoft once offered have been cut roughly in half, sliding from around 60 percent to near 30 percent. Rising cost to stay, falling reward to leave. The gap only widens from here, and it widens against the company that waits.
The line is already forming
This is the number that should reframe the whole conversation. Microsoft counts something like 15,000 companies still on GP in the US, and only about 40 partners have the depth to run these migrations at scale. Do the math on realistic project throughput and the entire ecosystem can move roughly 1,000 companies a year, which means the backlog would take more than a decade and a half to clear even though core support ends in 2029. That is not a comfortable margin.
Early movers get experienced teams and a schedule they control. The companies that wait for the deadline to feel real will be reaching for the same scarce specialists at the exact moment everyone else does.
The people who know GP are leaving
The last pressure is the quietest. The pool of consultants fluent in Dexterity, the layer GP customizations are written in, thins out a little more each year as veterans retire or retrain on newer platforms. Every custom report, every integration, every workaround your business depends on needs someone who understands it to move it safely.
Those people are not being replaced. Wait too long and the expertise your migration requires may have already walked out the door.
Business Central Is the Default, Not the Decision
Search the topic and you will find a wall of advice pointing GP customers toward Dynamics 365 Business Central, most of it written by the partners who sell it. That guidance is not wrong so much as it is incomplete.
Business Central is where Microsoft would like its GP customers to go, and that is a different thing from where a given business ought to go. Even coverage sympathetic to Microsoft's own path acknowledges the gap.
Business Central suits some companies well, but it is not the automatic answer for every GP replacement, and businesses with more operational complexity or bigger ambitions in reporting, manufacturing, and growth are often better served elsewhere, NetSuite included.
End of life forces evaluation, whether you wanted one or not. The mistake is letting a shared vendor logo make the decision for you. The move worth making is a real comparison against your own requirements, and for a large slice of the GP base, that comparison does not end at Business Central.
Where NetSuite Fits for GP Customers
The GP customers most ready to move tend to look alike. Several legal entities. A growth plan that has outrun the system. A finance function stitched together with add-ons and month-end reconciliations that everyone dreads. That profile happens to describe exactly the terrain where NetSuite is strongest.
Even comparisons that tilt toward Business Central give NetSuite its due here. NetSuite leads on native multi-subsidiary consolidation and on managing tax compliance across regions, which is precisely the close-cycle pain that multi-entity GP shops feel every single period.
And where GP was built for an on-premise world it never fully left, NetSuite brings finance, CRM, supply chain, ecommerce, analytics, and operations onto one cloud platform instead of a core ledger surrounded by bolt-ons.
Then there is AI, which is Microsoft's headline pitch this year. Business Central's 2026 release introduced AI agents for tasks like payables and sales orders that GP simply cannot reach. That is a fair strike against staying on GP, and it deserves a direct response rather than a dodge.
Automation of that kind now lives in modern cloud ERP as a category, and NetSuite brings its own AI capabilities to that same table. So the question is not whether to leave GP for something that can keep pace. It is which cloud platform fits your business best. For multi-entity, growth-minded companies coming off Great Plains, that answer is very often NetSuite.
Action Your Great Plains Migration With GURUS Solutions
The best time to plan is while you still hold the choice of when, how, and with whom. For over 20 years and across 2,500+ projects, GURUS Solutions has moved mid-market companies onto NetSuite and helped them get more from it once they arrive. We evaluate the move on your terms, map your GP data and customizations honestly, and run a migration shaped around your calendar rather than a market-wide rush.
Contact GURUS Solutions to discuss the end of life of Dynamics GP.
Frequently Asked Questions
Is Microsoft Dynamics GP being discontinued?
Effectively, yes. Sales have ended, core support runs out at the close of 2029, and security coverage ends in 2031. You can keep running GP and adding users in the meantime, but it is a system winding down on a fixed schedule.
When does Dynamics GP support actually end?
The date that matters most is the end of 2029, when Microsoft stops delivering enhancements, technical support, and the tax and regulatory updates that keep you compliant. Security patches continue until spring 2031. Note that several older versions, GP 2016 among them, are already unsupported.
Do I have to migrate to Business Central?
No. It is Microsoft's recommended path, not a requirement. Depending on your complexity, reporting needs, and growth plans, a platform like NetSuite may be the better fit. The deadline forces a decision, not a specific destination.
Why move now instead of closer to 2029?
Because every part of the equation works against waiting. Maintenance rates keep climbing while migration incentives keep falling, and the small pool of experienced partners means the industry backlog stretches well past a decade. Starting early buys better pricing, a stronger partner, and a timeline you set yourself.
Is NetSuite a good replacement for Great Plains?
For a lot of GP customers, yes. Its strengths in native multi-subsidiary consolidation and cross-region compliance line up with where growing GP shops feel the ceiling, and it unifies finance, operations, and reporting on one cloud platform rather than a patchwork.