GP is Headed for Retirement. Are You Ready for What’s Next?

UPDATED MARCH 2026

If you’re one of the many finance or operations leaders who’ve relied on Microsoft Dynamics GP (Great Plains) for years, this is no longer just a future planning conversation. Microsoft will end Dynamics GP product enhancements, regulatory updates, and technical support on December 31, 2029, with security updates ending April 30, 2031.

Microsoft has also clarified that new customers can only license GP subscriptions through April 1, 2026, and that after April 30, 2031, service plan coverage ends, subscription licenses will no longer be renewable, and additional perpetual users can no longer be added to existing GP systems.

For teams managing AP workflows, month-end close, reporting, and day-to-day financial operations, that matters. But this is about more than a software retirement date. It’s a chance to step back and ask whether the systems, processes, and workarounds built around GP are still helping the business move forward, or quietly making everything harder than it needs to be.

And while 2029 may sound far off, the smartest teams know this kind of transition does not start with a go-live date. It starts with planning. Microsoft has been clear that full cloud migration isn’t something organizations can accomplish overnight, and that businesses should begin the conversation now.

What Microsoft’s Retirement of GP Means in Real Terms 

When software companies announce a sunset, it can feel distant. There is a tendency to think, “We still have time.” Technically, that’s true. But the real impact starts much earlier than the final deadline.

As support winds down, the burden of keeping GP current, sustainable, and aligned with business needs shifts back to your team. That means fewer updates, fewer improvements, and eventually fewer options. Even if GP still works, the bigger question becomes whether it still supports the level of speed, visibility, and control finance teams are now expected to deliver.

For some organizations, the pressure is already showing up in familiar ways: longer close cycles, spreadsheet-heavy reconciliations, reporting that depends on a few long-time power users, approval delays, or manual AP processes that have become “normal” simply because they’ve been around for years.

GP’s retirement isn’t creating every problem from scratch. In many cases, it’s simply forcing a closer look at issues that have been building quietly over time.

Why This Matters More in 2026 Than It Did in 2025

A year ago, the GP retirement story could still be framed as a future ERP issue. In 2026, it’s much more connected to broader finance priorities. According to Deloitte’s Q4 2025 CFO Signals survey, 50% of North American CFOs said digital transformation of finance is their top priority for 2026, 49% said automating processes to free employees for higher-value work is the leading finance talent priority, and 87% expect AI to be very or extremely important to finance operations this year.

That context matters because finance teams are not just being asked to keep the books clean. They are being asked to move faster, improve visibility, reduce manual work, strengthen controls, and do more with leaner teams. That makes the GP conversation bigger than ERP replacement. It turns it into a chance to rethink how finance actually operates.

Why This is the Right Time to Step Back, and Step Up

When something familiar is going away, the natural instinct is to find the nearest replacement and move on. But this moment is bigger than a plug-and-play swap.

This is the right time to ask better questions.

• What should the ERP environment look like over the next decade?
• Which manual tasks have become permanent?
• Which reports are still being patched together outside the system?
• Where are teams duplicating work across tools, emails, spreadsheets, and disconnected processes?

Before teams choose what comes next, they need a clear picture of what they have today, what still works, and what is quietly slowing them down.

That matters because many organizations didn’t outgrow GP all at once. Instead, they built around it. They added bolt-ons, custom reports, spreadsheets, manual approval chains, and secondary systems in other parts of the business. Over time, those decisions may have helped keep things moving, but they also created more complexity.

What started as a practical workaround can turn into a costly operating model. One that’s harder to scale, harder to support, and harder to defend when leadership starts asking why finance still needs so much manual effort to stay on track.

What ERP Consolidation Can Unlock

For teams running multiple systems, the day-to-day friction is real. IT has more integrations to maintain. Finance has more data to reconcile. Leadership gets slower answers and less confidence in the numbers.

Consolidation can help reduce that friction. It can create a cleaner source of truth across entities, improve consistency in reporting, reduce duplicate vendor records, and make it easier to manage approvals, liabilities, and cash flow in one connected environment.

But the real value isn’t just simplification for its own sake. It’s the opportunity to create a stronger operational foundation. One where teams spend less time chasing information across systems and more time using data to make decisions.

Evaluating What Comes Next: It Starts with Assessment

With GP on the way out, evaluating the next ERP is inevitable. But one of the most common mistakes teams make is treating ERP migration like a product selection exercise when it really starts with assessment.

The first question isn’t “What should replace GP?” The first question is “What do we need the next environment to do better than the current one?”

That means taking an honest look at how finance work really happens today. Which workflows are still manual? Which approvals stall out? Which reports still need spreadsheet cleanup? Which processes depend on someone knowing exactly where to look or who to email?

A GP migration is rarely just a data move. It usually involves reviewing integrations, reports, workflows, customizations, and the manual processes that built up around the system over time. Microsoft’s current migration guidance reflects that, emphasizing assessment, planning, and preparation well before the move itself.

That’s why this is such an important moment to pause before making a decision based only on familiarity. The right next step should be guided by business needs, operational complexity, and long-term fit, not just what feels most comfortable in the short term.

Building Internal Buy-In Before You Buy Anything

Even when everyone agrees GP is nearing the end of the road, alignment isn’t automatic.

Controllers may care most about cleaner closes and better reporting. AP teams may want fewer manual touchpoints and less exception chasing. CFOs may focus on visibility, scalability, and return on investment. IT may be thinking about integrations, security, and supportability.

That’s why internal buy-in matters so much. A strong business case isn’t built around Microsoft’s timeline alone. It’s built around the current pain points each team is already feeling and the business impact of keeping those issues in place.

The more clearly teams can connect today’s friction to tomorrow’s risk, inefficiency, or missed opportunity, the easier it becomes to build alignment before vendor selection even begins.