Inc. 5000 Fastest-Growing Company in the US

Inc. 5000 logo
Home
Breadcrumb arrow
Blog
Breadcrumb arrow
Dynamics GP End of Life: Dates, Options and Next Steps

Dynamics GP End of Life: Dates, Options and Next Steps

Dynamics GP (formerly Great Plains) end of life means Microsoft stops product enhancements, tax and regulatory updates and technical support for Dynamics GP on December 31, 2029, with security patches, if needed, until April 30, 2031. It affects every company still running GP, and older versions lose support sooner.

For manufacturers still running Dynamics GP, neither date should be the starting line for a migration. A manufacturing ERP move is not a data transfer. It touches production processes, bills of material, routings, inventory, warehouse systems, EDI, reporting, third-party applications and years of company-specific modifications. Planning early gives your team time to understand those dependencies, choose the right platform and move on a schedule that works for the business.

This guide to Dynamics GP end of life covers the full timeline, the three options GP customers have, what each one costs and risks, and the steps to take now.

Dynamics GP end of life timeline

The dates below come from Microsoft’s published lifecycle for Dynamics GP. Which one applies to you depends on the version you run.

DateWhat changesWhat it means for you
April 1, 2026Dynamics GP sales are limited to existing customers.No new companies can start on GP. Existing customers should confirm their licensing position with their partner.
July 14, 2026Extended support ended for Dynamics GP 2016 and 2016 R2.These versions no longer receive updates of any kind. Companies on them should decide between an interim upgrade and a migration.
January 11, 2028Extended support ends for Dynamics GP 2018 and 2018 R2 under the Fixed Lifecycle Policy.Installing any compatible tax release or hotfix moves these systems to version 18.5 or later, which falls under the Modern Lifecycle Policy.
December 31, 2029Product enhancements, regulatory and tax updates, and Microsoft technical support end for Dynamics GP 18.x.Continuing on GP will require your own plan for support, compliance, tax changes, infrastructure and connected applications.
April 30, 2031Microsoft’s final window for security updates or patches, if needed, closes.After this date, there are no Microsoft-provided fixes of any kind for Dynamics GP.

There is one condition for organizations counting on support through 2029. Microsoft says customers on Dynamics GP 18.x stay current by taking at least one of the three planned GP updates released each year, typically in June, October and December. An environment that falls behind may need to be updated before Microsoft will support it.

Your options at Dynamics GP end of life

Every GP customer ends up in one of three places. None is right for everyone, and the choice depends on how much GP is holding back the business today and how much risk you can accept later.

Option 1: Keep running GP without Microsoft support

Dynamics GP will not stop working on January 1, 2030. You can keep using it, but responsibility for keeping it viable moves to your organization.

  • Risks: no tax or regulatory updates from Microsoft after 2029 and no security patches after April 2031; connected applications (shipping, EDI, warehouse scanning, payroll, banking) dropping GP compatibility; aging server, database and operating-system dependencies; a shrinking pool of people with deep GP expertise; harder questions from auditors, insurers and customers’ security teams.
  • Costs: low in the short term, then rising. Manual workarounds for tax changes, custom fixes, older infrastructure and the cost of an eventual rushed migration all grow each year.
  • When it makes sense: rarely as a long-term plan. It can work as a short bridge when a migration date is already set.

Option 2: Stay on GP with support from a partner

A Dynamics partner can keep supporting your GP environment after Microsoft’s support ends: functional help, troubleshooting, report and integration fixes, and keeping the system current while updates are still available. Ascent offers Dynamics GP and NAV support for companies in this position.

  • Risks: a partner cannot replace what only Microsoft provides. After December 31, 2029 there are no new tax or regulatory updates, and after April 30, 2031 no security patches. Third-party applications may still drop GP compatibility on their own timeline.
  • Costs: an ongoing support agreement, plus any upgrade needed to reach a supported version. If you are on a GP version before 18.x, an interim upgrade to 18.x is often the first step; our guide to Dynamics GP upgrades explains what that involves.
  • When it makes sense: when you need time to budget, finish another project or wait for the right business window, and you have a target date for the move.

