Dynamics GP End of Life: What the 2029 Deadline Actually Means and How to Migrate to ERPNext

At a Glance

• Microsoft is ending support for Dynamics GP, and your deadline depends on the version you run: December 31, 2029, on build 18.5 or later; January 11, 2028, on GP 2018; and already expired on GP 2016 or earlier.
• Support ends in two stages. Tax updates, enhancements, and technical support stop at the end of 2029, and security patches continue only until April 30, 2031, when subscription and SPLA licences also expire.
• Payroll teams lose the most. Tax tables, W-2, 1099, T4, and RL-1 updates all stop on the same date, and maintaining them becomes your team’s job.
• GP will keep running after the deadline. The cost shows up as audit findings, cyber insurance exclusions, frozen Windows Server and SQL Server compatibility, and fewer GP consultants every year.
• ERPNext and Business Central both take nine to eighteen months to implement, so the version date you check today is what decides when you need to start.

Microsoft has announced the Dynamics GP end-of-life timeline, winding down its on-premises ERP for small and mid-sized businesses. Finance teams still call it Great Plains. Many have run their general ledger, payables, bank reconciliation, and US and Canada payroll on it for fifteen years or more, on a system that was never built for one industry and did the financials well enough that nobody had a reason to look elsewhere.

Announcements like this generate more noise than clarity, and the GP users reaching out to us are arriving with the same three questions. What actually stops working. When it stops. What replaces it. The answers turn on one detail most coverage skips: Microsoft runs GP under two separate lifecycle policies, and the version sitting in your environment decides which date is yours. On version 18.x, it is 2029. On an older release, it is January 2028, or it has already passed. Check your version number before you plan anything else.

Dynamics GP End of Support Dates by Version

Two separate things are happening, on separate clocks. The first is product discontinuation. Microsoft stopped selling Dynamics GP to new customers, with perpetual license sales ending April 1, 2025, and subscription sales ending April 1, 2026. Both gates have closed. No organization can start on GP today.

The second is the end of support for the customers already on it, and this is the clock that governs your planning. Microsoft moved Dynamics GP to the Modern Lifecycle Policy in October 2019. Version 18.x sits under that policy. Everything released before it stayed on the Fixed Lifecycle Policy, with its own published dates that the 2029 announcement did not extend.

What Ends on December 31, 2029: Tax Updates, Support, and Enhancements

For customers on version 18.x, Microsoft will end support for product enhancements, regulatory and tax updates, service packs, and technical support on December 31, 2029. The originally announced date was September 30, 2029. Microsoft pushed it to the end of the calendar year so that customers would not be switching ERP systems partway through a tax year.

For payroll teams, this is the date that matters most. Annual payroll and year-end updates stop. W-2, 1099, T4, and RL-1 form updates stop. US and Canadian tax table changes stop. The software will still open on January 1, 2030. It will just be calculating against last year’s rules.

What Ends on April 30, 2031: Security Patches and Subscription Rights

Security updates and patches, if Microsoft deems them necessary, remain available until April 30, 2031. This is a narrower commitment than it sounds. It covers security fixes only, not general bug fixes and not tax updates.

April 30, 2031 is also the end date for subscription billing and for use of Dynamics GP under SPLA agreements. Customers on those licensing models cannot operate the product past that date. If you hold a perpetual license, you can keep running GP indefinitely, unsupported. If you are on subscription or SPLA, the system has to be off.

Why Dynamics GP 2015, 2016, and 2018 Have Earlier End Dates

Versions governed by the Fixed Lifecycle Policy follow a separate schedule:

There is one practical detail worth knowing. Installing any compatible Dynamics GP tax release or hotfix on GP 2018 or GP 2018 R2 brings the installation to version 18.5 or later, which places it under the Modern Lifecycle Policy and the 2029 timeline. Microsoft has not released any tax update or hotfix for those versions that lets you stay on the Fixed Lifecycle. So applying updates buys you time. It also means many organizations that believe they are on “GP 2018” are actually on 18.5 or higher already, and the only way to know is to check the version number in the client.

