Microsoft has now set firm dates for the end of Dynamics GP. Mainstream support, covering product updates, regulatory changes, payroll updates and technical support, ends on 31 December 2029. Security patches continue until 30 April 2031, after which Dynamics GP receives no support of any kind from Microsoft.
If you are running Dynamics GP today, you have time. The system will keep working. But the clock is running on a specific set of capabilities, and the gap between the system you have now and the system you will have after December 2029 will widen in ways that matter commercially. This article explains what those dates mean in plain terms, what the real risks are, and what a good GP partner should be doing with you right now regardless of when you plan to migrate.
The Two Dates and What They Each Mean
It is worth being precise about what Microsoft has confirmed, because there has been some confusion in the market about what the dates cover.
31 December 2029: Mainstream support ends
This is the date that matters most for the majority of GP businesses. After 31 December 2029, Microsoft will no longer provide product enhancements, regulatory and tax updates, payroll updates, hotfixes, or technical support for Dynamics GP. This means:
If HMRC introduces a change to Making Tax Digital requirements that requires a system update, that update will not come. If the payroll tax tables change for the new financial year, the update will not come. If a bug is discovered in a core GP function, the fix will not come. If your version of GP develops a compatibility problem with a Windows or SQL Server update, Microsoft will not address it.
For businesses using GP for payroll, the December 2029 date is the operative deadline because the last payroll update from Microsoft will cover that tax year. After that, payroll users are on their own.
30 April 2031: Extended support ends
Between January 2030 and April 2031, Microsoft will continue to issue security patches for Dynamics GP if critical vulnerabilities are identified. This is often described as the "extended support" period, but it is important to understand what it does not cover: it does not include tax updates, payroll updates, regulatory compliance changes, feature fixes, or technical support. It covers critical security patches and nothing else, and only where Microsoft determines a patch is necessary.
After April 2031, Dynamics GP receives nothing further from Microsoft. The system continues to function but is entirely unsupported.
What This Means in Practice for a Typical GP Business
The impact of the 2029 date depends heavily on how your business uses GP. A business using GP primarily for financial ledger management, where the key workflows are chart of accounts, purchase ledger, sales ledger, and management reporting, will feel the impact differently from a business relying on GP's payroll module or running custom integrations against the GP codebase.
If you use GP payroll
The December 2029 date is your hard deadline. After that date, the annual payroll and tax table updates that GP requires to calculate deductions correctly will no longer come from Microsoft. Running payroll on outdated tax tables creates compliance exposure with HMRC. Payroll users should treat 2029 as their go-live deadline for Business Central, which means starting the migration process no later than early 2028, and ideally by mid-2027.
If you rely on Making Tax Digital compliance
HMRC's MTD programme continues to expand. MTD for Income Tax is already in phases of rollout and the scope of digital record-keeping requirements will likely extend further before 2029. System updates required to maintain MTD compliance will not be delivered into GP after December 2029. Whether that becomes a material problem depends on what MTD looks like in 2029, which is an unknown worth treating as a risk rather than an assumption.
If you run integrations with modern platforms
GP was not built with an open API architecture. Connecting GP to modern e-commerce platforms, carrier management systems, or third-party applications typically requires bespoke middleware or ISV add-ons. Those add-ons have their own support lifecycles, and many ISV solutions built for GP are already being wound down as their vendors shift development resource to Business Central. Integration reliability is likely to degrade before the Microsoft support dates arrive, simply because the ecosystem around GP is contracting.
If your primary use is financial management without payroll
You have more time. The ledger, reporting, and purchasing functions that most businesses use GP for daily will continue to work after 2029 without immediate compliance exposure. The risk profile shifts gradually rather than immediately, and the dominant argument for planning now is commercial rather than urgent: doing the migration on your own timeline is significantly less expensive and disruptive than doing it under deadline pressure.
The Risks That Accumulate Silently
The support timeline creates four specific risks that most GP businesses have not formally assessed. None of them requires immediate action today. All of them are worth understanding and tracking.
Cyber insurance policy terms
A growing number of cyber insurers are reviewing the technology environments of policy holders as part of underwriting and renewal assessments. Running business-critical finance software on a system that is in a declining support lifecycle, or that will reach end of mainstream support during the policy period, is beginning to appear in insurers' risk assessment criteria. It is worth reviewing your current cyber policy for any clauses that reference software support status, and raising the question with your broker at the next renewal.
Third-party add-on lifecycles
The ISV ecosystem for Dynamics GP is actively contracting. Reporting tools, bank connectivity add-ons, payroll extensions, and sector-specific modules built for GP are being wound down as their developers stop investing in GP-compatible versions. If your GP environment relies on third-party add-ons, check with each vendor what their support roadmap for GP looks like. Some are already on fixed timelines that end before 2029.
Integration maintenance costs
Integrations between GP and other systems, whether to e-commerce platforms, carrier systems, or bank feeds, require ongoing maintenance as the connected systems update their own APIs and interfaces. GP's closed architecture means that maintaining these integrations requires custom development each time. As GP moves closer to end of mainstream support, the pool of developers able and willing to do that work shrinks, and the cost of maintaining integrations rises accordingly.
The 2028 resource crunch
Businesses that decide to migrate in 2028 or 2029 will find a significantly more constrained implementation market than those migrating in 2025 or 2026. Experienced Business Central implementation partners with deep GP migration knowledge are a finite resource. As the deadline approaches, demand increases, partner capacity tightens, and project costs rise. Businesses that start their planning conversation now are choosing their implementation partner; businesses starting in 2028 are taking whoever is available.
What a Good GP Partner Should Be Doing Right Now
The mainstream support end date is three years away. That does not mean your GP partner's responsibilities have not already changed. A partner who is treating GP support as business as usual, closing tickets and sending changelog links, is not preparing you for what is coming. A partner who is actively supporting GP businesses should be doing three things in parallel.
First, keeping your current GP environment properly maintained. That means staying current with available GP updates, monitoring the ISV and integration landscape for add-ons that are approaching end-of-life, and proactively raising any configuration or security issues before they become problems.
Second, having an honest conversation about your migration options and timeline. Not a sales pitch for the most complex implementation possible, but a frank assessment of what your specific GP environment would require to move to Business Central, what the timeline looks like, and what the commercial case is for starting now versus waiting.
Third, connecting the migration conversation to what Business Central can do today that GP cannot. The case for migrating is not just about the 2029 date. It is about the AI capability, the real-time reporting, the open API architecture, and the twice-yearly improvement cadence that comes with Business Central. A partner who only talks about migration risk without talking about what you gain on the other side is giving you half the picture.
The Right First Step
If your GP environment is stable and your partner is engaged, you are in a reasonable position. The priority is to get a clear picture of what your migration would involve before the timeline starts narrowing your options.
Advantage's Transformation Sprint is a free, no-obligation session that maps your current GP environment, assesses the migration path to Business Central, and produces a prioritised roadmap you can act on at your own pace. It is the practical starting point before any commercial commitment.
If you are not confident your current partner is having the right conversations with you about 2029 and beyond, we are also happy to provide a second opinion. Contact our GP team or call 020 3004 4600.
Related Resources
- GP to Business Central: What the Migration Actually Involves
- Dynamics GP vs Business Central in 2026: What You Are Missing and Whether It Matters
- Switching Dynamics GP Support Partner: What Changes and What Stays the Same
- Dynamics GP Support and Migration
- Data Migration and Legacy Modernisation
- Advantage Transformation Sprint
Frequently Asked Questions — Dynamics GP Support
Common questions about what the Dynamics GP mainstream support end date means for UK businesses, and what action to take.
When does Dynamics GP mainstream support end?
Microsoft has confirmed that mainstream support for Dynamics GP ends on 31 December 2029. This is the final date for product enhancements, regulatory and tax updates, payroll updates, hotfixes, and technical support from Microsoft. Security patches only continue until 30 April 2031, after which Dynamics GP receives no further support of any kind from Microsoft.
What is the difference between mainstream support and extended support for Dynamics GP?
Mainstream support covers the full range of Microsoft support: product enhancements, new features, regulatory and payroll updates, hotfixes, bug fixes, and technical support. Extended support covers security patches only, and only where Microsoft determines a patch is necessary. After mainstream support ends on 31 December 2029, Dynamics GP will no longer receive tax updates, payroll updates, bug fixes, or product improvements from Microsoft.
Can I still use Dynamics GP after 2029?
Yes. Your Dynamics GP system does not stop working in December 2029. What changes is that you will no longer receive tax updates, payroll updates, regulatory compliance changes, or bug fixes from Microsoft. Security patches continue until April 2031. Businesses using GP for payroll will feel the impact of the 2029 date most directly and should treat it as a functional go-live deadline for Business Central rather than a distant planning horizon.
Why should I start planning a GP migration now rather than waiting until closer to 2029?
A properly executed GP to Business Central migration typically takes 9 to 18 months from first conversation to go-live. Businesses that start planning in 2026 or early 2027 have a full choice of implementation partners at current market rates. Businesses that wait until 2028 are competing for resource at peak demand alongside every other organisation that also waited, which drives up project cost and extends timelines. Planning now gives the flexibility to migrate on your own terms rather than against a calendar.
