Dynamics GP End of Life: Your Migration Options Explained

If your organization runs Microsoft Dynamics GP, the clock is now ticking down towards its eventual end of life. The first major milestone, the end of new perpetual license sales, passed on April 1, 2025. The second, the end of new subscription license sales, passed on April 1, 2026. You can still use GP. You can still add users to your existing instance. But the doors to the platform are closing, and Microsoft has published a clear, unambiguous schedule for what comes next.

This article is for Dynamics GP users who want to understand exactly what the end-of-life timeline means for them, what their migration options are, and how to think about timing and cost, including a significant Microsoft financial incentive that's available right now and won't last forever.

At A BC Consulting Group, we've been implementing and supporting Dynamics GP for over two decades. Our team has completed hundreds of GP implementations and migrations, and we've spent the last several years helping clients navigate this specific transition. What follows is the honest, practical picture, not a sales pitch, but the kind of clarity we give clients in direct conversations.

The Complete Dynamics GP End of Life Timeline

Microsoft has been methodical about how it's communicated the GP sunset. Understanding each date and what it means matters, because the nuances are important:

April 1, 2025 — End of new perpetual license sales (already passed) 

New customers could no longer purchase traditional, owned perpetual licenses for GP. Existing customers were unaffected and could still add perpetual licenses to their current instances.

April 1, 2026 — End of new subscription license sales (already passed) 

This was the final door closing on new GP customer acquisition. No new instances of Dynamics GP can be purchased in any form. Existing customers on active Enhancement Plans can still add users and functionality but cannot purchase a net-new GP environment.

December 2028 — Final year-end update 

This is the last time GP will receive a year-end tax update, the annual update that keeps payroll calculations and tax tables current. For organizations that use GP for payroll, this date is operationally critical. After December 2028, payroll on GP becomes a manual, high-risk process.

December 31, 2029 — End of mainstream support

Microsoft stops providing product enhancements, regulatory updates, service packs, and technical support. The final payroll and year-end update for non-payroll modules is issued. After this date, GP does not receive fixes for regulatory changes, new tax requirements, or software bugs. Your system will still run, but you're entirely on your own for compliance.

April 30, 2031 — End of security updates and official end of life 

This is the hard stop. After this date, Microsoft will no longer issue security patches for Dynamics GP. Known vulnerabilities will go unaddressed. Any organization still running GP at this point faces a genuinely exposed security posture, not a theoretical risk, but a real one in an environment where ERP systems are a primary target for ransomware and data theft.

What This Means in Practice

The software doesn't shut off at any of these dates. Your GP environment won't stop working on January 1, 2030. But what happens is this: every passing milestone means you're running a system that Microsoft has stopped investing in, fixing, and securing. The risks compound gradually, then urgently.

For payroll users, 2028 is the practical deadline, not 2029 or 2031. After the final year-end update, staying on GP for payroll requires your team to manually calculate and apply tax changes, which is both time-consuming and error-prone.

For everyone else, 2029 is the date that concentrates minds. After mainstream support ends, a regulatory change in your state or industry, such as new tax rules, updated reporting requirements, revised depreciation schedules, will not be addressed by Microsoft. Your team absorbs that work or your compliance posture deteriorates.

There's also a less obvious pressure building right now: the talent market. Experienced GP consultants, ISV vendors who built add-ons for GP, and the broader ecosystem of GP expertise is shifting toward Business Central. The firms and specialists who know GP inside and out are increasingly pivoting their practices toward cloud platforms. Every year that passes, the pool of qualified GP support narrows. A BC Consulting Group is committed to supporting our GP clients through this transition, but the industry-wide trend is real and worth factoring into your planning horizon.

The Financial Case For Moving Now: Microsoft Bridge To Cloud 3 Promotion

This is the part of the conversation that changes the economics of migration significantly, and it has a deadline.

Microsoft launched its Bridge to Cloud 3 (BTC3) promotion on January 1, 2026. BTC3 offers eligible customers a 30% discount on Dynamics 365 online licenses for three years, locked in through a fixed-term commitment. The promotion is available for enrollment through December 31, 2027.

