Dynamics GP End of Life: What It Means and Why the Real Deadline Is Earlier

Microsoft will end support for Dynamics GP, formerly known as Great Plains, on December 31, 2029. That date replaced the original September 30, 2029 deadline. GP won't stop running when support ends, and existing customers can keep using it. But the date on Microsoft's lifecycle page isn't the date that should drive your plan.

From when we're writing this in late 2026, a little over three years sounds like plenty of runway. It sounds different once you count backward from how long an ERP migration actually takes, then add time to evaluate options, choose a partner, and avoid cutting over in the middle of year-end close. For most mid-market companies running GP, the real decision deadline lands in 2027 or 2028.

When does Dynamics GP support end?

Microsoft is discontinuing Dynamics GP on a published timeline, and two of its four milestones have already passed.

Microsoft moved the main support date from September 30 to December 31 specifically so customers would be covered through the tax year-end. The April 2031 date didn't move.

That second date often gets described as "extended support," which overstates it. Under Microsoft's lifecycle policy for Dynamics GP, the only commitment after December 31, 2029 is security updates if needed. Tax updates, enhancements, and technical support will already be gone.

These dates apply to current GP releases (version 18.x) under Microsoft's Modern Lifecycle Policy. Older versions run on a separate, earlier clock. GP 2016 and 2016 R2 passed the end of support in July 2026, and GP 2018 and 2018 R2 reach theirs in January 2028. If you're on a 2018 release, installing any current GP tax release or hotfix moves you onto the modern policy and the 2029 timeline. If you're on 2016 or earlier, getting current comes first, regardless of what you decide after that.

Is Dynamics GP the same as Dynamics 365?

No, though the naming makes it easy to assume. Great Plains is the original name of the product Microsoft later rebranded as Dynamics GP, which is why you'll see the same timeline described as Great Plains end of life, Dynamics GP end of support, or Great Plains sunsetting. Dynamics 365 is Microsoft's family of cloud business applications, and Dynamics 365 Business Central is the ERP in that family Microsoft points most GP customers toward.

Business Central isn't GP renamed for the cloud. It's a different product with a different architecture and a different way of handling things like account structure and reporting. That's why moving from GP to Business Central is an ERP migration and implementation rather than an upgrade.

What changes for your business before and after 2029

GP's end of life plays out in stages rather than on a single date.

Through December 31, 2029, very little changes as long as you stay current. Microsoft keeps shipping regular GP updates with tax table changes, regulatory updates, fixes, and technical support available. From January 2030 through April 2031, GP sits in a security-only window, which is useful as a buffer for a company finishing its move but a poor place to start one. After April 30, 2031, Microsoft has no commitment to GP at all.

The first transition is the one finance teams will feel. Once regulatory updates stop, every change to payroll tax tables, W-2 and 1099 formats, ACA reporting, or electronic filing specs lands on your team. You might be able to cover those gaps with third-party tools, custom development, or manual workarounds, but someone has to own them, and the cost grows with each change. Payroll needs its own plan for another reason as well, because it rarely moves cleanly with the rest of the ERP.

Audit and insurance questions grow out of the same issue. Running unsupported financial software doesn't automatically create a SOX deficiency, but your auditors will want to understand how you're handling patching, access, and change control on a system its vendor no longer maintains. Cyber insurers ask similar questions on applications and renewals. Neither one turns into a cliff on a specific date. Both get harder to answer the longer GP runs without vendor support.

To be fair to GP, it isn't frozen yet. Current releases support SQL Server 2025 and Windows Server 2025. The bigger risk comes later, because once Microsoft stops maintaining GP, it also stops making sure GP works with whatever comes next. GP won't stop working on one specific day. It stops being maintained, and every change around it becomes your responsibility after that.

Why moving off GP isn't a software upgrade

Much of the underestimation we see starts here. Anyone used to consumer software expects something close to an update button. An ERP migration is nothing like that. It's an enterprise-wide initiative.

