.jpg)
Microsoft has set the end of support for Dynamics GP on December 31, 2029. After that date, organizations still running GP will no longer receive product updates, regulatory compliance support, or technical assistance from Microsoft. A limited security window runs through April 30, 2031, but full product support does not.
For organizations still running GP, that timeline requires immediate attention.
On average, it takes 9–18 months from the decision to move off Microsoft GP to go-live because organizations spend 3–6 months evaluating solutions and selecting a vendor, followed by 6–12 months for implementation, data migration, and testing, along with additional time for training, change management, and post–go-live stabilization.
For companies in manufacturing or distribution, data complexity, integrations, and operational requirements can extend that timeline further. The organizations that transition successfully are the ones that start planning before urgency sets the schedule.
What Is the Dynamics GP End of Support Date?
Microsoft has confirmed the following lifecycle dates for Dynamics GP:
- December 31, 2029 — End of mainstream product support
- April 30, 2031 — End of extended security updates (issued only if deemed necessary by Microsoft)
After December 31, 2029, Microsoft
will stop delivering:
- Product enhancements
- Regulatory and tax updates
- Technical support
Security patches may be issued through April 2031, but only at Microsoft's discretion and only for critical vulnerabilities. There is no guarantee of frequency or coverage.
If your organization depends on regular compliance updates, regulatory patches, or payroll support, that coverage ends in 2029. The extended security window through 2031 is conditional and limited. It is not a substitute for active product support.
What Does "End of Support" Actually Mean for GP Users?
End of support is not just a product milestone. It has direct consequences for how your team operates day to day. Here is what changes on December 31, 2029:
No Regulatory or Tax Updates - GP will no longer receive annual payroll updates, state tax table releases, or compliance patches. If your organizations operate across multiple states, entities, or jurisdictions, this creates direct compliance exposure.
No Technical Support from Microsoft - If a critical process breaks, whether that is a payroll run, a month-end close, or an integration, Microsoft will not troubleshoot or resolve it. You are relying entirely on your internal team or a third-party partner.
No Product Enhancements - GP will be frozen at whatever version it reaches in 2029. Your business will continue to evolve. Your ERP won't.
Limited and Discretionary Security Coverage - Microsoft may issue security patches through April 2031, but only for vulnerabilities they deem critical and only at their discretion. For a business running finance and operations on that platform, the difference matters.
Important: Not All GP Versions Follow the Same Timeline
The 2029/2031 dates apply to versions of Dynamics GP covered under Microsoft's Modern Lifecycle Policy. But if your organization is running an older release — such as GP 2016, GP 2018, or another version governed by the Fixed Lifecycle Policy — your end-of-support date may have already passed or be arriving sooner than you think.
Under the Fixed Lifecycle Policy, older GP versions follow a defined support window that is not extended by the 2029 announcement. That means:
- No hotfixes
- No regulatory or tax updates
- No technical support from Microsoft
If you are unsure which lifecycle policy governs your current GP version, that is an important thing to find out before you build a transition timeline. Running an unsupported version today changes the conversation entirely.
Why 2026 and 2027 Are the Years That Actually Matter
The 2029 deadline sounds distant. It is not, once you account for how ERP transitions actually work.
Most organizations moving off GP go through a process that looks something like this:
- 3 to 6 months of evaluation, demos, and vendor selection
- 6 to 12 months of implementation, data migration, and testing
- Additional runway for change management, training, and go-live stabilization
Start that process in early 2027 and your go-live lands in late 2028. That leaves you less than a year before product support ends, with no room for the delays that almost every ERP project encounters.
There is one more factor worth considering, and most companies are not talking about it yet: implementation partner capacity.
The most experienced Dynamics 365 partners, the ones with deep knowledge in manufacturing, distribution, and complex operations, are already in active conversations with GP customers. As 2027 and 2028 approach, their availability will tighten. The partners best equipped to handle complex implementations will fill their pipelines before the market peaks, not during it.
Waiting does not buy you time. It costs you options.
What Are Your Options After Dynamics GP?
The good news for GP users: you don't have to leave the Microsoft ecosystem. The two most common paths are:
Microsoft Dynamics 365 Business Central
Best fit for small to mid-market organizations with moderate operational complexity. Business Central is a strong option for distribution, manufacturing, food and beverage, wine and spirits, and multi-entity businesses that need modern cloud ERP without enterprise-level overhead. If GP has been your system of record and your team works primarily in Microsoft 365, the transition to Business Central tends to be the most natural.
Microsoft Dynamics 365 Finance & Supply Chain Management
Best fit for larger or more complex enterprises, particularly those with advanced manufacturing requirements, multi-site or global operations, high transaction volumes, or significant regulatory complexity. This path carries more implementation weight, but also more long-term scalability.
How do you choose? The determining factors are usually operational complexity and where you expect the business to be in five to seven years.
Start with a structured readiness assessment, not a vendor demo.
Both paths keep you in the Microsoft ecosystem, which means continued integration with Microsoft 365, access to Copilot AI features, and a long-term product roadmap that isn't going anywhere.
What Should You Do Now?
The question has moved from "should we leave GP?" Most organizations already know the answer. The real question is: when do we start, and with whom?
Here's what's happening in the market right now: GP customers are actively evaluating their options. Boards are asking questions. IT leaders are scoping projects. CFOs are building multi-year budget models. The transition from awareness to active planning is already underway, and implementation partner capacity is finite. Customer demand for Dynamics 365 implementations will outpace partner capacity, meaning the most experienced partners—and their top resources—will be booked early and unavailable to those who wait.
Starting the conversation in 2026 doesn't mean you're rushing. It means you're choosing on your terms.
Your Next Step Framework
If you’re currently running Dynamics GP, here’s the approach that we recommend:
1. Start with a Dynamics 365 Readiness Assessment
Before you sit through a single demo or evaluate a vendor, take stock of your own environment. What version of GP are you running? Which integrations, customizations, and workflows does your business actually depend on? What shape is your data in? Those answers will do more to define your path and timeline than any vendor presentation will.
2. Align Your ERP Decision to Where the Business Is Going
Do not size your ERP for the business you have today. If acquisitions are on the horizon, if you are expanding warehouse operations, or if automation is part of your growth plan, your ERP needs to support those goals, not become the thing that constrains them. That kind of decision requires a five-to-seven-year view of the business, not a feature checklist.
3. Secure an Experienced Partner Before the Market Tightens
The most qualified Dynamics 365 partners, especially those with real depth in manufacturing, distribution, and complex operations, are already working with GP customers on transition plans. Having an early conversation does not lock you into anything. It just means you are talking to the right people while you still have the luxury of choosing them.
Take the First Step: Estimate Your Dynamics 365 Investment
For most organizations starting a GP transition, cost is the first real question. It is also the one that most commonly stalls internal momentum before it ever gets started.
Western Computer’s self-guided Dynamics 365 Cost Estimator is built specifically for customers in the early stages of evaluation. In a few minutes, you can build a realistic cost model, compare Business Central and Finance & Supply Chain Management, and walk into your next internal conversation prepared with real numbers rather than whatever a vendor handed you.
Start with Western’s Self-Guided Dynamics 365 Cost Estimator
The Timeline Is Clear. Your Strategy Should Be Too.
Dynamics GP product support ends December 31, 2029. Security updates may extend to April 30, 2031. Those dates are not changing.
The organizations that come out ahead will not be the ones who waited the longest. They will be the ones who decided early, while they still had room to do it right.
They'll move with intention. They'll secure experienced guidance. And they'll modernize on their own schedule, not because a deadline left them no other choice.
That window is still open. The question is how long you want to wait before you use it. If you’re running Dynamics GP today, the best time to start your Dynamics 365 strategy is now.
