Dynamics GP End of Support Migration Assessment
Dynamics GP customers have to decide what replaces GP, and when. This assessment turns that vague worry into a score you can show your CFO, and a short list of what to fix first.
1. Which Dynamics GP version and service pack are you running in production?
Check Help > About Microsoft Dynamics GP.
2. Have you confirmed the Microsoft support dates that apply to your GP version?
Use the Microsoft Lifecycle page for your exact version.
3. How many third-party add-ons and ISV products does GP depend on?
4. How much custom code lives in GP (Dexterity, VBA, Modifier, SQL stored procedures, SSRS)?
5. What is the state of your GP master data (items, customers, vendors, chart of accounts)?
6. How many companies (databases) and how many years of history does GP hold?
7. Do you have a named project owner and budget for the successor system?
8. How well do you understand the target options (Business Central, Finance and Operations, another ERP)?
9. Who knows how GP really works in your company (tables, jobs, integrations)?
10. Do audit, tax and compliance teams know how historical GP data must be kept?
How to use this assessment
Answer each question for your production environment, not your wish list. The best use is a short workshop with the controller, the GP administrator and whoever owns the SQL Server. Disagreement between them is itself a finding. The score runs from 0 to 100 and each band comes with three actions. Save the PDF and repeat it in six months to show progress. Nothing is sent anywhere, the scoring runs in your browser.
- Run it with finance and IT in the same room
- Answer for what is true today
- Export the PDF for your steering committee
- Re-run after the add-on inventory is finished
What the questions measure
The ten questions cover five risk areas: version and support position, third-party and custom code, data quality and history volume, ownership and budget, and knowledge concentration. Add-ons and custom code are weighted by the number of questions because they usually decide cost. A GP system with only standard modules is a cleaner migration than one that depends on Dexterity dictionaries and a dozen ISV products, whichever target you choose.
Reading your result
A low score does not mean you must act in a panic, it means you lack facts. The cheapest first step is almost always an inventory: companies, add-ons, custom reports, integrations, SQL jobs and users. A high score means you can begin vendor selection. Either way, treat the target as a separate decision. Business Central, Finance and Operations and non-Microsoft ERPs fit different company sizes and process needs, and a fit-gap beats a brochure.
Common mistakes
Companies tend to underestimate history, forget reports built directly on SQL tables, and assume every add-on has a cloud equivalent. Another frequent error is waiting until the last month of support before starting, which forces a migration at year end. Plan cutover for a quiet period, not for the close. Confirm your actual dates on the Microsoft Lifecycle page, since support terms differ by version.
Frequently Asked Questions
When does Dynamics GP support end?
Microsoft publishes support dates per version on its Lifecycle page. Dates change and depend on your release, so confirm them there rather than relying on a blog post. This assessment asks you to write your dates down and attach a decision deadline.
Is Business Central the only replacement for GP?
No. Business Central is the closest Microsoft path for many small and midsize GP companies, but Finance and Operations or a different ERP can fit better for manufacturing, multi-entity or complex needs. Run a fit-gap before choosing.
Can we keep running GP after support ends?
Technically yes, but you lose updates and fixes, and operating systems, SQL Server, Office and tax updates keep moving. Auditors and insurers may also ask questions. Most companies treat it as a short bridge, not a plan.
Does this tool send my answers anywhere?
No. Scoring runs in your browser and only the optional follow-up form sends anything. You can use the assessment and export the PDF without contacting anyone.
If you want an outside view of your GP estate, the SQL tables you rely on, and what a read-only archive could hold, we can review your inventory with you.
Related Tools
Dynamics GP to Business Central Migration Checklist
Thirty checks across scoping, data, add-ons, cutover and go-live for a GP to Business Central move.
Costing & FinanceGP vs Business Central Migration Cost Comparison Calculator
Multi-year cost comparison of staying on GP versus moving to Business Central, with payback period and a horizon chart.
Microsoft DynamicsDynamics GP SQL Table Reference (IV00101, SOP10100, POP10100)
Searchable reference of common Dynamics GP tables with module, purpose and work, open or history status.
ERP Migration & SelectionLegacy ERP Data Archive Checklist
Twenty-eight checks to decide what history to keep, where to keep it and how to decommission a legacy ERP safely.
More Microsoft Dynamics tools
See all- 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 Unsupported Risk Exposure Calculator
- Dynamics GP Work, Open and History Table Map