On April 1, 2026, Microsoft officially stopped selling Dynamics GP subscription licenses to new customers. For many manufacturers still running GP, that date came and went without any fanfare. No system alerts. No disruptions. Invoices still processed. Shipments still went out. Life went on.
This reaction is understandable. When there are no visible issues, it is easy to treat such changes as minor administrative details and continue as usual.
However, the significance of this date should not be overlooked. The GP ecosystem is beginning to close, and manufacturers who act now will have more options than those who delay.
As new businesses stop adopting the platform, third-party developers discontinue support, and consultants with GP expertise shift to newer platforms. Support resources are becoming limited. Manufacturers needing critical customizations in the future will have fewer qualified professionals available than today.
The current period is a transition window for GP. It is open now but will not remain so indefinitely.
What “End of Sale” Actually Means for Your Business
Let’s be clear about where things stand: the end of new GP license sales doesn’t mean your system stops working tomorrow. Microsoft continues to support existing GP customers under their current agreements, and mainstream and extended support timelines remain in place.
This change means GP has entered a managed wind-down. Microsoft is redirecting development investment to Dynamics 365 Business Central, the designated mid-market successor. GP will continue to receive regulatory updates and critical security patches during the support period, but it will not receive new AI features, cloud-native architecture, or enhanced supply chain capabilities available in Dynamics 365.
Here’s what that translates to practically for manufacturers on GP right now:
-
- The platform has hit its functional ceiling. What exists today is largely what you’ll have going forward.
- Migration becomes more challenging over time. Data becomes outdated, workarounds accumulate, and institutional knowledge is lost as team members depart. A migration that takes six months today may require nine months in two years, not due to process changes, but because the environment becomes more complex.
- Experienced migration partners are limited. As more manufacturers begin migrating, available implementation capacity decreases. Early adopters benefit from more options, greater scheduling flexibility, and better pricing leverage.
The Two Paths Forward for Discrete Manufacturers
If you are currently using GP and considering next steps, there are two main options within the Microsoft ecosystem. The best choice depends on your business’s operational needs.
Dynamics 365 Business Central is the recommended solution for most mid-market manufacturers. It provides financial, supply chain, manufacturing, and project management capabilities in a cloud-native platform, with Microsoft Copilot included. If GP’s functionality met your needs and you seek a modern, maintainable platform with similar coverage and cloud benefits, Business Central is typically the best option.
Dynamics 365 Supply Chain Management is better suited for manufacturers with complex operational needs, such as high-volume discrete manufacturing, advanced production scheduling, sophisticated warehouse management, or multi-site global operations. It offers enhanced manufacturing execution capabilities but involves greater implementation complexity and cost. This platform is designed for businesses that have outgrown mid-market solutions.
In most cases, GP manufacturers are best suited for Business Central. However, those who have significantly expanded since their original GP implementation, or who have consistently encountered GP’s manufacturing limitations, may benefit more from Supply Chain Management. Determining the right fit requires a thorough review of operational requirements rather than a simple feature comparison.
The Part Nobody Talks About Enough: Your Data
Every GP migration involves data challenges, which are often more complex than anticipated.
GP implementations accumulate extensive historical data, including transactions, item records, vendor and customer information, and open balances. Some of this data should be migrated, some archived, and a significant portion typically requires cleaning before migration.
The item master often presents the greatest challenge. Over time, GP item records may accumulate duplicates, inactive entries, inconsistent units of measure, and outdated costing data. Migrating unclean item master data into Business Central or Supply Chain Management results in a modern system burdened by legacy issues.
BOM and routing data also require careful validation. Manufacturing configurations that operate in GP may need to be restructured to align with Business Central or Supply Chain Management processes for production orders, work centers, and routings. This is not only a data migration but also a configuration decision that requires operational input.
Our standard GP migration approach begins with a data audit. Understanding your current data, identifying what is needed, and determining what to leave behind is essential to ensure the migration results in operational improvement rather than simply a new system.
What a Realistic Timeline Actually Looks Like
For a mid-size discrete manufacturer migrating from GP to Dynamics 365, a realistic implementation timeline is 5 to 9 months, depending on data complexity, the number of integrations involved, and the scope of the implementation.
Timelines under five months for complex manufacturers often involve shortcuts that lead to post-implementation issues. Timelines exceeding twelve months typically indicate improper project phasing or an attempt to address all requirements simultaneously.
Phased approaches, beginning with financials and core operations and then adding manufacturing execution and advanced supply chain, often deliver faster value and help manage operational risk more effectively than large-scale implementations.
Weighing the Move: Pros & Cons of Migrating Now
Deciding when to move from a stable system like GP to a modern platform like Dynamics 365 is a balancing act. Here is a look at the trade-offs:
Migrating to Dynamics 365
| Pros | Cons |
| Microsoft Copilot & AI: Access to predictive insights for supply chain and automated financial reporting. | Initial Investment: Upfront costs for licensing, implementation, and data migration. |
| Eliminate Servers: Move away from on-premise hardware maintenance and security risks. | Learning Curve: Your team will need time to adapt to a new interface and modern workflows. |
| Seamless Integration: Native connections with Power BI, Outlook, and Teams. | Operational Disruption: The transition process requires dedicated time from your key personnel. |
| Automatic Updates: No more “version lock”; the system stays current without massive upgrade projects. | Data Sanitization: Requires the hard work of cleaning up years of “messy” GP data. |
Frequently Asked Questions
Q. Will my Dynamics GP stop working after April 2026?
No. Your system will continue to function. The “End of Sale” only applies to new customers. However, as the user base shrinks, so does the pool of experts and third-party developers, making support more expensive and harder to find.
Q. What is the main difference between Business Central (BC) and Supply Chain Management (SCM)?
Think of Business Central as the agile, comprehensive choice for mid-sized manufacturers. Supply Chain Management is designed for enterprise-level complexity—think global multi-site operations, high-volume production, and advanced warehouse logic.
Q. Does Microsoft offer any incentives for GP customers to move?
Yes. Microsoft frequently offers “Bridge to the Cloud” promotions that provide significant licensing discounts for existing GP customers moving to Dynamics 365. We can help you determine which current offers apply to your organization.
Q. Can I keep my historical GP data?
Yes, but we don’t recommend moving everything. We typically help you migrate opening balances, active master data (items, vendors, customers), and a specific window of historical transactions while archiving the rest for compliance.
So, When Should You Start?
If your organization uses Dynamics GP, now is the appropriate time to begin migration planning. While there is no immediate crisis, planning and partner selection require time, and starting early provides more options.
At CEM Business Solutions, we have over two decades of experience executing Dynamics migrations. We specialize in working with manufacturers, so we understand how BOMs, routings, production orders, and inventory configurations must translate between platforms, not just how to transfer data.
We have seen the positive impact of well-planned migrations on manufacturing operations, as well as the challenges that arise from inadequate planning. The difference is substantial.
If you are using GP and would like an objective assessment of your migration—including timeline, data complexity, platform recommendations, and cost estimates—we are available to guide you through the process. There is no sales pressure, only a clear understanding of your situation. Please review our client success stories to see examples of our work.
