Key Takeaways:

• Microsoft ends Dynamics GP product enhancements, tax and regulatory updates, and technical support on December 31, 2029, and security updates on April 30, 2031.
• Dynamics GP will keep running after those dates, but without tax updates or support, compliance and security risks grow every year.
• Microsoft recommends transitioning to Microsoft Dynamics 365 Business Central, but the right choice depends on your organization's needs
• Organizations that start planning well before 2029 are better positioned to control their timing, budget, and choice of system.

Microsoft announced in September of 2024 that their product, Dynamics Great Plains, is scheduled for retirement. Product enhancements, tax and regulatory updates, and technical support end on December 31, 2029, and security updates end on April 30, 2031. Although the software will still work after those dates, the year-end tax and payroll updates finance teams rely on will cease as will support from Microsoft.

For most organizations, the real deadline comes well before 2029, because choosing and implementing a replacement ERP and accounting system takes time.

When Does Current Dynamics GP Support End?

Date	Milestone	What it means for you
April 1, 2025	No new customers for GP perpetual licenses	Only existing customers can remain on GP perpetual licensing.
April 1, 2026	No new customers for GP subscription licenses	GP is now closed to new customers.
December 31, 2029	End of product enhancements, regulatory (tax) updates, service packs, and technical support	No more year-end tax or payroll updates and no Microsoft support.
April 30, 2031	End of security updates	No patches for newly discovered vulnerabilities.

Microsoft originally set September 30, 2029 as the end of product support, then moved it to December 31, 2029, so GP customers could meet payroll and tax obligations for the full year*.

What Happens to Dynamics GP Customers After December 31, 2029?

Dynamics GP will keep running after December 31, 2029. What stops is Microsoft’s maintenance of it. For many GP customers, this will create gaps that only widen every year.

• Tax and regulatory updates stop. Microsoft will no longer update payroll tax tables, year-end forms, or regulatory changes. For organizations that run payroll or 1099 reporting in GP, this is where the impact shows up first.
• Technical support ends. Microsoft will no longer help resolve issues. Third party support providers exist, but the pool of experienced GP professionals is likely to decline over time.
• Security updates end on April 30, 2031. After that date, newly discovered vulnerabilities stay open. That matters to auditors, cyber insurers, and anyone relying on the controls in your financial system.
• Compatibility gets harder. As operating systems, databases, and connected applications move on, keeping GP and its add-ons working together takes more effort and cost.

The risk is rarely a sudden failure. It is a gradual buildup of workarounds, cost, and exposure that is easy to underestimate until an audit, a tax change, or a security review forces the issue.

Why Have So Many Organizations Stayed on Microsoft Dynamics GP?

Dynamics GP has reliably handled core accounting, purchasing, inventory, and reporting for organizations in distribution, manufacturing, nonprofit, and professional services for decades. Many organizations bought perpetual licenses long ago, so their teams know the system well.

Those same strengths make leaving GP harder than it looks. A GP environment that has grown over many years carries customizations, third party add-ons, custom reports, spreadsheets, and workarounds that people depend on without always knowing it. Each one needs to be understood before anything moves, so the business can decide what to keep, what to redesign, and what to retire.

What Are the Next Steps for Current Dynamics GP Users?

Dynamics GP users have four choices. No option is right by default; the best fit depends on your processes, industry, growth plans, and total cost of ownership.
 

Option	What it involves	When it may fit	What to weigh
Move to Dynamics 365 Business Central	Microsoft’s recommended path for GP customers, supported by published migration guidance and tools for moving GP data	You want to stay with Microsoft, and Business Central’s functionality fits how your teams operate	It is a new implementation, not an upgrade: a different data model, redesigned processes, and retraining
Move to another ERP platform	A broader evaluation that may include Microsoft Dynamics 365 Finance, Oracle NetSuite, Sage Intacct, Acumatica, Infor, or industry specific platforms	Your requirements, industry, or growth plans are beyond Business Central	More evaluation time up front, which can also provide a better long-term fit
Stay on Dynamics GP with a defined exit plan	Stay current on GP releases and, after 2029, rely on third party support while the move is planned	Another priority, such as an acquisition or restructuring, needs to come first	Rising compliance and security exposure; tax updates must come from somewhere else; waiting does not reduce the work
Consolidate into an existing system	Move GP entities onto an ERP already used elsewhere in the organization, such as a parent company’s platform	You are part of a larger group that already runs a standard ERP	Standardization versus local requirements, and the parent system’s own roadmap

Whichever direction you lean, compare the options against your requirements, cost, and risk before vendor demonstrations start shaping the conversation. That is the purpose of an independent ERP software selection process.

How Much Time Do You Need for an ERP Transition?

More than most organizations expect. If you're on Dynamics GP today, plan backward from December 31, 2029, not forward from now, and leave a buffer before that date rather than aiming for it.

An ERP replacement moves through five phases, each with its own decisions:

1. Assess: document your current environment, pain points, and business requirements
2. Select: evaluate options objectively, including scripted demonstrations built on your own processes
3. Contract: negotiate software and implementation agreements with clear scope, responsibilities, and testing expectations
4. Implement: design, data migration, testing, training, and cutover
5. Stabilize: support users after go-live and resolve the issues that only surface in live operations

A few timing factors deserve early attention:

• Fiscal year and payroll boundaries. Going live at the start of a fiscal year, or at the start of a calendar year for payroll, can simplify reporting and year-end processing.
• Resource demand. As 2029 approaches, demand for experienced implementation resources is likely to rise, which can affect both cost and availability.
• Internal capacity. Your finance and operations staff will carry out much of the work while still running the business. Plan around your close calendar, audits, and busy seasons.

How Should You Prepare? An ERP Transition Checklist

