GP 2029 guide

What the Dynamics GP support dates actually mean

A practical planning guide for organisations that depend on GP — without artificial migration urgency.

The short version

You have a deadline, but you also have time to plan properly.

Microsoft will end Dynamics GP product enhancements, regulatory updates, and technical support on 31 December 2029. Security updates and patches, if needed, remain available until 30 April 2031.

Those dates matter. They do not mean every GP customer needs to begin an immediate migration project. The useful response is to understand your environment, reduce avoidable risk, and create options while there is still time.

What changes at each date

31 December 2029

Product support ends

Microsoft ends product enhancements, regulatory and tax updates, and technical support for Dynamics GP.

30 April 2031

Security-update window ends

Microsoft’s stated window for security updates and patches, if needed, comes to an end.

What GP customers should do now

Confirm your exact GP version and lifecycle position.
Keep current with supported GP updates and test patches before production.
Document every integration, customisation, report, and dependent process.
Review backups, recovery procedures, permissions, and SQL Server health.
Identify operational knowledge that currently sits with one person or supplier.
Improve master-data quality and archive obsolete data.
Build a realistic transition roadmap without committing to a migration date.

What you do not need to do

You do not need to select a replacement platform simply because a vendor or partner creates urgency. You do not need to migrate before your organisation has a business case, clean data, documented integrations, internal capacity, and an acceptable risk plan.

Waiting without maintaining GP is risky. Using the available runway deliberately is not.

A sensible planning sequence

01
Stabilise

Resolve recurring issues, establish patch discipline, and confirm recoverability.

02
Document

Map integrations, customisations, reports, users, security, and business-critical processes.

03
Simplify

Remove obsolete data and unnecessary complexity before evaluating any future platform.

04
Assess

Compare the cost, risk, and benefit of remaining on GP against realistic transition options.

05
Decide

Move when the business case and organisational readiness support it — not because of a sales deadline.

Source note: Lifecycle dates are based on Microsoft’s published Dynamics GP guidance. Always confirm the lifecycle position of your specific GP version and circumstances.

View Microsoft’s Dynamics GP guidance →