← Insights
Platform Fit · Microsoft ERP
GP is retiring. The real question isn't which product replaces it.
Subscription sales for Dynamics GP (Great Plains) ended in April 2026. Security support ends in 2031. For the mid-market companies still running it, the clock has started — and the decision in front of them is bigger than Business Central versus Finance & Supply Chain Management (F&SCM).
Key takeaways
- Dynamics GP's subscription sales ended April 2026; mainstream support ends 2029, security updates stop entirely in 2031. The clock is real, not marketing urgency.
- The decision isn't just "which Microsoft product" — NetSuite and Sage Intacct are genuine, commonly-chosen paths for GP customers who aren't tied to the Microsoft ecosystem, not just theoretical alternatives.
- Microsoft Dynamics 365 is usually the strongest default for GP customers — ecosystem integration, cost, and AI trajectory are real, evidenced advantages — but it isn't automatically the right answer for every one of them.
- Because GP customizations don't transfer directly to any destination platform, this is also the moment to decide what the business actually needs to keep — which makes it a roadmap conversation, not a product swap.
Somewhere this quarter, a controller opened a renewal notice and noticed the subscription line for Dynamics GP looked different than it used to. Nothing has broken. Nothing is urgent in the way a system outage is urgent. But the sales window closed in April, and what used to be an open-ended "we'll deal with it eventually" has quietly become a dated decision with a real deadline behind it.
Microsoft has been unusually explicit about the timeline, which is worth taking at face value rather than reading as vendor pressure. Here's the timeline that actually matters — the sales window is already closed; the support window is what should drive planning.
Sales cutoff
Apr 2025
New perpetual GP licenses stop selling. (Passed.)
Apr 2026
New subscription GP licenses stop selling. (Passed — this year.)
Support cutoff
Dec 2029
Mainstream support ends — no more tax updates, regulatory fixes, or hotfixes. (Extended from an original Sep 2029 date, announced Jan 2025.)
Apr 2031
Security updates stop entirely.
GP remains functional for now, but Microsoft has put it in maintenance-only mode — no new features, no further investment — while Business Central ships two major releases a year plus monthly updates. 2029 is the date that actually matters for planning purposes industry EOL trackers, 2026, and Enterprise Resource Planning (ERP) migrations reliably take longer than the number anyone budgets for at the outset.
The decision underneath the decision
Most GP conversations skip straight to "we're moving to Business Central" — in part because Microsoft's own promotional messaging and a well-publicized migration discount point that direction. The field is actually wider than two Microsoft products.
$150K–$600K
Typical cost range for a mid-market GP migration, from a straightforward 20–50 user move up to a multi-entity migration with heavier customization — regardless of destination platform. The complexity of what you're actually running should set the direction, not the sales promotion attached to any one option.
This range typically excludes internal labor — industry estimates put that at another 15–25% of the base budget — and the ongoing cost of add-on modules most implementations eventually need. That figure also doesn't include what happens after go-live. Neither Business Central nor NetSuite arrives complete for most mid-market operations — both maintain active marketplaces of third-party add-ons (AppSource for Microsoft, SuiteApps for NetSuite) that most implementations end up needing for at least one function: industry-specific compliance, advanced warehouse management, multi-entity consolidation, tax automation, and similar gaps. Budgeting for the platform alone, on either side of this decision, understates what it actually costs to run.
There's a real case for staying inside the Microsoft ecosystem, and it's worth stating plainly rather than assuming it as background noise. Business Central's data structures map naturally onto decades of GP history, and it integrates with Microsoft 365, Teams, and Power BI without bolt-on connectors. On licensing alone — before either platform's add-on costs — independent comparisons consistently put Business Central meaningfully cheaper than NetSuite over three years, with the gap widening as user count grows. Layered onto Microsoft's own AI investment through Copilot, that's a substantive case, not just convenience.
Business Central fits comfortably under roughly $500M in revenue, for companies already standardized on Microsoft 365 and Power BI. That covers a lot of ground: professional services firms tracking projects and resourcing, distributors running a handful of locations, manufacturers with straightforward MRP (Material Requirements Planning) and routing needs.
F&SCM earns its place further up each of those same verticals — heavy or multi-plant manufacturing, global multi-site distribution, or retail and public-sector operations with regulatory and consolidation demands that Business Central's native tools weren't built to handle alone.
The real minority worth checking, not assuming: organizations scaling toward multiple subsidiaries, currencies, or sales channels, or ones never that tied to the Microsoft ecosystem in the first place. For those, NetSuite — or in some cases Sage Intacct — deserves a genuine look before the default gets locked in. None of that makes Dynamics 365 the wrong instinct. Most of the time, it's the right one. It's just an instinct worth testing once, not assuming by default.
If the decision already got made
Plenty of GP shops aren't choosing anymore — a recommendation already came from an existing partner, often the same one who's supported the GP instance for years and has an obvious incentive to keep the relationship moving forward on their terms. That's not automatically the wrong call. A GP partner recommending Business Central may well be right — but it's still a recommendation from someone with a financial stake in the answer. And "our GP partner suggested it" is a different kind of answer than "we evaluated it against our actual operating model," and only one of those is easy to defend to a board eighteen months into a migration that's underperforming.
A recommendation that came from the firm that benefits from it isn't wrong by default. It's just not yet independently checked — and for a decision this size, that check is cheap relative to being wrong.
Why this is a roadmap conversation, not a swap
GP customizations are built on Dexterity and C/AL — a different technical stack from either destination platform. None of it moves over directly.
What transfers is the business logic those customizations were built to solve. Deciding what's actually still needed, versus what accreted over a decade and never got cleaned up, is a strategic call, not a technical one.
It's also the same moment worth asking three other questions: whether the data feeding the new system is actually ready, whether the decision rights around it are designed rather than assumed, and whether this move is sequenced against everything else already on the roadmap — or quietly competing with it.
Sources
- 1Microsoft product lifecycle documentation, via multiple 2026 EOL trackers (Lansweeper, KPC, ABCC Group, Rand Group). Used for: April 2025 perpetual license sales end, April 2026 subscription sales end, December 2029 mainstream support end (extended from an original September 2029 date, per Microsoft's January 2025 update), April 2031 security update end.
kpcteam.com/kpposts/microsoft-dynamics-gp-great-plains-end-of-life
- 2Econix Infotech, 2026. Dynamics GP End of Life: Complete Migration Guide. Used for: migration cost and timeline ranges by user count and complexity.
econixinfotech.com/insights/dynamics-gp-end-of-life-migration-guide
- 3ABCC Group, 2026. Dynamics GP End of Life: Your Migration Options Explained. Used for: customizations not transferring directly (different technology stack) and what actually carries over.
abccgroup.com/post/dynamics-gp-end-of-life-your-migration-options-explained
- 4Multi-Entity Accounting, 2026. Dynamics 365 Business Central vs Finance. Used for: revenue and entity-count thresholds distinguishing Business Central from Finance & Supply Chain Management fit.
multientityaccounting.com/dynamics-365-business-central-vs-finance
- 5Rand Group, 2026. What Is Replacing Microsoft Dynamics GP? Used for: NetSuite and Sage Intacct as genuine alternatives for GP customers not tied to the Microsoft ecosystem.
randgroup.com/insights/microsoft/dynamics-legacy/dynamics-gp/what-is-replacing-microsoft-dynamics-gp
- 6Multiple industry sources, 2026 (Folio3, ERP Software Blog, TrueVantage, Houseblend, Digmatix). Used for: Business Central running meaningfully cheaper than NetSuite on a licensing-only, 3-year TCO basis, with the gap widening at higher user counts. Figures vary by source (roughly 20% at low user counts, 40–50%+ at scale) — no single percentage is treated as definitive.
dynamics.folio3.com, erpsoftwareblog.com, truevant.com, houseblend.io, digmatix.com — 2026
- 7ERP Software Blog / enVista, 2026. How Dynamics GP Users Choose Between Business Central and Finance & Supply Chain Management. Used for: fit criteria spanning professional services, distribution, and manufacturing, not manufacturing alone.
erpsoftwareblog.com/2026/03/how-dynamics-gp-users-choose-between-business-central-and-finance-supply-chain-management
- 8TrueVantage / TopDynamicsPartners / NetSuite SuiteCloud documentation, 2026. Used for: both Business Central (AppSource) and NetSuite (SuiteApp Marketplace, 700+ listed apps) maintaining active third-party add-on ecosystems that most mid-market implementations draw from for at least one function.
truevant.com, topdynamicspartners.com, netsuite.com/portal/platform/developer/suitebundler.shtml — 2026