Option 3: Migrate to Dynamics 365 Business Central or Dynamics 365 Finance and Supply Chain Management

Moving to a cloud ERP replaces the end-of-life problem with a platform that receives continuous updates from Microsoft.

  • Risks: the usual risks of any ERP project: scope creep, data quality issues, integration rebuilds and the need for users to adopt new ways of working. All of them shrink with early planning and a defined testing plan.
  • Costs: a one-time implementation project (assessment, design, data migration, integrations, testing, training) plus subscription licensing instead of GP maintenance. The scope, not the size of your database, drives the cost.
  • When it makes sense: for most GP customers, especially those whose processes, reporting or integrations are already working around GP’s limits. Our guide to migrating from Dynamics GP to Business Central covers that path in detail.

Business Central or Dynamics 365 Finance and Supply Chain Management?

Moving away from GP does not mean every manufacturer should choose the same replacement.

Dynamics 365 Business Central often fits small and mid-sized manufacturers whose financial, distribution, inventory and production needs can be met with its standard capabilities and the right industry extensions. It offers cloud access, continuous product investment, Microsoft 365 and Power Platform integration and a broad partner ecosystem.

Dynamics 365 Finance and Supply Chain Management may fit better when an organization has more global, operational or multi-site complexity, advanced warehousing or planning requirements, extensive intercompany activity or enterprise-scale governance needs.

The decision should rest on requirements, not labels. The factors that matter most:

  • Number of companies, sites, countries and currencies
  • Manufacturing modes and production complexity
  • Planning, quality, maintenance and warehouse requirements
  • Transaction volume and performance needs
  • Reporting, consolidation and regulatory requirements
  • Integrations and industry-specific applications
  • Internal capacity for implementation and ongoing administration
  • Expected growth, acquisitions or operational change

Preparing for Dynamics GP end of life: what to do now

You do not need to start implementation tomorrow. You do need enough information to avoid a rushed ERP decision later.

1. Confirm your GP version and lifecycle policy

Document the version and build in production, the most recent update applied and whether the environment falls under Microsoft’s Fixed or Modern Lifecycle Policy. If you are on GP 18.x and plan to rely on Microsoft support, confirm that your update schedule keeps the system current.

2. Inventory the systems and processes connected to GP

List the customizations, integrations, reports and independent software vendor (ISV) applications the business depends on. For a manufacturer, that usually includes:

  • Bills of material and routings
  • Production scheduling and shop-floor processes
  • Inventory costing and lot or serial tracking
  • Warehouse management and barcode scanning
  • EDI, shipping, e-commerce and customer portals
  • Quality management or product lifecycle systems
  • Payroll, banking, tax and payment applications
  • Power BI, Management Reporter, SQL reports and spreadsheets
  • Custom code, integrations and manual workarounds

These dependencies, not the number of database tables, usually decide the real complexity of a migration.

3. Decide what the future system must improve

Don’t recreate every GP process just because it is familiar. Identify the outcomes a new ERP should support: a faster financial close, better production visibility, fewer manual entries, better inventory accuracy, easier reporting, remote access, or room for more sites and entities. At Ascent, we start with how the business needs to operate; the software decision follows those requirements.

4. Set a target window and work backward

Choose when you want the new environment to be live and stable, not merely when Microsoft support ends. Then allow time for discovery, solution design, data cleanup, configuration, integrations, testing, training, cutover and post-go-live stabilization.

What a Dynamics GP migration involves

The biggest concerns we hear from manufacturers are data, downtime and disruption. They become manageable once the scope, dependencies, data strategy and testing plan are defined. Moving the data is not the same as migrating the business. The decisions that matter more:

  • Which GP processes to keep, redesign or retire
  • How customizations will be replaced with configuration, extensions or a different process
  • Which integrations must be rebuilt
  • How much transaction history moves into the new ERP and what stays in a secure archive
  • How reports and KPIs will be reproduced or improved
  • How users will test the system and prepare for new ways of working