It also isn't really an IT project, even though it usually gets framed as one. A move off GP typically touches half to three-quarters of a company's day-to-day operations. The people who know GP best, the ones whose daily work lives inside it, have to relearn routine tasks in a system with different screens, terminology, and logic. That retraining is real work, and it happens while the same people keep the business running.

Then there's cutover. GP usually sits at the center of other systems, such as banking, AP automation, payroll, EDI, reporting, and CRM. Switching the ERP without breaking everything connected to it takes its own planning, testing, and timing, which makes cutover a project inside the project.

How long a GP migration takes, and when to start

In our experience, if everything is rushed and everything goes perfectly, an ERP project might come in around 90 days. That's the lucky case and it's extremely rare. A full platform migration more typically runs six to nine months, and sometimes takes up to 18 months when the environment is customized, integration-heavy, or unusual in any way.

Published estimates for a GP to Business Central migration range from about 12 weeks to 18 months. That looks contradictory until you notice the numbers describe different projects. The short estimates come from partners describing standardized, low-complexity moves with packaged configurations. The long ones include process redesign, many legal entities, or extensive integrations. Most mid-market GP environments land somewhere in between, and what pushes a project toward the long end is predictable:

• The number of legal entities and companies in GP
• Customizations and third-party add-ons, each needing a decision to rebuild, replace, or retire
• Integrations, and how many other systems depend on GP data
• The reports your finance team relies on today
• How much transaction history needs to come along
• How much time your own people can give to testing and sign-off

Here's how the timing works for a company on a calendar fiscal year that wants some margin for error. Aim to go live in early 2029 at the latest, so you can close a full year on the new system while GP is still fully supported as a fallback. Six to nine months of implementation puts kickoff in spring 2028. Evaluation, partner selection, and contracting before that put the real start of the process in late 2027.

Microsoft's incentives point to the same window. Its Bridge to Cloud 3 promotion gives eligible on-premises Dynamics customers 30% off Dynamics 365 cloud licenses for a fixed three-year term. Eligibility generally requires an on-premises license purchased before September 2024 and an active Enhancement Plan, and enrollment closes December 31, 2027. For a company planning a Dynamics GP to Dynamics 365 migration, the incentive deadline arrives two years before the support deadline.

That's what we mean by the real deadline. It's the point where waiting longer starts costing you options, and for most mid-market GP customers it arrives well before 2029.

Your options

Most GP customers end up choosing among five paths, and each has a legitimate place.

Stay on GP for now. For a company on a current release, this is a reasonable choice through 2029, as long as it comes with a date and a funded plan to leave. Staying is fine. Staying without a plan is how companies end up migrating in a hurry.

Rely on third-party support. Partners will keep supporting GP well after Microsoft stops, and that expertise has value. What they can't do is produce Microsoft's security fixes or regulatory updates.

Rehost GP in Azure. Moving GP onto Azure virtual machines can modernize your infrastructure and improve resilience. It's still the same GP, though, so the 2029 and 2031 dates stay exactly where they are.

Move to Business Central or Dynamics 365 Finance. Business Central is Microsoft's primary destination for GP customers and the target of its built-in GP migration tooling. Dynamics 365 Finance fits companies with more complex entity structures, consolidations, or international operations, and it's usually budgeted more like a new ERP implementation. Company size alone doesn't decide between them.

Move off Microsoft. Nothing requires you to stay in the Microsoft ecosystem. If a different ERP fits better, a structured ERP selection is the right process, and the 2029 deadline should set the timing of that evaluation rather than its outcome.

If you stay with Microsoft, ask your partner which current incentives apply to you. Beyond Bridge to Cloud 3, Microsoft also runs a Business Central migration voucher program whose eligibility and funding change by fiscal year.

Start with your own deadline

Microsoft has set the support deadline. The decision deadline is yours, and it should come from your own environment. How many entities, add-ons, and integrations do you run? How much change can your team absorb at once? Answering those questions starts with an honest inventory of what you have.

If you want help building that picture, Ascendex works with GP customers on migrations to Business Central and Dynamics 365, starting with an ERP assessment that maps your environment and a realistic timeline before you commit to a path.