- Microsoft stops selling new GP subscription licenses after April 1, 2026, ends mainstream and tax/regulatory updates at the close of 2029, and cuts security updates on April 30, 2031.
- The date to circle is end of 2029, when tax and regulatory updates stop, not the 2031 security cutoff that invites a last-minute fire drill.
- A 'Microsoft to Microsoft' move is not lift-and-shift: GP and Business Central have different data models, so history must be mapped and the chart of accounts cleaned up on the way over.
- Business Central can be scoped down for a two-person team, and limited-access licenses let approve-only or read-only users sit on much cheaper seats.
Earlier this year, the controller at a small economic development authority told us she had started shopping for a new accounting system for one reason: she'd heard Microsoft Dynamics GP was being retired. Her team was two people, the books lived in GP (the product many of us still call Great Plains), and she wanted a head start rather than a fire drill.
She's right to plan now, and she's far from alone. Here's how a small finance team should think about the move.
The clock, in plain numbers
Microsoft has put Dynamics GP on a published end-of-life timeline:
- New subscription licenses stop being sold after April 1, 2026.
- Mainstream support, including tax and regulatory updates, runs through the end of 2029.
- Security updates continue until April 30, 2031, which is the true end of the road.
So nothing breaks tomorrow. But "we have until 2031" is exactly how a project becomes an emergency in 2030. The date a finance team should actually circle is the end of 2029, when tax and regulatory updates stop.
The natural successor, and the honest caveat
For most GP shops, the natural landing spot is Business Central, Microsoft's current cloud ERP (enterprise resource planning) system. Staying inside the Microsoft world is a real advantage: a familiar feel, native Microsoft 365 integration, and a partner ecosystem that does GP-to-Business-Central moves all day.
A word of caution we give every GP customer: "Microsoft to Microsoft" does not mean "lift and shift." GP and Business Central are different systems with different data models. The migration still has to be scoped, your history still has to be mapped, and your chart of accounts is worth cleaning up on the way over, not after.
"Isn't Business Central more than we need?"
This is the fear we hear most from small teams, and it's the same complaint that often sent them looking in the first place: GP feels oversized for two people doing payables and financials. Business Central can be scoped down. You don't have to turn on manufacturing, jobs, or warehousing to run a clean set of books with bank reconciliation, in-system invoice approvals, and solid reporting.
Licensing helps here too. Not everyone needs a full seat. People who only approve invoices or read reports can often sit on a much cheaper limited-access license.
Time the cutover to your fiscal year
The single biggest scheduling constraint for a finance migration is your books, not the software. Most auditors will tell you to cut over at the start of a fiscal year for a clean break. That gives you one good window a year. Miss it, and the safe move is often to wait for the next one rather than split a year across two systems.
So the real planning math is simple: pick your target fiscal-year start, then count backward to leave time for discovery, data mapping, testing, and training. That's usually how "we have years" turns into "we should start this quarter."
If you're on GP and not sure whether you're looking at a 2027 project or a 2029 one, we're happy to walk through your specific setup and the calendar with you. No pressure, just a clear picture of your runway. Let's talk it through.