Dynamics GP end of life: what it means and what to do next.
Dynamics GP end of life comes in two steps. Microsoft ends product enhancements, tax updates and technical support on December 31, 2029, and makes security patches available, if needed, until April 30, 2031. GP will not switch off, but after those dates you run it unsupported. This guide covers the dates, the realistic options and a planning sequence for the move.
Updated

What has Microsoft announced about Dynamics GP end of life?
Microsoft announced that it would stop selling new Dynamics GP licenses to new customers from April 1, 2025. It also set out a schedule for winding down the product for existing customers. That schedule ends product enhancements and regulatory updates, such as US payroll tax table updates, at one point, and security updates and support at a later point.
Microsoft's Dynamics GP servicing page sets two end dates. Product enhancements, regulatory (tax) updates and technical support end on December 31, 2029. The earlier announced date was September 30, 2029. Security updates, if they are needed, stay available until April 30, 2031. The Lifecycle page lists GP under the Modern Lifecycle Policy with a retirement date of January 1, 2030. Plan against these pages rather than against dates passed on secondhand.
Which Dynamics GP end of life dates should you plan around?
What Dynamics GP end of life means in practice
The practical meaning is simple even without the exact dates. GP still works today and will keep working for a while, but its ecosystem is shrinking. Fewer ISVs will keep their GP add-ons current, fewer consultants will specialize in it, and tax and compliance changes will eventually stop arriving. Each year you wait, the move gets no easier and the pool of people who know GP well gets smaller.
Four realistic paths for a GP company
Move to Business Central online
Microsoft's intended destination for GP customers, with a cloud migration tool that brings GP master data, open items and selected history across.
- ✓Familiar Microsoft ecosystem
- ✓Continuous updates in the cloud
- ✓Some GP add-ons need a new equivalent
Stay on GP for now
Reasonable for a short, planned period if the system is stable and a move is scheduled. Risky if it becomes the default.
- ✓No project cost this year
- ✓Payroll and tax updates eventually stop
- ✓Add-on and skills support thins out
Move to Dynamics 365 Finance
Suits larger or more complex groups with many entities, heavy global requirements or high transaction volumes.
- ✓Broader enterprise scope
- ✓Larger project and license commitment
- ✓Worth it only when complexity demands it
Choose another vendor
NetSuite, Sage Intacct, Acumatica and others are valid options, and a GP exit is a natural moment to compare.
- ✓Every option needs a full migration
- ✓Compare on fit, not on the logo
- ✓See our comparison pages first
Staying on GP versus moving: the trade-offs
What to inventory in GP before you decide
- ✓Every module in use, including those enabled but rarely touched
- ✓Third-party add-ons and what each one does for you today
- ✓Customizations, Dexterity code and custom SQL reports
- ✓Integrations to banks, ecommerce, CRM, payroll and EDI partners
- ✓Companies in the GP instance and how intercompany works between them
- ✓How much history finance and audit really need to reach
A planning sequence that avoids a rushed exit
- 1
Confirm your dates
Read the Microsoft Lifecycle page for your GP version and note when payroll, tax and security updates stop.
- 2
Take stock of the system
Work through the inventory above so you know exactly what you must replace, rebuild or retire.
- 3
Choose a destination
Compare Business Central with the alternatives against your actual requirements, not a feature brochure. This is where you decide what comes next after Dynamics GP end of life.
- 4
Decide on history
Choose between open items and balances only, summarized history, or detailed history, and keep GP read-only for the rest.
- 5
Pick a cutover point
Aim for a fiscal period start that avoids audit, year end and peak season, and leave time to rehearse.
How GP concepts carry into Business Central
GP users usually find the move less foreign than they fear. Both systems are built around a general ledger with subledgers for receivables, payables, inventory and fixed assets. GP account segments typically become a main account plus dimensions in Business Central, which gives more flexible reporting without the long account strings. Checkbook IDs become bank accounts, classes become posting groups and templates, and batches become journals.
The bigger changes are around the edges. Management Reporter and FRx layouts are rebuilt as Business Central financial reports or Power BI dashboards. Payroll, which many US GP customers ran inside GP, moves to a payroll provider that posts summaries into the ledger. Custom Dexterity screens are either replaced by standard features, by an AppSource app, or by a small extension written in AL, Business Central's development language.
After the Dynamics GP end of life dates, this mapping is the next thing to get right. It keeps the move from feeling like a rebuild of every habit your team has.
Which Microsoft sources back this guide?
Microsoft Lifecycle, Dynamics GP: learn.microsoft.com/en-us/lifecycle/products/dynamics-gp. Dynamics GP servicing information: learn.microsoft.com/en-us/dynamics-gp/terms/lifecycle. Both checked November 6, 2026.
Microsoft updates its documentation often, so confirm the current wording on the page itself before you act on it.
GP end-of-life questions
Will Dynamics GP stop working on a certain date?
No, the software will not switch off, but updates and support end on Microsoft's published schedule. After that, you would run it without security patches, tax updates or Microsoft support. That is a growing risk for a system holding financial data. Check the Microsoft Lifecycle page for the dates that apply to your version.
Is Business Central the only path Microsoft offers GP users?
Business Central is Microsoft's intended path for most GP customers, but not the only option. Larger or more complex organizations may be better served by Dynamics 365 Finance. You are also free to choose another vendor. The right answer depends on your size, complexity and requirements.
Can our GP history come across to Business Central?
Yes, Microsoft provides a cloud migration tool that moves GP master data, open transactions and a chosen amount of history. Many companies bring summarized history and keep GP available read-only for detailed lookups. Detailed history adds effort and is worth moving only if people will truly use it. We help you decide based on audit and reporting needs.
More Dynamics GP end of life questions: what to do next
What happens to our GP add-ons?
Each add-on needs a replacement, a rebuild or a decision to retire it. Many common GP add-ons have Business Central equivalents on AppSource, sometimes from the same vendor. Some functions are standard in Business Central and need nothing extra. Listing every add-on early prevents surprises late in the project.
When should we start planning?
Start planning now, even if the move itself happens later. Taking stock of modules, add-ons and integrations is the cheapest next step after the Dynamics GP end of life news. It also makes every later decision faster. Partners and specialists get busier as deadlines approach. Starting early lets you pick a cutover date that suits the business rather than one forced by the calendar.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.