If your company has used Microsoft Dynamics GP for some years, there is a good chance someone has recently asked, “Are we on the latest version?” It sounds like a simple question, but the answer often leads to a bigger conversation about support, security, year-end tax updates and what the business plans to do before Microsoft’s support for GP ends in 2029.
A Dynamics GP system upgrade is the process of moving your GP installation, together with its data, customizations and add-on products, from an older release to a newer one. Done well, it is quiet and uneventful: users log in on Monday morning, find their familiar screens, and carry on working on a supported, more secure version. Done poorly, it can disrupt month-end, break integrations and leave the finance team without the reports they rely on.
Here, I will explain what a Dynamics GP upgrade involves, why it matters now, how the work is usually organised, and which issues to recognize early. The guidance reflects the project experience of our Dynamics GP consultants at Nevas Technologies, who have upgraded GP systems for organizations of many sizes.
Upgrade, Update or Migration: Knowing the Difference
These three words are often used as if they mean the same thing. They do not, and the difference affects your budget and timeline.
An update is a smaller change within the same version family, such as applying a year-end tax update or a hotfix. It usually takes hours rather than days.
An upgrade moves you from one GP release to a later one, for example from GP 2016 to the latest GP 18 release. The database structure changes, every table is converted, and add-ons and customizations must be brought forward too. This is a project, not a routine task.
A migration moves you off GP entirely, to a different system such as Dynamics 365 Business Central. Your data is extracted, transformed and loaded into a new product with its own structure and processes.
This blog focuses on the second of these: the upgrade.
Why Upgrading Matters Now
Microsoft has confirmed that Dynamics GP will receive product updates, tax updates and technical support until 31 December 2029, with security patches until 30 April 2031. However, those dates apply in full only to the current release.
Older versions are on a different footing. GP releases before October 2019 follow Microsoft’s older fixed lifecycle, and their support has either already ended or ends sooner. For example, extended support for GP 2018 and GP 2018 R2 finishes in January 2028. If you are running GP 2016, GP 2015, GP 2013 or anything older, you are already outside mainstream support.
In practical terms, running an unsupported version means:
- No year-end tax updates: US and Canadian payroll users depend on these every December.
- No fixes for newly found problems: If something breaks, Microsoft will not correct it.
- Growing compatibility risk: Older GP releases may not run reliably on current Windows Server, SQL Server or Microsoft Office versions.
- Security exposure: Old software on old infrastructure is a common weakness in audits and cyber-insurance reviews.
An upgrade to the latest release closes these gaps and gives you the longest possible period of Microsoft support while you plan your longer-term direction.
What Actually Changes During an Upgrade
When analyzing an upgrade, it helps to think of your GP environment as four layers, each of which must move forward.
The GP application: The client software on users’ machines, and any web client, is replaced with the new version.
The databases: The system database and each company database are converted to the new structure. GP Utilities runs this conversion, table by table. For large companies, this step can take several hours.
Customizations: Modified forms and reports, Dexterity code, VBA, SQL procedures and custom integrations all need to be checked, and some will need rework to function on the new release.
Third-party products: Every add-on, such as payroll extensions, document management, sales tax engines or budgeting tools, needs a version compatible with your target GP release. Each vendor sets its own release timing, and some products may have been withdrawn altogether.
The application and database layers are largely mechanical. The customization and third-party layers are where most of the risk and effort sit.
The Typical Stages of a GP Upgrade
Every upgrade is different, but well-run projects follow a similar path.
1. Assessment
The project starts with a review of your current environment: GP version, installed modules, company databases, data volumes, customizations, integrations, add-ons, server infrastructure and user count. The aim is to identify anything that could block or delay the upgrade before work begins.
2. Planning the Upgrade Path
Not every version can jump straight to the latest release. Very old versions may need an intermediate step, upgrading first to a middle release and then to the target. Your partner will confirm the supported path and set a timetable that avoids month-end, quarter-end and year-end.
3. Preparing the Infrastructure
The new release has its own requirements for Windows Server, SQL Server and client operating systems. Many companies use the upgrade as an opportunity to move to new servers or to a hosted environment, which also makes testing easier, because the old system remains untouched.
4. Test Upgrade
A copy of your live data is upgraded in a test environment first. This step is essential, and it should never be skipped to save time. It reveals conversion errors, measures how long the live upgrade will take, and gives the team a working system to test against.
5. User Acceptance Testing
Finance and operations staff then test their normal work in the upgraded system: entering transactions, posting batches, running reports, printing cheques and documents, and checking that integrations still exchange data correctly. I would emphasize that this testing must be done by the people who use GP every day, not only by IT. They are the ones who will recognize when a report total or a posting result is not quite right.
6. Live Upgrade
Once testing is signed off, the live upgrade is scheduled, usually over a weekend. Users stop work, full backups are taken, and the conversion is run again on live data. Key checks are carried out before users return.
7. Post-Upgrade Support
The first few weeks, and especially the first month-end, are when any remaining issues surface. A partner should be available to resolve them quickly.
Licensing and Registration
Upgrading GP does not normally mean buying the software again. Customers with an active Microsoft support plan, often called an Enhancement Plan, are generally entitled to new versions. You will, however, need new registration keys for the target release, and your partner will obtain these through Microsoft.
If your support plan has lapsed, reinstatement may be required before you can upgrade, sometimes with back-fees. Review your license position at the assessment stage, because it can affect both cost and timeline. It is also a good moment to remove modules and user licenses you no longer need.
Common Upgrade Problems to Recognize Early
From our project experience, most upgrade difficulties fall into a handful of categories.
Unsupported add-ons: A product your team relies on has no version for the target release. This needs to be discovered during assessment, not on upgrade weekend.
Undocumented customization: Modifications built years ago by a developer who has since left can be difficult to rebuild. A full inventory of custom code is one of the most valuable outputs of the assessment stage.
Data issues: Damaged records, orphaned transactions or very large history tables can cause the conversion to fail or run for an unexpectedly long time. Running GP’s data checks and reconciling subledgers before upgrading reduces this risk.
Modified reports: Report Writer reports that were customized in the old version may need to be checked and, in some cases, recreated.
Integration failures: Links to banks, e-commerce platforms, payroll services or warehouse systems may depend on specific GP versions or table structures.
Timing: Upgrading too close to year-end leaves no room to correct issues before critical processing.
How Long Does an Upgrade Take?
For a straightforward environment with a single company, few add-ons and little customization, an upgrade can be completed in a few weeks. Organizations with multiple companies, heavy customization or many third-party products should allow two to three months, including testing. The single biggest factor in the timeline is usually how quickly business users can complete their testing.
Should You Upgrade or Migrate?
With GP support ending in 2029, some businesses ask whether they should skip the upgrade and move straight to a new platform. The answer depends on timing. A migration to Business Central is a larger project that involves new processes, training and data conversion. If that move is still two or more years away, upgrading GP now keeps you supported, secure and receiving tax updates in the meantime. It also leaves you with cleaner data and a better-documented system to migrate from later.
Summarizing the Essentials
Summarizing the main points for your leadership team:
- A GP upgrade moves your application, data, customizations and add-ons to a newer release.
- Only the current release receives full Microsoft support until the end of 2029.
- Older versions are already outside mainstream support or close to it.
- Customizations and third-party products carry most of the upgrade risk.
- A test upgrade and proper user testing are essential.
- Upgrades are usually covered by an active support plan, but new registration keys are required.
- Upgrading now can be a sensible bridge to a later migration.
How Nevas Technologies Can Help
For more than a decade, Nevas Technologies has helped companies across the United States and Asia Pacific keep Microsoft Dynamics GP current and well supported. Our Dynamics GP upgrade service covers assessment, planning, test and live upgrades, customization and add-on checks, and support after go-live. Our Dynamics GP support team then remains available for day-to-day help.
If you are unsure which version you are running, or what an upgrade would involve for your business, contact us. We will review your environment and give you a clear plan, timeline and estimate.
Frequently Asked Questions
What is a Dynamics GP system upgrade?
A Dynamics GP system upgrade moves your GP installation, including its databases, customizations and add-on products, from an older release to a newer one. Users keep working in GP, but on a supported and more secure version.
What is the difference between a GP upgrade and a migration?
An upgrade keeps you on Dynamics GP and moves you to a later release. A migration moves you off GP entirely to a different system, such as Dynamics 365 Business Central, with new processes and a new data structure.
Why should we upgrade Dynamics GP if support ends in 2029?
Only the current GP release receives full Microsoft support, including tax updates and fixes, until the end of 2029. Older versions are already outside mainstream support or close to it. Upgrading keeps you supported and secure while you plan your longer-term move.
Do we need to buy new licenses to upgrade Dynamics GP?
Usually not. Customers with an active Microsoft support plan are generally entitled to new versions, although new registration keys are needed. If your plan has lapsed, reinstatement may be required before upgrading.
How long does a Dynamics GP upgrade take?
A simple environment with one company and few add-ons can be upgraded in a few weeks. Businesses with several companies, heavy customization or many third-party products should allow two to three months, including testing.
What are the most common Dynamics GP upgrade problems?
The most common issues are add-on products with no compatible version, undocumented customizations, data errors that interrupt the conversion, modified reports and integrations that depend on the old version. A thorough assessment and test upgrade help identify these early.
Can Nevas Technologies upgrade our Dynamics GP system?
Yes. Nevas Technologies provides full Dynamics GP upgrade services, including assessment, planning, test and live upgrades, customization and add-on checks, and support after go-live.
