Microsoft closes the book on Dynamics GP for good!
In three weeks, Microsoft closes the book on Dynamics GP for good.
April 1, 2026 is the end of for new licenses or customers on Dynamics GP.
While this isn’t a huge shock as they have been talking about sunsetting GP(Great Plains) for years now, this customer base still represents a cash cow for both Microsoft and a lot of Microsoft Partners.
Somewhere between 10,000 and 14,000 companies are still running GP, and every single one of them has a countdown clock now.
Most of the conversation is about the software and the platform to migrate to with D365 BC or F&O being the options within the Microsoft family or potentially moving outside of MS and going to a competitive platform altogether like NetSuite and others.
Almost nobody is talking about the talent problem.
Here’s what I’m seeing after 25 years in the Dynamics ecosystem:
The pool of experienced D365 implementation consultants and internal leads who can actually manage a GP migration is smaller than most companies realize. And it’s about to get a lot more competitive.
Every GP shop that finally pulls the trigger on migration will be chasing the same handful of people that still retain Dynamics GP experience.
Keep in mind Microsoft made this original announcement well over 10 years ago so the vast majority of the experienced GP consultants, administrators and Dexterity developers have had more than enough time to cross train into other ERP packages to ensure their market demand, while many others have retired.
This means that now there is only a small fraction of the of experienced Dynamics GP professionals still actively working with the application today to be in a position to knowledgably assist with these critical migrations.
If you’re a CFO, CTO, or operating partner with GP in your environment, the talent conversation needs to happen before the vendor conversation because that is the area of greatest friction or scarcity.
What are you seeing on the migration front? Are companies treating this as urgent yet, or still kicking the can?
April 1, 2026 is the end of for new licenses or customers on Dynamics GP.
While this isn’t a huge shock as they have been talking about sunsetting GP(Great Plains) for years now, this customer base still represents a cash cow for both Microsoft and a lot of Microsoft Partners.
Somewhere between 10,000 and 14,000 companies are still running GP, and every single one of them has a countdown clock now.
Most of the conversation is about the software and the platform to migrate to with D365 BC or F&O being the options within the Microsoft family or potentially moving outside of MS and going to a competitive platform altogether like NetSuite and others.
Almost nobody is talking about the talent problem.
Here’s what I’m seeing after 25 years in the Dynamics ecosystem:
The pool of experienced D365 implementation consultants and internal leads who can actually manage a GP migration is smaller than most companies realize. And it’s about to get a lot more competitive.
Every GP shop that finally pulls the trigger on migration will be chasing the same handful of people that still retain Dynamics GP experience.
Keep in mind Microsoft made this original announcement well over 10 years ago so the vast majority of the experienced GP consultants, administrators and Dexterity developers have had more than enough time to cross train into other ERP packages to ensure their market demand, while many others have retired.
This means that now there is only a small fraction of the of experienced Dynamics GP professionals still actively working with the application today to be in a position to knowledgably assist with these critical migrations.
If you’re a CFO, CTO, or operating partner with GP in your environment, the talent conversation needs to happen before the vendor conversation because that is the area of greatest friction or scarcity.
What are you seeing on the migration front? Are companies treating this as urgent yet, or still kicking the can?
hashtag#DynamicsGP hashtag#GreatPlains hashtag#Dynamics365 hashtag#MicrosoftDynamics hashtag#DynamicsFocus