Dynamics GP to Business Central Migration: The Hidden Cost of Waiting
The question every Dynamics GP finance leader is quietly asking
If you run finance on Microsoft Dynamics GP, you already know the platform has served you well. It closes the books, it handles the general ledger, and your team knows exactly where everything lives. So the instinct to leave it alone is understandable.
But there is a question sitting under most GP planning conversations right now, and it is rarely said out loud: "How long can we responsibly keep running on a product Microsoft has stopped selling?"
That question deserves a clear, unemotional answer — not a sales pitch. Because the decision to migrate from Dynamics GP to Business Central is not really a software decision. It is a risk, cost, and timing decision. And for most mid-market finance teams, the expensive mistake is not choosing the wrong platform. It is waiting too long to choose at all.
What Microsoft has actually announced
Let's separate fact from rumour, because a lot of what circulates about "Dynamics GP end of life" is exaggerated in both directions.
Here is what Microsoft has confirmed:
- Sales of new perpetual (owned) GP licenses stopped on 1 April 2025.
- Sales of new subscription GP licenses stop on 1 April 2026 — after which no new customer can adopt GP in any form.
- Mainstream product support ends on 31 December 2029. This covers product enhancements, regulatory and tax updates, service packs, and technical support.
- Security updates continue until 30 April 2031.
- The final major update for GP is expected around October 2028.
- Existing GP customers remain covered under Microsoft's Modern Lifecycle Policy until those dates. (For a fuller breakdown of what remains supported and for how long, see this guide to Dynamics GP support lifecycle policies and options.)
So GP is not switching off tomorrow. Your system will keep running. But the trajectory is fixed and public: no new investment, a hard stop on functional and tax updates at the end of 2029, and security-only life support after that.
For a finance leader, one line matters more than the rest. After 31 December 2029, you stop receiving regulatory and tax updates. For a system whose entire job is compliant financial reporting and accurate tax handling, that is the date that should anchor your planning — not 2031.
Why "we'll deal with it later" is the costliest option
Delay feels free. It isn't. The cost of waiting is real, it compounds, and most of it never appears on a software invoice. Here is where it accumulates.
Compliance and tax risk. Once regulatory updates end, every payroll change, tax-rate revision, or reporting requirement becomes a manual workaround or a custom fix. Each one carries risk of error, and errors in financial reporting are the kind auditors and boards notice.
Rising cost to stand still. As Dynamics GP expertise becomes scarcer, the specialists who maintain aging on-premises systems become more expensive. Server refreshes, database maintenance, and third-party integrations that were "set and forget" start demanding attention — and budget.
A shrinking, more crowded runway. A well-run mid-market ERP implementation typically takes six to eighteen months, depending on data complexity, integrations, and the number of entities involved. Work backward from the end of 2029 and the math gets uncomfortable quickly. A complex, multi-entity migration that needs eighteen months should be in active implementation well before 2028 — which means vendor selection and planning need to happen in 2027. The organisations that wait until 2028 to start will be competing for the same finite pool of experienced consultants, at the same time, at the worst possible negotiating position.
Opportunity cost. This is the one finance leaders underestimate most. Every quarter on GP is a quarter without real-time dashboards, without cloud accessibility for a hybrid finance team, and without the AI-assisted capabilities now built into modern ERP. The competitor who migrated last year is closing faster and forecasting with better data. That gap doesn't show up as a line item, but it is a cost all the same.
Waiting doesn't remove the migration. It just makes the same migration more expensive, more rushed, and riskier.
What you actually move to — and why it fits GP finance teams
Microsoft's designated successor for Dynamics GP is Dynamics 365 Business Central, a cloud ERP built for small and mid-sized organisations. (Larger or more complex organisations sometimes land on Dynamics 365 Finance instead — worth confirming which fits before you scope anything.) For a GP finance team, three things matter more than the feature list.
You gain visibility, not just a new interface. The biggest change GP leaders report after moving is not the software — it's the shift from waiting on month-end reports to seeing cash position, margin, and outstanding receivables in real time. When leadership can see a cash-flow trend forming weeks earlier, decisions get made before problems escalate rather than after.
AI is included, not an upsell. Microsoft Copilot is included with a Business Central online licence at no additional cost. In practice, that means routine finance work — matching, categorising, drafting — gets faster. Microsoft's 2026 release wave 1 extends this further with agent capabilities such as a payables agent that reads incoming invoices, matches vendors and accounts, and prepares them for approval, always with a human reviewing before anything posts. The point for finance is not novelty; it's fewer manual keystrokes and more time on analysis.
It stops the upgrade treadmill. Business Central updates automatically in the cloud, so you leave behind the cycle of major version upgrades, server maintenance, and end-of-support anxiety that defined the GP years. You migrate once, then you stay current with ongoing support rather than re-planning an upgrade every few years.
The honest caveat: Business Central is not GP with a new coat of paint. The data model is different, some GP customisations won't carry across one-to-one, and your chart of accounts and dimensions deserve a genuine rethink rather than a lift-and-shift. That is exactly why the migration is a project to plan, not a patch to apply — and why the partner you choose matters.
The mistakes that turn good migrations bad
Having delivered ERP migrations across the UK, US, and Canada, the same avoidable errors show up again and again. Knowing them in advance is half the protection.
Migrating your mess. The temptation is to replicate GP exactly — same accounts, same processes, same workarounds. A migration is the rare chance to clean up a bloated chart of accounts and retire manual processes. Skip that, and you pay to carry twenty years of clutter into a new system.
Underestimating data. Historical data decisions — how many years to migrate, what to archive, how to reconcile — are where timelines slip. This work should start early, not in the final month.
Treating it as an IT project. ERP migration is a business transformation that finance and operations must own. When it's delegated entirely to IT, adoption suffers and the value never materialises.
Choosing on price alone. The cheapest quote often reflects the narrowest scope. What protects you is a partner who understands GP, understands your industry, and has actually delivered these migrations before — not one discovering the pitfalls on your budget. If you want a rough order of magnitude before you talk to anyone, an ERP implementation cost calculator and a Business Central pricing and licensing breakdown will get you into the right range.
How a finance leader should decide — a simple framework
You don't need a hundred-page evaluation. You need honest answers to five questions.
- When does our compliance risk become unacceptable? Anchor to 31 December 2029, the end of regulatory and tax updates — and work backward from there, not from 2031.
- How complex is our environment, really? Count your entities, integrations, customisations, and years of historical data. The more of each, the longer the runway you need and the sooner you must start.
- What is standing still actually costing us? Add up maintenance, scarce-skills premiums, and the opportunity cost of delayed reporting and forecasting. Put a number on it.
- Do we have an internal owner? A migration without a finance or operations sponsor is a migration in trouble. Identify that person before anything else.
- Is our partner Microsoft-certified and GP-experienced? The gap between a smooth migration and a painful one is almost entirely down to who runs it.
Running Dynamics NAV rather than GP? The same timing logic applies — see the NAV to Business Central upgrade path.
If your honest answers point toward complexity and a 2027–2028 start, the responsible move is to begin scoping now — while you still have negotiating leverage and a calm timeline.
The bottom line
Dynamics GP will keep running for years. But "still running" and "still the right decision" are not the same thing. The support clock is fixed, the runway is finite, and the cost of every option except acting is rising quietly in the background.
The finance leaders who come out of this well won't be the ones who moved fastest. They'll be the ones who moved deliberately — who scoped early, cleaned up as they went, chose an experienced Microsoft partner, and turned a forced end-of-life into a genuine upgrade in visibility, efficiency, and confidence.
Take the next step
Not sure where your organisation sits on the timeline? Start with a Dynamics GP to Business Central migration assessment from Dynamics Square. In a focused session, our Microsoft-certified consultants map your environment's complexity, estimate a realistic timeline and cost range, and give you a clear-eyed view of your compliance runway — no obligation, no pressure.
If you're earlier in your thinking, walk through the five steps of a GP to Business Central migration to see how a structured move works phase by phase, or size the investment with the ERP implementation cost calculator.
Request your Dynamics GP migration assessment → — and replace "how long can we wait?" with a plan you can take to the board.
Frequently Asked Questions
When does Microsoft Dynamics GP support actually end?
Mainstream support — including product enhancements, tax and regulatory updates, and technical support — ends on 31 December 2029. Security updates continue until 30 April 2031. Microsoft stopped selling new perpetual GP licenses on 1 April 2025 and will stop selling new subscription licenses on 1 April 2026.
Do I have to migrate off Dynamics GP immediately?
No. Existing GP systems will keep running, and you remain supported under Microsoft's Modern Lifecycle Policy until the dates above. The urgency is about planning, not panic: because migrations typically take six to eighteen months, complex environments should begin scoping in 2027 to avoid a rushed 2028–2029 timeline.
How long does a Dynamics GP to Business Central migration take?
Most mid-market migrations take between six and eighteen months, depending on the number of entities, integrations, customisations, and years of historical data involved. A clear scope and early data decisions are the biggest factors in staying on the shorter end of that range.
Is Business Central a like-for-like replacement for GP?
Functionally it covers the same core finance and operations ground and more, but it is a different, cloud-based platform with a different data model. Some GP customisations won't transfer directly, which is why a migration is best treated as a chance to modernise processes rather than replicate them exactly.
Does Business Central include AI, and does it cost extra? Microsoft Copilot is included with a Business Central online licence at no additional cost. Microsoft's 2026 release wave expands this with agent capabilities — such as a payables agent that prepares invoices for approval — always with human review before anything is posted.
What's the biggest risk of waiting too long to migrate?
Beyond compliance exposure once tax and regulatory updates end in 2029, the practical risk is the shrinking runway: as more GP customers migrate at once, experienced consultants become scarcer and more expensive, and you lose negotiating leverage. Acting early is both cheaper and lower-risk.