Skip to content

ERP guide

Should a company leave Dynamics GP now or stay for the time being?

Staying on Dynamics GP for now is reasonable while Microsoft still ships tax updates and fixes, which it has said it will do until December 31, 2029. Plan the move before then, because Microsoft has stopped selling GP, add-on makers are dropping their GP connectors, and whichever system replaces GP, a product such as Business Central or a cloud custom build, takes a project to reach.

Updated . Researched by David Verneuille for Black Badger Software Solutions. How we rank

Leaving Dynamics GP or staying until 2029. Updated November 21, 2026.
What you are comparingStaying on Dynamics GPA custom build
Support endMicrosoft ends product support, updates and tax updates on December 31, 2029, and security updates on April 30, 2031. After that the software runs, but nothing is fixed.No vendor end date. You own the code, and Black Badger or any competent developer can maintain it for as long as the business uses it.
Servers and hostingMost GP installs run on servers the company owns or rents, with SQL Server, backups, Windows updates and remote access to keep running.Built and run in the cloud on accounts you own. Black Badger installs nothing on your site, and the servers GP ran on can be retired.
UpgradesEach GP update still has to be installed and tested against your add-ons and customizations, usually ahead of year-end tax changes.Changes ship when you ask for them and are tested against your own process. There is no vendor release schedule to keep up with.
IntegrationsAdd-on makers are leaving GP. Sana Commerce ended its GP connector on December 31, 2025, and partners report many GP add-ons in maintenance mode.Connections to your bank, payroll, e-commerce and shipping tools are built as part of the system and documented, so there is no third-party connector to lose.
Getting data outGP keeps its data in a SQL Server database you can query, which makes leaving easier than on many cloud products. Microsoft's own tool for Business Central moves master data, open balances and a chosen window of history.Your data stays in a database on an account you own, and you can query or export all of it at any time, with no export limit.
Fit to processYears of Dexterity changes, Report Writer reports and SQL scripts may fit your process today, but each one must be rebuilt whichever way you leave.Built from your process, with the work GP customizations did rebuilt once as part of the system and not as add-ons on top of it.
How each route is paid forA yearly enhancement plan on the licenses you own, plus the servers and the partner who keeps GP running. Partners report Microsoft raised enhancement plan rates in 2022 and again in 2023.A one-time build scoped in writing, then running costs such as hosting and support. No licenses and no yearly plan.
Who keeps it runningA GP partner, from a pool that partners and customers report is shrinking as firms move their staff to cloud products.A named owner on your side, with Black Badger or any competent developer maintaining code written to be read and extended.
Time to changeStaying needs no project now, but the move still has to happen before support ends, and a late start leaves less room to plan it.Starts with discovery and a written scope. Areas go live in stages, and the schedule is set in that scope.

When staying on Dynamics GP for now is the right call

Staying is reasonable when GP does its job, your add-ons still work, and Microsoft is still shipping tax updates, which it has said it will do through 2029. A company that rushes to beat a date pays for a worse project than one that moves on its own plan.

Staying also makes sense while a bigger change is under way, such as an acquisition, a new entity or a change of owner. Move after that settles, so the new system is built for the company as it will be.

In a 2024 Dynamics Communities survey, GP customers named cost as their main concern about leaving, and more than half had no plan to leave within three years. Waiting on the move is a choice many GP companies make. Waiting on the plan for it leaves less room to choose.

What leaving Dynamics GP involves

Leaving GP is three jobs. First, list every customization, report, integration and add-on, and decide which to rebuild and which to retire. Second, choose the system and the history to bring, since Microsoft's own migration tool for Business Central moves master data, open balances and a window of history, not every posted transaction. Third, run the old and new systems side by side through at least one month-end close before GP is switched off.

Payroll needs its own decision. Customers report that Business Central has no US payroll like the one in GP, so a GP company moving to Business Central plans for a payroll service at the same time.

How a cloud custom build replaces Dynamics GP

A custom replacement starts with discovery of how the company works today, including what the GP customizations and the spreadsheets beside GP were built to do. Black Badger then writes a scope and builds the system in the cloud, on accounts the company owns. Nothing is installed on site, and the servers GP ran on can be retired once the new system is live.

GP keeps its data in a SQL Server database, so the history can be read out and loaded into the new system on a plan set in the scope. A custom system does not have to replace everything either. Where a payroll service or a tax engine works, it stays and the new system connects to it.

What a custom build involves, and how to ask about one

Questions buyers ask

Is it safe to keep running Dynamics GP after 2029?

Dynamics GP will keep running after December 31, 2029, but Microsoft stops tax updates and fixes on that date and security updates on April 30, 2031. A company that stays past 2029 handles its own tax table changes and runs an unpatched system once security updates end. Fewer partners and add-on makers are likely to support GP by then.

How much time does a company have to leave Dynamics GP?

Microsoft's date is December 31, 2029 for GP product support, updates and tax updates. A move that rebuilds customizations and checks the history takes planning, so start well before that date and aim to close the books on the new system while GP is still supported.

Can Black Badger keep Dynamics GP running on our servers?

Black Badger does not install, host or maintain Dynamics GP, and does not install software on a company's own servers. Black Badger builds custom systems in the cloud, so what it offers a GP company is a cloud replacement built around how that company works.

Does a custom build keep the history from Dynamics GP?

A custom build can keep as much GP history as the company decides to bring, because GP stores its data in a SQL Server database that can be read in full. How many years to bring, and whether older years come as detail or as balances, is set in the written scope.

More from this guide