Microsoft stopped selling new Dynamics GP (Great Plains payroll) licenses in April 2026. Mainstream payroll support ends December 31, 2029. Discretionary security patches will continue through April 2031. Existing GP environments will keep functioning past that point, but without tax updates, hotfixes, or vendor support.

Organizations still running payroll on GP should consider a migration plan. Preserving a decade or more of payroll and HR history through that transition is where most plans fall short.

---

Key Takeaways

• Dynamics GP isn’t shutting down immediately, but mainstream support ends December 31, 2029, and security patches stop entirely after April 30, 2031.
• Organizations on older GP versions under the Fixed Lifecycle Policy may already be past mainstream support, so the real deadline for those environments can be sooner than 2029.
• New payroll and HCM platforms typically bring forward current data only, so historical records need their own migration plan.
• A dedicated, searchable archive protects historical records without the ongoing cost of a legacy system or the limits of static file exports.

---

Is Great Plains (Dynamics GP) Payroll Being Discontinued?

Great Plains (Dynamics GP) isn’t disappearing outright, but Microsoft has moved on. New perpetual license sales ended in April 2025; subscription licenses followed in April 2026. Current customers can still add users to an existing environment, but no organization can stand up a new GP instance today. Microsoft’s engineering investment is going to Dynamics 365 Business Central and its broader cloud portfolio, and GP isn’t part of that roadmap anymore.

For payroll and HR leaders, that distinction matters: GP still runs today, it just has no future development ahead of it, and support will eventually stop entirely.

---

What is the Dynamics GP Payroll End-of-Life Timeline?

Three dates define the Dynamics GP payroll end-of-life timeline:

• April 1, 2026: Final date for new GP subscription licenses.
• December 31, 2029: Mainstream support ends: no further tax table updates, year-end updates, regulatory changes, or hotfixes.
• April 30, 2031: Outer limit for security patches, which Microsoft issues only at its discretion for critical vulnerabilities. No fixed schedule, no guarantee of coverage.

Organizations running older GP versions under Microsoft’s Fixed Lifecycle Policy may already be past mainstream support, which means the effective deadline can be considerably earlier than 2029 for those environments. Before setting a migration timeline, confirm which GP version you’re running and which lifecycle policy governs it.

---

What Happens to Historical Payroll Data When Great Plains is Retired?

This is the question with the greatest compliance exposure, and it receives the least attention in most migration plans.

New payroll and HCM implementations bring forward current and go-forward data only. Years of pay history, W-2 records, wage statements, and deduction detail routinely stay behind, sitting in a decommissioned system, sitting in a pile of static file exports, or disappearing entirely once the new platform goes live.

That gap carries consequences:

• DOL wage-and-hour investigations have trended toward longer lookback periods.
• State-level retention requirements vary significantly, and several states mandate longer retention than employers typically assume.
• Litigation, unemployment claims, and pay disputes can surface years after a system transition, often well outside the timeline anyone budgeted for.
• Ongoing legacy system costs accumulate when organizations keep an old GP instance alive indefinitely, solely to answer occasional records requests.

Treat payroll history as a distinct workstream in the migration plan: scope it, budget it, and execute it on its own timeline, rather than letting it resolve itself as a byproduct of the new implementation.

---

What are the Alternatives to Great Plains Payroll?

Organizations moving off GP generally choose one of two paths. Microsoft’s own recommended path is Dynamics 365 Business Central, a natural fit for organizations already standardized on the Microsoft 365 stack and where financials remain the primary system of record. The alternative is a dedicated cloud HCM or payroll platform, which organizations typically choose when payroll and HR functionality, rather than ERP integration, drives the decision.

Neither path resolves the historical data question. That responsibility sits with the organization, independent of which new platform it selects.

---

How do I Retain Access to Historical Payroll Records After Migrating?

Organizations have three approaches to choose from, and they carry very different costs and levels of defensibility:

1. Maintain the legacy environment in read-only mode. This preserves access but carries ongoing licensing, hosting, and IT support costs indefinitely, for a system employees or auditors access only occasionally.
2. Export records to static files. Lower upfront cost, but static exports are difficult to search, easy to lose track of over time, and often inadequate when an auditor or investigator requests a specific, well-organized data set.
3. Migrate historical payroll data into a dedicated archive platform. This preserves searchability and audit readiness without the ongoing cost of keeping a full legacy ERP environment operational, and it holds up regardless of which new payroll or HCM platform an organization selects.

---

What Should Organizations do Before Starting a Dynamics GP Payroll Migration?

Before switching payroll vendors or setting a go-live date, settle a short list of decisions:

• Confirm the current GP version and the lifecycle policy governing it.
• Document retention requirements for every state in which the organization operates.
• Decide explicitly what happens to historical payroll and HR data, rather than leaving it up to whatever the new vendor imports by default.
• Compare the ongoing cost of a read-only legacy environment against a dedicated data archiving solution.
• Build the historical data plan into the migration budget and timeline from the outset, not after go-live.

---

The Expertise Payroll Migration Requires

Migrating off Great Plains is, at its core, an HR and payroll systems project. Preserving what GP leaves behind is a records management and compliance discipline, one most implementation partners don’t specialize in.

ResNav is the HR and payroll history expert, helping organizations retain full, auditable access to historical payroll and HR data through any system transition, on any timeline.

Planning a Great Plains payroll migration? Let’s discuss how to keep your payroll and HR history intact through the transition.

---

Frequently Asked Questions