Microsoft has set an expiration date for Dynamics GP. After more than three decades as one of the most widely used ERPs by small and medium-sized businesses around the world, the software that was born as Great Plains and that Microsoft acquired in the early 2000s is entering its final phase. Mainstream support will end on December 31, 2029, and the last security updates will be published on April 30, 2031.
This is not a rumor or speculation. Microsoft published the official announcement in September 2024 and updated it in January 2025 to extend the deadline by three additional months, allowing its customers to complete the 2029 fiscal year-end with support coverage.
The company has been clear: there is no going back. Dynamics GP will not receive new features, and its ecosystem of partners, integrations, and specialized consultants will progressively shrink as the industry migrates to cloud platforms.
For companies that have been operating with GP for years — many of them with accumulated customizations, third-party integrations, and well-established processes — this news raises a decision that should not be postponed. Not because the system will stop working overnight, but because the conditions for migrating in an orderly manner, with good timelines and access to experienced partners, are better today than in two or three years, when the demand for migration projects concentrates and resources become more expensive.
In this article we review the official calendar, the concrete risks of staying on an unsupported ERP, what Business Central offers as an alternative, and how to plan a migration without surprises.
Official calendar: the dates you need to mark
Microsoft has published a clear calendar with four milestones that mark the progressive closure of Dynamics GP. Knowing them is essential to properly size the real timelines of any migration project.
April 1, 2025 (already passed). End of perpetual license sales to new customers. From this date it is no longer possible to acquire the traditional “ownership” version of Dynamics GP. Existing customers are not affected and can continue operating normally.
April 1, 2026. End of subscription license sales to new customers. The entry door to the product is definitively closed. From this point on, no new company will be able to contract Dynamics GP in any modality.
December 31, 2029. End of mainstream support. Microsoft will stop publishing functional updates, service packs, tax and regulatory updates, and will stop offering technical support. This is the critical date for most companies: from here on, the system stops evolving and stops adapting to the regulatory changes of each country.
April 30, 2031. End of security updates. This is the definitive “end of life.” From this date, any vulnerability discovered in the system will remain unpatched. Operating Dynamics GP after this point means assuming a security risk that few audits or cyber insurance policies will tolerate.
An important nuance: current customers can continue purchasing additional user licenses and modules even after the closure of new sales. What disappears is Microsoft’s investment in the product. There will be no new features, no improvements, and progressively, no support.
Put directly: Dynamics GP does not shut down, but it freezes. And a frozen ERP in a regulatory, fiscal, and technological environment that changes every year is a problem that only grows over time.
.timeline { position: relative; padding: 1rem 0; margin: 1.5rem 0 2rem; font-family: 'Segoe UI', -apple-system, BlinkMacSystemFont, sans-serif; } .timeline::before { content: ''; position: absolute; left: 24px; top: 0; bottom: 0; width: 3px; background: linear-gradient(180deg, #0078D4 0%, #E74856 100%); border-radius: 2px; } .timeline-item { position: relative; padding-left: 60px; margin-bottom: 1.5rem; } .timeline-dot { position: absolute; left: 14px; top: 4px; width: 22px; height: 22px; border-radius: 50%; border: 3px solid #0078D4; background: #fff; } .timeline-item.passed .timeline-dot { background: #6B7280; border-color: #6B7280; } .timeline-item.critical .timeline-dot { background: #E74856; border-color: #E74856; } .timeline-item.upcoming .timeline-dot { background: #FFB900; border-color: #FFB900; } .timeline-date { font-size: 0.85rem; font-weight: 700; text-transform: uppercase; letter-spacing: 0.5px; color: #005A9E; } .timeline-item.passed .timeline-date { color: #6B7280; text-decoration: line-through; } .timeline-item.critical .timeline-date { color: #E74856; } .timeline-desc { font-size: 0.95rem; color: #333; margin-top: 0.2rem; line-height: 1.6; } .timeline-tag { display: inline-block; font-size: 0.7rem; font-weight: 700; text-transform: uppercase; letter-spacing: 0.8px; padding: 0.15rem 0.6rem; border-radius: 4px; margin-top: 0.3rem; } .tag-passed { background: #e5e7eb; color: #6B7280; } .tag-upcoming { background: #FFF3CD; color: #856404; } .tag-critical { background: #FDEAEA; color: #C62828; } April 1, 2025 End of
perpetual licensesales to new customers. It is no longer possible to acquire the "ownership" version of the software. Completed April 1, 2026 End of
subscription licensesales to new customers. The entry door to Dynamics GP is definitively closed. Upcoming December 31, 2029 End of
mainstream support: functional updates, service packs, tax/regulatory updates, and technical support are discontinued. Critical date April 30, 2031 End of
security updates. From this date, Dynamics GP is officially out of service with no patches or fixes of any kind. End of life
An important nuance: current customers can continue purchasing additional user licenses and modules even after the closure of new sales. What disappears is Microsoft’s investment in the product. There will be no new features, no improvements, and progressively, no support.
Put directly: Dynamics GP does not shut down, but it freezes. And a frozen ERP in a regulatory, fiscal, and technological environment that changes every year is a problem that only grows over time.
.callout-warning { font-family: 'Segoe UI', -apple-system, BlinkMacSystemFont, sans-serif; background: #FFF8E1; border-left: 4px solid #FFB900; border-radius: 0 12px 12px 0; padding: 1.5rem 1.75rem; margin: 1.5rem 0; line-height: 1.7; color: #333; } .callout-warning .callout-title { font-weight: 700; font-size: 1rem; margin-bottom: 0.5rem; display: flex; align-items: center; gap: 0.4rem; color: #1a1a2e; } .callout-warning .callout-icon { font-size: 1.3rem; } .callout-warning p { margin: 0; font-size: 0.95rem; } ⚠️ Important for existing customers
Current customers can continue using their licenses and even add users beyond 2026. However, there will be no new features or improvements to the product. The software will work, but it will stop evolving and, eventually, stop receiving security patches.
What happens if you decide not to migrate
It is tempting to think that if the system works today, it can keep working for a few more years without problems. And technically that is true: Dynamics GP will not stop starting up on January 1, 2030. But “working” and “working well” are very different things when we are talking about an ERP that supports the financial, accounting, and logistics operations of a company.
These are the real risks that accumulate as time passes without migrating.
Unpatched vulnerabilities. Without security updates, every new vulnerability discovered in the system will remain open indefinitely. Attackers know the end-of-support calendars perfectly and exploit them: an ERP without patches is a priority target for ransomware and unauthorized access. This is not a remote possibility; it is a documented pattern that repeats itself every time an enterprise product loses manufacturer support.
Tax and regulatory non-compliance. In Latin America, tax regulations change frequently. Electronic invoicing, withholdings, reports to tax authorities, changes in tax rates — all of this requires the ERP to be updated. Without regulatory updates after 2029, the company will have to find manual solutions or third-party patches to meet its obligations. In addition to being inefficient, it is risky: an error in tax settlement due to an outdated system does not exempt from penalties.
Integrations that stop working. The ecosystem around GP is contracting. Third-party software vendors have already begun withdrawing their connectors with GP to focus on platforms with a future. When your payment gateway, your CRM, or your e-commerce platform stops maintaining the integration with GP, you will find yourself looking for alternative solutions that will become increasingly scarce and more expensive.
Growing maintenance costs. Maintaining an on-premises infrastructure with declining software is not free. Servers, operating system licenses, backups, IT staff dedicated to a system that nobody else wants to touch. As the talent specialized in GP migrates to Business Central or other platforms, finding a consultant who knows the system will be more difficult and more costly. The law of supply and demand is unforgiving.
The pressure of deadlines. This is perhaps the most underestimated risk. If thousands of companies in the region need to migrate before 2029, the availability of partners with experience in GP → Business Central projects is going to tighten. Projects that are planned today calmly in 12 or 16 weeks could require months of waiting simply to secure an available team. Migrating earlier is not just a technical matter; it is a competitive advantage in access to resources and negotiating capacity.
Request your free consulting session now
And a consultant specialized in Dynamics GP to Business Central migrations will review with you.
- Your current situation with Dynamics GP.
- Which developments can be leveraged and which cannot.
- Real benefits you could obtain by migrating.
- Microsoft support programs and discounts available today.
- What your migration plan would look like in terms of time, cost, and support.
window.hsFormsOnReady = window.hsFormsOnReady || []; window.hsFormsOnReady.push(()=>{ hbspt.forms.create({ portalId: 7555051, formId: "aa5f209b-dbce-4c14-bddf-e0ac0640a9cc", target: "#hbspt-form-1784395809000-1580728088", region: "na1", })});
Why migrating earlier means migrating better
So far we have talked about what is lost by staying on an unsupported ERP. But migration is not just a defensive exercise. For many companies, it is the opportunity to solve operational problems that they have been dragging along with GP for years and had come to accept as normal.
Real access from anywhere. With GP, working outside the office involves VPNs, remote desktops, or configurations that never quite work properly. A cloud ERP allows the CFO to review closings from home, the sales team to check inventory availability from their phone, or an operation with offices in several countries to work on the same data in real time, without depending on the infrastructure of a single building.
Updates that do not paralyze operations. Any company that has gone through a version update in GP knows what it involves: weeks of planning, testing, scheduled downtime, and the tension that something will fail in the process. Modern cloud ERPs update automatically and continuously. Improvements arrive without the IT team having to intervene or the company having to halt its activity.
Information for making decisions, not just for recording transactions. GP fulfills its function well as a recording system, but obtaining real-time analytical information requires manual exports, spreadsheets, and a lot of preparation time. A modern ERP integrates analytics and reporting tools that allow building dashboards, detecting trends, and making decisions based on up-to-date data, not the report someone prepared last week.
Automation of tasks that currently consume hours. Bank reconciliations, generation of recurring journal entries, purchase approvals, collections follow-up — in GP, many of these processes depend on manual steps or customizations that someone developed years ago and that nobody dares to touch. Current platforms incorporate native automation and, increasingly, artificial intelligence capabilities that eliminate repetitive work and reduce errors.
An ecosystem that grows instead of contracting. While the universe of solutions compatible with GP shrinks, modern ERPs have extension marketplaces, native connectors with productivity tools, and an active development community. This means more options to expand functionality, better integrations with the software you already use, and access to innovations that arrive continuously.
Less dependence on the internal IT team. Maintaining GP requires servers, databases, backups, patch management, and staff who know the platform. With a cloud ERP, much of that burden disappears. The IT team can dedicate its time to projects that add value to the business instead of keeping an infrastructure alive that only ages.
And there is a factor that rarely appears in technical comparisons but that any CFO understands: the earlier you migrate, the sooner you start capturing that value. Every month the decision is delayed is another month operating with the limitations of the old system, paying for its maintenance, and accumulating technical debt. Companies that migrate with time on their side choose better, negotiate better, and execute better.
Business Central: the natural path from Dynamics GP
Microsoft has not left GP users without an alternative. Dynamics 365 Business Central is the platform that the company has designed as the direct successor, and it has been investing for years in specific tools to facilitate the transition from GP.
Why Business Central and not another ERP? For companies that already operate within the Microsoft ecosystem the answer is quite practical. Business Central integrates natively with Outlook, Teams, Excel, and Power BI. Users do not change worlds: they change tools within an environment they already know. This reduces the learning curve and accelerates adoption, which is usually the point where most migration projects get stuck.
At a functional level, Business Central covers the same areas as GP — accounting, purchasing, sales, inventory, project management — but with a modern architecture that resolves many of the historical limitations of the previous system. Updates arrive automatically twice a year with functional improvements and monthly with corrections, without the need for downtime or technical team intervention.
One of the most relevant changes is the incorporation of Microsoft Copilot, which introduces artificial intelligence capabilities directly into the ERP: cash flow forecasts, assisted bank reconciliation, automatic product descriptions, and suggestions based on historical data analysis. This is not science fiction or a future promise; it is functionality available today that GP will never have.
For companies that due to internal policy or regulatory requirements need to keep data on their own servers, Business Central also offers an on-premises deployment option. It is not the option Microsoft prioritizes — AI capabilities and some advanced features are only available in the cloud version — but it exists and is a valid path for organizations that need to take that intermediate step.
One point worth being clear about: migrating from GP to Business Central is not pressing an update button. They are different products with different architectures. Microsoft offers migration tools that facilitate the transfer of master data and transactions from the main modules, but customizations, custom fields, and third-party solutions require specific analysis and adaptation work. This should not frighten anyone — it is expected in any ERP change — but it does reinforce the importance of having a partner who knows both worlds and has executed this type of project before.
And this is where the choice of technology partner makes the difference. Not all Microsoft partners have real experience in migrations from GP. Those who do know the critical points, know what data to migrate and what to archive, and can anticipate problems before they appear in production.
.comparison-table { font-family: 'Segoe UI', -apple-system, BlinkMacSystemFont, sans-serif; width: 100%; border-collapse: separate; border-spacing: 0; border-radius: 12px; overflow: hidden; margin: 1.5rem 0 2rem; box-shadow: 0 2px 12px rgba(0,0,0,0.06); } .comparison-table thead th { background: #0078D4; color: #fff; padding: 1rem 1.25rem; text-align: left; font-size: 0.95rem; font-weight: 600; } .comparison-table thead th:first-child { border-radius: 12px 0 0 0; } .comparison-table thead th:last-child { border-radius: 0 12px 0 0; } .comparison-table tbody td { padding: 0.85rem 1.25rem; border-bottom: 1px solid #E2E8F0; font-size: 0.92rem; color: #333; line-height: 1.6; } .comparison-table tbody tr:nth-child(even) { background: #F5F7FA; } .comparison-table tbody tr:last-child td { border-bottom: none; } .comparison-table tbody td strong { color: #1a1a2e; } .check { color: #107C10; font-weight: 700; } .cross { color: #E74856; font-weight: 700; } @media (max-width: 640px) { .comparison-table { font-size: 0.85rem; } .comparison-table thead th, .comparison-table tbody td { padding: 0.65rem 0.75rem; } }
| Aspect | Dynamics GP | Business Central |
|---|---|---|
| Deployment | On-premises (own servers) | Cloud native (also on-premises) |
| Updates | Manual, costly, and disruptive | Automatic, semi-annual + monthly |
| Remote access | Limited, requires VPN or remote desktop | Native from any device and location |
| Microsoft 365 integration | Partial, no continuity guarantee | Native with Teams, Outlook, Excel, Power BI |
| AI and automation | ✗ Not available | ✓ Microsoft Copilot integrated |
| Security | Dependent on client infrastructure | Encryption, compliance, and Microsoft Azure patches |
| Extension ecosystem | Declining ISVs, expiring integrations | AppSource with thousands of active extensions |
| Manufacturer support | Until 2029 (security until 2031) | Continuous support, product in active development |
| Total cost of ownership | Servers + IT + licenses + updates | Monthly subscription, infrastructure included |
How to plan the migration without surprises
An ERP migration is not a project that is improvised. But it does not have to be a traumatic process if approached with method and reasonable timelines. The simplest migrations can be completed in 10 or 12 weeks. The more complex ones — with customizations accumulated over years, integrations with multiple systems, and operations in several countries — may need six months or more. In both cases, the key is the same: start with a good picture of the starting point.
Audit of the current environment. Before thinking about the destination, you need to understand the origin well. Which GP modules are actually used? Which customizations were made and which are still necessary? Which third-party solutions are active? How many years of historical data have accumulated and how many have real operational value? Many companies discover in this phase that they have been maintaining customizations that nobody uses or storing data that could be archived without any impact on daily operations.
Definition of scope and objectives. This is the moment to decide what is migrated as-is, what is redesigned, and what is discarded. It is tempting to want to replicate GP exactly in Business Central, but that approach is one of the most costly mistakes that can be made. The migration project is the best opportunity to simplify processes, eliminate obsolete workflows, and take advantage of native Business Central features that in GP required custom development.
Data cleansing. Migrating dirty data to a new system means starting off on the wrong foot. Duplicate records, inactive vendors, customers with no activity for years, historical transactions that provide no operational value — all of this must be reviewed and cleaned up before migration. In most jurisdictions, keeping more than seven years of transactional history within the active ERP has little practical value. The rest can be archived and consulted through other means.
Execution with a partner who knows both worlds. The migration from GP to Business Central has particularities that only those who have done it before know. Being an expert in Business Central is not enough; you need to understand how GP works, how its data is structured, where customizations are hidden, and what problems typically arise during the transfer. A partner with real experience in this type of project can anticipate obstacles that would otherwise appear at the worst phases of the project.
Training and change management. Users have been working with the GP interface for years. Although Business Central has a more modern and intuitive design, the change generates resistance. Investing in training before Go-Live — not after — is what makes the difference between a smooth launch and weeks of support tickets and frustration. Identifying key users within each department and turning them into internal champions of the new system accelerates adoption far more than any manual.
Go-Live and stabilization period. Choosing a launch date during a period of lower activity, keeping GP accessible in read-only mode during the first weeks, and having a dedicated support team during the stabilization period are basic precautions that avoid unnecessary surprises.
.steps { font-family: 'Segoe UI', -apple-system, BlinkMacSystemFont, sans-serif; margin: 1.5rem 0 2rem; } .step-item { display: flex; gap: 1.25rem; margin-bottom: 1.25rem; align-items: flex-start; } .step-number { flex-shrink: 0; width: 44px; height: 44px; background: #0078D4; color: #fff; font-size: 1.1rem; font-weight: 700; border-radius: 50%; display: flex; align-items: center; justify-content: center; } .step-content h4 { font-size: 1.05rem; color: #1a1a2e; margin: 0 0 0.3rem; } .step-content p { font-size: 0.92rem; color: #6B7280; margin: 0; line-height: 1.65; } 1 Audit of the current environment
Review which GP modules you actually use, which customizations have been implemented, which third-party ISVs are active, and what the volume of historical data is. This initial picture is the foundation of the entire project.
2 Definition of objectives and scope
Establish which processes will be migrated as-is, which will be redesigned, and which customizations you really need to keep. This is the moment to simplify: not everything that exists in GP needs to be replicated.
3 Data cleansing and preparation
Remove duplicate, inactive, or obsolete records. In most jurisdictions, keeping more than 7 years of transactional history offers little value. A clean database speeds up migration and improves the performance of the new system.
4 Partner selection and execution
Work with a certified Microsoft partner that has demonstrable experience in GP → Business Central migrations. Request references, review their methodology, and ensure the team includes trainers for your users.
5 Testing, training, and Go-Live
Conduct thorough testing with real data, train key users, and plan a Go-Live during a period of low activity. Keep GP accessible as a historical reference system during the first months if necessary.
.callout-plazos { font-family: 'Segoe UI', -apple-system, BlinkMacSystemFont, sans-serif; background: #FFF8E1; border-left: 4px solid #FFB900; border-radius: 0 12px 12px 0; padding: 1.5rem 1.75rem; margin: 1.5rem 0; line-height: 1.7; color: #333; } .callout-plazos .callout-title { font-weight: 700; font-size: 1rem; margin-bottom: 0.5rem; display: flex; align-items: center; gap: 0.4rem; color: #1a1a2e; } .callout-plazos .callout-icon { font-size: 1.3rem; } .callout-plazos p { margin: 0; font-size: 0.95rem; } ⏰ About timelines
The simplest migrations can be completed in 10-12 weeks. The more complex ones — with multiple customizations, third-party integrations, or very large data volumes — may require 6 months or more. The key is to start planning as early as possible to avoid being forced into an accelerated migration.
The time is now
The dates are set and they are not going to change. Every quarter that passes, the margin to plan an orderly migration shrinks. It is not about rushing, but about not standing still.
Companies that start moving now will migrate under better conditions: greater availability of experienced partners, more negotiating capacity on licensing, more time to clean data, train teams, and do things right. Those that wait until 2028 or 2029 will face a demand bottleneck, compressed timelines, and less margin for error.
If your company operates with Dynamics GP, the first step is not to sign a migration contract. It is to understand where you stand: which modules you use, which customizations you have, how much historical data you need to keep, and what the real complexity of your environment is. With that picture, any subsequent decision is made with judgment and not with urgency.
At KCP Dynamics we have been accompanying companies in Latin America for more than 20 years in the implementation and evolution of Microsoft Dynamics solutions. We are a Microsoft Solutions Partner, part of the FastTrack program, and we have teams that know both GP and Business Central from the inside. We have accompanied migrations in sectors such as retail, distribution, manufacturing, services, and financial sector, and we know that no two projects are alike.
If you want to know the real state of your GP environment and what a migration to Business Central would entail, we can help you evaluate it without commitment. It is a conversation worth having now, not when the clock is ticking.
FAQs about the end of Microsoft GP support
.faq-container { font-family: 'Segoe UI', -apple-system, BlinkMacSystemFont, sans-serif; margin: 1.5rem 0 2rem; } .faq-item { border: 1px solid #E2E8F0; border-radius: 10px; margin-bottom: 0.75rem; overflow: hidden; } .faq-question { padding: 1rem 1.5rem; font-weight: 600; font-size: 0.95rem; color: #1a1a2e; cursor: pointer; display: flex; justify-content: space-between; align-items: center; background: #F5F7FA; transition: background 0.2s; margin: 0; } .faq-question:hover { background: #EBF3FB; } .faq-toggle { font-size: 1.2rem; color: #0078D4; transition: transform 0.2s; flex-shrink: 0; margin-left: 1rem; } .faq-item.active .faq-toggle { transform: rotate(45deg); } .faq-answer { padding: 0 1.5rem; max-height: 0; overflow: hidden; transition: max-height 0.3s ease, padding 0.3s ease; } .faq-item.active .faq-answer { padding: 0 1.5rem 1rem; max-height: 300px; } .faq-answer p { font-size: 0.95rem; color: #6B7280; line-height: 1.7; margin: 0; } Will Dynamics GP stop working after 2029? +
No, the software will continue to work technically. However, from December 31, 2029, it will not receive functional, regulatory, or technical support updates. Security updates extend until April 2031, but after that date the system will be completely without manufacturer backing.
Can I continue buying GP licenses if I am already a customer? +
Yes, existing customers can continue acquiring additional user licenses and modules after the new sales cutoff dates. What closes is the possibility for new customers to acquire the product.
Is Business Central the only alternative to Dynamics GP? +
No. Although Microsoft recommends Business Central as the natural migration path, there are other options such as Oracle NetSuite, SAP Business One, Sage Intacct, or Acumatica. The choice depends on the size of the company, the sector, functional requirements, and available budget. That said, for companies already integrated into the Microsoft ecosystem, Business Central offers the most direct path with the least friction.
How much does it cost to migrate from GP to Business Central? +
The cost varies significantly depending on the complexity of the GP environment, the number of customizations, the volume of data, and the necessary integrations. There are standardized migration packages starting from 10-week timelines, but each project is unique. The recommended approach is to request a diagnostic audit from a certified partner to obtain a quote tailored to your situation.
Will I lose my historical data during the migration? +
No, as long as the migration is properly planned. Historical data can be migrated to Business Central, kept accessible in the original GP database in read-only mode, or consulted through tools such as Power BI. The historical data strategy must be defined at the beginning of the project.