# Dynamics GP End of Support Migration Assessment > Source: https://netray.co/tools/dynamics-gp-end-of-support-migration-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Ten-question readiness score for Dynamics GP customers who need a decision on what comes after GP. ## Category microsoft-dynamics ## Erp Microsoft Dynamics GP ## Audience - CFO - Controller - IT manager - ERP admin ## Tool **Kind:** assessment **Questions:** #### Which Dynamics GP version and service pack are you running in production? **Help:** Check Help > About Microsoft Dynamics GP. **Options:** ##### Several versions behind, or unsure **Score:** 0 ##### Two or three releases behind **Score:** 1 ##### One release behind **Score:** 2 ##### Current release with latest year-end update **Score:** 3 #### Have you confirmed the Microsoft support dates that apply to your GP version? **Help:** Use the Microsoft Lifecycle page for your exact version. **Options:** ##### No, we have not looked **Score:** 0 ##### Someone has an idea but nothing is written down **Score:** 1 ##### Dates are documented but not tied to a plan **Score:** 2 ##### Dates documented and a decision deadline is set **Score:** 3 #### How many third-party add-ons and ISV products does GP depend on? **Options:** ##### More than ten, several unsupported **Score:** 0 ##### Six to ten **Score:** 1 ##### Three to five, all with a known vendor **Score:** 2 ##### Two or fewer **Score:** 3 #### How much custom code lives in GP (Dexterity, VBA, Modifier, SQL stored procedures, SSRS)? **Options:** ##### Heavy, undocumented **Score:** 0 ##### Heavy but documented **Score:** 1 ##### Moderate and inventoried **Score:** 2 ##### Little or none **Score:** 3 #### What is the state of your GP master data (items, customers, vendors, chart of accounts)? **Options:** ##### Duplicates and inactive records everywhere **Score:** 0 ##### Known problems, no cleanup yet **Score:** 1 ##### Cleanup under way **Score:** 2 ##### Clean and reviewed this year **Score:** 3 #### How many companies (databases) and how many years of history does GP hold? **Options:** ##### Many companies and 10+ years nobody wants to lose **Score:** 0 ##### Several companies, 7 to 10 years **Score:** 1 ##### One or two companies, 5 to 7 years, archive policy exists **Score:** 2 ##### One company, retention policy agreed with finance and audit **Score:** 3 #### Do you have a named project owner and budget for the successor system? **Options:** ##### No owner, no budget **Score:** 0 ##### Owner but no budget **Score:** 1 ##### Budget range approved, owner part-time **Score:** 2 ##### Owner, budget and partner shortlist in place **Score:** 3 #### How well do you understand the target options (Business Central, Finance and Operations, another ERP)? **Options:** ##### Not evaluated **Score:** 0 ##### Read marketing material only **Score:** 1 ##### Seen demos and compared against requirements **Score:** 2 ##### Fit-gap done against our real processes **Score:** 3 #### Who knows how GP really works in your company (tables, jobs, integrations)? **Options:** ##### One person, close to retirement or leaving **Score:** 0 ##### One person, no backup **Score:** 1 ##### Two people plus a partner **Score:** 2 ##### Documented, with a team that can support the project **Score:** 3 #### Do audit, tax and compliance teams know how historical GP data must be kept? **Options:** ##### Not discussed **Score:** 0 ##### Discussed informally **Score:** 1 ##### Retention periods listed per record type **Score:** 2 ##### Retention and read-only access approach agreed **Score:** 3 **Bands:** #### Exposed **Min:** 0 **Max:** 34 **Verdict:** You have limited visibility into GP risk and no committed path. The cost of waiting is rising, mostly through unsupported add-ons and key-person dependence. **Recommendations:** - Confirm the exact support dates for your GP version and write the decision deadline down. - Inventory add-ons, customizations and integrations before talking to any vendor. - Name an owner and ask for a rough budget range this quarter. #### Aware but unprepared **Min:** 35 **Max:** 59 **Verdict:** You know the problem exists and have started work, but gaps in data, code inventory or ownership will slow any migration. **Recommendations:** - Start master data cleanup now, it is cheap and useful for every target system. - Run a fit-gap against two target options using real process scripts. - Agree retention rules with audit so the archive scope is known. #### Planning well **Min:** 60 **Max:** 79 **Verdict:** Most foundations exist. The remaining risk is execution: cutover timing, add-on replacements and history strategy. **Recommendations:** - Fix the target platform and choose the implementation partner. - Decide which history migrates and which goes to a read-only archive. - Schedule mock loads well before a fiscal year end. #### Ready to execute **Min:** 80 **Max:** 100 **Verdict:** You have the owner, data quality and documentation a migration needs. Protect the timeline and avoid scope creep. **Recommendations:** - Lock scope and freeze new GP customizations. - Plan at least two full mock migrations with finance sign-off on balances. - Prepare a rollback and a parallel-run window for the first close. ## Content **Intro:** 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. **Sections:** #### How to use this assessment **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### When does Dynamics GP support end? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms dynamics gp end of support, dynamics gp end of life, gp migration assessment, what to replace dynamics gp with, dynamics gp to business central, dynamics gp alternatives, gp end of life plan, gp migration readiness --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json