Dynamics GP has been a trusted ERP system for many organizations for decades—but like all technology, it has a finite lifecycle, and the end of that lifecycle is on the horizon. With Microsoft ending GP support in 2029, businesses still running on the platform have important decisions to make.
In a previous article, we shared ways to get more value out of your current GP system while you still can. Here, we’ll take it a step further by outlining practical, incremental steps you can take now to make your eventual move—especially to Microsoft Dynamics 365 Business Central—simpler, smoother, and far less stressful.
The key takeaway? You don’t have to do everything at once—but you do need to start.
Get the GUIDE TO MAKING THE MOST OF DYNAMICS GP - WHILE PREPARING FOR WHAT’S NEXT
Before you can plan where you’re going, you need a clear picture of your current GP environment.
A great place to start is the Migration Assessment Tool, a free resource that evaluates your GP setup and highlights potential migration challenges. It reviews things like:
The tool doesn’t capture business-specific data or provide tailored recommendations, but it does flag common pain points that could slow down a migration.
If you have SQL access, you can also run SQL scripts to:
Addressing these issues early can save significant time and effort later.
If you’re using Management Reporter, you’re not alone—but it’s important to know that it does NOT carry forward into Business Central.
Rather than waiting until your migration is underway, consider transitioning to a new reporting solution now. Doing this early:
There are several options for Business Central reporting. (See what my teammate had to say about the tools available!)
For many BC users, Power BI is an attractive option because it’s:
No matter which reporting tool you choose, making the change ahead of your ERP migration helps ensure continuity and confidence.
Payroll is one area you can’t afford to put off.
While GP includes native payroll today, tax and payroll updates will stop in 2029, making payroll in GP increasingly risky and eventually unusable.
It’s also important to note:
Because payroll directly impacts compliance and employee trust, selecting and implementing a new solution should be a top priority—not something left until after your ERP migration.
Start evaluating your options with a free, 2-minute payroll assessment here
Your chart of accounts plays a major role in how smooth (or painful) a GP-to-BC migration will be.
GP and Business Central handle account structures very differently:
This means that most GP-to-BC migrations require some level of account restructuring. Underused or outdated accounts often need to be combined and in some cases, a full redesign makes sense.
Before migrating, it’s also critical to:
Since account categories are used more heavily in Business Central, any mistakes in GP will carry forward unless addressed.
To make changes safely, many organizations use add-on tools such as:
While these tools add cost, they often pay for themselves by avoiding delays, errors, and post-migration disruptions.
As Dynamics GP approaches the end of support, the clock is ticking—but that doesn’t mean you need to rush into a full migration tomorrow.
By taking small, intentional steps now, you can:
Payroll, reporting, and account structures deserve special attention, as delays in these areas can directly impact operations and compliance.
For organizations planning to move to Dynamics 365 Business Central, these incremental actions can make the difference between a stressful migration and a confident, well-planned transition with minimal downtime.
The best migrations don’t start at go-live—they start well before it.
Get the GUIDE TO MAKING THE MOST OF DYNAMICS GP - WHILE PREPARING FOR WHAT’S NEXT