Here's what that means in practical terms:

30% off Business Central licensing for three years

For an organization paying $1,000/month in BC licensing, that's $360 saved annually,  and $1,080 over the three-year term before even factoring in infrastructure costs. The discount is locked in, giving you budget predictability during the migration period and after.

Dual access rights

Under BTC3, Microsoft provides dual use rights, allowing customers to continue running their current on-premises GP system alongside Business Central while the migration is underway. This is a critical operational benefit. You don't have to pick a hard cutover date and hope everything works. You can stand up Business Central, run in parallel, train your team, and cut over when you're ready while GP continues to operate your day-to-day business.

Enhancement Plan extension at no additional cost

As part of the promotion, Microsoft extends your Enhancement Plan for your on-premises GP at no additional cost during the BTC3 term, meaning your GP support and updates continue while you implement Business Central.

Eligibility requirements to know:

• You must have a valid perpetual Dynamics GP license purchased prior to September 1, 2024

• Your Enhancement Plan must be active at enrollment (there is a 30-day grace period for recently lapsed plans)

• The annualized value of your new Business Central licenses must equal or exceed your current annual EP renewal amount

• Organizations that participated in Bridge to Cloud 1 or Bridge to Cloud 2 are generally not eligible for BTC3

The BTC3 enrollment window closes December 31, 2027. Migration discounts have dropped from 60% in 2021 to around 30% today, representing a 50% reduction in incentive value over that period. There is no guarantee that a comparable program will be available after BTC3 expires. Waiting costs real money.

What The GP to Business Central Migration Involves

The question we hear most often from GP customers: "How disruptive is this going to be?"

The honest answer is that it depends heavily on three factors: the complexity of your current GP environment, the quality of your data, and the experience of the partner running the migration. A straightforward GP installation with clean data and minimal customizations can migrate to Business Central in as few as ten to twelve weeks. A heavily customized environment with years of accumulated data, multiple integrations, and ISV add-ons will take longer, typically four to eight months.

Here's the general shape of a well-run GP to Business Central migration:

Discovery and gap analysis

Before any configuration begins, your current GP environment needs to be thoroughly understood. What modules are in use? What third-party add-ons are installed? What customizations were built, and are they still serving a business purpose? What integrations connect GP to other systems? What data needs to migrate, and in what condition is it? This phase surfaces the decisions that drive everything else.

Process design

This is where many migrations go wrong, and where experience matters enormously. Business Central's out-of-the-box processes are designed around modern best practices. Not every GP workflow needs to be rebuilt in BC,  some GP workarounds exist because GP had limitations that BC has already solved. A good migration partner challenges you to redesign processes where BC does something better, rather than recreating GP's approach in a new system.

Configuration and development

Business Central is configured, through its chart of accounts, dimensions, posting groups, approval workflows, document layouts, user permissions, to match your business requirements. Any custom extensions needed are built in AL, stored in version-controlled repositories, and tested before deployment. ISV add-ons relevant to your industry (Binary Stream for multi-entity or lease accounting, Avalara for tax compliance, and others) are installed and configured.

Data migration

Microsoft provides a built-in cloud migration tool specifically designed for Dynamics GP to Business Central migration. It connects your on-premises SQL database to Business Central online and replicates data table by table. Master data, such as customers, vendors, items, chart of accounts, migrates cleanly. Historical transaction data requires decisions about how much history to bring over and in what form. Open transactions, such as outstanding invoices, open purchase orders, in-progress projects,  require particularly careful handling.

Testing and validation 

Before going live, your team runs user acceptance testing against realistic business scenarios. Can you process a purchase order end to end? Does the month-end close produce the right reports? Do integrations with your payroll provider, your bank, your CRM, or your e-commerce platform work correctly? This phase is where problems are caught before they affect real operations.

Training and go-live

Business Central's interface is different from GP's. Your team needs training built around the workflows they'll actually use, not a generic walkthrough of every module. Go-live support should include hypercare in the days immediately following cutover, when questions and edge cases inevitably surface.

