The clock is officially ticking on Dynamics GP. Here’s what the end-of-support announcement means for your business, why Dynamics 365 Business Central is the right move, and how to prepare for a smooth migration.
For more than 30 years, Microsoft Dynamics GP (Great Plains) has been the financial backbone of thousands of small and mid-sized businesses. If your company runs on GP, it has probably served you well — closing your books, running payroll, and keeping the wheels turning year after year.
But Microsoft has made it official: Dynamics GP is reaching the end of the road. In September 2024, Microsoft announced the end of support for Dynamics GP, and the dates are now set in stone. If GP is still running your business, the question is no longer if you’ll move — it’s when, and who you’ll trust to get you there.
The Dynamics GP End-of-Support Timeline
Here are the key dates every GP customer needs to know, straight from Microsoft’s official lifecycle documentation:
- April 2025 — Microsoft stopped selling new Dynamics GP perpetual licenses.
- April 2026 — Microsoft stopped selling new GP subscription licenses.
- December 31, 2029 — End of product support. No more product enhancements, regulatory (tax) updates, service packs, or technical support from Microsoft.
- April 30, 2031 — End of security updates. After this date, no patches will be issued — even for critical vulnerabilities. Customers on subscription or SPLA licensing must stop using GP entirely.
Between 2029 and 2031, security patches will only be issued at Microsoft’s discretion for critical vulnerabilities — there is no guarantee of coverage. In practical terms, December 31, 2029 is the date your GP system stops being a supported product.
That may sound far away. It isn’t. A well-run ERP migration takes months of planning, data work, testing, and training — and as the deadline approaches, experienced migration resources will be increasingly scarce. The businesses that move early get the best talent and the smoothest transitions. The ones that wait get whoever is left.
Why Move from Dynamics GP to Business Central?
Microsoft has positioned Dynamics 365 Business Central as the go-forward successor to GP — and it’s where all of Microsoft’s ERP investment for small and mid-sized business is going. We compared the two platforms back in 2021 in our post Dynamics GP vs. Dynamics Business Central, and the gap has only widened since. Here’s why the move makes sense.
Security: The Risk of Standing Still
This is the big one. Once support ends, every day you run GP is a day you run an unpatched financial system.
- No more security patches after April 30, 2031 — and only discretionary critical patches between 2029 and 2031. Unpatched ERP systems are prime targets for ransomware and data breaches, and your ERP holds your most sensitive data: banking details, payroll, vendor payments, and customer records.
- Aging infrastructure compounds the risk. GP depends on on-premises Windows Server and SQL Server versions that are aging out of support on their own timelines.
- Compliance exposure. Without regulatory and tax updates after 2029, payroll tax tables, 1099 formats, and other compliance requirements become your problem to solve manually. Auditors and cyber-insurance carriers increasingly flag unsupported software as a material risk — some insurers will raise premiums or deny coverage outright.
Business Central, by contrast, runs on Microsoft’s cloud with enterprise-grade security, automatic updates, encrypted data at rest and in transit, multi-factor authentication, and continuous compliance updates built in. Security stops being your server room’s problem and becomes Microsoft’s job.
Modernity: A Platform That Moves Forward
GP is in maintenance mode — the December 2029 release will be the last version, ever. Business Central receives two major release waves every year, each packed with new capabilities.
- AI built in. Business Central includes Copilot for tasks like bank reconciliation, sales line suggestions, and analysis — and Microsoft is now shipping autonomous AI agents for payables, sales orders, and more. We covered this in our recent post on building AI agents in Business Central. None of this is coming to GP.
- Native Microsoft 365 integration. Work directly in Outlook, Excel, and Microsoft Teams without leaving your workflow.
- Power Platform connectivity. Extend Business Central with Power BI dashboards, Power Automate workflows, and Power Apps — no custom code required.
- Anywhere access. Business Central runs in any browser and on mobile apps for iOS and Android. No VPNs, no remote desktop sessions, no server maintenance windows.
Ease of Use: Your Team Will Actually Like It
GP’s interface reflects its 1990s origins. Business Central looks and behaves like the modern Microsoft applications your team already uses every day.
- A clean, role-based interface that shows each user what matters to them
- Powerful search (“Tell Me”) that takes users straight to any page or action
- Excel integration that lets users edit and publish data from a familiar grid
- Personalization without programming — users can rearrange fields, columns, and views themselves
The practical result: faster onboarding for new hires, fewer support tickets, and far less tribal knowledge locked in the heads of your longest-tenured GP users. Once your team is live, posts like our 7 Business Central productivity tips and tricks show just how much day-to-day friction disappears.
Ease of Migration: A Well-Traveled Path
Moving off a system you’ve run for 20 years sounds daunting. The good news: the GP-to-Business Central path is the most well-supported ERP migration in the Microsoft ecosystem.
- Microsoft provides purpose-built migration tooling. The official cloud migration tool brings GP accounts, customers, vendors, inventory items, and historical transaction summaries into Business Central in a structured, repeatable way.
- Your GP history doesn’t have to disappear. Tools like eOne’s Popdock let you access historical GP data from inside Business Central without dragging decades of records into your new system.
- Your ISV ecosystem comes with you. Most of the third-party publishers GP customers rely on — Avalara, Binary Stream, eOne, Jet Reports, and others — offer mature Business Central versions of their products.
- Thousands of companies have already made this exact move, so the common pitfalls are well documented and avoidable — with the right partner leading the project.
The single best predictor of a smooth migration is preparation. Here’s how to get ready.
1. Assess Your Current GP Environment
Inventory what you actually use: which modules, which customizations, which third-party products, which integrations. Most GP systems carry years of accumulated customizations that nobody uses anymore. Knowing what you truly need — versus what came along for the ride — dramatically simplifies the project.
A migration is the best data-cleansing opportunity you’ll ever get. Deactivate obsolete vendors, customers, and items. Resolve unposted batches and reconcile your subledgers. Decide how much history you need to bring forward and what can live in an archive. Clean data in means clean data out.
3. Map Your Business Processes
Don’t just replicate GP in the cloud. Business Central handles many processes differently — and often better. Document how work flows through your organization today, then identify where modern capabilities like workflow automation, approvals, and AI can eliminate manual steps. This is where business process development expertise pays for itself.
4. Plan Your Timeline Around Your Fiscal Calendar
Most companies target a go-live at a fiscal year start or quarter boundary. Working backward from that date, a typical mid-sized GP migration needs three to nine months for discovery, data migration, configuration, testing, and training. Starting in 2026 or 2027 means you migrate on your schedule. Starting in 2029 means you migrate on Microsoft’s.
5. Budget for Training and Change Management
Your team has years of GP muscle memory. Build training into the project from day one — not as an afterthought in the final week. A partner who offers structured, ongoing training and live webinars will shorten the adjustment period dramatically.
6. Choose Your Partner Carefully
This is the decision that determines whether your migration is a success story or a cautionary tale. Ask hard questions: Who exactly will work on my project? How many GP-to-BC migrations have they personally led? Do they know GP as deeply as they know Business Central? Beware of fixed-price implementations that look attractive on paper but hide change orders and junior staffing behind the quote.
Why Aisling Dynamics Should Lead Your Migration
There are plenty of Microsoft partners who will happily take on your migration. Here’s why Aisling Dynamics is different.
You Only Work With Senior-Level Business Central Technicians
At most Microsoft partners, your project is staffed in “levels” — a senior architect appears in the sales meetings, and then junior consultants learn on the job at your expense. We don’t do that. Aisling Dynamics keeps only experts on staff. Every person who touches your migration is a senior-level Business Central technician with deep, hands-on Dynamics experience. Projects get done more efficiently and more accurately because there’s no learning curve happening on your dime — and no game of telephone between the person who scoped your project and the person doing the work.
We Know GP as Deeply as We Know Business Central
A successful migration requires fluency in both worlds — the system you’re leaving and the one you’re moving to. Our team has been supporting Dynamics GP since 2009, including the full ecosystem of GP ISV products your business depends on. We know where GP hides its data, how its quirks map to Business Central, and how to preserve the processes that work while modernizing the ones that don’t. Partners who only know Business Central can’t do that.
Full-Service, From First Assessment to Long After Go-Live
We’re not a “go live and goodbye” shop. Aisling Dynamics provides end-to-end functional consulting, technical consulting, systems integrations, ongoing technical support, and free training webinars throughout the year. When you go live, we’re still here — for the next question, the next integration, and the next release wave.
Since 2009, we’ve delivered business application implementations across a wide range of industries, resolved thousands of support cases, and built long-term client relationships — including GP customers who came to us after being orphaned by their previous partner. As one client put it: “They are very knowledgeable in GP, as well as the 3rd party applications that are available… Jo’s team is always there to assist when needed.”
Dynamics GP had a great run, but Microsoft has made the future unambiguous: support ends December 31, 2029, security patches end April 30, 2031, and every new investment is going into Business Central. Waiting doesn’t avoid the migration — it just compresses your timeline, raises your risk, and shrinks your pool of available expert help.
Ready to talk about your move? Book a free consultation with our senior Business Central team, or contact us with your questions. We’ll give you an honest assessment of what your migration involves — no pressure, no junior consultants, no surprises.