Start with what you have, then decide where you are going. This checklist works whether you move to Business Central, another platform, or stay on GP for a defined period.

1. Confirm your GP version and which lifecycle dates apply to you.
2. Inventory the GP modules, customizations, and third-party add-ons you use, and check each add-on vendor’s own roadmap.
3. Document integrations, custom reports, and the spreadsheets and workarounds that exist because of GP.
4. Define business requirements and goals before looking at software.
5. Decide which historical data to migrate, archive, or retire, and how auditors will reach history after cutover.
6. Review your chart of accounts. Many modern ERP platforms use reporting dimensions rather than long segmented account strings, so plan any redesign early.
7. Build a budget on total cost of ownership, not license price alone.
8. Name an executive sponsor and the business owners who will make key decisions.
9. Evaluate options objectively, using demonstrations scripted around your processes.
10. Confirm how each option will be supported after go-live, and by whom.
11. Plan data migration, testing, training, and change management as part of the project from the start, with training and support that continue past go-live, so people use the new system instead of working around it.
12. Build a business continuity plan, including how you would run old and new systems in parallel or fall back if cutover runs into trouble.
13. Tell employees early and often what is changing, when, and why.
14. Set a target go-live date with a buffer before December 31, 2029.

What Mistakes Should You Avoid When Transitioning Away From Dynamics GP?

Many of the costliest errors in a GP replacement are locked in early, while scope and approach are still being decided.

• Treating the move as an upgrade. Rebuilding every GP customization in a new system carries old limitations forward. Revisit processes first.
• Letting a vendor define your requirements. Requirements should come from the business, so every option is measured against the same standard.
• Waiting until 2029. A late start compresses selection, testing, and training, the steps that protect go-live.
• Migrating all history by default. Moving everything adds cost and complexity. Decide what the business actually needs.
• Underestimating reports and integrations. In our experience, this is where GP environments have the most customizations, so this is where teams first notice gaps.
• Forgetting third party add-ons. Some GP processes depend on add-on products that need their own replacement plan.

How RubinBrown Helps Organizations Migrate Off End of Life ERP Systems

RubinBrown is software and vendor neutral. We do not sell or implement ERP software, so our advice has no stake in which platform you choose or who implements it.

Our independent ERP consultants help organizations assess their current GP environment, define requirements, and evaluate options objectively. Once a direction is set, we help with everything surrounding the implementation, from contract negotiation, project governance, and data readiness to testing, training, and change management, through our ERP implementation services.

While you plan, RubinBrown’s Information Technology Services group supports organizations running sunsetting software, so the transition can happen on your timeline rather than under last minute pressure.

Frequently Asked Questions

Will Dynamics GP stop working after December 31, 2029?
No. Dynamics GP will keep running, but Microsoft will stop releasing product enhancements, tax and regulatory updates, service packs, and technical support. Security updates continue until April 30, 2031. After that, the system runs with no Microsoft maintenance at all, and compliance and security risk grow each year.

Can we still buy Dynamics GP?
Not as a new customer. Microsoft stopped selling GP perpetual licenses to new customers on April 1, 2025, and subscription licenses to new customers on April 1, 2026. Existing customers can continue to use GP through the support dates Microsoft has published.

Is Dynamics 365 Business Central an upgrade from Dynamics GP?
No. Business Central is a different product with a different data model and design. Microsoft provides guidance and tools for moving GP data, but processes, reports, customizations, and training all need attention. Plan it as a new ERP implementation, even if you stay with Microsoft.

Do we have to move to a Microsoft product?
No. Microsoft recommends Business Central, but GP users can choose any ERP that fits their requirements. An objective evaluation compares Microsoft and non-Microsoft options on functional fit, total cost of ownership, and risk before a decision is made.

Should we wait until closer to end of support to decide?
Waiting rarely reduces the work. It shortens the time available for selection, data migration, testing, and training, and puts you in the market when demand for implementation resources is likely to be highest. Starting early keeps timing, budget, and choice in your hands.

What happens to our historical Dynamics GP data?
You decide. Many organizations migrate master data, open transactions, and a limited amount of history, then archive the rest in a format that stays accessible for reporting and audits. The right balance depends on reporting needs, retention requirements, and migration cost.

Discuss Your GP Timeline with RubinBrown

If Dynamics GP is on your roadmap, contact RubinBrown to talk through your timeline and options. One of our partners would love to talk through your next best steps for a smooth transition.

_{*These dates apply to current GP releases (version 18.x), which fall under Microsoft’s Modern Lifecycle Policy and customers stay on them by installing at least one of Microsoft’s three annual GP updates. Organizations still on older versions under the Fixed Lifecycle Policy face earlier dates: extended support for GP 2018 and 2018 R2 ends January 11, 2028, and support for GP 2016 and 2016 R2 ended July 14, 2026.}

Sources

• Microsoft Dynamics 365 Blog, Announcing End of Support for Dynamics GP, September 25, 2024, updated January 15, 2025
• Microsoft Learn, Understand the Lifecycle Policies: Dynamics GP
• Microsoft Dynamics Community, Discontinuing support for Microsoft Dynamics GP (license sales dates and Business Central discount note)
• Microsoft Learn, Dynamics GP data migrated to Business Central online (Microsoft’s cloud migration tools)
• Microsoft Dynamics 365 Blog, Explore migration options for Microsoft Dynamics NAV, Microsoft Dynamics GP, and Microsoft Dynamics SL customers, July 28, 2026

Published: 10/01/2026

_{^{Readers should not act upon information presented without individual professional consultation.}}

_{^{Any federal tax advice contained in this communication (including any attachments): (i) is intended for your use only; (ii) is based on the accuracy and completeness of the facts you have provided us; and (iii) may not be relied upon to avoid penalties.}}