Dynamics GP Renewal vs QuickBooks: Pricing the Three Renewals Left Before Microsoft’s 2029 Deadline

Written & reviewed by Ram Singh, founder, Numerawise Solutions · Last reviewed September 11, 2026

Short answer: from today there are three GP enhancement-plan renewals left that buy you anything. Microsoft ends Dynamics GP product support on 31 December 2029: no more enhancements, no more regulatory or tax updates, no more technical support. Security patches, if needed, continue only to 30 April 2031. A renewal that lands in late 2026 buys the 2027 tax tables; one in 2027 buys 2028; one in 2028 buys 2029. The renewal after that buys a product Microsoft has stopped updating. This worksheet prices each of those renewals against a QuickBooks Enterprise or QuickBooks Online subscription plus a one-time conversion, so the decision is made on your invoice rather than on the countdown.

The dates, from Microsoft’s own pages

Microsoft’s lifecycle page for Dynamics GP states that support ends on 31 December 2029 “for product enhancements, regulatory (tax) updates, and technical support,” and that “security updates/patches, if needed, will be made available until April 30, 2031.” The original announcement of 25 September 2024 had set 30 September 2029; the 15 January 2025 update moved it to year-end specifically “to allow GP customers to meet their payroll and taxes obligations for the full year.” Read that reason carefully: Microsoft itself frames the last useful deliverable as the 2029 tax and payroll updates.

Two other dates matter for anyone still on an older build. GP 2016 and 2016 R2 left extended support on 14 July 2026; if you are on either, you have been on unsupported software for two months. GP 2018 and 2018 R2 stay on the fixed lifecycle until 11 January 2028, but Microsoft notes that installing any compatible tax release or hotfix moves the install to version 18.5 or later, which enacts the Modern Lifecycle. Under that policy you stay supported only by taking at least one of the three yearly updates (typically June, October and December). In practice, every customer who applies a tax update is on the same 2029 clock.

Left column: what each remaining renewal costs

Microsoft does not publish enhancement-plan pricing; it comes from your reselling partner as a percentage of your protected list price. Copy it from the renewal notice. Then add what the notice does not show.

1. The enhancement plan itself, for the 2026–27, 2027–28 and 2028–29 cycles. Apply last year’s increase to each following year.
2. Partner support hours. Microsoft’s page tells GP customers to “reach out to their Dynamics GP reselling partner with any questions or concerns.” Your partner’s block of hours or per-incident rate is the real technical-support line.
3. The server and SQL licences GP runs on, their maintenance, and the person who patches them. Include the Windows Server and SQL Server lifecycle dates for your versions; GP is not the only clock in the room.
4. Third-party ISV modules (Mekorma, Binary Stream, SmartConnect, Management Reporter successors). Each has its own renewal and its own end-of-life posture now that the platform is retiring.
5. The last-year premium. Whatever you pay in 2029 buys a product with twelve months of tax updates left and then nothing. Price 2029 as a full renewal for a quarter of the value.

Right column: QuickBooks, and what the move costs

1. Subscription for the plan and user count, for the same 24 months. QuickBooks Enterprise is the usual landing for GP companies with multiple entities, inventory or job costing; QuickBooks Online Advanced fits single-entity service businesses. Both product pages print current prices; copy them on the day.
2. The conversion. A GP file carries segmented account strings, multiple companies, and often a decade of history. The GP to QuickBooks Enterprise page covers the scope questions; enter the fixed-price quote you receive after the scoping call.
3. What you rebuild. Management Reporter or SSRS reports become QuickBooks reports or a spreadsheet layer; account segments become classes and locations; intercompany becomes journal entries or a consolidation tool. Price each.
4. One overlap month of GP costs during the parallel close, plus internal training time.

The worksheet

Now run it a second time with a different left column: the cost of staying until after 2029. That version adds a forced migration in 2030 under time pressure, with no tax updates in the meantime, and it is the true alternative to converting now. Almost nobody chooses it deliberately; a lot of companies drift into it one renewal at a time.

A worked example, clearly hypothetical

Invented numbers. A two-company distributor pays a $14,000 enhancement plan, up 5% a year, plus $6,000 of partner hours, $4,500 of ISV renewals and roughly $9,000 of server, SQL and IT time a year. Left column over 24 months: $14,000 + $14,700 + $12,000 + $9,000 + $18,000 = $67,700, for a product with three tax cycles left.

Right column: a QuickBooks Enterprise subscription for the same seats at whatever Intuit’s page prints today (call it E), a $12,000 conversion quote for two companies with five years of history, $4,000 to replace one ISV function, $2,800 for one overlap month and $2,500 of training. Total: 2E + $21,300. The right column wins whenever E is under about $23,000 a year, and the gap widens every year the left column is renewed, because the GP lines do not fall while the countdown does.

Three things that swing the verdict

Payroll. If you run GP payroll, the tax-update line is the whole reason to renew, and it disappears after 2029. Companies that already run payroll outside GP have less to lose from leaving early and less to gain from staying.

Business Central. Microsoft’s own recommended path is Dynamics 365 Business Central, and for a company that genuinely needs an ERP that is the right comparison, not QuickBooks. Run the same worksheet with Business Central in the right column, including implementation, before you assume QuickBooks is the destination.

History. The more years of GP detail you need queryable after the move, the higher the conversion quote and the more the timing matters: a conversion done in a quiet quarter with a supported GP instance behind it is cheaper and safer than one done in 2030 against an unsupported install.

When renewing GP is the right answer

Renew if you are mid-way through a Business Central project and need GP live until go-live; if a heavily customised Dexterity build runs a process no packaged product replaces and you have budgeted the 2030 rebuild; or if a sale, merger or restructuring in the next eighteen months will change which system you need anyway. In each case the renewal is a bridge with a named end date. What the worksheet is designed to expose is the renewal with no plan behind it, three years out from a date Microsoft has already put in writing.

If the right column wins on your numbers, start with the Dynamics GP to QuickBooks Enterprise conversion page or, for a single-entity service business, the GP to QuickBooks Online page, and schedule the scoping call so the cutover lands on a period end with a supported GP instance still running behind it.

Frequently asked questions

When does Microsoft Dynamics GP support end?

Microsoft's Dynamics GP lifecycle page states that support for product enhancements, regulatory (tax) updates and technical support ends on December 31, 2029, and that security updates or patches, if needed, will be made available until April 30, 2031. The original September 2024 announcement said September 30, 2029; the January 15, 2025 update moved it to year-end so customers could complete the 2029 payroll and tax year.

Is Dynamics GP 2016 still supported?

No. Microsoft's lifecycle table shows extended support for Dynamics GP 2016 and 2016 R2 ending on July 14, 2026. GP 2018 and 2018 R2 remain on the fixed lifecycle until January 11, 2028, but applying any compatible tax release or hotfix moves the install to version 18.5 or later under the Modern Lifecycle Policy, which requires taking at least one of the three yearly updates.

Does Microsoft publish the Dynamics GP enhancement plan price?

Not on its lifecycle or support pages; enhancement-plan renewals are quoted through Microsoft's reselling partners. Use the figure on your own renewal notice for the worksheet and apply last year's percentage increase to the following years.

Should a GP company move to QuickBooks or to Business Central?

Microsoft's recommended path is Dynamics 365 Business Central, and for a company that needs a full ERP that is the right comparison. Run the same 24-month worksheet with Business Central in the right column, including implementation, before assuming QuickBooks is the destination. QuickBooks Enterprise or Online Advanced is usually the better fit for companies that use a fraction of GP's capacity; see the GP to QuickBooks Enterprise page.