What Happens If You Stay on Dynamics GP After End of Support

The system keeps running. That is what makes this deadline easy to postpone, and it is why finance teams tend to underestimate the exposure. The costs show up in four places.

Dynamics GP Payroll and Tax Updates Stop

This is the first hard break. Tax tables change every year regardless of your ERP roadmap. Once updates stop, someone on your team owns the job of manually maintaining rates, brackets, and statutory forms, and owns the error when a filing is wrong. For organizations processing payroll in multiple states or provinces, that workload compounds fast. Teams looking at what a supported replacement covers can start with this guide to open source payroll software.

No Security Patches After April 2031

After April 2031, there are no security patches at all. Between 2029 and 2031, patches arrive only if Microsoft judges the vulnerability serious enough. An ERP system holds your general ledger, vendor bank details, customer records, and payroll data. Running it on software with a known and permanently open vulnerability is a different risk category from running an old reporting tool.

Audit Findings and Cyber Insurance Exclusions

Auditors ask whether financial systems are vendor-supported. Cyber insurance underwriters increasingly ask the same question, and some policies carry exclusions for unsupported software. Organizations in manufacturing, distribution, healthcare, and financial services tend to hit this constraint before they hit any technical one. The system works fine. The auditor still writes it up.

Windows Server and SQL Server Compatibility Freezes

Support ending also stops the supported platform matrix from advancing. New Windows Server and SQL Server releases will not be certified against GP, so the ERP and the infrastructure under it end up frozen together. IT teams lose the ability to patch or refresh the server estate on their own schedule, and what started as a finance system decision becomes a constraint on the infrastructure roadmap.

Fewer Dynamics GP Partners and Consultants Every Year

Microsoft stopped selling GP to new customers in 2025 and 2026. No new customers means no new GP consultants entering the market. Partners are already redirecting their practices. Every year past 2029, the pool of people who can fix a GP problem gets smaller, and their rates get higher.

Why Dynamics GP Users Are Choosing ERPNext

ERPNext is an open-source ERP built on the Frappe framework, covering accounting, inventory, manufacturing, purchasing, sales, projects, and HR in a single system. For GP users, four things tend to drive the evaluation.

ERPNext Has No Per-User Licensing Costs

GP licensing has shaped how a lot of organizations work. Warehouse staff, shop floor supervisors, and field teams get kept out of the system because adding seats is expensive, so they submit information on spreadsheets that someone else keys in. ERPNext is licensed under GPLv3 with no per-user fee. Self-hosting costs infrastructure and support, and those are real numbers, though they do not scale with headcount. The practical effect is that you stop rationing access.

Open Source Code and Full Customization Control

GP customizations typically live in Dexterity, eConnect, or third-party add-ons, and each one becomes a dependency you have to re-validate at every upgrade. ERPNext gives you the source. Customizations can be built as separate apps that sit alongside core, which keeps them maintainable across upgrades. You are also not waiting on a vendor roadmap to decide whether your requirement is worth building.

ERPNext Modules That Replace the Dynamics GP Core

The modules GP users depend on have direct equivalents: general ledger with multi-company and multi-currency, accounts payable and receivable, bank and payment reconciliation, fixed assets, inventory with multiple valuation methods, and manufacturing with BOMs, work orders, and production planning. Financial reporting is built in rather than bolted on through Management Reporter or a separate BI tool.

On-Premise, Cloud, or Hybrid Deployment

GP is on-premises. Business Central is cloud. ERPNext runs either way, or as a hybrid. For organizations with data residency requirements, or ones that simply are not ready to move financial data off their own infrastructure on Microsoft’s schedule, that flexibility is often the deciding factor. The trade-offs between self-hosted ERPNext and Frappe Cloud are worth working through before you commit to either.

Dynamics GP to ERPNext Migration: What the Project Involves

An ERP migration is a re-implementation. Treating it as a data transfer is the most common reason these projects overrun.

