Bramvia — Business Central Experts

Dynamics GP vs Business Central: what changes, what it costs, and how GP customers move

Microsoft has ended new Dynamics GP sales and set the clock on support. What Business Central does differently, what GP users miss most, what a migration costs ($30,000-120,000), and how to move without losing 20 years of history.

Short answer: Dynamics GP has no future roadmap — Microsoft stopped selling it to new customers and its support horizon is fixed, with no new functionality coming. Business Central is Microsoft's designated successor for GP customers: same vendor, cloud-native, two updates a year included, Copilot and AI agents, and Power BI apps in the box. The move is real work, not a version upgrade: GP's data model, Dexterity customizations, SmartLists, Management Reporter and third-party add-ons do not carry over. A typical US GP migration runs $30,000-120,000 depending on entities, customizations and integrations, plus licenses at $80-110 per full user per month. The good news for GP shops: your history stays accessible, your chart of accounts can be rationalized on the way, and most GP add-ons have a Business Central equivalent on AppSource.

Why GP customers are moving now

What actually changes

Area Dynamics GP Business Central
Deployment On-premises (or hosted) Cloud-native SaaS (on-premises available)
Updates Year-end and tax updates; upgrades are projects Two releases a year, included and automatic
Customization Dexterity, VBA, modified forms AL extensions, decoupled from the standard
Reporting SmartLists, Management Reporter, SSRS Power BI (4 apps included), financial reports, analysis mode
Integrations eConnect, Integration Manager, direct SQL REST APIs, OData, webhooks — no direct SQL
AI None Copilot included; agents billed by consumption
Multi-company Separate databases Multiple companies in one tenant, intercompany, consolidation
US sales tax GP tax tables or add-on Standard localization plus Avalara or Vertex
Licensing Perpetual + enhancement plan Per user per month ($80 Essentials, $110 Premium, $8 Team Members)

What GP users miss most (and what replaces it)

SmartLists. The thing GP users love. Business Central's answer is analysis mode on any list plus saved views and Power BI — more powerful, different muscle memory. Budget training time for this specifically.

Management Reporter. Replaced by native financial reports (row/column definitions) and, from version 29, report packages delivered as a single scheduled PDF. Most MR layouts rebuild in days, not weeks.

Fixed Assets and Payroll. Business Central has fixed assets natively. US payroll it does not have — GP customers running GP Payroll need a third-party payroll system integrated by journal. This is the single most common surprise, so raise it in the first meeting.

Dexterity customizations. They don't convert. Each one gets triaged: covered by the standard, available as an AppSource app, or rebuilt as an AL extension. In practice a large share of GP customizations exist in the Business Central standard.

20 years of history. Migrate masters, open transactions and opening balances; keep GP read-only as an archive, or extract history to a data warehouse or Power BI dataset. Migrating two decades of detail is expensive and rarely used.

What a GP migration costs in the US

Profile Typical project cost
Single company, standard GP modules, few customizations, 10-25 users $30,000-55,000
Multi-company, moderate Dexterity/integration footprint, 25-75 users $55,000-120,000
Many entities, heavy customization, several ISV add-ons $120,000+

Plus licenses. Note the licensing shift: GP was perpetual plus an annual enhancement plan; Business Central is a subscription. Compare five-year total cost, including the servers and upgrade projects you stop paying for. Full US cost breakdown.

How the move works

  1. Inventory — GP modules in use, Dexterity/VBA customizations, SmartLists that matter, integrations, ISV add-ons, and your real chart of accounts.
  2. Triage — standard / AppSource app / AL extension, for each customization. This step is where a good partner saves you the most money.
  3. Chart of accounts rationalization — GP charts grow segments over 20 years. The migration is the moment to simplify; dimensions in Business Central do the work segments used to.
  4. Data — masters, open AR/AP, inventory, opening balances. History archived.
  5. Test with your real month-end close in a sandbox, not with demo data.
  6. Cut over at a period end, GP read-only as the fallback.

Typically 4-8 months. We do this work for US companies from Europe and with team members across several US states, each part invoiced only after you accept it.

FAQ

Will GP stop working? No. It stops receiving new functionality now and support at the end of its published lifecycle window. It keeps running — unsupported, on servers you maintain.

Can we keep GP for history and run Business Central live? Yes, and it is the usual approach: GP read-only for lookups, Business Central for operations. Plan how long you'll keep the GP server licensed.

What about GP Payroll? Business Central has no US payroll. You'll integrate a payroll provider and post summary journals — standard practice, but budget for it.

Is Business Central cheaper than GP? Licenses are a new recurring line; servers, SQL, backups and upgrade projects disappear. Over five years most GP shops come out level or ahead — and get AI and included Power BI that GP can never have.

Are there Microsoft incentives for GP customers moving to the cloud? There have been, and terms change. Ask a CSP partner for what's current before you build the business case around it.

Running GP and wondering what your move looks like? Free assessment, no commitment — module inventory, customization triage and a phased plan with a real go-live date.


Bramvia · bramvia.net