Microsoft Dynamics GP End of Support: Dates and Options

The Microsoft Dynamics GP support end date is 31 December 2029, as at October 2026. On that date Microsoft stops supporting the current Dynamics GP 18.x releases for product enhancements, regulatory (tax) updates and technical support. Security patches, where needed, are due to continue until 30 April 2031. Microsoft moved the end date from 30 September 2029 to 31 December 2029, per Microsoft's Dynamics GP lifecycle page.

That gives a finance team roughly three years and two months from today. It sounds generous, but an ERP replacement rarely fits in a casual plan. Most organisations need time to choose a direction, clean data, test year-end processes, run the old and new systems side by side and train people.

This guide sets out the Dynamics GP end of support timeline, what each date means in practice, the realistic options (stay, move to Dynamics 365 Business Central, or move to another ERP) and how to sequence the work. Our team at NetMonkeys, a Manchester-headquartered managed IT support provider and Microsoft Solutions Partner, sees the infrastructure, security and data side of these projects. The choice of ERP itself is a business decision that belongs with your finance director and software partner.

What is the Microsoft Dynamics GP support end date?

The Dynamics GP end of support date is 31 December 2029, and it applies to the current version, Dynamics GP 18.x. Microsoft states that support ends on that date for product enhancements, regulatory (tax) updates and technical support, with security updates and patches available until 30 April 2031 if needed (Microsoft's Dynamics GP lifecycle page, read October 2026).

Dynamics GP also appears in the Product Retirements table on Microsoft's 2029 end-of-support list, listed as retiring on 31 December 2029.

Three points are worth stating plainly:

• The date has already moved once. The previously announced date was 30 September 2029. Treat 31 December 2029 as the current date, and check Microsoft's page again before you sign anything long-term.
• GP does not stop working on that day. It becomes unsupported. There are no tax or regulatory updates and no technical support from Microsoft.
• The security patch tail is conditional. Microsoft says patches will be made available until 30 April 2031 "if needed". It is not a commitment to a full extended support period, so do not plan around it.

What is the Dynamics GP end of support timeline?

The Dynamics GP timeline has two parts: older fixed-lifecycle versions that have already reached or are reaching their end dates, and the current 18.x release on Microsoft's Modern Lifecycle Policy. The table below uses the dates Microsoft publishes.

Source: Microsoft's Dynamics GP lifecycle page, read October 2026.

The practical reading for October 2026: if you are still on GP 2016, its extended support finished in July 2026, so you are already running without Microsoft fixes. GP 2013 and 2015 have been out of support for longer.

Installing any compatible tax release or hotfix on GP 2018 or 2018 R2 takes you to version 18.5 or later, which enacts the Modern Lifecycle Policy. Microsoft says there are no tax releases or hotfixes that would let you stay on the fixed lifecycle. So most live GP 2018 systems that are being kept up to date are effectively on the 2029 date, not the 2028 one.

Dynamics GP lifecycle dates, from Microsoft's published lifecycle page.

How does the Modern Lifecycle Policy affect Dynamics GP?

Under the Modern Lifecycle Policy you stay supported by staying current, and falling behind is what creates risk before 2029. Microsoft says customers keep supported by taking at least one of the three all-inclusive GP updates, typically released in June, October and December each year. The updates normally consist of hotfixes, tax updates and relevant regulatory updates.

For a finance team this has a few consequences:

• Tax and regulatory updates are tied to the update cycle. If you skip updates, you can fall out of support before 2029 and miss changes you need for payroll-adjacent or VAT reporting.
• Updates need testing. Third-party add-ons, custom reports, integrations and Excel-based tools can break with a new build. A test company and a written regression checklist save year-end pain.
• Someone has to own it. In many small finance teams the person who ran GP updates has left or moved on. Confirm who applies updates today and what the fallback is.

A sensible check this month is to confirm which GP build you are on, when it was last updated, and whether your add-ons are certified for the current release. If you cannot answer those three questions in a few minutes, that is the first piece of work.

What are my options when Dynamics GP support ends?

You have three realistic options: stay on GP and accept the risk, move to Dynamics 365 Business Central, or move to a different ERP. There is also a variant of the first option, where you stay for now but only with a dated exit plan.

None of these is automatically right. The main decision criteria we see in practice are the number of integrations, the amount of GP customisation, the finance team's appetite for process change, the licensing and subscription position, and how long the business expects to operate in its current form.

Your ERP or finance software partner should lead the product comparison. Where a managed IT provider helps is in the surrounding work: infrastructure, identity, security, data movement and user support.

Should I migrate from Dynamics GP to Business Central?

For many Microsoft-centred organisations Business Central is the natural candidate, but it should be chosen on fit, not because the logo matches. Microsoft documents a cloud migration route from Dynamics GP to Business Central online, and notes that the Cloud Migration setup guide for Dynamics GP is supported for the United States, Canada and United Kingdom markets (Microsoft's Business Central cloud migration documentation, read October 2026).

Points to weigh before committing:

• Functional fit. List what GP does for you today, including the awkward parts: intercompany, multi-currency, fixed assets, project costing, custom reports. Check each against Business Central standard functionality and any add-on you would need.
• Cloud versus on-premises thinking. GP is often hosted on your own servers. Business Central online changes how you handle updates, backups, access and integrations. That is a benefit to some teams and a loss of control to others.
• Licensing. Subscription pricing differs from GP's licence and maintenance model. Ask your Microsoft partner for a written quote for your user mix rather than relying on list-price assumptions.
• Reporting. Many GP sites run on Management Reporter, SmartList or Excel extracts. Plan the replacement reporting early, because finance directors notice reporting gaps before anything else.

How does Dynamics GP data migration work?

Data migration moves your GP records into the new system through a mix of automated tooling and manual preparation, and the quality of the source data decides how smooth it is. For Business Central, Microsoft's documentation describes installing the Dynamics GP Historical Data, Dynamics GP Intelligent Cloud and Dynamics GP Intelligent Cloud (US) extensions and running the Cloud Migration Setup guide (Microsoft's Business Central cloud migration documentation). The older Dynamics GP Data Migration extension is deprecated from Business Central 15.3, and Microsoft points users to the cloud migration route.

Microsoft's pages do not give a single list of everything that transfers, so confirm scope with your implementation partner in writing before you rely on any assumption. Whatever the tooling, the work usually breaks down like this:

• Decide what to bring. Opening balances and live master records are usually essential. Full transaction history is a separate decision. Some firms keep history in a read-only archive instead.
• Clean before you move. Duplicate customers, dormant vendors, obsolete items and inconsistent coding are cheaper to fix before migration than after.
• Map structures. Chart of accounts, dimensions, tax codes and payment terms rarely map one-to-one. Document the mapping and have finance sign it off.
• Rehearse. Run at least two trial migrations and reconcile trial balances, ageing and stock values each time. The third run is the real one.
• Plan the archive. UK businesses must keep accounting records for statutory periods, so decide where old GP data will live, who can read it and how it is backed up.

Our data migration services cover the technical movement, validation and rehearsal side of this kind of project, working alongside your ERP partner.

What should a Dynamics GP migration timeline look like?

Work back from 31 December 2029 and aim to finish live running well before it, ideally after at least one full financial year-end on the new system. The illustrative plan below is an example with stated assumptions, not a quote or a promise: a mid-sized UK business with one legal entity, a moderate number of integrations and a decision made in 2027.

Assumptions: single entity, no major acquisitions during the project, the finance team has time to test alongside the day job. If any of those are untrue, add time. The most common mistake is to start the clock when the vendor date is close, then find that the selection stage alone took longer than planned.

Avoid putting go-live in the last quarter of 2029. If something slips, you have no room left, and you are asking staff to do a year-end close in an ERP that is about to lose support.

What are the risks of staying on Dynamics GP after support ends?

Staying on an unsupported ERP raises compliance, security and operational risk, and the risks grow each month. Because Microsoft says support ends for tax and regulatory updates on 31 December 2029, any later change to UK tax or reporting rules would have to be handled outside the product.

The main risks:

• Regulatory drift. Without Microsoft regulatory updates you rely on workarounds or third parties for changes to tax and reporting requirements.
• Security exposure. The security patch tail runs to 30 April 2031 "if needed". Beyond it, GP, SQL Server, Windows Server and Office components underneath it carry their own lifecycles, and an unsupported stack is hard to defend.
• Insurance and assurance questions. Cyber insurers, auditors and customers increasingly ask about unsupported software. Expect questions in renewals and supplier questionnaires.
• Skills risk. GP consultants and administrators will gradually move to other platforms, making support slower and dearer.
• Integration breakage. Connected systems such as banking tools, expenses and CRM change their interfaces over time. An ERP that cannot be updated becomes the weak link.

If you do have to run GP for a period, treat it like any legacy system: restrict network access, enforce multi-factor authentication on remote access, keep underlying servers patched, and test restores. Our guidance on cybersecurity best practices and a cybersecurity assessment are good starting points, and Cyber Essentials controls apply to the servers and endpoints around GP.

What should you do in the next 90 days?

Spend the next 90 days on facts, not vendor demos: build an inventory, set an owner and agree a decision date. A checklist you can use as it stands:

• Record your GP version, build number, last update date and database server version.
• List every add-on, custom report, SmartList, macro and Excel link, with an owner for each.
• List every integration: bank feeds, payroll, CRM, e-commerce, expenses, EDI, reporting tools.
• Confirm who applies GP updates and how they are tested. Name a deputy.
• Check the supported status of the servers and operating systems GP runs on, and whether remote access uses MFA.
• Confirm backups and test a restore of the GP database, not just the file share.
• Ask finance which reports and processes the business cannot operate without for a week.
• Agree a decision date and a steering group of finance, operations and IT.
• Request written proposals from at least two partners, including your current GP partner, with scope and assumptions stated.

If your IT is already outsourced, ask your provider for the infrastructure side of this inventory. If you are weighing support models, our comparison of outsourced and in-house IT support may help, and a clean IT support handover checklist is useful if responsibility for GP is moving between teams.

How can NetMonkeys help with Dynamics GP end of support?

We help with the technology around the ERP decision, and we say so plainly: your finance software partner leads application design and configuration. As a Microsoft Solutions Partner with offices in Manchester, Nottingham and London and field engineers across around 12 UK cities, our role tends to fall into five areas.

• Infrastructure and hosting. Reviewing where GP runs today and, where relevant, planning a move to Azure through managed cloud services and cloud migration services.
• Data movement and validation. Supporting extraction, cleansing, rehearsal and reconciliation through our data migration work.
• Identity and Microsoft 365. Aligning user access, single sign-on and licences with Microsoft 365 support so the new ERP fits your tenant.
• Security. Running a cyber security audit on the legacy and target environments, and keeping controls in place during the transition.
• Resilience. Making sure backups, access and continuity arrangements work throughout cut-over. Our business continuity plan template is a starting point for that planning.

Conclusion: planning around the Dynamics GP support end date

The Microsoft Dynamics GP support end date is 31 December 2029 for the current 18.x release, with security patches available to 30 April 2031 if needed. Older fixed-lifecycle versions have already ended or end sooner, and GP 2016 extended support finished in July 2026. As at October 2026, that leaves enough time for a well-run decision and migration, but not enough to drift.

The sequence that works is: confirm your version and dependencies, set the decision date, choose between staying, Business Central or another ERP on functional evidence, rehearse the migration and keep go-live away from the final quarter of 2029.

If you want infrastructure, security and data migration support alongside your ERP partner, contact NetMonkeys to talk through your timeline.

Frequently Asked Questions (FAQs)