For moves to Business Central, Microsoft provides cloud migration tooling for supported GP data, which can include financial information, customers, vendors, open receivables and payables, inventory, open purchase orders and selected history. The tools reduce the technical effort of moving data, but they don’t replace solution design, reconciliation, testing, training or change management. After go-live, Business Central support keeps the new system running as your team settles in.

How long does a Dynamics GP migration take?

There is no universal duration. These are Ascent’s early planning ranges:

Migration scopeEarly planning range
Business Central with mainly core financial requirementsAbout 2–3 months
Business Central reimplementation with manufacturing, distribution, integrations or multiple entitiesAbout 5–10 months
Focused Dynamics 365 Finance and Supply Chain Management implementationAbout 5–8 months
Multi-site or multi-entity Dynamics 365 Finance and Supply Chain Management program12 months or more

These are planning estimates, not commitments. Data quality, process complexity, integrations, custom development, resource availability, testing and change management all affect the schedule. If your migration is likely to take 5 to 10 months, the decision can’t wait until late 2029: you also need time before the project for assessment, budgeting and vendor selection, and time after it for stabilization.

Plan the move before Dynamics GP end of life plans it for you

Not sure which path fits? The first step is understanding your current GP environment, the processes built around it, and the requirements a future system needs to support. 

Ascent Innovations helps mid-market manufacturers evaluate what should come next for their Dynamics GP environment. We assess your current version, processes, data, integrations and operational requirements, then determine whether an interim GP strategy, Business Central, or Dynamics 365 Finance and Supply Chain Management makes the most sense and build a practical roadmap.

Book a GP Migration & Modernization Review

You can also reach Ascent Innovations at +1 (847) 572-8000 or sales@ascent365.com.

Dynamics GP end of life: frequently asked questions

Dynamics GP end of life dates and versions

When does Dynamics GP support end?

For Dynamics GP 18.x, Microsoft ends product enhancements, regulatory and tax updates and technical support on December 31, 2029. Security updates, if needed, remain available until April 30, 2031. Older versions lose support sooner: support for GP 2016 and 2016 R2 ended on July 14, 2026, and GP 2018 and 2018 R2 lose it on January 11, 2028.

Is Microsoft Great Plains reaching end of life?

Yes. Microsoft Great Plains is the product now called Microsoft Dynamics GP, and Microsoft ends product enhancements, regulatory and tax updates and technical support on December 31, 2029. Security patches, if needed, continue until April 30, 2031. GP keeps running after those dates, but keeping it compliant, secure and compatible with connected applications becomes your organization’s responsibility.

Planning your next step

What should we do if we’re still on Dynamics GP?

Start planning now, while you still have Microsoft support. Confirm which GP version you run and whether it is on Microsoft’s lifecycle policy, inventory the systems and processes connected to GP, and decide whether you will stay on GP with partner support or migrate to Dynamics 365 Business Central or Dynamics 365 Finance and Supply Chain Management. Since April 1, 2026, GP sales are limited to existing customers, so if you need more users or modules in the meantime, confirm your options with your partner.

Do I need to be on GP 18.x to stay supported until 2029?

Yes. Only GP 18.x is supported through December 31, 2029, and only if you take at least one of the three GP updates Microsoft releases each year. GP 2016 and 2016 R2 are already out of support, and GP 2018 and 2018 R2 lose extended support on January 11, 2028.

What should I replace Dynamics GP with?

Business Central is a common migration path for GP customers, and Microsoft provides migration tooling from GP to Business Central. Companies with multi-site, global, advanced warehousing, planning, or more complex operational requirements may be better suited to Dynamics 365 Finance and Supply Chain Management. The right choice depends on your business requirements.

How long does a migration from Dynamics GP to Business Central take?

In Ascent’s experience, about 2–3 months for mainly financial requirements and about 5–10 months when manufacturing, distribution, integrations or multiple entities are involved. Assessment, budgeting and post-go-live stabilization add time on either side.

Related reading

Share

Table of Contents