Step 1: Dynamics GP Environment and Customization Assessment

Start with an inventory: GP version and lifecycle policy, active modules, every customization and third-party add-on, and every integration touching the system. Most Great Plains environments have accumulated more than anyone remembers. This assessment determines the size of the project more than anything else.

It also surfaces a constraint that catches some organizations late. Installations customized heavily enough, or left through enough skipped upgrades, cannot practically be brought to a current GP version at all. For those teams, staying on GP was never really an option, and the choice was always going to be a re-implementation somewhere.

Step 2: Data Extraction and Cleansing

GP data lives in SQL Server, which makes extraction technically simple and deceptively so. The work is in cleansing. Duplicate vendor records, inactive customers, obsolete item codes, and stale open transactions have usually been accumulating for a decade or more. Migrating that debt into a new system carries it forward permanently.

Step 3: Deciding Which Historical Data to Migrate

Bring open transactions, current balances, and master records. Two to three years of transaction history covers most reporting and audit needs. Older history belongs in a read-only archive of the GP database, which stays queryable without slowing the new system or complicating the cutover. Moving fifteen years of detail into ERPNext is a decision people regret.

Step 4: Chart of Accounts and Open Balance Mapping

This is the step that determines whether your first close in the new system is clean. GP account structures use segments that need mapping to ERPNext account trees, and the migration is a rare chance to rationalize a chart of accounts that has grown by accretion. Trial balance parity between the two systems is the checkpoint before anything else proceeds.

Step 5: Rebuilding Integrations

Every connection into GP has to be rebuilt: banking feeds, EDI, ecommerce, CRM, payroll services, warehouse systems, and reporting tools. Scope this early. Integration work is the most frequently underestimated part of an ERP migration and often exceeds the core configuration effort.

Step 6: Parallel Run and Cutover

Run both systems through at least one full monthly close. Reconcile the trial balance, sub-ledgers, and inventory valuation across both. Cutting over at a fiscal period boundary keeps the comparative reporting clean, which is a large part of why Microsoft moved the 2029 date to a year-end.

How Long Does a Dynamics GP Migration Take?

Across the market, ERP transitions of this size take nine to eighteen months from decision to go-live. Three to six months go to evaluation and vendor selection before implementation begins. Data complexity, integrations, and change management extend that for manufacturers and distributors.

Set that against your actual date. On version 18.x, a 2029 deadline means evaluation should be underway by early 2028 at the latest, and sooner if GP runs your payroll, since the last usable year-end update lands in 2029. A GP 2018 organization with a January 2028 deadline needs to be in vendor selection now to avoid a compressed timeline. Organizations on GP 2016 or earlier are already past their date and should treat the schedule as urgent.

Ksolves: Your Trusted ERPNext Migration Partner

Ksolves is a Frappe Certified Partner in India and the USA, working as an ERPNext migration partner for finance and operations teams moving off legacy ERP. The company was founded in 2012, is listed on the NSE and BSE, holds a CMMI Level 3 appraisal, and runs its ERPNext practice alongside more than 600 engineers across its technology teams.

The ERPNext migration services cover the full sequence set out above: environment and customization assessment, data extraction and cleansing, chart of accounts and open balance mapping, integration rebuild, parallel run, cutover, and support through your first period close in the new system.

Delivery runs at roughly half the standard timeline. Every consultant uses AI tools daily for data mapping, test coverage, and configuration review, which shortens the project, lowers the total cost, and reduces the volume of issues that surface after go-live.

Choosing an ERPNext migration company for a financial system comes down to two questions. Has the team moved general ledgers before without breaking the audit trail, and will they still be around at your first year-end? Ask both of any partner you shortlist, including this one.

Dynamics GP End of Life: What to Do Next

Dynamics GP end of life is not one date. It is a set of dates, and the one that governs your organization depends on the version running in your environment today. Check your version number before you plan anything else. Then work backward from your real deadline, allowing nine to eighteen months for the transition, and you will be choosing your ERP on your own terms rather than under a deadline someone else set.