Picture a mid-sized distributor in early 2030. Its accounts team opens Dynamics GP on a Monday morning, posts the weekend’s receipts, and prints the cash report. Nothing looks different. Yet something important has changed: the company is now running its finances on software that its maker no longer looks after.
Is that a problem? It depends on how the company prepared. Many GP users are now asking whether an independent support firm can stand in for Microsoft once official cover ends. Our consultants at Nevas Technologies hear this question almost daily, and our answer is always the same: a partner can take on a large share of the work, share some of the risk with you, and leave a smaller but serious set of risks entirely in your hands. Knowing which is which is the whole decision.
So let us sort every concern into three groups: what you can hand over, what you share, and what you keep.
First, a Quick Word on Timing
Microsoft has been winding GP down in stages. New customers lost the option to buy it in 2025 and 2026, although existing users can still extend what they have. The stage that affects you most comes at the close of December 2029, when Microsoft ends its help desk, its fixes and its tax releases for the product. A final stage follows in late April 2031, when Microsoft also stops security patching and subscription-based use of GP comes to an end.
Two details often get overlooked. First, if your company is still on the 2018 releases of GP, Microsoft’s cover for those versions finishes sooner, in early 2028. Second, the end of support does not switch the software off. Perpetual license holders may go on using GP as long as they wish. The real question is not “can we?” but “should we, and on what terms?”
Group One: What You Can Hand Over
These are the areas where a capable GP partner can fully replace, or even improve on, what Microsoft offered.
Everyday problem solving. The great majority of GP tickets are not software defects at all. A posting fails because a period is closed. A report total looks wrong because a distribution was coded to the wrong account. A user cannot see a window because of a security role. A partner who knows your organization and its setup resolves these quickly, often faster than a large vendor queue ever did. This is precisely the day-to-day work our Dynamics GP support service is built around.
Closing routines. Period-end and fiscal year-end in GP are sequences of steps with checks in between. None of them needs new code from Microsoft. They need someone who has done them many times and knows what a healthy result looks like.
Database repair. When records become damaged, batches hang mid-posting, or a subledger drifts away from the General Ledger, the fix is usually a careful piece of SQL work. That skill sits with experienced GP technicians rather than with any product team.
Training and handover. Staff leave, and knowledge leaves with them. A partner can retrain new team members, write internal procedure notes, and act as a memory for how your system is meant to work.
Group Two: What You Share
In these areas, a partner does much of the work, but your own decisions and investment still determine the outcome.
Customization. Few GP systems run exactly as installed. Most carry custom windows, modified reports, scripts, integrations with banks or warehouses, and stored procedures written years ago. A partner can maintain and repair all of this. However, the partner can only work with what exists. If nobody documented why a modification was built, or the original developer has vanished, recovery takes time and money. Your part is to fund a review now, while there is no crisis.
Add-on products. Many companies rely on independent vendors for payroll, budgeting, document management or electronic banking inside GP. Nevas Technologies works with a broad network of these vendors and can coordinate fixes on your behalf. Yet every vendor makes its own commercial choices. Some will follow Microsoft’s timetable; some may withdraw earlier. Your part is to ask each vendor for its plans in writing.
Infrastructure. A partner can recommend server builds, backup schedules, recovery tests and hosting set-ups that keep GP stable for longer. You, in turn, have to accept that newer Microsoft platforms will not be formally tested with GP, and you may need to hold back some upgrades to protect compatibility.
Payroll and tax. Once Microsoft stops issuing tax updates after 2029, a partner can help you keep tables current by hand or move payroll to a dedicated product. Either way, final accountability for correct withholding and filing rests with your finance team.
Group Three: What You Keep
These risks cannot be transferred to any outside firm, no matter how skilled. I want to emphasize them because they are the ones that most often get played down in sales conversations.
Defects in Microsoft’s own code. Outside firms do not hold GP’s source code. When a fault lies inside the core application, a partner can design a workaround but cannot release a true correction.
Unpatched vulnerabilities. After April 2031, newly discovered security weaknesses in GP will stay open. Firewalls, restricted access and private hosting can reduce the exposure, but cannot close the gap. Companies that answer to auditors, regulators or cyber insurers should check now whether unsupported financial software is acceptable to them.
Licensing limits. A support partner has no power over Microsoft licensing. Perpetual users keep their rights. Subscription users, including those hosted under SPLA arrangements, lose access when renewals end. Before you plan anything else, confirm exactly which license type you hold.
Long-term platform risk. Each year after 2029, the gap between GP and the systems around it grows a little wider. Eventually, the operating system or database version GP needs will itself reach end of life. At that point, staying becomes harder and more expensive every month.
Recognizing Whether Staying Suits You
From our work with clients, we recognize a clear pattern among companies for whom a limited extension makes sense. They usually:
- Own perpetual rather than subscription licenses;
- Have already moved to the latest GP release;
- Process payroll outside GP;
- Keep a documented record of customization and integrations;
- Host GP in a restricted, well-managed environment;
- Have a dated, funded plan to move to a new platform.
Where several of these are missing, the safer course is to complete your move before 2030, or at the very latest before the 2031 cut-off.
Analyzing the Decision Together
When analyzing your options, it helps to bring finance, IT and compliance leads into one room and agree answers to a short list of questions:
- Which license type do we hold, and how will 2031 affect it?
- Which processes depend on Microsoft tax or regulatory releases?
- Which add-ons do we use, and what have their vendors committed to?
- How much custom code do we run, and who can maintain it?
- What do our auditors and insurers require of financial software?
- What would a week of downtime cost us?
- How long and how much would a move realistically take?
Clear answers will tell you whether a short extension is a sensible bridge or an unnecessary gamble.
Choosing the Right Support Partner
Not every provider is equally suited to supporting GP beyond Microsoft’s involvement. Before signing an agreement, look for a partner that can show:
Depth across versions: A team that has worked on many GP releases understands how older data and older modifications behave.
Technical as well as functional skill: You need people who can both explain an accounting routine to a user and repair a damaged table in SQL.
Established vendor relationships: Direct contacts with add-on vendors shorten the time it takes to resolve issues that cross product boundaries.
Clear service levels: Response times, escalation routes and out-of-hours cover should be written into the agreement, not promised verbally.
Migration experience: The same partner should be able to guide you onto your next platform when the time comes, so that knowledge of your system is not lost at the most important moment.
A short reference call with one or two existing clients will tell you more than any brochure.
A Sensible Order of Work
If you decide to stay for a period, the order in which you prepare matters.
Get onto the latest release: A Dynamics GP upgrade gives you the longest stretch of official cover and a cleaner starting point for later migration.
Reduce what you carry: Archive old years, retire unused modifications, and reconcile every subledger. A lighter, cleaner system is cheaper to support and cheaper to move.
Formalize outside support: Sign a support agreement with a GP specialist before 2029, not after a failure forces your hand.
Set an exit date: Compare destinations, such as Dynamics 365 Business Central, and fix a go-live date that suits your financial calendar.
Summarizing in One Paragraph
Summarizing the three groups: you can hand over daily support, closing routines, data repair and training. You share responsibility for customization, add-ons, infrastructure and payroll. You keep the risks tied to Microsoft’s source code, security patching, licensing and future platform compatibility. A planned, time-limited stay on GP with strong outside support can be a sound business choice. An open-ended one is not.
Plan Your Next Step with Nevas Technologies
For more than a decade, Nevas Technologies has helped companies in the United States and Asia Pacific run Microsoft Dynamics GP reliably. Our Dynamics GP consultants provide support, upgrades, customization maintenance, vendor coordination and migration planning.
If you are considering life on GP beyond 2029, contact us for a frank assessment of your environment and a timeline built around your business.
Frequently Asked Questions
Will Dynamics GP stop working after 31 December 2029? No. GP will continue to open and process transactions as normal. What ends is Microsoft’s involvement: no new fixes, no tax releases and no help desk. Companies that hold perpetual licenses can keep using the software for as long as they choose.
What is the difference between the 2029 and 2031 deadlines? At the end of December 2029, Microsoft stops product support, defect fixes and tax updates for GP. At the end of April 2031, it also stops security patching, and subscription-based use of GP, including SPLA hosting, comes to an end.
Can a third-party partner provide security patches for Dynamics GP? No. Outside firms do not have access to GP’s source code, so they cannot patch the application itself. A partner can reduce exposure through firewalls, restricted access and private hosting, but the underlying weakness remains.
Who will handle payroll tax updates after 2029? Microsoft’s final tax release for GP is planned for the end of 2029. After that, tax tables must be maintained manually with a partner’s help, or payroll must move to a separate product. In both cases, responsibility for accuracy rests with your finance team.
Can a support partner maintain our GP customization and add-ons? Yes. An experienced partner can maintain and repair custom code, reports and integrations, and can work with add-on vendors on your behalf. However, each add-on vendor decides independently how long it will continue to support GP.
How long can a business safely stay on Dynamics GP? It depends on your license type, payroll arrangements, security obligations and add-on products. A planned, time-limited extension with strong outside support can be sensible. Most businesses should aim to complete their move to a new platform before April 2031.
How can Nevas Technologies help? Nevas Technologies provides Dynamics GP support, upgrades, customization maintenance, vendor coordination and migration planning. We can assess your environment and help you set a realistic timeline for staying on GP or moving to a new platform.
