# Dynamics GP End of Support: Cost of Waiting Calculator

> Source: https://netray.co/tools/dynamics-gp-unsupported-risk-exposure-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Adds up support fees, compensating controls, manual workarounds and expected incident loss to show what another year on Dynamics GP really costs.

## Category

microsoft-dynamics

## Erp

Microsoft Dynamics GP

## Audience

- CFO
- Controller
- IT manager

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### Active GP users

**Key:** users

**Type:** number

**Default:** 25

**Min:** 1

**Step:** 1

**Unit:** users

#### Annual support and enhancement fees

**Key:** support_cost

**Type:** number

**Default:** 30000

**Min:** 0

**Step:** 500

**Unit:** per year

**Help:** What you still pay Microsoft or your partner each year to keep GP running.

#### Compensating security controls

**Key:** controls

**Type:** number

**Default:** 12000

**Min:** 0

**Step:** 500

**Unit:** per year

**Help:** Extra network isolation, monitoring, backups or audit effort because the product ages.

#### Manual workaround hours

**Key:** workaround_hours

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 5

**Unit:** hours/month

**Help:** Spreadsheets, re-keying and reconciliations that exist because GP cannot do the job.

#### Loaded hourly rate

**Key:** hourly

**Type:** number

**Default:** 55

**Min:** 0

**Step:** 5

**Unit:** per hour

#### Annual incident probability

**Key:** incident_prob

**Type:** slider

**Default:** 15

**Min:** 0

**Max:** 100

**Step:** 1

**Unit:** %

**Help:** Your own estimate of a serious outage, breach or failed audit finding in a year.

#### Cost of one incident

**Key:** incident_cost

**Type:** number

**Default:** 80000

**Min:** 0

**Step:** 5000

**Unit:** per event

#### Planning horizon

**Key:** years

**Type:** slider

**Default:** 3

**Min:** 1

**Max:** 10

**Step:** 1

**Unit:** years

**Outputs:**

#### Workaround labour per year

**Key:** workaround_annual

**Expr:** workaround_hours * 12 * hourly

**Format:** currency

#### Expected incident loss per year

**Key:** expected_loss

**Expr:** incident_prob / 100 * incident_cost

**Format:** currency

**Description:** Probability times impact.

#### True annual cost of staying

**Key:** annual_total

**Expr:** support_cost + controls + workaround_annual + expected_loss

**Format:** currency

**Primary:** true

#### Cost per user per year

**Key:** per_user

**Expr:** annual_total / users

**Format:** currency

#### Share that is not on an invoice

**Key:** hidden_share

**Expr:** (controls + workaround_annual + expected_loss) / annual_total * 100

**Format:** percent

#### Total over horizon

**Key:** multi_year

**Expr:** annual_total * years

**Format:** currency

**Primary:** true

**Chart:**

#### Annual cost of staying vs incident probability

**Type:** line

**X:** incident_prob

**From:** 0

**To:** 60

**Steps:** 31

**Series:**

- annual_total

**Disclaimer:** Planning estimate built from your own inputs. Confirm current Dynamics GP lifecycle dates on Microsoft's lifecycle pages.

## Content

**Intro:** Many Dynamics GP teams compare the cost of a migration against the invoice they pay today. That comparison hides the costs that grow as the product ages. This calculator puts those hidden costs on one line so the decision can be made on numbers.

**Sections:**

#### How to use it

**Body:** Enter the fees you still pay, then estimate the extra work and risk. Be honest with workaround hours: ask finance who exports GP data into Excel each month-end and for how long. For incident probability use a range, run the calculator at 5, 15 and 30 percent, and watch the chart line to see how sensitive the answer is.

**Bullets:**

- Start with real invoices
- Ask the AP and GL teams for hours
- Run low, mid and high probability
- Export the result for the business case

#### The method

**Body:** Annual cost of staying equals support fees plus compensating controls plus workaround labour plus expected loss. Expected loss is probability times impact, the standard risk-weighted approach. Workaround labour is hours per month times 12 times the loaded rate. The tool does not discount future years, so treat the multi-year figure as a simple sum.

#### Reading the result

**Body:** If the share that is not on an invoice is above 40 percent, your visible budget is understating the problem. Compare the multi-year figure with the migration investment from the other calculators in this set. Common mistakes are setting incident probability to zero because nothing has happened yet, and ignoring auditor time spent explaining legacy controls.

**Cta:** If you want the workaround hours and report usage measured from your actual GP data instead of estimated, Netray can review it with you. This calculator works fully without that.

**Faq:**

#### Does Dynamics GP stop working at end of support?

**Answer:** No. The software keeps running, but Microsoft stops providing the fixes and updates described in its lifecycle policy. The risk grows over time through regulatory changes, security exposure and compatibility with newer operating systems and SQL Server versions.

#### What incident probability should I use?

**Answer:** Use a range rather than a single guess. Five percent suits a well-isolated system with strong backups, thirty percent suits an exposed system with key-person dependency. The chart shows how total cost moves across the range.

#### Is the cost of waiting always higher than migrating?

**Answer:** No. For a small, stable company with few workarounds, staying a little longer can be rational. The calculator shows whether your own numbers support waiting or not.

#### Where do I find the official dates?

**Answer:** Microsoft publishes lifecycle dates for each GP release on its lifecycle site. Check your exact version, because year-versioned releases carry different dates.

## Search terms

dynamics gp end of support, dynamics gp end of life cost, stay on dynamics gp risk, gp unsupported risk, dynamics gp migration business case, dynamics gp security risk, cost of delaying erp migration

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json