Dynamics GP 18.x In-Place Upgrade Checklist
This checklist plans an in-place upgrade of an on-premises Dynamics GP system from GP 2016 or GP 2018 to the current 18.x build under Microsoft's Modern Lifecycle. It covers the lifecycle dates, pre-checks, a timed test upgrade, cutover and the posting tests that prove it worked.
0 of 36 items complete
6 critical items still open - these are the highest-risk gaps.
1. Plan
2. Pre-upgrade data checks
3. Test upgrade
4. Production cutover
5. Post-upgrade validation
Do not start production until every critical item in groups 1 to 3 is complete. A version mismatch between any client and the database blocks login.
Get your GP upgrade plan reviewed
Send your current build, company count and ISV list and we will flag the hops, risks and cutover timing.
Optional. The tool and every export work without this. No spam.
How to use it
Run the five groups in order and treat the test upgrade as mandatory: it gives you real timings per company and surfaces conversion errors before the business is waiting. Tick items as you confirm them, export to Excel and keep the completed list with your change record. Critical items are the ones that cause failed logins, broken integrations or a rollback when skipped. If you have many companies, time the largest one in test and add a margin for production.
Lifecycle facts to plan around
Microsoft moved GP to the Modern Lifecycle in October 2019. Version 18.x stays supported as long as you keep taking the updates and tax releases Microsoft publishes for it. GP 2018 and 2018 R2 remain under the Fixed Lifecycle with extended support ending January 11, 2028, but installing any compatible tax release or hotfix moves them to 18.5 or later and the Modern policy. Microsoft has announced the end of GP support for enhancements, tax updates and technical support on December 31, 2029, with security updates if needed until April 30, 2031.
- GP 2016 and 2016 R2 extended support ended July 14, 2026
- Stay current means staying on a recent 18.x update
- Tax updates stop after December 31, 2029
Checking versions and restarting a failed company
GP Utilities records versions in DYNAMICS..DB_Upgrade (one row per database and product) and upgrade progress in DYNAMICS..DU000020. Before and after each run, select from both tables and confirm every company and product shows the target version. If a company stops part way through, do not keep relaunching GP Utilities: follow Microsoft's troubleshooting article on restarting the upgrade of a company database, which resets the version information for that company so the upgrade reruns cleanly, after you fix the underlying table error. Restore the company backup if the error cannot be fixed.
Common mistakes
The most expensive mistakes are an ISV product without a certified build, a forgotten terminal server still on the old client, and modified dictionaries that were not upgraded. Table conversion errors reported in the community, for example on PM00204, are usually data problems in that table on that system, so investigate the specific error text and the table contents rather than assuming a known cause. eConnect and Integration Manager must match the GP version, so integrations break silently if they are left on the old release.
Frequently Asked Questions
What is the upgrade path from GP 2018.3 to the latest 18.x?
GP 2018 (18.x) builds can generally be upgraded within the 18.x line by installing the newer build and running GP Utilities. Confirm your exact starting build is listed as a supported source in Microsoft's upgrade notes for the target release, and check that every ISV product has a matching build before you start.
How do I restart a Dynamics GP upgrade that failed on one company?
Fix the error first, using the GP Utilities message and the table it names. Then follow Microsoft's article on restarting the upgrade of a company database, which resets that company's version information in DB_Upgrade so GP Utilities treats it as not yet upgraded. If you cannot fix the data, restore the company backup and rerun.
What does the PM00204 upgrade error mean?
PM00204 has appeared in community threads as a table where conversion failed during an upgrade. The root cause varies by system, often data that violates the new table definition. Read the full error, query the table in a test copy, and fix or open a support case with the exact message. Do not apply another site's fix unchecked.
Do I have to upgrade 18.6 to 18.8 if 18.6 still works?
Under the Modern Lifecycle you need to stay on a recent update to keep getting fixes and tax updates. Staying on an old 18.x build works technically, but year-end and payroll tax releases target current builds. Plan at least one update per year until you leave GP.
If you are keeping GP on-prem through 2029 and want users to query it in plain English on your own servers, we can add that layer without touching the upgrade path.
Related Tools
Dynamics GP Word Template Setup and Troubleshooting Checklist
Work through enablement, company assignment, print destination, template editing and Template Processing Engine debugging for GP 2013 R2 through 18.x.
Microsoft DynamicsDynamics GP eConnect SOP Invoice XML Generator (taSopHdrIvcInsert)
Fill in customer, item, quantity and price to get a ready eConnect SOPTransactionType document and the C# call that posts it into Dynamics GP.
Microsoft DynamicsDynamics GP End of Support Migration Assessment
Ten-question readiness score for Dynamics GP customers who need a decision on what comes after GP.
Microsoft DynamicsDynamics GP Unsupported Risk Exposure Calculator
Adds up support fees, compensating controls, manual workarounds and expected incident loss to show what another year on Dynamics GP really costs.
More Microsoft Dynamics tools
See all- Dynamics GP SQL Table Reference (IV00101, SOP10100, POP10100)
- Dynamics GP Chart of Accounts Mapping Worksheet
- GP to Business Central Cutover Runbook Template
- GP Third-Party Add-On Inventory Worksheet
- GP Cutover Open Balances Reconciliation Worksheet
- GP to Business Central Partner RFP Letter Template
- GP and AX User Role to Business Central Permission Mapping Worksheet
- GP Open Transactions SQL Query Generator
- Dynamics GP Work, Open and History Table Map
Keep exploring
Free tools
- Dynamics GP Word Template Setup and Troubleshooting ChecklistWork through enablement, company assignment, print destination, template editing and Template Processing Engine debugging for GP 2013 R2 through 18.x.
- Dynamics GP Year-End Close ChecklistA step-by-step checklist for closing a fiscal year in Dynamics GP, from subledger reconciliation to final backup and sign-off.
- Dynamics GP End of Support Migration AssessmentTen-question readiness score for Dynamics GP customers who need a decision on what comes after GP.
ERP fixes and how-tos
- Adding a Private AI Layer to Dynamics GP On-PremAdd AI to Dynamics GP on-prem without cloud: curated SQL views, eConnect for writes, retrieval index, local LLM, mirrored GP security, approved write-back.
- Dynamics GP POP Tables: Purchase Order Processing Reference and Sample SQLReference for Dynamics GP Purchase Order Processing tables: POP10100, POP10110, POP30100, POP30110, receipt tables, key joins and sample SQL queries.
Integrations
- How to use ChatGPT with Microsoft Dynamics GPConnect ChatGPT to Dynamics GP safely: export versus live access, custom GPT actions over an API gateway, enterprise data controls, and when to go private.
- How to add AI agents to Microsoft Dynamics GPHow to add AI agents to Microsoft Dynamics GP: a read-only tool layer over SQL views, eConnect for approved writes, and human sign-off, on-prem if needed.