Updated · Originally published
TL;DR
Microsoft ended new Dynamics GP license sales in April 2026. For organizations still running GP, the question is no longer whether to migrate — it is when and how. Business Central is the most common path and the right one. TMC has been doing GP-to-BC migrations since before most partners knew what Business Central was. Here is what the switch actually looks like.
In This Article
- Why more organizations are making the move now
- What a GP to BC migration actually involves
- What to look for in a migration partner
- Common questions about the switch
Microsoft ended new Dynamics GP license sales in April 2026. For organizations still running GP, the question is no longer whether to migrate — it is when and how to do it without disrupting the business.
The switch from GP to Business Central is the most common path and for good reason. Business Central is Microsoft's actively developed cloud ERP for small and mid-sized organizations. It covers the same core functions GP handles — financials, purchasing, inventory and reporting — but in a modern cloud architecture with continuous updates, native Microsoft 365 integration and no infrastructure to maintain.
GP users: Microsoft ended new GP license sales in April 2026. If your organization is still on GP, now is the time to start planning your migration — waiting too long means losing control of your timeline.
Why Organizations Are Making the Switch Now
GP has served a lot of businesses well for a long time. The decision to move is not about GP failing — it is about what comes next.
Microsoft has confirmed that mainstream support for GP is winding down. Organizations that wait too long lose control over the migration timeline and end up rushing a project that deserves careful planning.
Business Central connects directly with the tools most teams already use — Excel, Outlook, Teams and Power BI. For organizations already running on Microsoft 365, the integration is immediate and the learning curve is shorter than most expect.
Cloud deployment means no server maintenance, no upgrade projects and no falling behind on software versions. Updates ship automatically twice a year.
What the Migration Actually Involves
A GP to Business Central migration is not a lift-and-shift. The two systems have different data structures, different chart of accounts conventions and different ways of handling things like inventory costing and intercompany transactions. That is why the partner doing the work matters as much as the software itself.
A well-run migration covers four things: data cleanup before anything moves, configuration that reflects how the business actually operates, testing against real scenarios before go-live and training that gets users productive quickly rather than just technically familiar with the new interface.
Organizations that try to self-implement or work with a partner without GP migration experience tend to hit the same problems — data that imports incorrectly, configurations that do not match business processes and go-live delays that could have been avoided with better upfront planning.
What to Look for in a Migration Partner
The right partner has done this before — not just Business Central implementations generally, but GP-to-BC migrations specifically. The two require different skills. GP has its own data structures, reporting tools like Management Reporter and FRx and customizations that need to be evaluated before migration begins.
Technology Management Concepts (TMC) has been implementing Microsoft Dynamics ERP since 1984. The team includes consultants who know GP deeply and have migrated hundreds of organizations to Business Central. That experience means realistic project scoping, clean data migration and a go-live that does not require months of cleanup after the fact.
If your organization is running GP and starting to think seriously about what comes next, the best first step is an honest assessment of your current environment — what customizations you have, what your data quality looks like and what timeline actually makes sense for your business.
Ready to start your migration assessment? TMC has been running GP-to-BC migrations since before most partners knew what Business Central was. Let us help you scope the project the right way from day one.
Frequently Asked Questions
How long does a GP to Business Central migration take?
For a mid-sized organization with a straightforward GP environment, three to six months is a realistic range. More complex environments — multiple entities, significant customizations or large data volumes — should plan for six to twelve months. Starting the assessment early gives you more control over the timeline.
Can we keep our GP data after migrating?
Yes. Historical GP data can be migrated into Business Central or archived separately depending on how much ongoing access you need. Most organizations migrate open transactions and key master records and archive the rest. Your implementation partner should assess data quality before migration begins — records that were adequate in GP often need cleanup before they are fit for Business Central.
What happens to our GP customizations?
Each customization needs to be evaluated individually. Some GP customizations address gaps that Business Central handles natively. Others need to be rebuilt as extensions. A few may no longer be necessary given how Business Central works. A good migration partner will assess each one before the project begins so there are no surprises mid-implementation.
Is Business Central more expensive than GP?
The cost model is different. Business Central uses subscription licensing rather than a one-time license fee, which shifts spending from capital to operating. When you factor in the elimination of server infrastructure, IT overhead and upgrade costs, most organizations find the total cost of ownership is comparable or lower over a five-year horizon. A realistic TCO comparison should be part of any migration evaluation.