Microsoft Dynamics GP End of Support: Should You Stay, Upgrade, or Move to Business Central?
Dynamics GP may still be doing exactly what your company needs. Finance knows how to close the books, your reports are established, and payroll, purchasing, or manufacturing may depend on GP-specific processes. Replacing it would be a significant investment.
But Microsoft is ending GP support, and waiting has a cost of its own. You could spend another two years maintaining old infrastructure, rebuilding GP customizations, or preparing reports by hand, only to face the same ERP decision closer to the deadline.
The question is how long staying on GP makes financial and operational sense. That depends on your version, the cost of keeping it supported, what Business Central would actually replace, and how much time your company needs to make the change.
When does Microsoft Dynamics GP support end?
Microsoft will end Dynamics GP product enhancements, tax and regulatory updates, and technical support on December 31, 2029. Security updates and patches, if needed, will continue through April 30, 2031, according to Microsoft's Dynamics GP lifecycle policy.
Date | What changes |
|---|---|
July 14, 2026 | Extended support ended for GP 2016 and GP 2016 R2. |
January 11, 2028 | Extended support ends for GP 2018 and GP 2018 R2 under the Fixed Lifecycle policy. |
December 31, 2029 | Microsoft ends GP enhancements, tax and regulatory updates, and technical support. |
April 30, 2031 | Security updates and patches end, along with GP Service Plan coverage and specified licensing options. |
GP 18.x is governed by Microsoft's Modern Lifecycle policy. To stay supported, customers must keep current by taking at least one of the three planned annual updates. Older releases have different deadlines. The version number and the support status of your SQL Server, Windows environment, and third-party products should be checked together.
Can you continue using GP after 2029?
An existing GP installation will not automatically stop running. Continued use depends on its license terms, hosting arrangements, and technology dependencies.
But from January 2030, Microsoft will no longer provide regular technical support or tax and regulatory updates. That creates a more immediate concern for companies running GP Payroll or depending on tax-related changes. The April 2031 security-patch date does not extend those other services.
Microsoft has also announced licensing restrictions effective April 30, 2031, including the end of specified subscription renewals and the ability to add perpetual users. Confirm the rules that apply to your own agreement before assuming you can operate or expand GP indefinitely.
Should you stay on GP, upgrade it, or replace it?
There are four credible choices. An upgrade to a current GP release may preserve support for a few more years. Moving to Business Central involves replacing GP with a different ERP and validating its fit across the business.
Option | When it makes sense | What could change the decision |
|---|---|---|
Stay on GP for now | GP is supported, stable, and meeting business requirements. | Unsupported add-ons, growing support costs, or manual processes that hold the business back. |
Upgrade GP | You need to restore or preserve support while preparing for eventual replacement. | The upgrade requires major infrastructure or customization spending that will soon be discarded. |
Move to Business Central | It meets your financial and operational requirements at a justifiable total cost. | Payroll, manufacturing, reporting, or integration gaps expand the scope and budget. |
Evaluate another ERP | Essential requirements cannot be met by Business Central at an acceptable cost. | A validated Business Central design resolves those requirements without excessive customization. |
Stay when GP is reliable and the numbers support it
A company running a supported GP release, with stable financial processes and few new requirements, may have a good reason to keep it for another year. Replacing the ERP now could pull finance and IT away from more urgent priorities.
Before approving that choice, calculate annual GP spending, confirm how long key vendors will support the environment, and set a date to revisit the replacement decision. Include planned server upgrades and any critical GP changes in the forecast.
Upgrade when the additional supported time is worth the expense
A company on GP 2016, for example, is already beyond its extended-support date. Upgrading may be the practical way to reduce risk while the company evaluates its next ERP.
Ask for a complete upgrade estimate. Include SQL Server and Windows changes, payroll and ISV compatibility, modified forms, SmartList and SQL reports, integrations, and user testing. Microsoft's GP upgrade checklist calls for validating customizations and connected applications.
Compare that upgrade cost with the amount of supported time it buys. You may be paying for GP infrastructure and customizations that will be replaced again during the ERP migration. Sometimes that overlap is necessary, but it should be visible in the investment decision.
What will change if you move from GP to Business Central?
Both products support core financial management. Their accounting structures, reporting tools, development models, and operational features differ. Microsoft's GP-to-Business Central process guide documents changes to familiar accounting tasks.
GP capability or dependency | What to validate in Business Central |
|---|---|
U.S. Payroll | Business Central does not provide an equivalent native U.S. payroll module. Identify the provider or extension, payroll-to-GL integration, and replacement cost. |
Manufacturing | Manufacturing is available with Business Central Premium. Test BOMs, routings, production orders, WIP, inventory valuation, and cost variances. |
SmartList and financial reporting | Reproduce the actual management reports, inquiries, reconciliations, and custom SQL reports used for close and decision-making. |
Customizations and integrations | GP Dexterity code and direct SQL integrations cannot simply run against Business Central online. Decide what to retire, replace, or rebuild using supported extensions and APIs. |
Project accounting and service management | Validate project billing, contract rules, margins, service orders, and repair processes against real transactions. |
Historical data | Confirm how employees will retrieve prior invoices, payments, GL detail, and audit records. Selected GP history can be stored as snapshots rather than standard BC transactions. |
Microsoft confirms that Business Central Premium includes manufacturing and service management. Its GP migration documentation identifies the records its tools can migrate and how historical snapshots are stored.
Consider a manufacturer that uses GP production orders, item costing, and a custom month-end report for WIP and variances. Before signing off on Business Central, run a representative production order, post material consumption and capacity, and compare inventory values and GL entries with the required accounting results. If the reports or numbers differ, identify the configuration or additional software needed to meet the requirement.
Finance should do the same with its critical reports. A demonstration of a standard Business Central dashboard does not establish that the controller can reproduce the company's month-end P&L, reconciliations, and audit reports.
Microsoft's migration tools can move supported GP data. They do not automatically replace the processes, extensions, and integrations built around that data.
What does staying on GP cost compared with replacing it?
Use the same planning horizon for every option, such as three to five years. A GP maintenance invoice and a Business Central subscription quote do not provide a complete comparison.
Cost category | Keep or upgrade GP | Replace GP |
|---|---|---|
Licensing and software | GP maintenance or subscription, ISV products, and renewal obligations | Business Central Essentials or Premium, extensions, and separate payroll software where needed |
Infrastructure | Servers, SQL Server, hosting, backups, security, and upgrades | SaaS subscription or hosting, integrations, and any retained GP environment for historical access |
Consulting | GP support, repairs, upgrades, and customization maintenance | Application design, implementation, data migration, reporting, integrations, testing, and support |
Internal effort | System administration, manual reporting, recurring corrections, and user support | Finance and operations input, data cleanup, testing, training, cutover, and ongoing administration |
Transition | Possible GP upgrade now and ERP replacement later | Parallel operation, final reconciliations, and cutover support |
Include costs that tend to be left out of replacement estimates. If GP currently handles payroll, Business Central licensing alone cannot cover the replacement. The same applies to a custom integration, a reporting solution, or historical record access that must remain available after cutover.
Waiting carries an opportunity cost
Suppose your finance team spends 10 hours a week exporting GP data, correcting spreadsheets, and assembling reports. At an estimated labor cost of $60 an hour, including wages, payroll taxes, and benefits, that represents $31,200 of employee time each year, or $62,400 over two years.
That is an illustrative cost of effort, not a guaranteed saving from replacing GP. Some of those tasks may be necessary in any ERP. A relatively small GP reporting improvement might eliminate them for less than a migration. Measure the current hours, test the proposed improvement, and count only the benefit it can reasonably deliver.
Look beyond finance, too. Delayed invoices can slow collections. Poor visibility into WIP can leave margin problems undiscovered until month-end. Separate inventory spreadsheets can add reconciliations and errors. Use actual billing delays, corrections, employee hours, and costs to estimate the impact. Avoid counting the same issue in several categories.
Waiting may also increase the cost of the eventual migration. As the 2029 deadline approaches, companies may compete for the same experienced GP and Business Central consultants. Limited availability could delay a start date or force additional staffing to meet a fixed go-live deadline. Consulting rates could rise, although there is no basis to promise a particular increase. Compressed testing and extended parallel operation can add expense even without a change in hourly rates.
Microsoft increased Business Central list prices in November 2025, demonstrating that the licensing assumptions used in today's comparison may not hold indefinitely.
Another date may affect the decision. Microsoft's Bridge to Cloud 3 promotion offers eligible on-premises Dynamics customers a 30% discount on qualifying three-year Dynamics 365 subscriptions, with enrollment scheduled to end December 31, 2027. Review eligibility, existing Enhancement Plan requirements, and the subscription commitment before including the discount in a forecast.
The promotion may change the economics of the timing decision. Application fit should still be established before committing to Business Central.
When must you decide?
If your GP version is already unsupported, address that exposure now. You may need an upgrade while evaluating the replacement, or you may have enough information to proceed directly with a new ERP.
If GP is supported, choose a target date for completing the application and investment decision, then build a replacement schedule backward from the intended go-live. Account for requirements review, data preparation, integrations, report redevelopment, business testing, training, and cutover. Avoid major close and payroll periods where possible.
A company using GP mainly for GL, AP, and AR will have different requirements from one using payroll, manufacturing, multiple legal entities, and several GP-specific integrations. Neither should accept an implementation duration before those dependencies are reviewed.
The December 2027 Bridge to Cloud 3 enrollment deadline is a separate licensing consideration. It may be worth evaluating, but it does not require a company to select Business Central before confirming that it meets the business's needs.
What should leadership know before approving the investment?
Ask the controller which reports, reconciliations, and payroll processes must be preserved. Ask operations which inventory, production, project, or service transactions need to produce the same results. Ask IT which GP customizations, integrations, servers, and third-party applications are involved.
Then compare the credible options on three measures: total cost over the same period, what the business gains or gives up, and the time needed to make the change safely. The recommendation should state whether to stay, upgrade, replace, or evaluate another ERP, along with the reasons and the date to revisit the decision.
If Business Central looks promising, the Dynamics 365 Implementation Planner can provide an early implementation cost range based on scope and complexity. It is a planning estimate, not a quote. A Business Central Confidence Roadmap can evaluate application fit, scope, risks, dependencies, and investment expectations before approval.
Microsoft has established the GP support deadline. Your company still needs to decide how much longer GP is worth maintaining and whether a replacement will solve problems that justify the cost.
If you're weighing a GP upgrade against a move to Business Central,
