Is Great Plains an ERP System? Dynamics GP Support End Dates & Your Options

Yes — Microsoft Dynamics GP (Great Plains) is a full ERP system, not just accounting software: it covers finance, distribution, HR, payroll and light manufacturing. It is also end-of-life. Microsoft ends GP support on December 31, 2029, with security updates continuing until April 30, 2031.

Updated July 2026.

That leaves finance leaders running Great Plains with a narrow, concrete question: what do you do between now and then? This article is about that decision — running GP as-is inside the supported window, buying third-party support, or migrating — rather than a product tour. ERP Research is independent and sells none of these options.

Microsoft Dynamics GP Support: The Dates That Matter

Microsoft publishes the schedule on its own Dynamics GP lifecycle page. Two dates govern current GP installations, and four more govern older versions still on the Fixed Lifecycle Policy.

Two details are worth flagging, because a lot of published commentary still gets them wrong.

The 2029 date was revised. Microsoft originally announced an end date of September 30, 2029 and later moved it to December 31, 2029. Several widely-shared articles still quote the older date. If you are building a migration plan around a quarter-end, use December 31, 2029.

Security patches outlast support by 16 months. The April 30, 2031 date covers security updates "if needed" only. It is not an extension of technical support, tax tables, or bug fixes — it is a narrow safety net, and planning to sit on it for 16 months is a risk decision, not a support strategy.

GP is already closed to new customers. Alongside the support timeline, Microsoft ended sales of new Dynamics GP perpetual licenses on April 1, 2025 and new subscription licenses on April 1, 2026 — both dates have now passed. Existing customers on an active plan can still add users and modules; a new organisation cannot start on GP at all. That matters for the first option below: staying on GP is a decision to run out a platform that is closed to new entrants, not a neutral hold.

Support Status: The Practical Difference

Support for GP is really four separate things bundled into one annual fee, and the right decision depends on which of them you actually consume:

1. Regulatory and tax updates — year-end payroll tables, 1099 and W-2 formats, sales-tax changes. For most GP users this is the single hardest thing to live without, especially if you run GP Payroll.
2. Technical support — access to Microsoft or your partner when something breaks.
3. Product enhancements — the year's feature updates. GP has been in maintenance mode for years, so this is the least valuable component today.
4. Security updates — patches for vulnerabilities in the product itself.

Current GP (version 18.x) sits under the Modern Lifecycle Policy, introduced in October 2019. Staying supported means staying current: you take at least one of the three updates Microsoft ships each year, typically in June, October and December. Older releases sit under the Fixed Lifecycle Policy with the fixed end dates in the table above. Note that installing any compatible tax release or hotfix on GP 2018 or 2018 R2 moves the install to 18.5 or later — and therefore onto the Modern Lifecycle, with its December 31, 2029 horizon rather than the January 11, 2028 one.

The Three Options Open to a Great Plains User

Option 1: Stay on GP and Run It Through the Supported Window

Keep paying the annual enhancement plan, take the yearly updates, and use GP until the support window closes.

Who this suits: organizations whose processes are stable, whose GP install is heavily customized, and who have a bigger transformation already competing for the same budget and the same finance team. If you are a 40-person distributor with a working system and no growth-driven change coming, buying four more years of stability is a legitimate answer.

The trade-offs: you are paying maintenance on a platform that will not gain meaningful new functionality, and the desktop client keeps aging against what your team sees elsewhere. The real cost is deferred, not avoided — you will still run the migration, just later and probably alongside fewer available partner resources as the deadline approaches. Set a date now for when you start the replacement project, and put it in the plan rather than leaving it to be triggered by the deadline.

Option 2: Buy Third-Party or Partner Support

Independent firms — many staffed by ex-Microsoft and ex-partner GP consultants — will support your GP estate outside Microsoft's programme, usually below the cost of the annual enhancement plan.

Who this suits: organizations that have already committed to replacing GP and need to hold it steady for the 12–36 months the replacement takes, or those on an older version (GP 2015 or 2016) where Microsoft support has already ended and upgrading to 18.x purely to stay supported is not worth the project.

The trade-offs, honestly: third-party providers can fix, tune and keep GP running, but they cannot issue Microsoft product code, so you inherit whatever version you froze on. The critical due-diligence question is regulatory updates — ask specifically how the provider delivers payroll tax tables and statutory reporting changes, who is liable if a filing is wrong, and what their track record is on delivering those on time each January. Get that in writing. A provider strong on break-fix and weak on tax compliance is a poor fit for a finance system.

Third-party support is a bridge with a defined end, not a destination. If you choose it, decide up front what it is a bridge to, and fund that.

Option 3: Migrate to a New ERP

Replace GP — most commonly with Microsoft's designated successor, but the end-of-life moment is also the cheapest opportunity you will get to re-evaluate the market properly.

Who this suits: organizations that are growing, acquiring, adding entities or locations, moving to a cloud-first IT posture, or hitting GP's limits on reporting, multi-entity consolidation or remote access. If any of those apply, paying maintenance to defer is spending money to stand still.

The trade-offs: migration is a data and process project, not a software swap, and it consumes finance-team capacity for months. Budget for data cleansing, integration rebuilds, report parity and training — those, not license fees, are where GP migrations overrun. Starting early matters: partner capacity for GP migrations will tighten as 2029 gets closer.

We cover the migration path — including the step-by-step move to Business Central and how the two products compare — in the full guide:

Microsoft Dynamics GP (Great Plains): overview, pricing and Business Central migration guide

Choosing Between the Three Options

The decision usually resolves faster than people expect, because it is driven by what is happening to your business rather than by the software:

Whichever you pick, the sequencing rule is the same: choose a target end state before you choose a support arrangement. Support decisions made without a destination tend to get renewed indefinitely until the deadline forces a rushed project.

Next Steps

Rather than repeat our product research here, these are the pages that go deeper on each part of the decision:

• Microsoft Dynamics GP overview, modules, pricing and migration steps — the full GP guide, including the GP vs Business Central comparison table
• Dynamics 365 Business Central: independent ERP overview — Microsoft's designated GP successor
• Business Central pricing and implementation costs — what the successor platform actually costs
• Find a certified Microsoft Dynamics implementation partner — partners experienced in GP migrations

Frequently Asked Questions

Can I run Dynamics GP without a support contract?

Yes. Dynamics GP is installed on your own servers and will keep running whether or not you hold an active enhancement plan. Nothing switches off. What you lose is access to updates: no regulatory or tax table updates, no product fixes, no vendor technical support, and no security patches. The software keeps working; the risk sits with you.

Is third-party support for Dynamics GP worth it?

It is worth it in one specific scenario: you have decided to replace GP and need to keep it stable and cheaper for the 12–36 months that takes, or you are on a version Microsoft no longer supports and will not upgrade. It is poor value as an open-ended arrangement, because no third party can issue Microsoft product code. Before signing, confirm in writing how payroll tax and statutory updates are delivered and who carries the liability.

What happens if I stop paying for Dynamics GP support?

Your system continues to operate, but you drop off the update path immediately. The practical consequences show up at year-end, when payroll tax tables and statutory reporting formats change and you have no supported way to apply them. Reinstating the plan later typically means paying back-maintenance, so lapsing is rarely cheaper than it looks. Security exposure compounds quietly in the background.

Is Great Plains an ERP system?

Yes. Great Plains — sold as Microsoft Dynamics GP since Microsoft acquired the company in 2001 — is a modular ERP system for small and mid-sized businesses, not just an accounting package. It covers general ledger, payables and receivables, multi-currency, sales and purchase order processing, inventory, project accounting, HR and payroll, plus light manufacturing in the Extended Pack.