Microsoft Dynamics GP End of Life: The Official Timeline

In September 2024, Microsoft announced the end of support for Dynamics GP, closing out a product line that began as Great Plains Software in the 1980s. Here are the official dates, what each one means, and why the practical deadline arrives sooner than 2029.

The Official Dates

  • September 2024 Microsoft publicly announced end of support for Dynamics GP on the Dynamics 365 blog.
  • April 1, 2025 End of new perpetual license sales to new customers.
  • April 1, 2026 End of new subscription license sales to new customers.
  • December 31, 2029 End of product support, product enhancements, service packs, and tax and regulatory updates. (Microsoft originally announced September 30, 2029, then extended to year-end in January 2025 so customers could complete a final full payroll/tax year.)
  • April 30, 2031 End of security patches. After this date Dynamics GP receives no updates of any kind.

Common misconception: you may see earlier dates (such as 2028) circulating online. The authoritative source is Microsoft's own lifecycle documentation: mainstream product support ends December 31, 2029 and security updates end April 30, 2031. Always confirm against Microsoft's published lifecycle policy.

Sources: Microsoft's end-of-support announcement and the Dynamics GP lifecycle policy on Microsoft Learn.

What "End of Support" Actually Means for Your Business

No more tax and regulatory updates (the real deadline)

For most GP customers, the binding constraint is not security — it's compliance. After December 31, 2029, Microsoft will not ship payroll tax tables, year-end updates, or regulatory changes. If you process payroll or produce statutory filings from GP, the 2029 year-end update is the last one you will receive.

No more fixes or support tickets

After product support ends, there are no service packs, hotfixes, or Microsoft support incidents. Issues that surface — for example after a Windows Server or SQL Server upgrade — are yours to work around.

Security exposure after April 2031

An unpatched system of record for your general ledger, vendor master, and payroll data is a serious exposure. Cyber-insurance questionnaires and financial audits increasingly flag unsupported software.

A shrinking ecosystem before the dates hit

Well before 2029, expect the practical ecosystem to thin out: fewer GP-experienced consultants, ISV add-on vendors sunsetting their GP products, and integrations that stop being tested against GP. Ecosystem decay is gradual, and it has already begun.

Why You Shouldn't Wait Until 2029

A mid-market ERP replacement typically takes 12–18 months from evaluation to go-live: requirements and vendor selection (2–4 months), data cleansing and migration (3–6 months), configuration, testing, and training (4–8 months), plus a stabilization period — ideally aligned to your fiscal year-end. Counting backward from December 2029, businesses that want a calm, well-tested cutover should be in active evaluation during 2026–2027.

Waiting also concentrates demand: as the deadline approaches, implementation partners will be booked out by other migrating GP customers, and rushed projects cost more and fail more often.

Next step: see how Totaum compares to Dynamics GP for product businesses, or jump straight to the migration planning guide.