# GP vs Business Central Migration Cost Comparison Calculator

> Source: https://netray.co/tools/gp-to-business-central-migration-cost-comparison-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Multi-year cost comparison of staying on GP versus moving to Business Central, with payback period and a horizon chart.

## Category

cost-finance

## Erp

Microsoft Dynamics GP

## Audience

- CFO
- Controller
- IT manager

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### GP annual support or enhancement plan

**Key:** gp_support

**Type:** number

**Default:** 38000

**Min:** 0

**Step:** 1000

**Unit:** per year

**Help:** From your latest invoice.

#### GP hosting, servers and backups

**Key:** gp_hosting

**Type:** number

**Default:** 24000

**Min:** 0

**Step:** 1000

**Unit:** per year

#### GP admin and DBA labour

**Key:** gp_admin

**Type:** number

**Default:** 30000

**Min:** 0

**Step:** 1000

**Unit:** per year

**Help:** Share of salaries spent on GP.

#### GP add-on maintenance

**Key:** gp_addons

**Type:** number

**Default:** 12000

**Min:** 0

**Step:** 500

**Unit:** per year

#### Business Central users

**Key:** bc_users

**Type:** number

**Default:** 55

**Min:** 1

**Step:** 1

**Unit:** users

#### BC price per user per month

**Key:** bc_price

**Type:** number

**Default:** 80

**Min:** 10

**Step:** 5

**Unit:** per month

**Help:** Use your quote, not list price.

#### BC add-on subscriptions

**Key:** bc_addons

**Type:** number

**Default:** 9000

**Min:** 0

**Step:** 500

**Unit:** per year

#### BC admin and partner support

**Key:** bc_admin

**Type:** number

**Default:** 14000

**Min:** 0

**Step:** 1000

**Unit:** per year

#### One-time migration cost

**Key:** one_time

**Type:** number

**Default:** 120000

**Min:** 0

**Step:** 5000

**Unit:** once

**Help:** Partner services, data migration, training, testing.

#### Comparison horizon

**Key:** years

**Type:** slider

**Default:** 5

**Min:** 1

**Max:** 10

**Step:** 1

**Unit:** years

**Outputs:**

#### GP annual run cost

**Key:** gp_annual

**Expr:** gp_support + gp_hosting + gp_admin + gp_addons

**Format:** currency

#### Business Central annual run cost

**Key:** bc_annual

**Expr:** bc_users * bc_price * 12 + bc_addons + bc_admin

**Format:** currency

#### GP cost over horizon

**Key:** gp_total

**Expr:** gp_annual * years

**Format:** currency

#### BC cost over horizon incl. migration

**Key:** bc_total

**Expr:** bc_annual * years + one_time

**Format:** currency

#### Net difference (positive favours BC)

**Key:** savings

**Expr:** gp_total - bc_total

**Format:** currency

**Primary:** true

#### Annual run cost difference

**Key:** annual_delta

**Expr:** gp_annual - bc_annual

**Format:** currency

#### Payback on one-time cost

**Key:** payback

**Expr:** if(gt(annual_delta, 0), one_time / annual_delta, 0)

**Format:** years

**Primary:** true

**Description:** Zero means no payback from run cost alone.

**Chart:**

#### Cumulative cost by horizon

**Type:** line

**X:** years

**From:** 1

**To:** 10

**Steps:** 10

**Series:**

- gp_total
- bc_total

**Disclaimer:** A simple cost model from your own inputs. It ignores benefits such as productivity, risk reduction, support lifecycle and upgrade effort, and does not include prices from any vendor. Confirm numbers with your own quotes.

## Content

**Intro:** Finance leaders need a number before they approve a move off GP. This calculator compares the ongoing cost of GP with Business Central over a horizon you choose, including the one-time migration spend.

**Sections:**

#### How to use the calculator

**Body:** Fill GP costs from real invoices and payroll allocations, including hosting and a fair share of the people who keep GP running. Enter Business Central costs from a partner quote: users, price per user and add-ons. Add the one-time cost for migration, data work, testing and training. Move the horizon slider to see how the break-even changes. The chart plots cumulative cost for both options.

**Bullets:**

- Use real invoices for GP
- Use a quote for Business Central
- Include internal labour fairly on both sides
- Test several horizons, not only five years

#### The model

**Body:** Each platform has an annual run cost. GP is support, hosting, admin labour and add-ons. Business Central is users times price times twelve, plus add-ons and admin or partner support. Total cost over the horizon multiplies annual cost by years, with the one-time cost added to Business Central. Payback is the one-time cost divided by the annual run cost saving, shown only when Business Central runs cheaper per year.

#### Reading the result

**Body:** A positive net difference favours Business Central over your horizon. If the payback is longer than your horizon, the move is justified by other factors such as support lifecycle, security patching or capabilities, not cost. A negative result is not a reason to stay if GP will lose support, because the cost of an unsupported system is risk that this model does not price. Run a conservative case with higher migration cost and lower savings.

#### Common mistakes

**Body:** Leaving internal labour out of GP costs makes GP look cheaper than it is. Using list prices instead of a quote, or forgetting add-on subscriptions in the cloud, distorts Business Central. Another error is ignoring the cost of running both systems in parallel for a close or two. Add that to the one-time cost. Finally, remember cloud subscription pricing is recurring, so compare over a long enough horizon.

**Cta:** If you want help estimating migration cost from your actual GP data volumes and add-ons, we can review your inputs. Optional.

**Faq:**

#### Does this include Microsoft list prices?

**Answer:** No. You enter your own quoted price per user because prices and licence types vary by plan, region, agreement and over time. Always use a current partner quote.

#### Why compare over several years?

**Answer:** Migration is front-loaded and Business Central is a subscription, so the answer changes with the horizon. Five years is a common view for a business case, with a longer view as a sensitivity check.

#### What is not in this model?

**Answer:** Productivity gains, risk reduction, compliance, upgrades, extra modules and the cost of delay. These matter, so add them in your business case alongside this cost view.

#### What if GP is cheaper to run?

**Answer:** That can happen for small user counts or heavy subscriptions. If GP support is ending, weigh the risk and effort of staying unsupported, and compare other targets besides Business Central.

## Search terms

gp vs business central cost, dynamics gp migration cost, business central cost calculator, gp to business central tco, dynamics gp total cost of ownership, erp migration business case, gp vs business central pricing

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