Post-go-live optimization 

A good implementation gets your organization operational. A great one stays engaged through the first month-end close, the first quarter-end, the first annual audit, the moments when the real test of the configuration comes. We treat the first three months after go-live as part of the engagement, not a separate project.

Why GP Experience in Your Implementation Partner Matters More Than You Might Think

Not all Business Central partners have meaningful Dynamics GP experience. Many have built their practices entirely around Business Central and have never worked inside a GP environment. That creates gaps:

They may not fully understand which GP modules map cleanly to Business Central equivalents, and which require process redesign. They may not know the quirks of GP's data structure that affect how cleanly historical data migrates. They may not recognize when a client's "customization" is actually a workaround for a GP limitation that doesn't exist in BC.

A BC Consulting Group has been implementing Dynamics GP since its Great Plains Software days. Shannon Mullins, our founder and a Microsoft MVP, has been working with GP customers for over 23 years. Our team has run hundreds of GP implementations which means we understand the platform our clients are migrating from, not just the platform they're migrating to. That matters when we're evaluating your environment, designing the migration approach, and guiding decisions about what to replicate and what to leave behind.

Common Questions from GP Customers

"GP is still working fine. Why should I move now?"

Because the value of waiting is declining, and the cost of waiting is rising. Enhancement Plan costs have increased from 16% in 2021 to 20% in 2026, while migration discounts have dropped from 60% to around 30% over the same period. The BTC3 promotion is available now and closes at the end of 2027.

The talent pool for GP support is narrowing. A migration started in 2026 or early 2027 has plenty of runway. A migration started under pressure in 2028 or 2029, when tax updates are ending and every other GP customer is trying to migrate simultaneously, will cost more and find fewer available partners.

"What happens to our data after we migrate?"

Your GP data doesn't disappear. The typical approach is to migrate active master data and open transactions to Business Central and retain historical transaction data in a read-only GP environment or a data archive for the period required by your record retention policy. Most organizations maintain read-only access to their GP history for three to seven years post-migration.

"We have a lot of customizations in GP. Will they transfer?"

Directly, no. GP customizations are built on an entirely different technology stack (Dexterity and C/AL) that doesn't exist in Business Central. What transfers is the business logic those customizations were implementing. In our discovery process, we evaluate each customization, is it still needed? Does Business Central already do this natively? If it needs to be rebuilt, we build it as an AL extension. Some clients discover that a significant portion of their GP customizations address limitations that BC has already solved, which reduces the rebuild scope meaningfully.

"How do we handle our ISV add-ons?"

This is one of the first questions in discovery. Some GP ISV solutions have direct Business Central equivalents on AppSource — Binary Stream, for example, has both GP and BC products. Others require evaluation of the BC marketplace for a comparable solution. Some are no longer being maintained at all, which makes the migration a good opportunity to rationalize the software stack. We map every add-on in your current environment to a recommended BC equivalent and flag any gaps that require custom development.

"What's a realistic budget for a GP to BC migration?"

Implementation costs vary considerably based on project complexity, data volume, number of users, and customization scope. A straightforward migration for a single-entity organization with clean data and minimal customizations can fall in the $30,000–$60,000 range. Complex multi-entity environments with significant custom development, multiple integrations, and large data sets will run higher. We provide fixed-fee proposals based on a proper discovery assessment — not time-and-materials estimates that expand as the project unfolds.

Dynamics GP Migration: What to do Now

If you're on Dynamics GP, the most valuable thing you can do in the next 60 days is get a clear picture of your current environment and understand what a migration would actually involve for your specific organization.

That's a conversation we have every week. It typically takes about an hour, costs nothing, and produces a picture you can actually take to leadership with confidence.

Contact A BC Consulting Group to schedule a GP migration assessment. We'll review your current environment, determine your BTC3 eligibility, and give you an honest view of what a migration looks like for your organization — including timeline, cost, and the right sequence for getting there.